Accessibility statement
Last reviewed
We want insurancegroupchecker.co.uk to be usable by everyone, and we build to the WCAG 2.2 AA standard. This statement describes what we've actually done, where we know we fall short, and how to tell us when we get it wrong.
Keyboard and focus
Every interactive element — the registration input, the make and model dropdowns, the cost estimator, the sortable groups table and the collapsible FAQs — is reachable and operable with a keyboard alone. A skip-to-content link is the first focusable element on every page, and focus states are visible rather than suppressed.
Structure and labelling
Pages use semantic HTML with one H1 and a heading order that never skips a level. Form fields have real associated labels, the registration field announces validation errors via role="alert", and the mobile menu button exposes its expanded state to assistive technology.
Colour and contrast
Body text meets at least 4.5:1 contrast against its background. Colour is never the only way information is conveyed: the 1–50 group scale is always accompanied by the number itself and a written band label such as "low" or "very high".
Charts and data
The insurance group prices chart carries a descriptive text alternative, and the same data is always available as a real HTML table with proper headers — so nothing is locked inside a graphic.
Zoom and small screens
Layouts reflow down to 320px wide and support 200% browser zoom without loss of content. Wide data tables scroll horizontally inside their own container rather than forcing the whole page sideways.
Known limitations
We'd rather list these than claim perfection. Our accessibility work is based on our own testing — semantic review, keyboard walkthroughs and contrast checks — and has not yet been independently audited by a third-party accessibility specialist, nor tested exhaustively across every screen reader and browser combination.
The reg checker also depends on a live DVLA lookup. If that service is slow or unavailable, the result simply doesn't appear; we show a written error message rather than leaving you with an unexplained empty state, and the make-and-model search remains available as an alternative route to the same answer.
Reporting a problem
If any part of this site is hard to use with a keyboard, screen reader, magnification or voice control, we treat that as a bug rather than a feature request. Tell us the page and what went wrong via our contact page and we'll fix genuine issues as quickly as we can — accessibility reports are prioritised alongside data corrections.