ADA Title II Website Compliance for State & Local Government
The Department of Justice's final rule requires all state and local government websites and mobile apps to meet WCAG 2.1 Level AA. The deadline for entities serving 50,000+ people is April 26, 2027. Compliapoint provides source-level audits, remediation, and compliance documentation built for government procurement and legal defense.
What the Title II Rule Actually Requires
Published April 24, 2024, the DOJ’s final rule under ADA Title II eliminates decades of ambiguity. WCAG 2.1 Level AA is now the legally mandated standard for all government digital content. An interim final rule published April 20, 2026 extended the original compliance dates by one year: entities with a total population of 50,000 or more now have until April 26, 2027, and entities under 50,000 or any special district government until April 26, 2028.
Large Entities (50,000+ population)
- State government agencies and departments
- Counties and cities over 50,000
- State universities and large school districts
- Large transit authorities and public utilities
- Covers existing and new web content and apps, with narrow exceptions such as archived content
Smaller Entities (<50,000 population)
- Small cities, towns, and villages
- Small counties and townships
- Independent school districts
- Special district governments
- Same WCAG 2.1 AA standard — one extra year to comply
Covered Digital Content
The rule covers every digital touchpoint used to deliver government programs, services, or activities:
Websites & Web Apps
All government websites, portals, and web-based applications — including those built and managed by third-party vendors.
Mobile Applications
Government mobile apps including parking, transit, utilities, emergency alerts, and citizen service apps.
Documents & PDFs
All downloadable documents including meeting agendas, forms, applications, reports, budgets, and public records.
Video & Multimedia
Public meetings, training videos, informational content, and live streams require captions and audio descriptions.
Payment Portals
Online payment systems for taxes, utilities, permits, fines, and fees — even when operated by third-party processors.
Social Media Posts
New social media posts made after your compliance date must be accessible. Pre-existing posts are exempt.
⚠️ Third-Party Vendors Do Not Absolve You
The Title II rule holds government entities responsible for all digital content and services they provide — regardless of whether a third party developed or manages them. If a vendor-built payment portal, CMS, or SaaS tool is not WCAG 2.1 AA compliant, the government entity is liable. Include WCAG 2.1 Level AA conformance requirements in all technology contracts, with clear remediation timelines and indemnification language.
🚫 Accessibility Overlays Will Not Satisfy Title II
Overlay widgets inject JavaScript that attempts to fix accessibility at render time. They do not repair the underlying HTML, CSS, or document structure that WCAG 2.1 AA evaluates. In 2025, the FTC ordered the largest overlay vendor to pay $1 million in 2025 for deceptive marketing claims. Accessibility professionals have signed the Overlay Fact Sheet opposing these tools. Compliapoint fixes your actual source code — producing results that hold up in federal review.
What Runs Your Site Decides What We Can Fix
Most government entities are not on the platforms source-level remediation reaches, and it is better to say so before you scope an engagement. A 2024 study by ProMET Source of the top 1,000 counties, the top 1,000 cities and all 50 states found CivicPlus at 26.6%, WordPress at 11.8%, Granicus at 11.1% and Drupal at 8.3%. Proprietary platforms account for 52.4% of government sites; open-source platforms for 25.8%.
We remediate WordPress at source, and Shopify where an entity runs a store for permits, passes or merchandise. We do not have code access to CivicPlus, Granicus or Revize — and neither does your IT department. Nobody outside the vendor does.
On those platforms we audit every page, document each finding against WCAG 2.1 AA, and give you the evidence to require the fix from your vendor under your contract. That is not a lesser service for a Title II entity; it is the one the rule actually demands, because the obligation sits with you no matter who built the site.
What Compliapoint Delivers for Government Entities
Every engagement is scoped to your entity's specific digital footprint and delivered with documentation suitable for federal review, procurement, and legal defense.
- Comprehensive WCAG 2.1 AA Audit — Every page, document, form, video, and interactive element evaluated against the full WCAG 2.1 Level AA success criteria
- Source-Level Remediation — Violations fixed directly in your HTML, CSS, templates, and document source files. Repairs placed where an update cannot overwrite them — a child theme or site-specific plugin on WordPress
- PDF & Document Remediation — All downloadable documents tagged for screen reader navigation, including meeting minutes, budgets, applications, and public records
- Video Caption Services — Captions meeting WCAG 1.2.2 (Level A) for recorded public meetings, training videos and informational content, and WCAG 1.2.4 (Level AA) for live-streamed meetings
- VPAT / ACR Generation — Voluntary Product Accessibility Template documenting conformance for procurement, RFP responses, and vendor qualification
- Accessibility Test Record — Dated record of the WCAG 2.1 AA audit and remediation — suitable for DOJ inquiries and legal defense
- Detailed Deliverable Report — Complete audit trail documenting every finding, remediation action, and conformance status
- Vendor Accessibility Review — Assessment of third-party tools and platforms your entity relies on, with risk documentation
- Monthly Monitoring — Ongoing accessibility monitoring to catch new violations introduced by content updates or vendor changes
- Rush Processing Available — Expedited delivery in 1–3 business days for entities approaching their deadline
Limited Exceptions Under the Rule
The Title II rule includes narrow exceptions. These require careful documentation and do not remove the obligation to provide access through alternative means.
Archived Content
Content posted before your deadline, retained only for reference or recordkeeping, clearly labeled as archived, and not updated. If content remains relevant to current programs or is updated in any way, it must comply.
Pre-Existing Documents
Documents posted before the deadline that are not currently used to apply for, access, or participate in services. Documents about a specific individual that are password-protected may qualify.
Third-Party Posts & Comments
Content posted by members of the public (such as social media comments) that is not posted under a contract or arrangement with the government entity.
📌 Important: Exceptions Are Not Blanket Exemptions
Even when an exception applies, your entity must provide an accessible alternative if a person with a disability requests one. The safest strategy is to make all current and commonly accessed content fully WCAG 2.1 AA compliant rather than relying on narrow exceptions that may not hold up under review.
Consequences of Non-Compliance
The Title II rule creates enforceable legal obligations with real consequences for government entities that fail to meet WCAG 2.1 AA by their deadline.
DOJ Investigation
The Department of Justice can investigate complaints and initiate enforcement actions requiring mandatory remediation under federal oversight.
Enforcement and Legal Costs
The DOJ can investigate complaints and sue. These cases are often resolved by a settlement or consent decree that sets your remediation timetable for you. Individuals can sue too, and a winning plaintiff's attorney's fees can be charged to the entity.
Private Lawsuits
Individuals can file private lawsuits under ADA Title II. More than 5,000 digital accessibility lawsuits were filed in 2025 across federal and state courts (UsableNet 2025 Year-End Report), with government entities increasingly targeted.
Funding & Procurement Risk
Non-compliance can affect federal funding eligibility and disqualify entities from procurement opportunities that require accessibility conformance.
Steps to Comply Before Your Deadline
Whether you have weeks or months, Compliapoint can scope and execute a compliance plan matched to your entity's size and digital footprint.
Inventory
Catalog all websites, apps, PDFs, third-party tools, and digital content your entity provides or makes available.
Assess
Complete our 3-minute Site Accessibility Assessment. We review your digital footprint and scope the engagement.
Audit & Remediate
We conduct a full WCAG 2.1 AA audit and fix violations directly in your source code. Standard 7–10 days; rush in 1–3.
Document
Receive your audit report, accessibility test record, VPAT, and complete deliverable package for federal review.
Frequently Asked Questions
Common questions from government IT directors, procurement officers, and ADA coordinators about Title II compliance.
Related Compliance Resources
The April 2027 Deadline Is Approaching
Our assessment takes 3 minutes. We respond with a clear written proposal scoped to your entity's digital footprint — fixed price, no obligation, no surprises.
Start Your Government AssessmentMay qualify for the federal Disabled Access Credit — ask your tax professional