MotoReady Open the app
← Back to motoready.pro

Accessibility Statement

MotoReady should be usable by every rider, whether you navigate with a keyboard, a screen reader, voice control, zoom, or a phone in a cold garage with gloves on. Here’s what we aim for, what we’ve built in, and where we know we can do better.

Effective October 1, 2026

On this page
  1. Our goal
  2. What’s built in
  3. Known limitations
  4. Making it easier to use
  5. Report a barrier

Our goal

We aim for the app and this website to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. MotoReady is built and maintained by a very small team, and we have not yet had an independent accessibility audit, so we don’t claim full conformance. We test as we build, fix what we find, and treat accessibility problems as bugs.

What’s built in

  • Keyboard use: the app can be used without a mouse. Dialogs trap focus while they’re open, close with Escape, and return focus to the button that opened them.
  • Screen readers: dialogs are announced as dialogs with a title, form fields have visible labels that are tied to their inputs, and list counts update through polite live regions.
  • Forms: errors appear next to the field in plain language, not only as a brief message, and the field is marked as invalid for assistive technology.
  • Not color alone: maintenance status is always a text label (Overdue, Due Soon, Current) as well as a color.
  • Light and dark themes: choose whichever is easier on your eyes. Colors are set to keep text readable in both.
  • Text size and zoom: layouts reflow for phones, tablets and desktop, and respond to browser zoom and larger text settings.
  • Reduced motion: if your device is set to reduce motion, we turn animations down.

Known limitations

We know of areas that may not yet work as well as they should, and we’re working through them:

  • Charts and summary graphics on the dashboard and cost pages may not describe their data fully to screen reader users. The same numbers are available in the lists and tables.
  • Some touch targets and secondary controls may be smaller than ideal on small phones.
  • Photos of bikes are illustrative. They may not have detailed descriptions, and the bike’s make, model and year are always shown as text.
  • Third-party pieces we rely on, such as Stripe’s checkout and billing pages, follow their own accessibility practices.

Making it easier to use

  • Use your browser’s zoom or your device’s text-size setting. The app adapts.
  • Switch between light and dark themes in the app.
  • Export your data (Data tab on any bike) as CSV or JSON if you’d rather work with it in a spreadsheet or another tool.
  • Use the app on your phone or computer: they have the same features.

Report a barrier

If something in MotoReady is hard or impossible to use, we want to know. Tell us what you were trying to do, the page or screen, and the device, browser and assistive technology you use if you can. We read every message and aim to reply within 5 business days, and we’ll offer another way to get you the information or help you need while we fix it.

support@motoready.pro