Skip to content

Draft for legal review before production launch. This template is a starting point, not legal advice.

Accessibility

What we have built in, and how to tell us where we fell short.

Our target

We aim to meet WCAG 2.2 Level AA. We are not claiming full conformance; this page describes what is actually implemented and is updated as we improve.

What is built in

Every interactive control is reachable and operable by keyboard, with a visible focus ring that meets contrast requirements in both themes.

Live score changes are exposed to screen readers through polite live regions, and the score bar carries a text description of the current split.

Light and dark themes are both tested for contrast; team colours use separate, darker text variants on light backgrounds so they stay legible.

All motion respects prefers-reduced-motion: animated counters render instantly and CSS transitions are disabled.

Touch targets on primary actions are at least 44 pixels tall, and layouts are tested from 320 pixels upward with no horizontal scrolling.

Every form control has a programmatic label, and errors are announced rather than shown by colour alone.

Known gaps

The activity ticker scrolls continuously; it is marked decorative and duplicated as static text in the battle feed, but we intend to add a pause control.

We have not yet completed a full audit with assistive-technology users.

Tell us

If something is unusable for you, email support@example.com with the page and what happened. Accessibility reports are treated as bugs, not feature requests.