ADA Accessible Car Dealer Websites

What the rules actually say, why an overlay widget is not a remediation, and the questions that put the work back on the vendor who owns your site.

This is not legal advice and you should talk to your own counsel, but it helps to understand the shape of the thing before a vendor explains it to you.

The Americans with Disabilities Act predates the commercial web. Title III covers places of public accommodation, and a dealership showroom clearly qualifies. Whether and how that extends to a dealership's website has been worked out through litigation and Department of Justice guidance rather than through a single technical rule written for private businesses, and courts have not landed in exactly the same place everywhere.

What has emerged in practice is that the Web Content Accessibility Guidelines, commonly at the 2.1 AA level, are the reference everyone reaches for. WCAG is not a statute. It is a technical specification published by a standards body, and it has become the working benchmark because there was nothing more specific to use.

Two consequences follow, and both matter commercially. First, no vendor can honestly hand you a certificate that closes the question, because there is no certifying authority to issue one. Anyone selling you certainty is selling you something they do not have. Second, the reasonable posture is documented, ongoing effort rather than a one time project you declare finished. A site changes weekly. Accessibility is maintenance, not a milestone.

Automotive retail has been a recurring target for web accessibility complaints and demand letters, and it is worth understanding why rather than treating it as bad luck.

Dealer sites are unusually complex for their size. An inventory search with a dozen filters, a payment calculator, a trade valuation tool, a credit application, a chat window, video walkarounds and a stack of third party widgets is a lot of interactive surface for a business with no in house web team. Every one of those is a place where keyboard focus can get lost or a control can go unlabeled.

They are also highly templated. Thousands of stores run near identical sites from a handful of platform vendors, so a single structural defect is reproduced across an entire network. That makes the pattern easy to find at scale, which is exactly what tends to attract volume complaints.

And the buying decision is made by someone whose expertise is retail automotive, not front end engineering, which means these defects survive procurement. None of that is a moral judgment on dealers. It is a description of an industry where the responsibility sits with the platform vendor but the exposure sits with the store.

Somebody has almost certainly pitched you a script tag. One line of JavaScript, a little accessibility icon in the corner of your site, a monthly fee, and the problem is described as handled.

Be careful here. An overlay adds a layer of controls on top of a page. It can raise contrast, enlarge text or expose a menu of preferences. What it does not do is change the underlying markup that assistive technology actually reads. If a filter control has no accessible name, if focus order jumps around, if a modal traps a keyboard user, those defects live in the page and the overlay sits above them.

There is also a practical problem worth knowing about. Many people who rely on screen readers already have their setup tuned exactly the way they want it, and a script that intervenes can interfere rather than help. Accessibility practitioners and disability advocacy groups have been publicly critical of the overlay category for years, and demand letters have been reported against sites that had an overlay running.

Use one if you want a user preference panel. Do not buy one believing it substitutes for fixing the page, and do not accept a website vendor telling you it does. Ask them instead for the remediation plan on the underlying template.

Concrete beats abstract, so here is where the real problems tend to sit. You can check several of these yourself in an afternoon.

Images without meaningful alternative text. A vehicle detail page with thirty photos all labeled with a file name tells a screen reader user nothing. Feed generated alt text is a common culprit because nobody ever wrote it.

Inventory filters that need a mouse. Custom dropdowns, sliders and toggles built without keyboard support are the single most common blocker on an automotive site, and inventory search is the primary task on the whole site.

Unlabeled form fields. Lead forms, trade forms and credit applications that rely on placeholder text instead of real labels. A placeholder disappears when typing starts, which is a problem for far more people than just screen reader users.

Contrast on badges and disclaimers. Light grey payment disclaimers on white are everywhere in automotive, and they are also the text most likely to matter legally.

Modals and chat windows that trap focus. A keyboard user who tabs into a chat widget and cannot get out has effectively lost the site. Video without captions. Walkaround videos are increasingly central to merchandising and frequently ship with no captions at all.

Before you spend money, spend an hour. These checks cost nothing and will tell you whether you have a small problem or a large one.

Unplug your mouse. Try to complete the three tasks that matter on your own site: find a vehicle using the filters, submit a lead form, and start a credit application. Use only the keyboard. Watch whether you can always see where focus is. If you lose track of the highlight, so does every keyboard user.

Turn on the screen reader already built into your operating system and listen to a vehicle detail page. You do not need to be proficient. Thirty seconds of hearing photo underscore nine three seven dot jpg read aloud makes the alt text problem vivid in a way no audit report does.

Zoom your browser to two hundred percent and check whether anything overlaps or disappears. Then run an automated checker on three pages. Automated tools catch perhaps a third of real issues, so a clean report is not proof of anything, but a messy one is a legitimate finding you can put in front of your vendor.

