For two decades, web accessibility lived in a gray zone: clearly the right thing to do, frequently litigated, but rarely spelled out in regulation. That era is over. Government mandates in the United States now name a specific technical standard for digital accessibility and attach real compliance deadlines to it, and the first of those deadlines is now less than a year away. Here is who is affected, why this is happening, and what to actually do about it.

The deadlines, up front: under the U.S. Department of Justice Title II rule, state and local government entities serving 50,000 or more people must meet WCAG 2.1 Level AA by April 26, 2027. Smaller public entities and special district governments have until April 26, 2028. These dates were already pushed back once (by a year, in an April 2026 interim final rule), so treat them as firm but confirm the date that applies to you with legal counsel.

Why This Is Happening

Three forces converged.

The web became the front door of public services. Paying a utility bill, enrolling a student, requesting a record, applying for a permit: for most people these now happen on a website or in an app. When that front door does not work with a screen reader or a keyboard, people with disabilities are excluded from services they are legally entitled to use.

The standards matured. The Web Content Accessibility Guidelines (WCAG) gave regulators something concrete to point to. Instead of arguing about what “accessible” means, a rule can simply require conformance with WCAG 2.1 Level AA, a published, testable checklist.

Litigation forced the issue. Years of accessibility lawsuits made it clear that voluntary adoption was not happening fast enough. Regulation followed the courtroom. (We look at the lawsuit numbers in detail in ADA Website Lawsuits Are Surging.)

The centerpiece is the Department of Justice final rule under Title II of the ADA (28 CFR Part 35), which requires the web content and mobile apps of state and local government entities to conform to WCAG 2.1 Level AA.

Who Is Affected

The Title II rule covers state and local government entities, which is a much longer list than most people expect:

  • Cities, towns, and counties, including every department inside them
  • Public school districts, community colleges, and public universities
  • Courts, clerks, and public records offices
  • Public transit agencies, libraries, parks departments, and utilities
  • Special-purpose districts and authorities

Two ripple effects widen the circle further. First, public entities are responsible for content they deliver through third-party platforms, so the vendors, website builders, and CMS providers that serve government clients inherit the requirement in practice. Second, private businesses that serve the public fall under Title III of the ADA, where courts have repeatedly held that websites must be accessible even though a parallel technical regulation has not yet been issued. Organizations that receive federal funding also face accessibility obligations under related federal law. If you are waiting for a rule with your name on it before acting, the lawsuit data says that is the expensive strategy.

When Are the Deadlines?

The compliance dates are phased by the size and classification of the entity. In April 2026 the Department of Justice published an interim final rule that extended the original dates by one year, so the current schedule is:

  • April 26, 2027: for entities serving populations of 50,000 or more, which includes most public colleges and universities.
  • April 26, 2028: for smaller public entities and special district governments.

If your organization is a state or local government, a public university, a court, or a special district, your deadline to meet Title II of the Americans with Disabilities Act is approaching. One detail catches people off guard: a public college or university is classified by the population of the state it operates in, not by its enrollment, so even a mid-sized campus in a populous state falls under the earlier 2027 date. Because classification can be nuanced, confirm the exact date that applies to you with your legal counsel or your state attorney general’s office. The practical takeaway does not change either way: the window for “we will get to it eventually” has closed.

What the Mandates Actually Require

Conformance with WCAG 2.1 Level AA across your web content and mobile apps: roughly 50 testable success criteria covering things like text alternatives for images, keyboard operability, color contrast, form labels, and content structure. Three points trip organizations up:

  • It covers what you publish, not just what you build. Documents, third-party widgets, and platform templates count.
  • It is continuous, not one-time. Every new page, post, and PDF restarts the clock. A site that passed an audit last year can be out of conformance today.
  • Evidence matters. The recognized defenses (fundamental alteration, undue burden) and any good-faith posture all depend on documentation you can produce when asked.

How a Third-Party Accessibility Platform Helps

Meeting a technical standard across hundreds of pages on a deadline is an operations problem, and it is exactly the problem accessibility platforms like Ardor Accessibility exist to solve.

  • Find the problems at scale. Automated WCAG 2.1 AA scanning crawls your site page by page and produces a prioritized, auditor-style violation report in minutes instead of weeks of manual review.
  • Fix a large share automatically. Our remediation widget corrects common violation classes in the visitor’s browser in real time (missing alt text, broken form labels, heading structure, contrast, keyboard navigation aids) and gives visitors assistive profiles for vision, motor, and cognitive needs.
  • Document everything. Every scan and every remediation attempt is timestamped and logged. The platform generates the compliance paper trail (gap analyses, remediation plans, conformance statements, VPAT/ACR documentation) that demonstrates sustained good-faith effort.
  • Stay compliant after the deadline. Monthly automated rescans and reports catch regressions as your content changes, so conformance is a state you maintain rather than a project you finish.

One honest caveat: no automated platform delivers 100% of WCAG conformance by itself. Some criteria require human judgment, which is why we pair automation with manual review guidance (see Automated vs. Manual Accessibility Testing). What a platform does is collapse the cost and timeline of the largest share of the work, and prove, with evidence, that the rest is underway.

Where to Start

  • Run a baseline WCAG 2.1 AA audit of your site. Our free scan takes about a minute.
  • Confirm your compliance date with counsel.
  • Remediate the high-impact violations first, automate the rest, and document as you go.
  • Put scanning and reporting on a recurring cadence.

Ardor Accessibility handles the scanning, remediation, documentation, and monitoring for one flat annual price. Request a demo and we will show you exactly where your site stands.

This article is for informational purposes only and does not constitute legal advice. Please talk to your legal counsel about your specific compliance obligations and deadlines.