Loading...
Residents cannot choose a different government. That is why federal agencies answer to Section 508, state and local entities now face explicit WCAG deadlines under the ADA Title II rule, and inaccessible PDFs, forms, and legacy systems have become legal liabilities. Here is the full picture.
federal agencies have been bound to WCAG-based ICT standards under the Revised Section 508 rules — no grace period left
current ADA Title II web deadlines for state and local governments after the DOJ's April 2026 one-year extension
the technical standard the Title II rule adopts for public entities' web content and mobile apps
US adults has a disability — and unlike private customers, residents cannot take government services elsewhere
Government services are the one category of digital service no one can opt out of. Paying taxes, renewing a license, applying for benefits, requesting records, registering to vote, and receiving emergency alerts all increasingly happen online — and the residents most likely to depend on those services are disproportionately likely to have disabilities. One in four US adults has a disability, with higher rates among older adults, veterans, and lower-income residents. When a benefits portal fails a screen reader user, there is no competitor to switch to; the service is simply denied.
Digital accessibility is also an equity multiplier for government. The same structural quality that serves assistive technology — semantic HTML, plain language, logical forms, real text instead of image scans — makes services work for residents on old phones, slow connections, and limited English. Agencies that invested in accessible digital services consistently report fewer call-center escalations and in-person visits, because the online channel finally works for everyone it was built to replace.
And government sets the market. Because Section 508 and state procurement rules require agencies to buy accessible technology, every RFP that takes accessibility seriously pushes the entire vendor ecosystem — the same platforms that private-sector sites then reuse. Public-sector compliance work, tracked alongside private litigation in our lawsuit and enforcement research, is where accessibility standards become industry norms.
Which rules bind you depends on your level of government. Full statutory detail lives in our Section 508 guide and ADA compliance guide.
Section 508 of the Rehabilitation Act requires federal agencies to make their information and communication technology (ICT) accessible to employees and members of the public with disabilities. The Revised 508 Standards, in force since January 2018, incorporate WCAG 2.0 Level AA for web content and apply it to electronic documents and software as well. Crucially, 508 governs procurement: agencies must buy accessible ICT, which is why vendors selling to the federal government live and die by their Accessibility Conformance Reports (VPATs). Agencies must also handle 508 complaints and report on compliance — and inaccessible systems routinely surface in Inspector General findings and litigation by federal employees.
The DOJ's April 2024 final rule under ADA Title II gave state and local governments their first explicit web accessibility standard: WCAG 2.1 Level AA for web content and mobile apps. Original deadlines were April 24, 2026 for entities serving 50,000 or more people and April 26, 2027 for smaller entities and special districts; a DOJ Interim Final Rule in April 2026 extended both by one year, to April 26, 2027 and April 26, 2028. The rule covers everything a public entity offers online — services, programs, activities — including content provided through contractors. The extension moved dates only; the standard, scope, and exceptions are unchanged, and private Title II lawsuits and state-law claims continue regardless.
Several states legislate beyond the federal floor. Colorado's HB21-1110 makes inaccessible state and local government ICT a civil rights violation with statutory damages, with obligations live since July 2024. Illinois's Information Technology Accessibility Act binds state agencies and universities, and many states pin their standards to current WCAG or Section 508 by policy. The DOJ's federal extension does not pause any of these — a Colorado municipality, for example, has been exposed to state claims since 2024 no matter what the federal Title II timeline says.
Government does not build most of its technology; it buys it. Payment processors, permit systems, agenda-management platforms, transit apps, and emergency-alert services are vendor products — but Section 508 and the Title II rule hold the government entity responsible for what residents experience, including services delivered through contractors. That makes accessibility clauses, honest ACRs/VPATs, independent verification, and remediation commitments in contracts a compliance requirement, not a nice-to-have. For vendors, it means WCAG conformance is now the price of admission to the public-sector market.
Deep dive: our analysis of the DOJ Title II deadline extension and what it does — and does not — change.
Public-sector estates share a distinctive failure profile: documents, forms, and legacy systems. Each issue links to the relevant WCAG success criterion.
Government's defining accessibility problem is documents: decades of meeting minutes, ordinances, permit applications, budgets, and reports published as untagged or scanned PDFs that screen readers cannot parse. The Title II rule's exception for pre-existing documents evaporates the moment a document is needed to access a current service or program. Triage rather than boil the ocean — tag the documents residents actually use, convert forms and high-traffic content to accessible HTML, fix the templates that generate new documents, and test with our free PDF accessibility checker.
Benefits applications, permit and license forms, tax payments, records requests, and service complaints are the core transactions of digital government — and they are riddled with unlabeled fields, inaccessible CAPTCHAs, rigid session timeouts, and error messages that never reach assistive technology. A resident who cannot complete the online benefits form is not inconvenienced; they are denied a government service, which is precisely what Title II and Section 508 prohibit.
Court records systems, utility-billing portals, GIS map viewers, and job-application platforms often run on decade-old vendor software with custom widgets that have no accessible names, no keyboard support, and no ARIA semantics. These systems fail hardest and are slowest to fix, so start the vendor conversations now: demand conformance roadmaps at renewal, require ACRs for replacements, and where remediation is genuinely infeasible, stand up an accessible alternative channel while the replacement is procured.
Government sites are sprawling — hundreds of departments, thousands of pages — and without skip links, sane heading hierarchies, and descriptive link text, screen reader users must wade through repeated menus on every page to find anything. Information architecture is an accessibility issue at this scale: consistent templates, landmarks, and a working site search determine whether residents with disabilities can locate the service at all.
Council-meeting streams and recordings need captions; emergency alerts published as images of text on social media are unreadable to screen readers exactly when the stakes are highest. Public-meeting video is explicitly within the Title II rule's scope going forward, and effective communication during emergencies is a long-standing ADA obligation — publish alerts as real text, caption public videos, and keep contrast and legibility high in crisis communications.
Sized for the realities of government: federated ownership, procurement cycles, and estates measured in thousands of pages.
Name an accessibility coordinator with authority, then inventory the full estate: websites and subdomains, mobile apps, vendor portals, document repositories, kiosks, and social channels. Government estates are federated across departments — compliance fails where ownership is ambiguous, so assign every property an owner and a deadline.
Federal agencies audit against the Revised 508 Standards (WCAG 2.0 AA baseline, with WCAG 2.1/2.2 AA as good practice); state and local entities against WCAG 2.1 AA per the Title II rule. Combine automated crawls — invaluable at government scale — with manual keyboard and screen reader testing of the top resident transactions, and validate against the WCAG 2.2 checklist.
Fix the services residents depend on first: payments, benefits, permits, emergency information, and the documents those services require. A tagged budget PDF from 2015 helps no one if the water-bill portal is unusable. Publish your prioritization — transparency about the plan is itself a defensible posture under Title II.
Add explicit WCAG/508 conformance requirements, ACR/VPAT submission, independent verification, and remediation obligations to every ICT solicitation and renewal. Section 508 has made accessible procurement mandatory federally since the standards took effect; state and local entities need the same discipline or every new purchase adds to the backlog.
Train content authors (the people publishing agendas and notices daily), enforce accessible templates in the CMS, run continuous automated monitoring with scheduled manual re-audits, and publish an accessibility statement with a responsive barrier-reporting channel. Document everything — under both 508 and Title II, a dated record of progress is your best evidence in any complaint or investigation.
Triage your document backlog — test agendas, forms, and reports for tagging and structure.
Meets and exceeds both the Title II standard and the Section 508 baseline.
Estate-wide audits against 508 or Title II, with triage built for public-sector scale.
Operating internationally? See how the European Accessibility Act compares.
Section 508 applies to federal agencies (and is contractually flowed down to their vendors), requiring accessible ICT under the Revised 508 Standards, which incorporate WCAG 2.0 AA — it also governs what the federal government may buy. The ADA Title II web rule applies to state and local governments and adopts WCAG 2.1 AA for web content and mobile apps, with compliance deadlines phased by population size. Many states additionally require 508-equivalent standards for their own agencies by statute or policy, so a given system can be subject to several regimes at once.
The 2024 final rule originally required WCAG 2.1 AA conformance by April 24, 2026 for public entities serving populations of 50,000 or more, and by April 26, 2027 for smaller entities and special district governments. In April 2026, the DOJ issued an Interim Final Rule extending both deadlines by one year — to April 26, 2027 and April 26, 2028. Nothing else changed, and state laws like Colorado's HB21-1110 and private litigation did not pause, so prudent entities are keeping the original dates as internal targets.
Not all at once. The Title II rule contains exceptions for archived web content and for pre-existing electronic documents — but the exceptions end where current use begins: any document someone needs to apply for, access, or participate in a current service, program, or activity must be accessible, and individuals can always request accessible versions as effective communication. The practical strategy is triage: tag the actively used documents, move forms and high-traffic content to accessible HTML, fix generating templates so new documents are born accessible, and handle true archives on request.
Yes. Both Section 508 and the Title II rule hold the government entity responsible for the accessibility of services it provides through contractors and vendor platforms — residents experience the permit system as the city, not as the software company. That is why procurement is the main lever: require WCAG conformance and current ACRs/VPATs in solicitations, verify claims through your own testing, and negotiate remediation timelines. If a legacy vendor system cannot be fixed promptly, provide an equally effective accessible alternative in the interim.
Through several channels at once. The DOJ can investigate and sue under Title II, and individuals can file DOJ complaints or private lawsuits — Title II carries a private right of action. Section 508 requires agencies to accept complaints, and federal employees and members of the public have litigated under it. Funding agencies enforce Section 504 against grantees, state attorneys general and private plaintiffs enforce state laws like Colorado's, and advocacy organizations routinely test public-sector sites. The volume across all channels is tracked in our lawsuit and enforcement research.
Build to WCAG 2.2 Level AA. It is the current W3C recommendation and is backwards-compatible: meeting 2.2 AA automatically satisfies the Title II rule's 2.1 AA requirement and the 2.0 AA baseline in the Revised 508 Standards, while adding criteria — focus appearance, target size, accessible authentication — that materially help residents. Building to the newest standard also future-proofs procurement specs and avoids re-auditing when regulations inevitably move forward.
We audit government estates against Section 508 and the Title II rule, triage by resident impact, and deliver remediation plans and procurement language your teams can execute before the deadlines land.