PageAudit

Government Website ADA Compliance: The Complete Guide

Everything your agency needs to know about Title II web accessibility requirements, from understanding the law to achieving and maintaining compliance.

This scanner requires a Pro plan or higher. Running a free Accessibility scan instead.

Start with a free scan. No signup required.

Understanding Title II and Web Accessibility

Title II of the Americans with Disabilities Act prohibits state and local government entities from discriminating against people with disabilities in their services, programs, and activities. For decades, the application of this law to government websites was interpreted through guidance documents and case-by-case enforcement. That changed in April 2024, when the DOJ published its Final Rule establishing WCAG 2.1 Level AA as the explicit technical standard that government web content must meet.

The rule applies to every state and local government entity in the country, with no minimum size threshold. Cities, counties, state agencies, public universities, school districts, transit authorities, courts, public hospitals, and special districts all fall under its scope. The standard covers all web content and mobile applications that the entity makes available to the public, including websites, portals, online forms, PDFs, videos, and interactive tools.

WCAG 2.1 Level AA is built around four core principles: content must be Perceivable (users can see or hear it through assistive technology), Operable (users can navigate and interact without a mouse), Understandable (content and interface behavior are predictable and clear), and Robust (content works with current and future assistive technologies). There are 50 individual success criteria at Level AA, covering everything from color contrast ratios to form error handling.

Common Accessibility Failures on Government Websites

With 94% of government websites failing WCAG 2.1 AA, the same issues appear again and again. Understanding the most common failures helps you prioritize remediation and allocate resources where they will have the greatest impact.

Inaccessible PDFs are the single most widespread problem on government websites. Scanned documents uploaded as image-only PDFs cannot be read by screen readers at all. Agendas, meeting minutes, budgets, ordinances, and public notices are frequently published this way, effectively locking out residents who rely on assistive technology. Every PDF must be properly tagged with a logical reading order, alternative text for images, and bookmarks for navigation.

Missing form labels prevent screen reader users from understanding what information a form field expects. This is especially damaging on government websites where forms are used for permit applications, utility payments, public records requests, and benefits enrollment. Poor color contrast makes text unreadable for users with low vision or color blindness. Missing alt text on images means screen reader users receive no information about charts, maps, photos of officials, or infographics.

Inaccessible interactive maps and widgets are common on government sites that display zoning information, transit routes, or facility locations. These tools are often built with frameworks that do not generate accessible markup. Missing video captions on public meetings, press conferences, and training videos violate both WCAG and Section 508 requirements.

How to Achieve Compliance

Achieving WCAG 2.1 AA compliance is a process, not a single event. The most effective approach combines automated scanning with manual testing, follows a clear remediation workflow, and includes ongoing monitoring to prevent regressions. Here is how government agencies can structure their compliance effort:

Automated scanning is the essential first step. An automated scanner can evaluate every public-facing page in minutes and surface the violations that affect the largest number of users. Tools like PageAuditors use the axe-core engine inside a real browser to test against WCAG 2.1 AA criteria, catching issues like contrast failures, missing labels, broken ARIA attributes, and heading structure problems. This gives you a prioritized list of issues ranked by severity.

Manual testing with screen readers covers the issues that automated tools cannot detect. Have someone navigate your most important user flows using NVDA, JAWS, or VoiceOver. Can a resident find contact information, submit a form, pay a bill, or request a public record without using a mouse? These real-world tasks reveal interaction problems that no automated rule can catch.

Remediate by severity. Start with critical and serious issues because they block users entirely and carry the highest enforcement risk. Then move to moderate and minor issues. Most common violations have straightforward fixes, and the scan report provides plain-English guidance for each one.

Ongoing monitoring maintains compliance after the initial remediation is complete. Content updates, CMS upgrades, new page templates, and third-party widget changes can all reintroduce violations. Scheduled scanning catches these regressions before they accumulate into a compliance problem.

Ready to get started? Visit our Government ADA Compliance Scanner to learn about our scanning capabilities, review the compliance checklist for a point-by-point assessment, check the April 2026 deadline details, or run a free scan right now to see where your website stands.

Frequently Asked Questions

Which government entities are covered by Title II web accessibility requirements?
All state and local government entities are covered, regardless of size. This includes cities, counties, state agencies, public universities, community colleges, school districts, transit authorities, public libraries, courts, public hospitals, and special districts like water or fire authorities. If your entity receives public funding or exercises government authority, Title II applies to your web content.
Do we need to make archived content accessible?
The DOJ Final Rule includes a limited exception for archived web content, but the criteria are strict. Content qualifies as archived only if it was created before the compliance date, is maintained exclusively for research or reference, and is clearly labeled as archived. Content that residents still need to access for services, forms, or information does not qualify as archived, even if it is old.
Is automated scanning enough for compliance?
Automated scanning is an essential first step, but it is not sufficient on its own. Automated tools can detect approximately 30 to 40 percent of WCAG 2.1 AA violations, including color contrast, missing alt text, and unlabeled form fields. The remaining issues require manual testing, such as verifying that content is logically structured for screen reader users or that complex interactive widgets are operable via keyboard alone.
What about third-party content embedded on our website?
Government entities are responsible for the accessibility of third-party content embedded on their websites, including social media widgets, embedded maps, video players, and payment processing forms. If a third-party tool is not accessible, you must either work with the vendor to fix it, provide an accessible alternative, or remove it. The DOJ has made clear that outsourcing does not outsource your accessibility obligations.
How often should we scan for accessibility issues?
At minimum, scan after every significant content update or redesign. Ideally, set up automated weekly or daily scanning to catch regressions early. Content management systems, plugin updates, and new page templates can all introduce accessibility violations that were not present in the original design. Ongoing monitoring is significantly cheaper than discovering issues during an enforcement action.