ADA Compliance for Auto Dealership Websites

Auto dealer websites combine the worst surfaces of ecommerce with the financial-services exposure of a lender, then bolt on a service-scheduling system, a parts catalog, and a half-dozen third-party widgets that the dealer principal does not control. The result is a site type that plaintiff firms specifically target and that NADA — the National Automobile Dealers Association — has been warning members about for nearly a decade. The 2018 NADA Driven Guide to Website Accessibility was the first industry-wide acknowledgment that dealer sites are subject to Title III, and the steady drumbeat of demand letters since then has confirmed it. This guide covers what gets sued, which platforms fail in which ways, and what franchise and independent dealers can actually do about it.

Why dealer sites get sued at outsized rates

A dealer website is an ecommerce store dressed in a local-business wrapper. The Eleventh Circuit's reasoning in Gil v. Winn-Dixie applies almost perfectly: a dealer's online inventory is tightly integrated with the in-store experience because shoppers research, configure payments, schedule a test drive, and submit credit applications online before ever walking onto the lot. Several courts have specifically held that a dealer's online VIN-specific inventory is a "good or service" offered through a place of public accommodation under Title III, and the Ninth Circuit's Robles v. Domino's nexus test applies cleanly because the website complements the physical showroom rather than substituting for it.

Used-car ecommerce platforms — Carvana, Vroom, Shift, Carmax online — face a stronger argument still. They offer end-to-end digital purchase, financing, and home delivery, which makes them functionally a fully online retailer. The First Circuit line of cases treating internet-only services as covered applies to that subset directly. CarMax in particular faced multiple suits before settling and committing to ongoing WCAG-conformance monitoring across both its online inventory and its finance pre-qualification flow.

The franchise/independent split mirrors the restaurant industry pattern. National brand websites (the OEM marketing sites — Ford.com, Toyota.com, BMWusa.com) have substantial internal accessibility programs and rarely show up in litigation. Individual franchise dealer sites, which are built and operated by the dealer principal even when they display brand assets, are the litigation targets. Independent used-car dealers running off generic CMS templates have the highest per-site violation counts and the lowest awareness of the rules.

Inventory search and VIN-coded photo galleries

