Public Sector and Government Portals: Meeting DOJ's Web Accessibility Rule

The DOJ Title II accessibility rule represents the most significant federal web accessibility regulation in decades. Published in April 2024, this rule establishes specific technical standards for state and local government web content—ending years of ambiguity about what "accessible" means under the Americans with Disabilities Act.

For public entities and the vendors who serve them, the DOJ web accessibility rule creates concrete obligations with defined timelines. Gone are the days of arguing about whether ADA applies to websites. The rule explicitly requires WCAG 2.1 Level AA compliance for web content and mobile applications, with compliance deadlines starting in 2026.

This guide covers what the DOJ rule requires, who must comply, common government portal accessibility failures, and practical strategies for achieving compliance—especially for organizations working with legacy systems under time pressure.

DOJ Title II and the New Baseline for Government Sites

What the Rule Actually Says

What does the DOJ web accessibility rule require? The DOJ's Title II web accessibility rule requires state and local government web content and mobile applications to conform to WCAG 2.1 Level AA standards, with compliance timelines based on population size—April 2026 for larger entities and April 2027 for smaller ones.

The Department of Justice Final Rule establishes:

Technical standard: WCAG 2.1 Level AA as the required conformance level. Not WCAG 2.0, not "substantially accessible"—specifically WCAG 2.1 AA.

Scope: Web content and mobile applications provided or made available by state and local governments.

Deadlines:

• Entities serving populations of 50,000+ must comply by April 24, 2026
• Entities serving populations under 50,000 must comply by April 26, 2027

Third-party content: Governments remain responsible for accessibility of content provided through third-party platforms, applications, and vendors.

Who Must Comply

The rule applies to Title II entities—state and local governments and their agencies:

State governments: All state agencies, departments, and programs.

Local governments: Cities, counties, townships, school districts, and special districts.

Public universities and colleges: State institutions of higher education.

Public utilities: Government-operated utilities and services.

Courts: State and local court systems.

Public transportation: Transit authorities and transportation departments.

Government contractors and vendors: Not directly covered, but governments must ensure vendor-provided content and platforms meet requirements—effectively flowing accessibility requirements to vendors.

What Content Is Covered

The rule covers web content and mobile applications that governments:

Provide: Content created and hosted by the government entity.

Make available: Third-party content linked from or integrated into government sites.

Use for services: Platforms used to deliver government services, even if operated by vendors.

This includes:

• Main government websites
• Department and agency sites
• Online service portals (permits, licenses, payments)
• Document repositories
• Mobile applications
• Constituent communication platforms
• Online meeting and hearing systems

What the DOJ Rule Expects in Practice

Scope of Web and Mobile Content

How does the DOJ rule define web content? Web content includes all information and functionality delivered via web browsers—HTML pages, PDFs, forms, applications, video, and interactive elements. Mobile applications are also explicitly included in the rule's scope.

The rule's definition of web content is comprehensive:

HTML content: All web pages including text, images, forms, and navigation.

Documents: PDFs and other downloadable documents must be accessible or have accessible alternatives.

Media: Video and audio content, including live streams of public meetings.

Applications: Interactive web applications and tools (payment systems, application portals, mapping tools).

Third-party integrations: Chat widgets, forms, payment processors, and other embedded third-party content.

Mobile apps: Government-provided mobile applications must also meet WCAG 2.1 AA (as applicable to mobile).

Limited Exceptions

The rule includes narrow exceptions:

Archived web content: Historical content not updated after the compliance date and maintained only for research or reference—but this exception has limits and doesn't apply to content still actively used.

Third-party content posted by constituents: Comments on social media, user-submitted content on public forums—but not content the government integrates into services.

Conventional electronic documents: Pre-existing documents not created or modified after compliance dates—but documents that must be used for current services must be accessible.

Undue burden: The standard ADA undue burden defense applies, but requires contemporaneous written determination and alternative access.

These exceptions are narrow. Don't assume your content qualifies without careful analysis.

Enforcement Posture

DOJ has indicated active enforcement:

Complaint investigation: DOJ investigates complaints of web accessibility barriers.

Compliance reviews: DOJ may proactively audit government web properties.

Settlement agreements: Past DOJ actions have resulted in settlement agreements requiring accessibility improvements, monitoring, and reporting.

Private litigation: While this is a Title II rule (DOJ enforcement), courts have allowed private lawsuits for government web accessibility under Title II.

Common Failures in Government Portals

Forms and Applications

Government forms are frequently inaccessible:

