Accessibility statement

What is this website built toward?

The website is built toward the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. The standard covers several concrete things. A clear heading structure on every page, text that meets contrast requirements against its background, controls that can be reached and operated with a keyboard alone, links whose purpose is clear from their own wording, form fields with real labels, meaningful alternative text on images that carry information, and respect for a reduced-motion preference set in your operating system are all part of it.

The list above states commitments about how the site is built, not a legal guarantee that every page meets every criterion at every moment. Where the site falls short, we would rather hear about it and fix it.

How does the site behave in practice?

Every page on this site is server-rendered and readable with JavaScript disabled. Nothing here depends on a script running. The same property that makes the site fast also lets it survive an assistive technology behaving differently from a browser.

The diagrams carry explicit width and height attributes so the browser reserves their space before they load. Cumulative layout shift is zero site-wide. The stability matters for accessibility as well as for speed: a page that moves under a magnifier or under a switch user's cursor cannot be operated reliably.

• No media plays automatically
• No pop-up, modal or chat widget traps keyboard focus
• No cookie consent banner, because the site sets no cookies of its own
• Comparison tables are real HTML tables with header cells, and scroll inside their own container

Does this site use an accessibility overlay?

No. The site uses no accessibility overlay, toolbar or widget. Overlays are marketed as an instant fix and are widely reported by disabled users and by assistive-technology vendors to interfere with the screen readers, magnifiers and browser settings people have already configured.

There is a second reason. An overlay is itself a third-party script that runs on every page, which is precisely the class of thing this site exists to argue against, especially from a speed product. Building the underlying pages correctly is the approach taken here instead.

What are the known limitations?

The free speed test and the ad-spend calculator are the most interactive parts of this site and therefore the most likely to hold a defect that automated checking cannot see. Both are operable from the keyboard. Both also label their fields, but if either is unusable for you, write to the published contact address and the same result will be produced and sent to you directly.

The speed test uses Google's own data. The wording and structure of what it returns are Google's, not ours, and we cannot guarantee it meets the same standard as the pages around it.

Automated checks find common problems. Judging whether a page is genuinely usable is different, and feedback from real use is the part that cannot be generated automatically.

How do I report a barrier?

If any page, control, field, table or tool on this website is difficult or impossible to use, write to the published contact address and begin the message with the word “Accessibility”. Include the page address and what happened: what you were trying to do, what your assistive technology did, and what you expected instead. The detail is what makes a report actionable.

We aim to acknowledge accessibility reports within five business days. We will give you either a timeframe for a fix or another way to get the information in the same reply. Please do not include sensitive personal information in an accessibility report.

What does this statement cover?

The statement covers this website only, not a dealership website that has the DealerSpeed Engine installed on it. That site is built and controlled by the dealership and its website platform, and its accessibility is theirs.

What can be said about the engine itself is narrower. The engine defers and re-orders third-party scripts, does not rewrite a page’s markup, and adds no overlay, no widget or control of its own to a host page, so it does not change a host page’s accessibility in either direction.

How is this statement maintained?

Accessibility is reviewed whenever this site’s shared templates or primary interactions change, rather than on a fixed calendar, because a template change is what actually moves accessibility across many pages at once.

The statement was last reviewed on September 5, 2026, and will be revised when the site’s structure changes materially, or when a reported barrier changes what can honestly be claimed here.