Last updated August 3, 2026 · Effective August 3, 2026
This is a tool for working professionals, and some of them use screen readers, keyboards, magnification, or need motion turned down. That is a normal part of the audience, not an edge case.
What we have done
- Semantic HTML throughout, with real headings, lists, tables and
landmarks, so assistive technology gets structure rather than a wall of divs.
- Every control has a label. Form fields, toggles and buttons all expose
an accessible name.
- Keyboard operable. You can reach and use everything without a mouse,
including the calculator, the rate guide, and the studio. Focus is visible. There is a skip link to the main content.
- State is announced, not just coloured. Toggles expose `aria-pressed`,
tabs expose `aria-selected`, and quote results are in a live region so a new quote is read out when it appears.
- Charts are not colour-alone. The revenue chart has a "View as table"
option with the same numbers, and values are labelled in text.
- Contrast is checked against the text and background pairs used across
the site.
- Reduced motion is respected. The scrolling ticker stops and smooth
scrolling is disabled when your system asks for reduced motion.
- Responsive and zoomable. The layout works down to a phone and up to 200%
zoom without horizontal scrolling.
We test with the keyboard and with the accessibility tree on every significant change, and we run the whole app through those checks rather than testing one screen.
Known limits
- The rate guide holds several hundred rows. It is navigable, but on a screen
reader it is a long document; the search box is the fastest way in.
- The monthly revenue chart is drawn as a graphic. It has a text alternative
and a table view, but the graphic itself is not individually navigable.
- Some content is drawn from third-party rate guides and keeps their original
wording, which is not always as plain as our own.
Standard we aim at
We aim to meet WCAG 2.2 Level AA. We have not commissioned a formal third-party audit, so this is a statement of what we build and test toward rather than a certified conformance claim. We would rather say that plainly than overstate it.
Tell us
If any part of this is hard to use, email rider@ridervo.com and tell us what you were trying to do and what got in the way. Accessibility reports go to the front of the queue, and we will tell you what we are doing about it.