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 — that includes both a testing coverage gap and a known, tracked set of unfixed violations, both described below.

We are not yet claiming full conformance for two reasons: our automated runtime accessibility scan does not yet reach most of the attendee player and in-venue display screens, and we have a tracked, in-progress fix for a light-theme color-contrast issue on a subset of pages (see Known limitations). Once both close, we intend to upgrade this statement to full conformance.

This statement covers redthreadhub.net in full: the public marketing site, account creation and sign-in, and the authenticated host and client product surfaces (event dashboards, live scoring consoles, leaderboards, the client portal, 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, the account-creation flow, and a cross-section of the signed-in app — every live-event console, the primary screen of each operational area, and every screen in the client portal — 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.

Most of the attendee player screens and the in-venue display screens are covered by our static lint check but not yet by our automated runtime scan. We test them by hand and through user reports today. Extending the runtime scan across that whole surface is planned, and this statement will be updated when that coverage lands.

Under our light color theme, some text on a subset of pages does not yet meet the 4.5:1 contrast ratio WCAG 1.4.3 requires. Our dark theme, the default, is not affected. We are working through the affected pages and will update this statement as they are fixed.

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@redthreadhq.net with the page and what happened, and we'll get back to you and work to fix it.