2026-05-17 · 6 min read
Government Website ADA Compliance 2027: The Complete Guide to the April Deadline
# Government Website ADA Compliance 2027: The Complete Guide to the April Deadline
If you run IT for a state or local government agency and someone has mentioned "the 2027 ADA website compliance deadline," this post tells you exactly what it is, what it requires, whether it applies to your agency, and what a compliance program looks like in practice.
What Changed and Why
Title II of the ADA has prohibited disability discrimination in government programs and services since 1990. That prohibition always applied to government websites — courts have generally interpreted it to require that online services not discriminate against people with disabilities. But until March 2024, there was no specific technical standard.
In March 2024, the Department of Justice published a Final Rule under Title II that established a specific standard: government websites and mobile apps must conform to WCAG 2.1 Level AA. This is the same accessibility standard used by the federal government under Section 508, by the European Union under EN 301 549, and by most major enterprise web accessibility programs.
The rule closes the "what does accessible actually mean?" question. The answer is now legally defined: WCAG 2.1 Level AA.
Who Must Comply and When
April 26, 2027: State and local governments with a total population of 50,000 or more.
April 26, 2028: State and local governments with a total population under 50,000.
The deadline applies to:
- State agencies
- County governments
- Municipal governments (cities, towns, villages)
- School districts
- Special districts (water management, transit, housing, port authorities, etc.)
- Community redevelopment agencies
- Any political subdivision of a state
"Total population" refers to the population of the entity's jurisdiction, not the population of the website's users or the size of the agency's staff.
An important clarification: The rule requires compliance — not just a plan for compliance — by the deadline. An agency with an audit and a remediation plan in progress but significant non-compliance remaining on April 26, 2027 is not compliant. The deadline is the compliance date, not the start-of-work date.
What WCAG 2.1 Level AA Requires
WCAG 2.1 Level AA has 50 success criteria organized under four principles:
Perceivable. Content must be presentable to users in ways they can perceive. The most commonly failed criteria:
- All images must have text alternatives (1.1.1)
- Video must have captions (1.2.2 for prerecorded, 1.2.4 for live)
- Text must have 4.5:1 contrast ratio against its background (1.4.3)
- UI components must have 3:1 contrast ratio (1.4.11)
- Content must reflow to a single column at 320px (1.4.10)
Operable. All functionality must be operable by users who cannot use a mouse. The most commonly failed criteria:
- All functionality must work via keyboard (2.1.1)
- Keyboard focus must never be trapped in a component (2.1.2)
- Skip navigation links must be present (2.4.1)
- Every page must have a descriptive title (2.4.2)
- The keyboard focus indicator must always be visible (2.4.7)
Understandable. Content and interfaces must be understandable. The most commonly failed criteria:
- Input errors must be identified in text with specific error descriptions (3.3.1)
- Labels and instructions must be provided for all form inputs (3.3.2)
- Suggestions for correcting errors must be provided when known (3.3.3)
- The page language must be identified in the HTML (3.1.1)
Robust. Content must be compatible with current and future assistive technology. The most commonly failed criteria:
- All UI components must have programmatically determinable name, role, and state (4.1.2)
- Dynamic status messages must be programmatically determinable without focus (4.1.3)
What Is Covered
The rule covers all web content and mobile apps that a public entity:
- Makes available to the public
- Uses to offer services, programs, or activities
This includes:
- The main public website and all subdomains
- PDFs, Word documents, spreadsheets, and other documents published on the website
- Web-based applications (permit portals, payment systems, service request forms)
- Mobile apps distributed to the public
- Third-party content the agency has procured and controls
Limited exceptions exist for truly archived content, pre-existing documents no longer actively used, and content posted by third parties not under contract to the agency.
What Is Not Covered
The rule does not apply to:
- Purely internal government systems (employee intranet, HR systems not accessible to the public)
- Third-party content the agency did not procure and cannot control (social media posts by the public on government platforms)
- Content that was created before the compliance date that is no longer actively used or maintained and is labeled as archived
The Enforcement Mechanism
DOJ enforcement of Title II web accessibility follows a complaints-first model. A resident with a disability files a complaint with the DOJ, DOJ investigates, and agencies that cannot demonstrate compliance face corrective action.
Corrective action under Title II typically includes:
- A binding corrective action agreement or consent decree
- Documented remediation timelines with specific milestones
- Periodic progress reporting to the DOJ
- A re-audit after remediation
- Monitoring by a DOJ-appointed third party in more serious cases
Agencies that have documented their compliance program — audit, remediation plan, progress tracking — are in a substantially different negotiating position than agencies that have ignored the requirement.
Private lawsuits under Title II of the ADA are also possible, though less common for government web accessibility than DOJ-initiated enforcement.
What a Compliance Program Looks Like
Four components make a defensible government website ADA compliance program:
1. A WCAG 2.1 Level AA audit. A professional assessment using both automated tools and manual testing with assistive technology (NVDA, VoiceOver) across a representative sample of the site and document library. Automated tools alone detect only 57% of failures and do not produce defensible compliance documentation.
2. A remediation plan. A documented timeline with responsible parties and target completion dates for each finding, organized by severity. Critical failures first, then major, then minor. Built to reach compliance by the deadline with margin for re-testing.
3. An accessibility statement. Published on the website, identifying the standard (WCAG 2.1 Level AA), the auditor, known limitations, and a contact mechanism for residents who encounter barriers.
4. Sustainable production processes. New content, new forms, new documents must meet the standard going forward. An accessibility fix overridden by the next content update is not a compliance program.
Starting Now
From today (May 2026) to the April 2027 deadline is approximately 11 months. A realistic plan:
- May–June 2026: Procurement and vendor engagement
- June–July 2026: Audit (4-6 weeks for a full 200-page assessment)
- August 2026: Remediation plan finalized and work begins
- August–January 2027: Remediation (critical findings: 90 days; major findings: 6 months)
- February 2027: Re-audit of remediating findings
- March 2027: Final corrections and accessibility statement published
- April 26, 2027: Compliance deadline
An agency starting procurement in Q3 or Q4 2026 is building a timeline that cannot realistically reach compliance by the deadline.
The Parallax WCAG audit from Morton Technology Consulting is designed for exactly this timeline — built for Florida government agencies, 200 representative pages, NVDA and VoiceOver manual testing, full findings report, remediation roadmap, accessibility statement. The sample audit report is at morton-digital.com/parallax-sample-audit.
If you need to establish a self-assessment baseline before engaging an auditor, the free WCAG 2.1 AA Checklist and the WCAG Pre-Audit Readiness Kit ($149) provide the tools to understand your current state before writing the RFP.
---
*Morton Technology Consulting LLC, Tallahassee, FL. Government website ADA compliance audits for the April 2027 deadline. [email protected]*
Sources
- [1] ADA.gov — DOJ Fact Sheet: New Rule on Accessibility of Web Content and Mobile Apps — "State and local governments must make sure that their web content and mobile apps meet WCAG 2.1, Level AA"
- [2] Federal Register — Interim Final Rule extending Title II compliance dates (April 20, 2026) — "The compliance date for State and local government entities with a total population of 50,000 or more is extended from April 24, 2026, to April 26, 2027"
- [3] Federal Register — Interim Final Rule extending Title II compliance dates (April 20, 2026) — "The compliance date for State and local government entities with a total population of less than 50,000 is extended from April 24, 2027, to April 26, 2028"
- [4] ADA.gov — Title II of the ADA — "Title II of the ADA prohibits discrimination against people with disabilities in all state and local government services, programs, and activities"
- [5] Deque University — Automated vs. Manual WCAG Testing — "automated testing tools can only detect 57% of accessibility issues"
Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →