Accessibility

1. Standard

We aim to conform to the Web Content Accessibility Guidelines 2.1 at Level AA across the whole site, on desktop and mobile. Reading and navigation work without JavaScript; some interactive forms still need it to submit (see Known limitations).

2. What is in place

• Every page is readable with JavaScript disabled, and scripted enhancements are islands on top of working HTML. Several interactive forms — reporting among them — currently need JavaScript to submit; that gap is listed under Known limitations.
• Keyboard operation everywhere: reactions, report, block, vote and menu controls are buttons with visible two-layer focus rings; menus close on Escape and return focus to what opened them.
• A skip link to the main content. Landmarks and labelled navigation regions. Headings in order.
• Text contrast of at least 4.5:1 in both the light and dark schemes; status is never conveyed by colour alone (rides, miracles, moderation states carry words).
• Minimum 44px touch targets on interactive controls.
• Reduced-motion preference honoured: transforms drop to zero, only short opacity changes remain.
• Forms have visible labels, help text, and error messages tied to their fields.
• No emoji in application-authored interface text; glyphs and words instead, so screen readers do not narrate decoration.
• Data tables (setlists, standings, ride boards) are real tables with header cells and scroll within their own container on small screens.

3. Known limitations

• The map view is a visual aid; every venue it plots is also listed as text on the venue and shows pages.
• Reaction GIFs from the search provider have only the provider’s alternative text, which is uneven.
• Long setlist tables on very small screens require horizontal scrolling within the table.
• Several interactive forms — the report intake among them — currently require JavaScript to submit; with scripting off the fields are present but the submission does not complete. Reading and navigation do not require JavaScript.
• A full manual audit with assistive technology has not yet been done, and automated accessibility checks are not yet part of the build. This statement will be updated when either changes.

4. Tell us

If something is unreadable, unreachable by keyboard, mislabeled, or otherwise in your way, write to [email protected] with the page address and what happened. Say which browser and assistive technology you use if you can. We reply within a week and fix what we can as a priority.

Statement prepared 2026-08-17. Reviewed with each significant change to the interface.