Know the revised dates and covered entity
On April 20, 2026 — four days before the original compliance deadline — the Department of Justice published an interim final rule extending Title II ADA web accessibility requirements for state and local governments. Large jurisdictions serving populations of 50,000 or more now have until April 26, 2027, to bring covered web content and mobile applications into conformance with WCAG 2.1 Level AA. Entities below 50,000 people and special district governments have an April 26, 2028 date.
The DOJ interim final rule frames the extension around implementation constraints. It reflects implementation concerns, but the extension alone does not quantify how many jurisdictions were unready.
The DOJ fact sheet explains scope and exceptions. Authentication does not automatically put a website outside the rule: an exception for certain secured individualized documents is not an exemption for the website itself.
Understand what the AI evidence does and does not show
The interim final rule discusses resource and staffing concerns, including correspondence warning that generative AI cannot reliably remediate STEM materials at scale without human oversight. The operational distinction matters: discovering a defect and fixing it are different tasks. An automated scan can help identify some barriers, while keyboard navigation, reading order, form instructions and assistive-technology behavior need human testing.
Remediation may involve captions, document structure, contrast, navigation and the service workflow itself. The rule also contains defined exceptions; agencies should evaluate whether particular archived material qualifies rather than assume every historical item has the same treatment. Accessibility planning needs both an inventory and a documented interpretation of what applies.
Existing duties still matter
The extension does not create a litigation-free period. Title II's underlying nondiscrimination and effective-communication obligations remain in force. Private plaintiffs and disability advocacy organizations can still file suit against state and local governments whose digital services are not meaningfully accessible, and the applicable obligations and remedies depend on the facts and governing law. States that interpret the one-year window as an opportunity to defer the problem rather than resolve it leave residents facing avoidable barriers and may leave existing obligations unmet.
Make accessibility testable in procurement
A procurement process can create a recurring accessibility backlog when it does not specify accessibility conformance requirements with sufficient precision to create enforceable vendor obligations. A statement that a vendor "shall comply with Section 508" or "shall support users with disabilities" is difficult to evaluate operationally without testing methods, review of an Accessibility Conformance Report (often prepared using a VPAT template), and acceptance criteria tied to the applicable standard. What gets purchased is what gets specified, so a document-only checkpoint can permit a system to pass without meaningful assistive-technology testing.
The corrective action is to equip procurement staff with technical review support and enforceable acceptance criteria, rather than assume a vendor declaration proves a usable service.
Build review capacity before acceptance
The one-year extension is worth something when states address the existing backlog and prevent new barriers through procurement. That means incorporating VPAT review into the vendor qualification process, requiring independent accessibility audits as a contract deliverable before final acceptance, and conditioning renewal and extension options on documented conformance rather than vendor self-attestation. It also means investing in accessibility program offices — actual teams with assistive technology expertise — alongside legal and program staff, so the review includes the technical depth needed to distinguish a conformant system from a documented one.
These are recommended ways to organize the work, not universal staffing or audit mandates. An agency may use an internal team, shared technical support or qualified external reviewers; it needs enough accountable technical judgment to evaluate the evidence and accept the service.
Use the remaining period deliberately
The window closes April 2027 for large jurisdictions. Whether a jurisdiction can finish its remediation depends on its inventory, resources and applicable exceptions. The remaining period should also be used to modernize the procurement and acceptance process so the next generation of state digital services is built correctly from the start. The choice states are making right now — in how they structure the next round of contracts, how they credential vendors, and how they define done — can help prevent new accessibility barriers from becoming the next remediation backlog. Plan procurement improvements alongside the staffing and remediation work your inventory identifies.
Make accessibility part of acceptance
- Inventory the complete service. Include websites, mobile apps, documents, authentication, payment flows and third-party components. Record ownership, usage and the applicable deadline.
- Prioritize essential resident journeys. Test applying, submitting evidence, receiving notices and correcting errors with keyboard and assistive technology. Include users with disabilities in evaluation.
- Turn conformance into acceptance evidence. Request the current Accessibility Conformance Report, independent test results, unresolved barriers and a remediation schedule. Confirm the report covers the version being purchased.
- Assign defect and exception decisions. Define who validates fixes, documents applicable exceptions and maintains an accessible path while remediation proceeds. Legal, accessibility and program staff should work together.
- Keep checking after launch. Re-test templates, content and vendor updates. A release that introduces a barrier should create an owned issue with a deadline and resident-impact priority.
What to measure
- Completion: can a resident finish the whole service using assistive technology?
- Defect aging: time to resolve barriers, separated by service importance and severity.
- Regression control: changes re-tested before release and recurring vendor defects escalated.
Accept the resident journey, including its failure path
Consider a hypothetical application that is easy to navigate until the resident must upload a supporting document. The upload fails, but the error is not announced to the person's assistive technology. A test that checks only the landing page or a completed form misses the point at which the service becomes unusable.
For acceptance, have qualified testers follow the complete journey under controlled conditions: sign in, find the service, enter information, attach a document, recover from a validation error and receive confirmation. Include the notices and instructions that tell the person what happens next. Record the product version, configuration, assistive technology and observed barrier so the supplier can reproduce the issue.
The following are recommended operating decisions, not additional statutory requirements:
- Define a release-blocking barrier. Program and accessibility staff should identify failures that prevent completion of an essential task and agree how they affect acceptance.
- Name the repair owner. A defect may sit in a vendor component, agency template or authored document. Route it to the party that can change it, with a person accountable for the end-to-end service.
- Validate the correction. Repeat the affected journey after the fix and check adjacent behavior. A ticket marked closed is not evidence that the resident can now finish.
- Document the interim route. When remediation is pending, determine an accessible way to obtain the service under applicable requirements. A generic telephone number is not proof that an equivalent, timely route exists.
Keep a vendor update from undoing the work
A one-time audit can establish evidence about a particular version and scope. It cannot show that a later form, document or component remains usable. Build accessibility checks into the change process and retain the test cases that revealed consequential failures.
A smaller agency may reasonably share specialist testing capacity rather than create a standalone office. A larger organization may need dedicated staff to manage frequent releases and many suppliers. The operating choice should reflect workload and access to expertise, with a named agency owner able to accept evidence and escalate unresolved barriers.
The next renewal discussion should address repeated defects, repair timeliness, version coverage and access to testing evidence. Use that record to decide whether continued remediation, a narrower deployment or replacement is justified within the agency's obligations. An extended deadline is useful only if it becomes a sequence of owned decisions and verified improvements.
Sources and further reading
- DOJ updated web-rule fact sheet — technical standard, dates and exceptions
- DOJ 2026 interim final rule — extension rationale and cited stakeholder comments
For Spartan X, accessibility belongs in the engineering and program-execution work that defines acceptance. Clear requirements and usable tests give agencies a stronger way to buy services residents can complete.
