revv.fm
accessibility.
last reviewed · 5 june 2026
We want every driver to be able to use revv.fm, including people who use assistive technology. We build to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA and treat accessibility as ongoing work, not a one-time check.
conformance status
This coming soon page is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the content meets the standard, but some parts do not yet fully conform. We have known gaps that we are actively working through (see Known limitations below), and manual screen reader testing is still in progress.
what we have done
- Automated checks report zero violations on two independent engines (axe-core and pa11y / HTML_CodeSniffer). The only items they cannot resolve automatically are color-contrast checks over the animated background, which return as "needs review" rather than pass or fail; we verify those by hand against the solid background colour.
- Color contrast meets the AA ratio for body text in both the dark and light themes; we are completing the check across every interactive state and theme combination.
- Keyboard: every control is reachable and operable by keyboard. We are still tightening focus-indicator visibility on a small number of controls (see Known limitations).
- Forms: the email field has a real label, and status and error messages are announced to screen readers.
- Motion and contrast preferences: we honour reduced motion, increased contrast, and Windows High Contrast (forced colors).
- Semantic structure: a single main landmark, a skip-to-main link, named page regions, and a logical heading order.
- No accessibility overlay widget. We do not use automated overlay tools; we fix accessibility in the page itself.
how we test
Automated: axe-core and pa11y (HTML_CodeSniffer) run against both themes. Manual: keyboard only walkthrough, browser zoom and reflow, reduced motion, and forced colors. Manual screen reader testing with NVDA and VoiceOver is in progress and this statement will be updated when it is complete.
known limitations
We are aware of the following gaps and are working to close them:
- Focus indicators: the theme-toggle control on secondary pages can fall back to the browser default focus outline in some browsers. A consistent custom focus ring is being rolled out.
- Narrow-screen reflow: a few horizontal control groups can clip below roughly 360 pixels wide. We are adding wrapping so content reflows cleanly down to 320 pixels.
- Touch target size: some inline controls are below the recommended minimum target size and are being enlarged.
- Full manual assistive technology testing (screen readers) is in progress, so we describe our conformance as partial until that review is documented.
feedback
If you hit a barrier, or anything is hard to use with assistive technology, please tell us. Email support@revv.fm with the page and what happened, and we aim to reply within 5 business days.