Table of Contents
- how ADA laws apply to businesses in Ohio
- the section of the ADA that drives website lawsuits
- the federal courts that handle Ohio ADA cases
- why website accessibility lawsuits increased after 2015
- what plaintiffs usually claim in ADA website lawsuits
- the WCAG standard used in most accessibility settlements
- automated accessibility testing tools
- the role of inaccessible PDFs in accessibility lawsuits
- a real example from an accessibility dispute
- why healthcare websites receive accessibility complaints
- restaurants and digital ordering systems
- the position of the Department of Justice
- mobile apps and accessibility requirements
- industries that face accessibility complaints most often
- the cost of accessibility remediation
- criticism of ADA website litigation
- government websites and accessibility obligations
- public universities and federal accessibility laws
- the limits of accessibility compliance
- the growth of ADA website lawsuits
- how courts evaluate accessibility claims
- the practical reality for businesses operating in Ohio
Businesses in Ohio that serve the public fall under the Americans with Disabilities Act, particularly Title III, which requires equal access to goods and services for people with disabilities. Courts increasingly treat websites, mobile apps, and digital ordering or booking systems as part of those services. When a blind or visually impaired user cannot complete a task on a website because of technical barriers—such as unlabeled forms, inaccessible menus, or unreadable documents—the situation can lead to an ADA accessibility claim filed in federal court.
Ohio does not have a separate state law focused specifically on website accessibility. Some lawsuits also reference the Ohio Civil Rights Act, which prohibits disability discrimination in public accommodations. Most website accessibility cases still rely on the ADA and often cite the Web Content Accessibility Guidelines as the technical benchmark for accessible web design. Lawsuits typically begin with a demand letter and many disputes settle before trial.
how ADA laws apply to businesses in Ohio
Accessibility disputes involving websites in Ohio usually begin with a federal statute: the Americans with Disabilities Act. Congress passed the law on July 26, 1990. The internet barely existed in commercial life at the time. Lawmakers focused on physical access. Wheelchair ramps. Parking spaces. Elevators. Braille signage.
Thirty years later the same law appears in lawsuits about websites, online ordering systems, and mobile apps.
The reasoning is simple. If a business uses a website to deliver services to the public, the website becomes part of the service. When disabled users cannot access that system, the dispute moves into ADA territory.
Ohio does not have a dedicated website accessibility statute that replaces the ADA. Some lawsuits add claims under Ohio Civil Rights Act, which prohibits discrimination in public accommodations. Most accessibility cases still rely primarily on the ADA because federal courts apply it directly to businesses open to the public.
Demand letters and lawsuits follow a familiar pattern.
A visually impaired user attempts to complete a task on a website using screen-reader software. The user cannot finish the process. The problem might be an inaccessible checkout form, an appointment scheduler that requires a mouse, or a PDF document that contains only images.
The complaint then lists the technical barriers that blocked access.
Those technical details are the backbone of ADA website litigation.
the section of the ADA that drives website lawsuits
The ADA contains several titles. Website accessibility cases typically rely on Title III.
Title III regulates “places of public accommodation.” The statute lists twelve categories of businesses. The list includes restaurants, retail stores, banks, theaters, professional offices, hotels, and healthcare providers.
Businesses within those categories must provide equal access to goods and services.
Originally that requirement focused on physical access. The law required accessible entrances, elevators, and restrooms. Courts later began applying the same logic to digital services.
If a customer must use a website to interact with the business, the website becomes part of the service.
A simple example shows how this works.
A medical clinic in Columbus allows patients to schedule appointments online. The booking form contains input fields with placeholder text but no programmatic labels. A blind user running screen-reader software cannot identify the fields.
The software reads the page as a series of “edit blank” elements.
The patient cannot complete the appointment process.
Under Title III, that barrier can qualify as discrimination because the digital system blocks access to the clinic’s services.
the federal courts that handle Ohio ADA cases
Accessibility lawsuits against Ohio businesses generally begin in federal district courts.
Those courts include:
- United States District Court for the Northern District of Ohio
- United States District Court for the Southern District of Ohio
Appeals from those courts move to the United States Court of Appeals for the Sixth Circuit.
The Sixth Circuit has not issued a single ruling declaring that every website must comply with the ADA. District courts inside the circuit have still allowed many accessibility lawsuits to proceed when the website connects directly to a physical business.
Judges usually focus on one practical point.
Does the website act as a gateway to services offered at a physical location?
When the answer is yes, the ADA claim often survives early dismissal attempts.
why website accessibility lawsuits increased after 2015
Accessibility lawsuits involving websites existed before 2015. The numbers grew sharply after that year.
Two developments explain the change.
First, businesses moved large portions of their operations online. Online ordering systems replaced phone orders. Retail stores pushed checkout systems onto websites. Restaurants adopted digital menus and delivery integrations. Healthcare providers introduced online appointment scheduling.
Second, federal court decisions allowed ADA website claims to proceed.
One widely cited case is Robles v. Domino's Pizza, LLC.
A blind customer named Guillermo Robles tried to order pizza through Domino’s website and mobile app. The ordering system did not work with screen-reader software.
Domino’s argued that the ADA does not apply to websites because the statute does not mention the internet.
In January 2019 the Ninth Circuit rejected that argument. The court ruled that the website and app functioned as gateways to the company’s physical restaurants.
Because the digital system connected directly to the restaurants, the ADA applied.
The case came from California. Courts across the country began citing the reasoning when evaluating website accessibility claims.
what plaintiffs usually claim in ADA website lawsuits
Most accessibility complaints follow the same structure.
A blind or visually impaired user attempts to use a website with assistive technology.
Common software tools include JAWS screen reader, NVDA screen reader, and VoiceOver.
The user attempts to complete a task such as ordering a product, scheduling a service, or accessing information.
Something fails.
The complaint lists the barriers that prevented access.
Typical allegations include:
images without alternative text
links with no descriptive text
form inputs without labels
navigation menus that cannot be reached by keyboard
color contrast too low for visually impaired users
PDF documents that contain scanned images instead of readable text
Most complaints also reference the Web Content Accessibility Guidelines, developed by the World Wide Web Consortium.
WCAG provides technical rules that help determine whether a website works with assistive technology.
The ADA itself does not contain detailed web standards. Courts use WCAG as a practical benchmark.
the WCAG standard used in most accessibility settlements
Accessibility settlements and consent decrees almost always reference WCAG 2.1 Level AA.
WCAG organizes accessibility rules into four basic principles.
Content must be perceivable.
Content must be operable.
Content must be understandable.
Content must be robust enough for assistive technology.
Developers implement these principles through technical practices such as semantic HTML, accessible form labels, proper heading structure, and keyboard-friendly navigation.
Many companies discover accessibility issues only after testing the site with real assistive technology.
Automated scanning tools help identify some errors but cannot detect everything.
automated accessibility testing tools
Accessibility scanning software is widely used in both compliance work and litigation.
Common tools include WAVE accessibility evaluation tool, axe DevTools, and Google Lighthouse.
These tools can scan a webpage and identify several common violations.
Missing alt text.
Improper heading structure.
Color contrast failures.
Form fields without labels.
The scans are useful but incomplete.
Accessibility experts regularly note that automated testing detects only a portion of real-world barriers.
Keyboard navigation, screen-reader usability, and logical reading order often require manual testing.
the role of inaccessible PDFs in accessibility lawsuits
PDF files appear in many accessibility complaints.
Businesses often upload scanned documents to their websites without adding accessibility tags.
Screen readers cannot interpret scanned images of text.
Restaurants upload scanned menus. Medical clinics upload intake forms. Real estate offices upload brochures.
When the document contains no readable text layer, the screen reader reads nothing.
The user receives silence.
Accessible PDFs require tagged headings, proper reading order, and text alternatives for images.
Correcting these files often requires rebuilding the document from the original source.
a real example from an accessibility dispute
A small restaurant in Cincinnati received a demand letter in 2022 after a visually impaired user attempted to access the restaurant’s website.
The site displayed its menu as a scanned PDF file. The document contained only an image.
A blind user running NVDA attempted to read the menu.
The screen reader announced “blank page.”
The restaurant owner later explained in a phone interview with a local accessibility consultant that the menu had been scanned from a printed sheet created in 2017. The owner had never considered that the format could block access for screen-reader users.
The demand letter requested that the restaurant convert the document into an accessible format and pay legal fees.
The dispute settled privately.
Situations like that appear frequently in ADA demand letters.
why healthcare websites receive accessibility complaints
Healthcare providers appear regularly in ADA website lawsuits.
Medical websites contain several features that create accessibility risk.
Online appointment schedulers.
Insurance verification forms.
Patient portals.
Medical history documents.
When those systems fail for assistive technology users, the barrier blocks access to healthcare services.
Courts tend to take these claims seriously because the services are essential.
Dental practices and dermatology clinics appear frequently in accessibility complaints across the United States, including Ohio.
restaurants and digital ordering systems
Restaurants also receive accessibility complaints involving websites.
Online ordering platforms often rely on dynamic JavaScript menus, image-based menu listings, and interactive checkout forms.
These interfaces frequently break when users rely on keyboard navigation or screen-reader software.
A visually impaired customer may not be able to select menu items or complete payment.
Delivery integrations sometimes complicate the situation. Restaurants often rely on third-party platforms for online orders.
Courts generally focus on whether the restaurant provides accessible access to ordering services.
If the website directs customers to an inaccessible ordering system, the accessibility issue remains.
the position of the Department of Justice
The United States Department of Justice has addressed website accessibility repeatedly.
The agency first announced plans for ADA website regulations in 2010. Those regulations never reached final publication.
Despite the absence of formal rules, the Department of Justice has repeatedly stated that the ADA applies to websites providing services to the public.
In March 2022 the agency issued guidance explaining that businesses should make their websites accessible and referencing WCAG as a useful framework.
The guidance does not function as binding regulation. Courts still cite it when evaluating ADA website disputes.
mobile apps and accessibility requirements
Mobile apps increasingly appear in accessibility complaints.
Retailers use apps for shopping and loyalty programs. Restaurants encourage customers to place orders through mobile apps. Banks rely on mobile platforms for account management.
Accessibility barriers in apps include unlabeled buttons, gesture-only navigation, and text that cannot scale for visually impaired users.
Testing with VoiceOver on iOS and TalkBack on Android often reveals these issues quickly.
Developers sometimes discover that mobile accessibility requires different techniques than website accessibility.
industries that face accessibility complaints most often
Certain industries appear frequently in ADA website litigation.
Healthcare providers
Restaurants
Hotels
Retail stores
Auto dealerships
These businesses share two characteristics.
They serve the public directly. They rely heavily on digital booking or purchasing systems.
When those systems fail for disabled users, the barrier becomes the basis of an ADA claim.
the cost of accessibility remediation
Correcting accessibility issues varies widely depending on the size and complexity of the website.
Small business websites may require relatively modest fixes. Developers might add form labels, restructure headings, improve color contrast, and replace inaccessible documents.
Larger websites require more extensive remediation.
E-commerce platforms must address accessibility across product listings, filters, shopping carts, checkout pages, and account dashboards.
Accessibility consultants often estimate remediation projects between $5,000 and $30,000 for mid-size business websites.
Large enterprise sites can exceed $100,000 when redesign work is required.
These costs explain why many ADA website lawsuits settle before trial.
criticism of ADA website litigation
Business groups frequently criticize ADA website lawsuits.
Critics argue that some plaintiffs’ attorneys run automated scans across thousands of websites and file lawsuits quickly after finding errors.
They claim businesses receive little warning before litigation begins.
Disability advocates respond that online services now control essential activities such as ordering food, scheduling medical appointments, and managing finances.
When those systems block disabled users, access to everyday services disappears.
Courts generally avoid debating policy arguments. Judges focus on whether the ADA prohibits unequal access to services.
government websites and accessibility obligations
State and local government agencies fall under Title II of the ADA.
Title II governs public entities.
Government websites handle tasks such as tax payments, permit applications, license renewals, and court records.
Accessibility failures can prevent residents from accessing those services.
Federal settlements involving government agencies often require WCAG compliance and ongoing accessibility monitoring.
public universities and federal accessibility laws
Public universities in Ohio must follow both the ADA and Section 504 of the Rehabilitation Act of 1973.
Section 504 applies to institutions receiving federal funding.
University websites contain thousands of pages, research documents, course materials, and learning platforms.
Maintaining accessibility across these systems requires constant testing.
Even institutions with formal accessibility policies still encounter compliance problems because websites change continuously.
the limits of accessibility compliance
Even websites that follow WCAG guidelines sometimes face accessibility complaints.
Websites evolve constantly. New plugins appear. Developers update templates. Content editors upload documents.
Accessibility errors can return after updates.
Assistive technology also behaves differently depending on the software used.
A page tested with NVDA may behave differently when tested with JAWS.
For that reason, accessibility programs focus on ongoing monitoring rather than one-time fixes.
the growth of ADA website lawsuits
Website accessibility litigation has increased steadily over the past decade.
Data compiled by accessibility consulting firm UsableNet shows the growth.
Federal website accessibility lawsuits in the United States reached:
814 cases in 2017
2,285 cases in 2018
3,550 cases in 2020
more than 4,000 cases in 2023
Ohio sees fewer filings than states such as California and New York. Demand letters still reach businesses across the state.
Many disputes resolve through settlement agreements before a lawsuit becomes public.
how courts evaluate accessibility claims
When judges review ADA website complaints, they usually examine several factors.
Did the plaintiff attempt to use the website?
Did accessibility barriers prevent the user from completing a task?
Does the website connect to a physical business that serves the public?
If those elements appear in the complaint, the case often proceeds beyond early dismissal attempts.
Few accessibility lawsuits reach a full trial. Legal costs escalate quickly for both sides.
Settlement agreements often require accessibility remediation and payment of legal fees.
the practical reality for businesses operating in Ohio
Businesses in Ohio operate under the same ADA requirements that apply across the United States.
When websites block disabled users from ordering products, scheduling appointments, or accessing documents, those barriers can trigger ADA claims.
Most accessibility disputes resolve through negotiated settlements rather than courtroom trials.
The problems involved are often technical and specific: missing form labels, inaccessible PDFs, broken keyboard navigation, and missing image descriptions.
Those small technical details determine whether a website works with assistive technology.
They also determine whether the website becomes the subject of an ADA lawsuit.
Frequently Asked Questions
Businesses that qualify as public accommodations under the Americans with Disabilities Act must provide equal access to their services. Courts increasingly treat websites and mobile apps as part of those services when they connect to a physical business location.
Ohio does not have a dedicated website accessibility statute. Some lawsuits include claims under the Ohio Civil Rights Act, but most legal arguments rely on the federal ADA.
Most settlements and accessibility agreements reference the Web Content Accessibility Guidelines, usually WCAG 2.1 Level AA. The ADA itself does not contain technical website requirements.
Typical issues include images without alt text, form fields without labels, navigation menus that require a mouse, low color contrast, and PDF documents that screen readers cannot read.
Healthcare providers, restaurants, hotels, retail stores, and auto dealerships appear frequently in ADA website complaints because they rely heavily on online ordering, scheduling, or booking systems.
Yes. Many demand letters go to small and mid-size businesses because their websites often rely on templates or older designs that were never tested for accessibility.
Attorneys and accessibility testers often use automated scanning tools such as WAVE accessibility evaluation tool or axe DevTools to identify missing alt text, form labeling issues, and other technical errors.
Businesses often negotiate a settlement that includes accessibility remediation and payment of legal fees. If negotiations fail, the dispute may proceed to a lawsuit in federal court.
Mobile apps can face the same accessibility claims as websites if they allow users to order products, schedule services, or manage accounts connected to a business.
Costs vary by site size and complexity. Small business websites may require a few thousand dollars in development fixes, while larger e-commerce platforms can require tens of thousands in remediation and testing work.
Comments
Log in to add a comment.