Accessibility
Accessibility statement
Buying advice is only useful if everyone can read it. Here is what we have built in, what we know is not perfect yet, and how to tell us about a barrier.
Last updated
Our commitment
RideBenchmark aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is a goal we design and build toward. We have not commissioned a formal third-party accessibility audit, so we don’t claim certified conformance.
What’s built in
- Readable text. Body text is large, set in a single clear typeface, with comfortable line spacing and a limited line length.
- Contrast. Text colors are chosen to meet at least a 4.5:1 contrast ratio against their backgrounds. Our yellow highlight color is always paired with dark text.
- Keyboard access. Every link and control can be reached and used with a keyboard, and the keyboard focus is clearly visible.
- Skip link. A “Skip to content” link is the first thing keyboard and screen-reader users reach on every page.
- Structure. Each page has one main heading, a logical heading order and standard page landmarks (header, navigation, main content, footer), so assistive technology can move around it.
- Real links and text. Navigation uses ordinary links with descriptive text. Tables and checklists are real HTML, not images.
- Images. Informative images have text alternatives; purely decorative graphics are hidden from screen readers.
- Works without JavaScript. All content is in the page as delivered. Nothing important appears only after scripts run, scrolling or clicking a tab.
- Reduced motion. Animations are subtle and are switched off if your device is set to reduce motion.
- Zoom and small screens. Pages reflow for phones and remain usable when zoomed to 200%.
- Comfortable targets. Buttons and links are sized to be easy to tap.
Known limitations
- Third-party sites. Links to manufacturers, the affiliate network and YouTube take you to sites we don’t control, whose accessibility may differ.
- Manufacturer photos are described in their text alternatives, but fine product detail visible in a photo may not be fully conveyed in words.
- Testing coverage. We test with keyboard navigation and automated checks, but not yet with every combination of screen reader and browser.
Report a barrier
If anything on RideBenchmark is hard to read, navigate or use, please tell us. Email contact@ridebenchmark.com with “Accessibility” in the subject line, the page address, what you were trying to do, and — if you’re comfortable sharing — the device, browser and any assistive technology you use. A person reads every message, and we’ll work to fix the problem or provide the information another way.