Write down what you find with screenshots. That document is what turns a vague conversation into a work order.

Your website platform vendor controls the template, which means they control most of your exposure. Put the following in writing, at renewal if not sooner.

Ask for their current accessibility conformance documentation and the date it was produced. Ask which WCAG level they target and which known issues remain open. Ask who pays for remediation when a defect is found in their template rather than in your content, and how quickly they commit to fixing it. Ask whether accessibility testing is part of their release process or something they do when a letter arrives.

Then ask about third parties. Every widget on your site is code you did not write, and chat, trade tools, finance applications and inventory merchandising scripts are common sources of defects. Ask who is accountable when the failure is inside a partner's widget. In our experience this question produces the longest pause in the meeting.

Finally, put it in the contract. Our dealer website RFP template includes language for this, and the website platform page covers how the pieces of a dealer site are usually divided between vendors.

We are not a full dealer website provider and we are not an OEM compliant website vendor. If you need a franchise site that satisfies manufacturer program requirements, that is a different purchase and you should make it on its own merits, which is the same position we take on the custom dealer websites page.

What we supply is the conversion layer that sits around whatever site you run. Lead pages, which are landing pages built for a specific offer or campaign with their own URL settings. Personal salesperson websites. A free live chat widget you can drop onto your existing site. Customer facing deal pages, where a shopper opens their own numbers on their own phone and can sign electronically. Those are pages we build and maintain, and they are also, notably, the pages where a customer is asked to do something rather than browse.

We build those with keyboard operation, real form labels and readable contrast in mind, and we will fix defects you report. We are not going to tell you that makes your site compliant, because that would be a claim nobody can support and because most of the surface belongs to your website vendor, not to us.

Here is the part that makes this easier to fund internally.

Nearly every accessibility fix is also a conversion fix, because the underlying problem is the same: the page is harder to use than it needs to be. Real form labels reduce abandonment for everyone, not only for screen reader users. Visible focus states help anyone filling out a long application. Contrast that passes a checker is contrast that survives a phone screen in direct sunlight on your lot, which is where a large share of your traffic actually is.

Captions on walkaround videos get watched by the majority of people browsing with sound off, which is most mobile shoppers most of the time. Keyboard operable filters are usually also faster filters. Clean heading structure that helps a screen reader also helps search engines understand the page, which is why this overlaps with the work on core web vitals.

So the internal argument does not have to be about risk at all. You can make it about the shoppers you are currently losing quietly, which is a conversation a general manager is much more willing to have.

Accessibility projects stall because they are scoped as everything at once. Sequence it instead.

1. Fix the three critical paths first. Inventory search, the lead form and the credit application. Those are the tasks that turn into money and they are where a blocked user has a real complaint.
2. Publish an accessibility statement with a genuine contact method, and make sure someone actually watches that inbox. A reachable, responsive store is in a materially different position than a silent one.
3. Get the template defects on your vendor's roadmap in writing, with dates. Content defects are yours; template defects are theirs.
4. Write alt text into your merchandising process so new inventory does not recreate the problem weekly.
5. Re-test after every site change, because a redesign undoes remediation quietly and nobody notices for months.

If you want help on the parts we do control, the chat widget and lead pages are covered on website chat software, and you can contact us with a specific defect and we will tell you plainly whether it is ours to fix.

Is there a law that says dealer websites must meet WCAG?

Not in the form of a single technical rule for private businesses. The ADA covers places of public accommodation, and how that applies to websites has been worked out through litigation and guidance. WCAG 2.1 AA has become the practical reference. Talk to your own counsel.

Will an accessibility overlay widget make our site compliant?

No. An overlay sits on top of the page and does not change the markup assistive technology reads. It can be a useful preference panel, but it does not fix unlabeled controls, broken focus order or missing alt text, and it should not be sold to you as remediation.

Does LeadLocate build ADA compliant dealer websites?

We do not build full dealer websites and we are not an OEM compliant website vendor. We supply lead pages, salesperson sites, a live chat widget and customer facing deal pages, built with keyboard operation, real labels and readable contrast in mind.

Can any vendor certify that we are compliant?

No, because there is no certifying authority for private websites to issue such a thing. What a serious vendor can give you is documented conformance testing, a list of known open issues, and a remediation commitment with dates.

Who is responsible when the problem is in a third party widget?

Ask that question in writing before you renew, because the answer is often nobody by default. Chat, trade tools, finance applications and merchandising scripts are frequent sources of defects and the accountability needs to be assigned in the contract.

What should we fix first?

The three paths that turn into money: inventory search, the lead form and the credit application. Fix those, publish a real accessibility statement with a monitored contact, then work the rest on a schedule instead of as one large project.

Lead pages, chat and customer deal pages built to be used with a keyboard and read aloud. Tell us what is broken and we will tell you whose it is.