ADA Title II Government Website Compliance: The Complete 2027 Guide
State and local governments now face firm, fast-approaching deadlines to make their websites and mobile apps accessible under the Department of Justice's updated Title II regulations.
State and local governments now face firm, fast-approaching deadlines to make their websites and mobile apps accessible under the Department of Justice's updated Title II regulations. This guide summarizes the rule, explains who and what it covers, and lays out a practical action plan to hit the April 2027 and April 2028 compliance dates with confidence.
1Background: Title II and the New Web Rule
Title II of the Americans with Disabilities Act (ADA) requires state and local governments to ensure that all of their services, programs, and activities are accessible to people with disabilities, including when those services are delivered online. For years, public entities knew they had accessibility obligations but lacked a clear, binding technical standard for their digital content. In April 2024, the U.S. Department of Justice (DOJ) issued a long-awaited final rule that for the first time specifies how websites and mobile apps must be made accessible, largely by adopting the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the baseline technical standard.
The rule was originally set to phase in beginning in 2026, with different compliance dates based on the size of the public entity. However, in April 2026, DOJ issued an interim final rule extending those compliance dates by one year. As a result, most state and local governments now must reach compliance by April 26, 2027, while smaller entities and special district governments have until April 26, 2028.
2Who Must Comply Under Title II
The rule applies to virtually all “public entities” covered by Title II, which includes:
- State governments, including executive agencies, legislatures, courts, and public universities
- Local governments, such as counties, cities, towns, villages, and school districts
- Special district governments, including transit authorities, water districts, housing authorities, and other public authorities
3Compliance Deadlines: April 2027 and April 2028
The 2024 final rule tied compliance deadlines to population size, and the 2026 interim final rule kept that structure while extending the dates by one year.
Deadline 1
April 26, 2027
State and local government entities with a total population of 50,000 or more
Deadline 2
April 26, 2028
Entities with population under 50,000, and all special district governments
Waiting until late 2026 or 2027 to begin remediation carries significant legal, operational, and budget risks. Agencies should treat 2026 as their active remediation year.
4What Websites, Apps, and Content Are Covered
The Title II web rule is intentionally broad — it covers all web content and mobile applications a public entity provides or makes available. Examples of covered content include:
- Main agency websites and department microsites
- Online forms, applications, and transactional portals (permits, licenses, payments, registrations)
- Online meeting platforms and portals used to deliver services or conduct public meetings
- Mobile apps for paying parking tickets, accessing transit schedules, or receiving emergency alerts
- Embedded maps, charts, videos, and social media feeds displayed on government-owned pages
- Online learning portals, recruitment and hiring systems, and public-facing intranet content
The rule also covers digital documents made available through those sites, such as PDFs, Word documents, spreadsheets, and slide decks.
5The Technical Standard: WCAG 2.1 Level AA
The core of the DOJ rule is its adoption of WCAG 2.1 Level AA as the primary technical standard. At a high level, it requires:
6Key Exceptions and Flexibilities
DOJ recognized that not every piece of digital content can or should be remediated immediately. Common exceptions include:
Preexisting conventional electronic documents
Certain files posted before your compliance date may be exempt, except when individuals specifically need them to access current services.
Archived web content
Content maintained solely for reference or recordkeeping and not updated after a certain date may qualify as archived.
Third-party content you do not control
User-generated comments or some embedded third-party services may be treated differently, though you must still avoid unnecessary barriers.
Individual-specific documents
Case-specific correspondence provided only to specific individuals may not need to meet WCAG the same way as public-facing documents.
7Enforcement and Risks of Noncompliance
DOJ's web rule is enforceable under the same mechanisms as other Title II requirements. Individuals can file complaints with DOJ or appropriate state agencies, and DOJ can open investigations, negotiate settlement agreements, and pursue litigation.
In addition to formal enforcement, agencies face reputational, operational, and equity risks if they miss the deadlines. Inaccessible digital services can prevent community members from applying for jobs, paying bills, registering for programs, or receiving critical emergency information — disproportionately harming residents with disabilities and undermining public trust.
8A Practical Action Plan for 2026–2028
Agencies have a finite window to move from awareness to implementation. This plan is designed for practical use by state and local governments of varying sizes.
- 1Designate an accessibility lead or small cross-functional team with representation from IT, communications, legal, HR, and key program areas.
- 2Secure executive sponsorship to ensure accessibility is treated as a programmatic and legal priority, not just a one-time IT project.
- 3Develop or update an accessibility policy that references WCAG 2.1 Level AA and clearly assigns responsibilities for websites, apps, documents, and procurement.
- 4Establish a governance structure for decision-making, exception handling, and coordination with vendors and contractors.
- 1Create a comprehensive list of all domains, subdomains, microsites, and major web applications.
- 2Identify all mobile apps your agency provides or makes available, including white-labeled or vendor-hosted apps.
- 3Catalog common document types (PDFs, forms, brochures, agendas, reports) and estimate volume, especially for high-impact areas.
- 4Flag systems and content that are mission-critical or heavily used by the public as highest priorities.
- 1Use automated scanning tools and manual testing (including screen reader and keyboard-only testing) on your main websites and applications.
- 2Assess content against WCAG 2.1 Level AA, paying attention to navigation structure, forms, error handling, media, and color contrast.
- 3Document issues in a centralized tracking system, tagging them by severity, user impact, and effort required.
- 4Develop a remediation roadmap from highest impact and risk to lower-risk content, factoring in your 2027 or 2028 deadline.
- 1Prioritize remediation of global templates, navigation menus, headers, footers, and core components that appear across your sites and apps.
- 2Update design systems and style guides to embed accessible patterns — heading hierarchies, color palettes, focus indicators, error messaging.
- 3Work with your CMS or platform vendors to ensure themes, widgets, and plug-ins support accessible markup and behavior by default.
- 4For mobile apps, coordinate with development teams to apply platform-specific accessibility best practices on iOS and Android.
- 1Identify which preexisting electronic documents to remediate, considering frequency of use, legal importance, and relevance to current services.
- 2Create templates for accessible PDFs and office documents going forward, so new content is created accessibly by default.
- 3Train staff who produce documents on headings, lists, tables, alt text, and export settings.
- 4For large legacy collections that qualify for an exception, establish a process for providing accessible versions on request.
- 1Update procurement policies and RFP templates to require vendors to meet WCAG 2.1 Level AA and provide Voluntary Product Accessibility Templates (VPATs).
- 2Include accessibility requirements and remediation timelines in contracts, along with the right to test and verify vendor claims.
- 3Avoid procuring new systems that will require extensive retrofitting to meet your 2027 or 2028 deadline.
- 4Engage vendors early about the DOJ rule so they can plan their own development and testing cycles.
- 1Provide role-based training for web developers, designers, content editors, communications staff, and program managers.
- 2Incorporate accessibility into onboarding for new employees who will publish content or manage digital services.
- 3Create quick-reference guides and checklists for common tasks like posting news items, creating event pages, or uploading documents.
- 4Recognize and reward teams that demonstrate leadership in accessible service delivery.
- 1Schedule periodic automated scans and targeted manual testing of high-traffic pages and key transactions.
- 2Set up an accessibility statement and feedback mechanism on your websites and apps, inviting users to report barriers.
- 3Track complaints, feedback, and resolution times, and use this data to refine your remediation priorities and training.
- 4Regularly review your governance structure and policies to ensure they remain aligned with evolving technology and standards.
9Practical Tips by Entity Size
Large Entities (50,000+ population)
- Stand up a central digital accessibility office or working group with authority to set standards.
- Leverage enterprise platforms and shared services to drive consistent accessible experiences.
- Develop detailed implementation guidance and checklists that departments can follow.
- Engage external accessibility experts for independent audits and validation.
Smaller Entities & Special Districts
- Focus first on your primary website, key online forms, and any mobile apps residents rely on most.
- Work closely with your web hosting provider or regional IT consortium for accessible templates.
- Use low-cost accessibility tools and checklists to guide content editors.
- Collaborate with neighboring jurisdictions to share training resources and vendor evaluations.
10Making the Most of 2026
With the deadlines extended to 2027 and 2028, 2026 becomes a critical preparation and execution year. Use this time to:
- Finalize governance, policies, and roles related to accessibility.
- Complete at least one comprehensive audit of your main website and mobile apps.
- Begin or continue remediation of high-impact templates and workflows.
- Integrate accessibility into procurement cycles for any new systems you plan to implement before 2028.
- Launch or expand staff training and internal awareness efforts.
11Looking Beyond the Deadlines
Compliance with the DOJ's Title II web rule is not the end of the journey; it is a baseline. Technology, user expectations, and accessibility standards will continue to evolve, and your digital services must evolve with them.
By embedding accessibility into your culture, governance, and technical practices now, your agency can deliver more inclusive, resilient, and user-friendly services for everyone who relies on them. The April 2027 and 2028 deadlines are important milestones, but the real goal is a long-term commitment to digital equity and equal access.
Ready to start your compliance journey?
WPPersona gives government agencies a WCAG-compliant website platform built for the 2027 deadline.
Schedule a Free Demo