We target WCAG 2.2 level AA on every page. When we miss, we want to hear about it, and we will fix it.
Where we stand
GayMoves is designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The statement below describes what the code does today and has not been audited by an outside accessibility specialist. Last reviewed October 31, 2026.
What we do
Every page has one main heading, landmarks, and a skip link as the first focusable element.
Everything works with a keyboard alone. Focus is always visible, with a 2px ring at 3:1 contrast, and returns to where you were when a dialog closes.
Text contrast is at least 4.5:1 and interface contrast at least 3:1, in both the dark and light themes. We check the color tokens with a script.
Buttons and links are at least 24 by 24 CSS pixels, and 44 pixels on touch screens.
Pinch-zoom is never blocked. Layouts reflow down to 320 pixels wide without sideways scrolling.
Every form control has a visible label. Errors are linked to their fields and summarized in a live region. Required fields say “required” in words.
Search suggestions follow the ARIA 1.2 combobox pattern, and result counts are announced politely.
The theme follows your device’s light or dark setting until you choose one, and city pages show miles and °F or kilometres and °C with a switch, so you can read measurements the way you are used to.
Motion respects the reduced-motion setting. Nothing flashes. Nothing autoplays.
Meaning is never carried by color alone: statuses use an icon and a word.
Charts and maps always have a text equivalent beside them.
How we test
Every pull request runs an ESLint accessibility ruleset, automated axe checks on each page, and our contrast script. We also tab through new interactions by hand and try them with a screen reader. Automated tools catch roughly a third of issues, so the manual pass matters.
Known limitations
The stylized maps are visual aids. All the same information appears in the lists next to them, and map markers are keyboard-operable.
Video introductions, when an agent adds one, must have captions.
Dialogs and drawers are built on Radix primitives, which handle focus and keyboard well, but we have not yet tested every screen reader and browser pairing.
Tell us what is hard
Say what you were trying to do, what got in the way, and what assistive technology you use if you are comfortable sharing.
Our public mailbox is not open yet. These routes work today: