Accessibility Statement

Red Thread Events targets WCAG 2.2 Level AA across the app. That is the de facto legal standard under ADA Title III — courts and DOJ guidance treat WCAG 2.1/2.2 AA as the reference point even though the ADA itself names no spec — and it covers what matters most for a public events product: color contrast, visible focus, resizable text, consistent navigation, and labeled form fields.

This statement describes where we stand against that target today, not where we intend to end up. We update it as our testing coverage changes.

This site is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means some parts of the content do not yet fully meet the standard — specifically, the automated testing coverage gap described below, which affects how much confidence we can claim rather than a known set of unfixed violations.

We are not yet claiming full conformance because our automated runtime accessibility scan does not yet run against authenticated pages (see Known limitations). Once that gap closes, we intend to upgrade this statement to full conformance.

This statement covers redthreadevents.com in full: the public marketing site, account creation and sign-in, and the authenticated host/attendee product surfaces (event dashboards, live scoring, leaderboards, and creator profiles).

It does not cover third-party content we link to but do not control, or content a host or attendee submits into free-text fields (team names, comments, question suggestions) that we cannot pre-validate for accessibility.

Every pull request runs a static lint check (`eslint-plugin-jsx-a11y`) against every page in the app, with no exceptions and no allow-list — a missing image description, an invalid ARIA attribute, or a click handler on a non-interactive element fails the build before it ships.

Our public marketing pages and account-creation flow also run through an automated runtime scan (axe-core) on every pull request, against the actual production build, including a pass under reduced-motion settings. This catches issues the static check cannot see: color contrast, focus order, and live regions.

Every interactive overlay — dialogs, drawers, menus — is built on a shared component that handles focus capture, keyboard trapping, focus return, and Escape-to-close consistently, rather than each surface reimplementing that behavior on its own.

Authenticated pages — event dashboards, host tools, and live scoring screens — are covered by our static lint check but not yet by our automated runtime scan. We test these pages by hand and via user reports today. Extending the runtime scan to authenticated routes is tracked in issue #507; this statement will be updated when that coverage lands.

If you hit a barrier using Red Thread Events — content you can't reach, a control you can't operate with a keyboard or screen reader, or anything else — tell us. Email robyn.mehta@gmail.com with the page and what happened, and we'll get back to you and work to fix it.