Accessibility Enforcement

Having a technical standard is one thing. Having that standard enforced is another. This post explains the main ways accessibility requirements are enforced in practice and what those mechanisms mean for different types of organizations.

The Main Enforcement Channels

Accessibility obligations are enforced through several overlapping channels. The most important are:

• Federal civil-rights enforcement (Department of Justice and Office for Civil Rights)
• Private lawsuits under the Americans with Disabilities Act
• Procurement and contracting requirements (especially Section 508)
• State attorneys general and state accessibility laws
• Complaint-driven investigations

Department of Justice and ADA Enforcement

The Department of Justice (DOJ) enforces Titles II and III of the Americans with Disabilities Act. Title II covers state and local governments; Title III covers private businesses that are places of public accommodation.

For many years the DOJ did not name a specific technical standard for websites. Courts and the Department nevertheless treated WCAG as the most widely accepted measure of accessibility. The 2024 Title II web and mobile accessibility rule changed that: it explicitly requires WCAG 2.1 Level AA for a wide range of state and local government web content and mobile apps, with compliance deadlines in 2027 and 2028.

DOJ can investigate complaints, negotiate settlement agreements, and bring lawsuits. Remedies often include remediation plans, monitoring, training, and monetary relief.

---

Office for Civil Rights (OCR)

The Office for Civil Rights within the Department of Education investigates disability discrimination complaints against educational institutions that receive federal funding. OCR has long treated inaccessible websites, learning management systems, and digital instructional materials as potential violations of Section 504 of the Rehabilitation Act and Title II of the ADA.

OCR investigations frequently result in resolution agreements that require specific accessibility improvements, policies, and reporting.

Private Litigation

Private individuals and advocacy organizations can sue under Title III of the ADA (and, in some circumstances, Title II). These lawsuits have become one of the most active enforcement mechanisms, especially against private-sector websites and mobile apps.

Typical claims allege that barriers prevent people with disabilities from accessing goods or services on equal terms. Many cases settle; some produce published decisions that further shape expectations around digital accessibility.

Because Title III does not yet contain an explicit WCAG mandate in the same way Title II now does, courts continue to look to WCAG as persuasive evidence of what “accessible” means.

Section 508 and Procurement

Section 508 is enforced primarily through the federal procurement process. Agencies are expected to purchase accessible ICT and to require vendors to document conformance, usually through a Voluntary Product Accessibility Template (VPAT) that becomes an Accessibility Conformance Report (ACR).

Failure to meet Section 508 requirements can result in lost contracts, corrective action, or exclusion from future opportunities. For vendors, a weak or inaccurate VPAT is a business risk as much as a legal one.

State and Local Enforcement

Many states have their own accessibility laws or have incorporated WCAG into procurement rules and civil-rights statutes. State attorneys general can bring actions, and some states allow private rights of action. Public entities that are already subject to the DOJ Title II rule may also face parallel state requirements.

What This Means for Risk Management

Enforcement risk is not theoretical. It shows up as:

• Complaint investigations that consume staff time and require formal responses
• Lawsuits that produce remediation obligations, monitoring, and legal costs
• Procurement barriers when a VPAT or audit report is missing or weak
• Reputational harm when accessibility failures become public

Organizations that treat accessibility as a one-time project or rely solely on automated scans carry higher residual risk. Those that maintain documented, ongoing programs — including manual evaluation, clear ownership, and continuous monitoring — are better positioned to respond to complaints, defend their practices, and meet contractual obligations.

Key Takeaway

Accessibility requirements are enforced through a mix of government investigations, private lawsuits, and procurement rules. The technical standard (WCAG) matters because it is the measure most often used in all of these channels. Understanding the enforcement landscape helps you prioritize work, document decisions, and reduce the chance that an avoidable barrier becomes a formal complaint or legal claim.

Next in the series: Bringing It All Together