In April 2024, the Department of Justice finalized a long-anticipated update to ADA Title II, formally clarifying that digital services provided by state and local governments must meet modern accessibility standards. For the first time, the rule sets explicit technical requirements and deadlines for websites, mobile apps, and online portals.
Digital accessibility is a core requirement of modern public service. In practical terms, that means it is no longer implied — it is defined and time-bound. State and local government agencies must ensure their websites, mobile apps, and digital tools conform to WCAG 2.1 Level AA by April 2026 or 2027.
Readiness isn’t about achieving perfection overnight; it’s about moving from reactive fixes to a proactive, managed strategy.
To help mitigate legal risk and ensure digital inclusion is built-in from the start, we recommend your agency follow these four steps to build a proactive procurement strategy.
Step 1: Audit your digital programs and services
The first step is identifying the digital systems that the public relies on to access programs, services, or activities. A defensible position starts with knowing exactly which services are in your scope so you can account for them.
- Inventory your full scope: Create a list of all public-facing platforms, including agency websites, mobile applications, and portals used to apply for benefits or pay fees.
- Identify essential services: Distinguish between required workflows (like filing a report or enrolling in a program) and purely informational content.
- Don't rely on "alternate access": Remember that providing a phone number or email address is not a substitute for an accessible digital experience. Under Title II, digital services must be accessible on equal terms.
- Use automated tools: Leverage tools like accessScanto get an immediate read on your public-facing pages and identify common accessibility gaps.
Step 2: Prioritize by public impact
Regulators focus on where barriers block people from completing essential tasks — not just where technical errors are easiest to find. You should sequence your work based on the consequences of an inaccessible service.
- Fix "service blockers" first: Prioritize remediation for pages that prevent a person from accessing essential services. If a user can't complete a task, that presents a higher risk than a minor formatting issue.
- Address high-risk channels: Focus on common friction points such as PDFs, mobile apps, and third-party systems. These "hidden" areas are often where accessibility most frequently breaks down.
- Sequence your work: Be ready to explain your logic—showing why certain high-impact services were addressed first helps prove you are acting in good faith.
Step 3: Formalize vendor and procurement rules
Government agencies remain legally responsible for accessibility, even when services are delivered through a third party. It is essential to stay involved with your contractors rather than assuming accessibility is handled elsewhere.
- Update your contracts: Ensure all new vendor agreements and renewals explicitly require conformance to WCAG 2.1 level AA.
- Verify vendor claims: Don't just collect an Accessibility Conformance Report (ACR/VPAT); review it to understand what the vendor controls versus what your agency needs to manage.
- Maintain oversight: Stay involved to ensure that third-party portals or tools provided to the public remain accessible and inclusive over time.
Step 4: Document your journey (keep the receipts)
Defensible progress is about being able to explain what you are doing—and showing that the work is actually happening. If a regulator reaches out, your documentation is your best defense.
- Maintain a remediation log: Record every audit, fix, and prioritization decision. Showing a schedule of upcoming improvements proves you are moving beyond one-time audits toward a sustained process.
- Publish an accessibility statement: Clearly state your agency’s commitment to inclusion and provide a clear way for the public to report barriers.
- Centralize management: Use a platform like accessFlow to provide your technical teams with a single source of truth for tracking and resolving code-based issues across departments.
What does defensible progress actually look like?
As the deadlines approach, many government entities, agencies, and organizations ask: how much progress is enough?
In practice, a government agency is generally in a defensible position when it can show that accessibility is not a one-time cleanup, but an ongoing part of how services are delivered.
You are in a strong position when:
- You know which digital services the public relies on most to access programs.
- You focus accessibility work on services where barriers block real-world access.
- You actively manage high-risk areas, including documents and third-party systems.
- You stay involved in vendor delivery instead of assuming the work is done elsewhere.
- You keep records that show decisions were made, issues were addressed, and progress continued over time.
Bridging the digital divide: How accessiBe helps public entities comply with Title II
Preparing for the April 2026 and 2027 deadlines is challenging. Digital services across state and local governments evolve constantly and are rarely managed by a single team. Accessibility responsibilities are often layered onto already complex IT, service delivery, and compliance priorities.
AI-driven automation for scale
Government websites and service portals change frequently — new announcements, updated forms, seasonal programs, and service alerts. Continuous monitoring helps identify accessibility issues early, providing consistent coverage without overwhelming internal teams.
Tools for technical teams
Agency developers and IT teams are rarely accessibility specialists. Developer-focused tools provide visibility into accessibility status across websites, portals, and digital services, along with practical guidance to support implementation and ongoing updates.
Expert support where judgment is required
Some digital assets — such as complex forms, legacy document libraries, and critical service workflows — require specialized review. Accessibility experts assist with document remediation, workflow evaluation, and remediation strategy where automation alone is not sufficient.
Activity is tracked and compiled into structured reports reflecting findings, actions taken, and progress over time — creating a documented record of oversight and measurable effort.
Because digital services continuously evolve, accessibility cannot be treated as a one-time project. Ongoing monitoring and reporting remain essential.
If your agency is preparing for the upcoming Title II deadlines, our accessibility specialists can review your current approach and help identify practical next steps. Book a call.
Frequently asked questions about government ADA Title II readiness
Q1. What are the official ADA Title II compliance deadlines for government agencies?
A1. Compliance deadlines are based on the population size served by the public entity. Large public entities (serving 50,000 or more people) must ensure their digital content conforms to required standards by April 24, 2026. Smaller entities (serving fewer than 50,000 people) and special district governments have until April 26, 2027, to meet the same requirements.
Q2. Which technical standard must our agency conform to?
A2. The Department of Justice (DOJ) has formally adopted Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the technical standard for ADA Title II compliance. This standard applies to your websites, mobile apps, and digital documents used to provide programs, services, and activities.
Q3. How should we prioritize remediation across thousands of public documents and pages?
A3. Agencies should prioritize based on "public impact." Focus first on "service blockers"—high-traffic workflows where a barrier would prevent a resident from accessing essential services, such as applying for benefits, paying taxes, or receiving emergency alerts. Remediation for these high-impact "hot zones" should take priority over purely informational or low-traffic content.
Q4. Is the agency responsible for the accessibility of third-party vendor systems?
A4. Yes. Public entities remain legally responsible for the accessibility of the tools they provide to the public, even if those services are hosted or managed by a third party. You must ensure that all new vendor agreements and renewals explicitly require conformance to WCAG 2.1 Level AA and verify their claims through regular oversight.
Q5. Can we provide a phone number as an "alternate access" route for inaccessible sites?
A5. No. Under the Title II rule, providing a phone number or email address is not a substitute for an accessible digital experience. Digital services must be accessible by default to ensure that people with disabilities have equal access to information and tasks on the same terms as everyone else.
Q6. What documentation is needed to show "defensible progress" to regulators?
A6. A defensible position is built on documentation that shows your progress is intentional, structured, and continuous. This includes maintaining a remediation log of audits and fixes, publishing a clear accessibility statement, and keeping records of how you prioritized high-impact services.
Q7. How can accessiBe help our agency reach Title II readiness?
A7. accessiBe delivers an end-to-end accessibility platform combining the best in AI automation, human expertise, and developer toolsto help agencies manage this transition. accessWidget provides a scalable layer of AI-powered remediation for decentralized agency websites, while accessFlow allows technical teams to audit and monitor code-level accessibility in complex portals. Additionally, accessiBe’s expert services provide professional remediation for complex PDF forms and manual audits to address high-risk public assets.