The inventory results page is where most dealer audits start, and it is where the bulk of violations accumulate. Each vehicle tile typically shows 20-40 photos auto-generated from a third-party VIN-explosion service (HomeNet, vAuto's iRecon, Dealer Specialties), and almost none of those photos carry meaningful alt text. The platform pulls the make, model, year, and trim into a generic alt string — "2024 Toyota RAV4 photo 7" — that conveys nothing about what is actually in the image. WCAG 1.1.1 Non-text Content requires alt text that conveys the same information; for a marketing photograph showing the dashboard, the alt should describe the dashboard layout, not enumerate the photo number.

Inventory filter controls are the second compounding failure. Faceted filters for body style, drivetrain, transmission, color, mileage, and price are usually built as custom checkbox and slider components. Most dealer-platform implementations announce the result count after a filter change as an alert once but do not follow the WCAG 4.1.3 Status Messages pattern of using aria-live="polite" on a persistent results region, so screen reader users miss the update if they have already moved focus. The price-range slider in particular almost always lacks role="slider", accessible name, and keyboard support beyond Tab — which violates WCAG 2.1.1 and 4.1.2 simultaneously.

Vehicle comparison tables — the side-by-side view of two or three VINs with rows for MSRP, MPG, drivetrain, and packaged options — are routinely rendered as div grids instead of semantic <table> markup. Screen reader users cannot navigate by row and column to compare a single attribute across vehicles, which is the entire point of the comparison tool. WCAG 1.3.1 Info and Relationships requires that the data relationships be programmatically determinable.

Finance applications, calculators, and trade-in widgets

The finance section of a dealer site combines the highest stakes (the customer is being asked to authorize a credit pull) with the heaviest reliance on third-party widgets. The payment calculator is typically licensed from RouteOne, Dealertrack, or the dealer platform's own engine. KBB Instant Cash Offer, Edmunds Trade-In Value, Black Book, and Manheim Express widgets are all embedded as iframes or as third-party scripts that inject custom shadow DOM. Each integration has its own accessibility profile, and the dealer site inherits all of them.

The credit application itself is the highest-risk surface. Dealertrack's online credit app, RouteOne's Credit Application Manager, and the F&I-vendor pre-qualification forms (700Credit, MeridianLink) frequently fail WCAG 1.3.1 (form fields without programmatic labels), 3.3.1 Error Identification (errors shown only as red borders without text announcement), and 3.3.2 Labels or Instructions (date-of-birth inputs split into three boxes with no group label). When a blind applicant cannot complete a credit application independently, that is direct evidence of denial of access to a financial service that the dealer is offering as a place of public accommodation — almost the strongest fact pattern a plaintiff can present.

Trade-in valuation widgets present a separate problem. KBB ICO and Edmunds Trade-In are pulled in via iframe with their own focus traps, and the "Get Offer" flow asks for VIN, mileage, and condition through a multi-step modal. Several recent dealer demand letters specifically cite the inability to complete a KBB ICO valuation with VoiceOver or NVDA. The dealer's argument that the widget is third-party rarely succeeds; courts treat the embedded functionality as part of the dealer's offering.

Service scheduling and parts catalogs

Service department scheduling tools — Xtime (Cox Automotive), myKaarma, Dealer-FX, and the OEM-specific schedulers (Toyota ServiceConnect, Ford's service module) — embed as standalone widgets or full-page integrations. The scheduling UI typically presents available appointment slots in a calendar grid. The same date-picker accessibility problems that drive hotel reservation lawsuits drive dealer service lawsuits: keyboard navigation between days is missing, sold-out times are indicated by color alone (failing WCAG 1.4.1 Use of Color), and the appointment-confirmation flow often requires a CAPTCHA that has no audio fallback.

Parts catalogs sit somewhere between an ecommerce store and a spec lookup tool. RevolutionParts and SimplePart power most dealer-branded parts ecommerce, and both have improved accessibility in recent platform versions but ship templates that frequently get customized into non-compliance. Part diagrams (the exploded-view illustrations with numbered callouts) are SVG or image content that requires either a text equivalent listing each numbered part or a description of the assembly. WCAG 1.1.1 applies; a generic "Diagram" alt is insufficient when the diagram is the entire purpose of the page.

Platform-specific failure patterns

Dealer.com (Cox Automotive) powers a large share of franchised dealer sites. The Composer platform has improved markedly since 2020 and ships with reasonable semantic markup on default templates, but the moment a dealer adds custom landing pages, third-party iframes, or asks the implementation team to enable certain "merchandising modules," the accessibility profile changes. Inventory tile customization is the most common regression source.

DealerOn sites are typically more accessible on the marketing surface than on the inventory surface. The inventory carousels, the chat widget integration (LivePerson, Gubagoo, ActivEngage), and the value-trade widgets compound into a pattern where a clean marketing audit produces a failing inventory-page audit on the same domain.

DealerInspire (Cars.com) sites tend to perform better on contrast and heading structure but worse on form labeling, especially in the credit pre-qualification widget and the test-drive request modal. The platform's SPA architecture also produces unannounced route changes that screen readers do not catch without WCAG 4.1.3 work.

CDK Global Digital Marketing and Reynolds & Reynolds ReyRey.com sites are heavily dependent on the dealer's individual configuration. Both platforms expose sufficient template control that two dealers running the same vendor can have wildly different audit outcomes. vAuto inventory feeds (Provision, Stockwave) into any of these platforms inherit the photo-alt and pricing-display issues described above.

Cost and timeline reality for auto dealers

Dealer remediation cost depends heavily on whether the dealer controls the platform or is on a vendor template. Vendor-hosted sites have lower direct fix cost but require coordination with the vendor to push template changes. Dealer groups with in-house dev teams have more direct control and typically faster timelines.

What to do today

Open your inventory results page and Tab through it. If you cannot reach the "Compare," "Save," and "View Details" controls on each vehicle tile, you have a WCAG 2.1.1 keyboard problem that any tester can document in under five minutes. Then click into a vehicle detail page and check the photo gallery alt text — open dev tools, inspect a photo, and read the alt string. If it says something like "Stock photo" or just repeats the year/make/model, you have a 1.1.1 problem on every VIN in inventory, multiplied by 30+ photos each.

Next, run your credit pre-qualification form with VoiceOver (Cmd+F5 on macOS) or NVDA. Listen for whether each field is announced with a clear label and whether errors are spoken aloud when you submit incomplete data. If errors appear only as red borders, that is a WCAG 3.3.1 violation and is among the most-cited issues in dealer demand letters. Finally, ask your platform vendor for a current VPAT and a written statement of WCAG 2.1 AA conformance — if they cannot produce one, escalate.