Towing & Roadside Assistance Accessibility Guide 2026 | ADA & WCAG

Last updated: 2026-07-28

Towing and roadside assistance sites are used under the worst possible conditions: at the roadside, on a phone, often at night, frequently by someone who is stressed, cold, or in an unfamiliar place. That context makes accessibility failures unusually costly, because the customer has no patience and no alternative path. It also means the audience skews toward exactly the people accessibility standards protect. Drivers with disabilities, older drivers, and people whose vision is worse in low light are all disproportionately likely to need roadside help and disproportionately likely to be blocked by a site that assumes a steady hand, a mouse, and good eyesight. The most common failures are basic. The phone number is baked into a header graphic, so a screen reader announces nothing and a magnifier user cannot find it. The 'request a tow' flow depends on a map pin dragged with a mouse, with no way to type an address or intersection. Service areas are shown only as a shaded region on a map, so no one can find out in text whether their location is covered. Driver ETA pages update in the background without announcing the change. Sticky call bars and popups swallow the screen at 200 percent zoom. Legally, a towing company serving the public is a place of public accommodation, and companies on municipal rotation lists or under government contract may also face Title II and Section 508 obligations. This guide covers the requirements, the failures, and a checklist you can act on.

Legal Requirements

Law / Standard Effective Date Summary Penalty
Americans with Disabilities Act (ADA) Title III In effect Towing and roadside assistance companies serving the general public are places of public accommodation. Their websites, request-for-service flows, and mobile apps are expected to be accessible under prevailing court interpretations, with WCAG 2.1 AA as the de facto standard for emergency request forms, service area information, dispatch tracking, and payment. No statutory damages under federal ADA, but plaintiffs recover attorney's fees and injunctive relief. California's Unruh Act allows statutory damages of $4,000 per violation per visit, and demand letters to local service operators commonly seek $5,000-$15,000 settlements.
ADA Title II (via municipal contracts and police rotation lists) 2024-06-24 Towing operators on a city or county police rotation list, or under contract for municipal impound and abandoned vehicle work, are delivering a service on behalf of a public entity. The Department of Justice web accessibility rule requires public entities to meet WCAG 2.1 AA for web content and mobile apps, and that obligation is routinely flowed down to contracted operators through procurement terms. DOJ enforcement and private suits against the public entity, with contractual indemnity, remediation obligations, and removal from the rotation list flowing to the operator.
State consumer protection and accessibility statutes In effect State civil rights laws such as California's Unruh Civil Rights Act, the New York State and New York City Human Rights Laws, and Colorado's HB21-1110 support website accessibility claims against local service businesses. Several states additionally regulate towing rate disclosure, and rate schedules posted only as images or untagged PDFs can fail both the accessibility standard and the disclosure requirement at once. Statutory damages per violation, attorney's fees, injunctive relief, and separately, state consumer protection penalties for inadequate rate disclosure.

Key Accessibility Issues in Towing & Roadside Assistance

The Phone Number Is a Graphic, and the Call Button Is Unlabeled

For a stranded driver the phone number is the product, and it is very often rendered inside a header image or a banner graphic. A screen reader announces nothing, a low-vision user cannot enlarge it without it turning to mush, and a voice control user cannot say 'click call'. Sites that do use a real link frequently label it with only an icon, so the accessible name is empty or reads as 'link'. Numbers written without separators are announced as a single unbroken figure that no one can transcribe.

How to fix:

Write the phone number as real text with standard separators, marked up as a tel link with a visible text label such as 'Call 555-018-2200 for 24/7 towing'. Never place the number only inside an image. Give any icon-only call button an accessible name, and confirm the number is readable and clickable at 200 percent zoom and on a 320 pixel wide screen.

Request-a-Tow Flows That Depend on Dragging a Map Pin

