Skip to content
DriveSimpleAuto Group

Commitment

Accessibility

The standard this site aims at, what has actually been tested, what is known to fall short, and how to tell us when something blocks you.

Last updated 11 September 2026

The standard

This site targets the Web Content Accessibility Guidelines 2.1 at level AA. That is the benchmark courts and regulators generally apply to retail websites, and it is the one worth measuring against rather than a vaguer promise.

What has been built and checked

  • Every interactive control is a real button or link, operable by keyboard, with a visible focus ring.
  • The main navigation, mega menus, search overlay and mobile drawer open on focus as well as hover, close on Escape, and expose their state through aria-expanded.
  • The mobile drawer traps focus while open and restores it on close.
  • Vehicle galleries support arrow keys, announce the current frame to screen readers, and disclose that the images are illustrations rather than photographs.
  • A skip link precedes the header on every page.
  • Filters on the inventory search are real links, so the results work without JavaScript and every filtered view has its own address.
  • All animation, including the homepage slider, stops under prefers-reduced-motion.
  • Pages are tested for horizontal overflow at 390, 768 and 1440 pixels.

Known gaps

Listing these is more useful than claiming full conformance. As of the date above:

  • The floating quick-action rail is a fixed overlay in the bottom corner. It can sit over a control beneath it; it collapses to a single button and can be dismissed entirely.
  • Some data tables — the lease comparison and the credit tier ladder — scroll horizontally inside their own container on narrow screens.
  • A full audit with assistive technology by a third party has not been carried out on this build.

Why there is no accessibility overlay

This site deliberately does not use an accessibility overlay or toolbar widget. Those products advertise instant conformance, and in practice they frequently interfere with the screen readers and keyboard behaviour that people already rely on. Building the underlying pages correctly is slower and is the only thing that actually works.

Reporting a barrier

If something on this site stops you completing a task, tell us and we will fix it and help you finish what you were doing in the meantime.

Please include the browser and any assistive technology you were using — it usually identifies the problem immediately.