Our target
We aim to meet WCAG 2.2 level AA across the public search, emergency request, provider onboarding and account journeys. Accessibility is part of design and release checks rather than a one-off overlay.
What the interface supports
- Semantic headings, landmarks and labelled form controls
- Keyboard operation, including the navigation menus, with visible focus indicators
- Text resizing and browser zoom without loss of core functionality
- Minimum 44 pixel targets for urgent actions and a thumb-reach action bar on phones
- Status information expressed with words and icons, not colour alone
- Reduced-motion preferences respected for every animation
- Server-rendered content that does not depend on JavaScript or animation to be read
Known limits
Third-party sign-in, payment, map and security challenges are partly controlled by their providers. Provider-written descriptions may vary in clarity until moderation. We test integrations but cannot alter every external screen.
Report a barrier
If something prevents you from searching, requesting help or managing a listing, use the contact form and choose “General enquiry”. Include the page, device, browser, assistive technology and what you were trying to do. For an urgent vehicle incident, a trusted person may submit the request on your behalf; immediate danger still requires 999.
Assessment and review
This statement is reviewed after production accessibility testing and whenever a material interface change introduces or resolves a known issue.