Modern dispatch forms ask the customer to place a pin on a map or accept browser geolocation. Dragging a pin is a mouse-only interaction that fails for keyboard, switch, and screen reader users, and it also fails for anyone with a tremor or limited fine motor control, which describes a meaningful share of people who break down at the roadside. When geolocation is denied or unavailable underground or in a rural dead zone, many of these forms offer no fallback at all and the request cannot be submitted.

How to fix:

Always provide a labeled text field for street address, intersection, mile marker, or landmark as a first-class alternative to the map, not a hidden fallback. Make the pin position adjustable with arrow keys and announce the resolved address in text after any change. Ensure the form can be completed and submitted end to end with a keyboard alone and no map interaction.

Service Areas Shown Only as a Shaded Region on a Map

Coverage is the first question a stranded customer has, and it is usually answered with an embedded map showing a shaded polygon and nothing else. The map frame is often unlabeled, the shading carries all the meaning, and there is no text anywhere on the page listing which towns, counties, ZIP codes, or highway corridors are covered. Screen reader users, colorblind users, and anyone on a slow roadside connection where the map fails to load get no answer.

How to fix:

List covered counties, cities, ZIP codes, and highway corridors as real text near the map, along with any distance limits and after-hours coverage differences. Give the embedded map frame a descriptive accessible title. Treat the text list as the authoritative source so the page still answers the question when the map does not load.

Driver ETA and Dispatch Tracking That Updates Without Announcing It

Once a truck is dispatched, the customer watches a tracking page showing status and estimated arrival. These pages poll in the background and rewrite the ETA and status silently, so a screen reader user hears nothing when the driver is assigned, delayed, or two minutes away. Status is commonly a colored dot, and the ETA is often drawn on the map only, so it disappears entirely for anyone not using the visual map.

How to fix:

Render status and ETA as text outside the map and mark that region as a live region so changes are announced automatically. Label each status stage in words rather than by color alone, include the last-updated time in text, and announce material changes such as driver assigned or delay with appropriate urgency without flooding the user with every minor refresh.

Sticky Call Bars, Popups, and Rate Sheets That Break at Zoom

Roadside sites lean heavily on sticky call-now bars, chat bubbles, and review popups. At 200 percent zoom or on a small phone in landscape these elements can cover most of the viewport, hiding the address field and the submit button with no way to dismiss them by keyboard. Chat bubbles in particular sit on top of form validation errors, so the customer never sees why the request failed. Rate schedules, which several states require to be disclosed, are frequently posted as images or untagged PDFs.

How to fix:

Keep sticky elements to a small share of the viewport height, make every overlay dismissible with a keyboard-reachable close control and the Escape key, and verify no overlay covers form fields, errors, or the submit button at 200 percent zoom. Publish rate schedules as real HTML tables with proper header cells so they are readable by assistive technology and satisfy disclosure rules at the same time.

Compliance Checklist

  • Phone number appears as real text with standard separators, marked up as a tel link with a visible label, never only inside an image
  • Icon-only call, chat, and menu buttons have accessible names, and all remain usable at 200 percent zoom and 320 pixel width
  • Request-a-tow forms offer a labeled text field for address, intersection, or mile marker as a first-class alternative to map or geolocation input
  • The entire service request can be completed and submitted with a keyboard alone, with errors announced and focus moved to the first error
  • Covered counties, cities, ZIP codes, and highway corridors are listed as real text near any map, and the map frame has a descriptive title
  • Driver status and ETA are rendered as text outside the map and announced through a live region when they change
  • Status stages are labeled in words, not conveyed by color alone, and indicators meet 3:1 non-text contrast
  • Sticky call bars, chat bubbles, and popups are dismissible by keyboard and never cover form fields, errors, or the submit button
  • Rate schedules and fee disclosures are published as real HTML tables rather than images or untagged PDFs
  • Payment and vehicle authorization forms use correct autocomplete attributes and are tested with a screen reader on a mobile device

Further Reading

Other Industry Guides