Missing form labels: Input fields without associated labels leave users guessing what information to enter.

Poor error handling: Error messages that don't identify which field has the problem or how to fix it.

inaccessible date pickers: Calendar widgets that only work with mouse, excluding keyboard and screen reader users.

Required field identification: Required fields indicated only by color or asterisk without text explanation.

Multi-step form confusion: Complex applications without clear progress indication or navigation.

These failures block constituents from applying for permits, registering for services, or completing required government interactions.

Document Downloads (PDFs)

PDFs are government portals' biggest accessibility liability:

Scanned image PDFs: Documents scanned as images with no text layer—completely inaccessible to screen readers.

Missing tags and structure: PDFs without proper heading structure, reading order, or tagged elements.

Inaccessible forms: PDF forms that can't be completed with assistive technologies.

Missing alt text: Images in PDFs without text alternatives.

According to research on government PDF accessibility, the vast majority of government PDFs fail basic accessibility requirements. Yet PDFs often contain critical information—applications, regulations, notices, and forms that constituents must access.

Payment Flows

Online payment systems present specific challenges:

Third-party payment processors: Many governments use external payment systems that weren't built with accessibility in mind.

Session timeouts: Payments that timeout before users with disabilities can complete transactions.

Inaccessible security features: CAPTCHA and multi-factor authentication that create barriers.

Receipt and confirmation issues: Transaction confirmations not accessible to screen readers.

When constituents can't pay taxes, fees, or fines online, they must use in-person alternatives—disproportionately burdening people with disabilities.

Maps and Geographic Information

Government mapping tools are notoriously inaccessible:

Mouse-only interfaces: Maps requiring mouse drag/zoom with no keyboard alternatives.

Missing text alternatives: Visual map information without text descriptions.

Inaccessible layer controls: Map filters and layers that keyboard users can't operate.

No alternatives: No text-based ways to find information shown only on maps.

Zoning information, polling locations, transit routes, and emergency information often exist only in inaccessible map formats.

Modernizing Legacy Systems Under Time Pressure

Prioritizing High-Impact Services

With limited time and resources, focus on what matters most:

Tier 1 (Critical): Services constituents must use and cannot accomplish otherwise. Tax payments, license renewals, permit applications, court filings.

Tier 2 (High value): Services with high usage or significant convenience benefit. Online scheduling, information requests, document downloads.

Tier 3 (Important): Services that enhance engagement. Public meeting videos, newsletter archives, community event information.

Tier 4 (Lower priority): Informational content, historical archives, rarely accessed pages.

Start with Tier 1. A constituent unable to renew their driver's license faces real harm; a constituent unable to read a historical newsletter does not.

Wrapping Legacy Systems

Complete replacement of legacy systems often isn't feasible before compliance deadlines. Wrapper strategies can help:

Accessible front-ends: Build accessible interface layers that interact with inaccessible backend systems. Users interact with the accessible layer; the backend handles data.

Alternative pathways: Where legacy systems can't be made accessible, provide alternative methods to complete the same transactions (phone, in-person, accessible PDF forms).

Phased modernization: Fix the most critical accessibility issues in legacy systems while planning replacement.

Vendor pressure: For vendor-provided systems, contractually require accessibility improvements with deadlines aligned to DOJ timelines.

Remediation Prioritization

Within each service, prioritize accessibility fixes:

Keyboard access: If users can't navigate with keyboard, nothing else matters. Fix keyboard traps and missing focus indicators first.

Form accessibility: Labels, error messages, and instructions enable completion of the actual transaction.

Document accessibility: For required documents, either remediate PDFs or provide accessible HTML alternatives.

Media alternatives: Captions for video, transcripts for audio.

Visual accessibility: Contrast, text sizing, clear structure.

Continuous Compliance with Automation

Using TestParty for Government Portal Monitoring

Government compliance requires ongoing monitoring, not just point-in-time assessment:

Domain-wide scanning: TestParty crawls entire government domains, identifying accessibility issues across hundreds or thousands of pages.

Scheduled monitoring: Regular automated scans catch regressions and new issues as content changes.

Vendor site scanning: Monitor accessibility of vendor-provided platforms and content you're responsible for under the rule.

PDF assessment: Identify inaccessible PDFs requiring remediation or alternative formats.

Compliance documentation: Generate reports documenting accessibility status for regulatory compliance evidence.

Monitoring Vendor Platforms

Governments are responsible for vendor content accessibility:

Pre-procurement scanning: Assess potential vendors' platform accessibility before contracting.

