Accessibility
Where BikeBee stands, honestly.
Our target
We are working towards WCAG 2.1 Level AA across the website and the mobile apps. We have not reached it yet, and this page says where the gaps are rather than claiming compliance we do not have.
What works today
- Semantic headings and landmarks on content pages
- Keyboard-operable navigation and forms
- Text that reflows and stays readable when zoomed to 200%
- Form fields with associated labels
Known gaps we are fixing
- Some vehicle photos are rendered as CSS background images, so they carry no alternative text for screen readers
- Filter controls on the search page do not show a clear focus outline
- Some colour pairings do not yet meet the 4.5:1 contrast minimum for body text
- Form validation errors are not consistently announced to assistive technology
- The site has not yet had a full audit with screen readers on iOS and Android
Tell us what is not working
If something on BikeBee is hard or impossible to use, we want to hear about it — that feedback is what moves this list. Reach us through help and support.