Skip to content

Inclusive design

Accessibility at TaMaarta

Hybrid competition should stay approachable across marketing pages and authenticated portal flows. TaMaarta targets WCAG 2.1 Level AAon the League #1-era surfaces enumerated below — with automated regression probes plus manual assistive-tech passes where automation cannot certify intent.

August 2026 baseline

Automated scans run axe-core tagged wcag2a, wcag2aa, wcag21a, and wcag21aa on the deterministic CI pathname set — homepage, canonical event URL probe, authentication, athlete portal workspaces, scoped submission shell, leaderboard shell, plus this accessibility statement page. Regression coverage lives in GitHub Actions; failing runs expose an axe-results.json artifact for engineering triage.

  • Public homepage
  • Event discovery/detail — seeded League slug /events/league-1-2026
  • Authentication — magic link / password /sign-in
  • Athlete portal hub — redirects unauthenticated viewers to sign-in
  • Athlete “my events” ledger — gated shell at /portal/events
  • Submission uploads — keyed shell at /portal/events/[eventId]/submit
  • Leaderboard — keyed shell at /portal/events/[eventId]/leaderboard

Registration choreography layered on /events/[slug] remains a manual VoiceOver / NVDA sweep — track evidence in-repo at docs/runbooks/a11y-audit.md until CI gains a dedicated authenticated fixture route.

Contact

Need a barrier surfaced or clarified? Email accessibility@tamaarta.com with URLs, browsers, AT builds, repro notes, screenshots, and the outcome you needed. Escalations follow the timelines described in Privacy and Terms.

Revisit this declaration whenever primary navigation swaps ship or axe coverage expands routes.