Ongoing monitoring: Continuously scan vendor-provided services for accessibility issues.

Contractual requirements: Include accessibility SLAs in vendor contracts with monitoring to verify compliance.

Issue escalation: When vendor platforms have accessibility issues, documented findings support remediation demands.

Evidence for Compliance

DOJ compliance may require demonstrating accessibility efforts:

Baseline assessments: Document current state before remediation begins.

Progress tracking: Track accessibility improvements over time with regular scans.

Remediation records: Maintain records of issues identified and fixes implemented.

Testing documentation: Document manual accessibility testing conducted.

Policy documentation: Accessibility policies, training records, and complaint procedures.

TestParty's historical reporting provides evidence of continuous accessibility monitoring and improvement.

Preparing for Compliance

Assessment Phase

Inventory digital properties: Catalog all web content, mobile apps, and digital services.

Prioritize by impact: Rank properties by constituent need and usage.

Baseline assessment: Conduct comprehensive accessibility assessment of priority properties using TestParty scanning plus manual evaluation of critical flows.

Gap analysis: Compare current state to WCAG 2.1 AA requirements.

Resource estimation: Estimate remediation effort for identified gaps.

Remediation Phase

Create remediation backlog: Convert assessment findings to tracked issues with owners.

Address high-priority first: Critical services and severe barriers take precedence.

Implement fixes: Remediate issues following WCAG guidance and TestParty recommendations.

Verify fixes: Re-test remediated issues to confirm resolution.

Document progress: Maintain records for compliance demonstration.

Sustainability Phase

Establish ongoing monitoring: Continuous TestParty scanning of all properties.

Implement accessibility in workflows: Accessibility requirements in procurement, development, and content processes.

Training: Staff training on accessibility requirements and practices.

Complaint handling: Accessible feedback mechanism and response process.

Regular reporting: Periodic accessibility status reporting to leadership.

Frequently Asked Questions

When must we comply with the DOJ web accessibility rule?

Compliance deadlines depend on population served. State and local government entities serving populations of 50,000 or more must comply by April 24, 2026. Entities serving populations under 50,000 have until April 26, 2027. Start remediation now—these deadlines approach quickly for complex government web properties.

Does the DOJ rule apply to vendor-provided platforms?

Yes, indirectly. The rule requires governments to ensure accessibility of web content they "provide or make available." If you use a vendor platform to deliver services, you're responsible for that platform's accessibility. This means either requiring vendor accessibility compliance contractually or providing accessible alternatives.

What about existing PDFs—must we remediate all of them?

Archived documents maintained only for historical reference may be excepted. However, PDFs currently used for government services or required for constituent transactions must be accessible. For large document repositories, prioritize documents by current use and importance. Consider accessible HTML alternatives for the most critical content.

Can we claim undue burden to avoid compliance?

The undue burden defense exists but is narrow. You must make a contemporaneous written determination that compliance would fundamentally alter services or create undue financial/administrative burden, document what specific aspects create the burden, and provide access through alternative means. Courts and DOJ scrutinize undue burden claims carefully.

What happens if we're not compliant by the deadline?

DOJ may investigate complaints, conduct compliance reviews, and pursue enforcement. This could result in settlement agreements requiring remediation with monitoring and reporting requirements. Private lawsuits are also possible. The reputational and legal costs of non-compliance typically exceed the investment required for compliance.

Conclusion – Build Trust by Making Services Truly Accessible

The DOJ web accessibility rule transforms government accessibility from aspiration to requirement. State and local governments have defined timelines to meet defined standards—WCAG 2.1 Level AA for web content and mobile applications.

Meeting these requirements means:

• Understanding scope: Knowing what content and applications the rule covers
• Prioritizing remediation: Focusing on high-impact services and critical barriers first
• Addressing legacy systems: Using wrapper strategies and alternatives where complete modernization isn't feasible
• Managing vendors: Ensuring third-party platforms meet accessibility requirements
• Monitoring continuously: Maintaining compliance through ongoing automated scanning
• Documenting compliance: Building evidence of accessibility efforts and status

Accessible government services aren't just about compliance—they're about ensuring every constituent can engage with their government. People with disabilities have the same right to access government services as anyone else. The DOJ rule makes that right enforceable.

Are you a public entity or government vendor preparing for DOJ's web rule? Book a demo with TestParty to see continuous compliance monitoring in action.

Related Articles:

• Automated WCAG 2.1 Testing: AI Implementation Guide 2025
• Your 90-Day Accessibility Turnaround Plan