The ADA Title II web accessibility deadline moved, but the work did not get smaller. For state and local governments, the Department of Justice has now set a specific technical target for web content and mobile apps: WCAG 2.1 Level AA. For many public entities, that means accessibility is no longer a vague best practice or a future procurement preference. It is a dated operational requirement with real implications for websites, forms, documents, portals, mobile apps, and vendor systems.
That matters for more than legal teams. Procurement groups need to know what accessibility evidence to request from vendors. Website managers need a realistic remediation backlog. Communications teams need publishing rules for PDFs, videos, public notices, and social content. IT leaders need to understand which issues require code changes, platform changes, content governance, or a new vendor conversation. Leadership needs a plan that can survive budget limits, election cycles, system dependencies, and daily service delivery.
The dates public sector teams should be tracking
As of May 31, 2026, the most important U.S. digital accessibility dates are no longer the original 2026 and 2027 dates many teams had on their calendars. In April 2026, DOJ issued an interim final rule extending the ADA Title II web and mobile app compliance dates by one year.
- State and local governments with a total population of 50,000 or more now have until April 26, 2027 to meet the Title II web and mobile app accessibility requirements.
- Public entities with a total population below 50,000, and special district governments, now have until April 26, 2028.
- Recipients of HHS funding with 15 or more employees now have until May 11, 2027 to meet Section 504 web and mobile accessibility requirements.
- HHS funding recipients with fewer than 15 employees now have until May 10, 2028.
- Federal agencies and many federal contractors still need to treat Section 508 as an active requirement, especially in procurement, website publishing, documents, and ICT delivery.
The extension should not be read as a reason to wait. DOJ also made clear that covered entities have ongoing obligations under Title II even before the new compliance dates arrive. A public service journey that cannot be completed by a resident using a keyboard, screen reader, captions, sufficient contrast, or accessible documents is still a service delivery problem today.
Why this is bigger than an accessibility scan
A scan can help find missing alt text, empty buttons, duplicate IDs, low contrast, missing form labels, and some structural problems. It cannot tell you whether a person can complete a benefits application, submit a permit, find an emergency update, understand a public meeting notice, renew a license, or use a vendor portal with assistive technology.
That is why government website accessibility compliance has to be managed like a product and operations effort, not a one-time report. The work needs inventory, triage, code remediation, content cleanup, document remediation, manual testing, assistive technology review, procurement governance, and a publishing model that prevents the same issues from returning.
For public sector teams, the highest-risk gaps often sit in the workflows people rely on most. Forms are unlabeled or time out without warning. PDFs are image-only or lack a logical reading order. Interactive maps require a mouse. Payment flows fail keyboard testing. Error messages are visual but not programmatic. Third-party systems claim accessibility without showing a current VPAT, accessibility conformance report, or remediation plan.
What should be in your accessibility inventory
The first useful question is not whether the homepage passes a scanner. The first useful question is what digital services the public actually depends on. That inventory should include more than the main website.
- Public websites, microsites, department pages, campaign pages, and landing pages.
- Authenticated portals for residents, employees, students, patients, applicants, vendors, or contractors.
- Mobile apps and responsive web apps connected to public services.
- Forms for applications, payments, complaints, permits, benefits, registration, and support.
- PDFs, Word files, spreadsheets, agendas, minutes, notices, reports, policies, and archived documents.
- Video, audio, captions, transcripts, embedded dashboards, maps, charts, and public data tools.
- Third-party platforms provided through contract, licensing, or other arrangements.
Once the inventory exists, teams can prioritize by public impact. A broken application flow should outrank a low-traffic archive page. A payment form should outrank a decorative landing page. A required PDF packet should outrank an old news release. Accessibility compliance is easier to defend and easier to fund when the work is tied to real services.
Procurement has to be part of the accessibility plan
Procurement teams are central to ADA Title II, Section 508, and public sector accessibility compliance because so many digital services depend on systems the public entity did not build. A website team can fix the public CMS and still fail if the permit platform, agenda software, payment provider, chatbot, learning system, or document workflow is inaccessible.
A strong procurement process should ask vendors for specific accessibility evidence, not broad claims. That can include a recent accessibility conformance report, the WCAG version tested, known exceptions, open remediation items, testing methods, assistive technology coverage, support timelines, and contract language that gives the public entity a path when issues are found.
This is where many organizations lose time. They discover accessibility problems after a platform is live, after staff have been trained, after residents have adopted the workflow, and after replacement is politically or financially hard. Accessibility belongs in selection, implementation, acceptance testing, renewal, and vendor management.
WCAG 2.1 AA is the floor. WCAG 2.2 is the planning signal
The DOJ Title II rule and the HHS Section 504 rule point to WCAG 2.1 Level AA. That is the compliance baseline public sector teams should be able to explain, test, and document. But WCAG 2.2 is the current W3C recommendation, and many teams are already using it as a planning signal to reduce future rework.
That does not mean every organization should pause until the legal standard changes. It means a smart audit can separate the required WCAG 2.1 AA findings from the WCAG 2.2 delta. Pure Path uses that pattern because it gives leadership a clean compliance baseline and a practical modernization path.
A practical 90-day accessibility plan
A public entity does not need to fix everything in the first 90 days. It does need to stop guessing. The goal of the first phase is to create an accurate picture of risk, fix the highest-impact barriers, and build a workflow that can continue.
- Days 1-15: Inventory websites, mobile apps, documents, forms, service journeys, analytics, ownership, vendors, and known complaints.
- Days 16-35: Run automated checks, manual keyboard testing, screen reader review, contrast checks, form validation review, mobile checks, and document triage on priority journeys.
- Days 36-55: Build a remediation backlog organized by severity, public impact, owner, system, and implementation effort.
- Days 56-75: Fix recurring code and template issues first so new pages, forms, and components do not keep reproducing the same barriers.
- Days 76-90: Put governance in place through publishing checklists, procurement language, acceptance testing, training, and leadership reporting.
This approach gives procurement, communications, IT, ADA coordinators, and leadership a shared operating model. It also makes accessibility work easier to fund because the plan is tied to service risk, not a vague list of technical violations.
What leadership should expect from a serious accessibility engagement
A serious accessibility engagement should produce more than a spreadsheet of defects. Leaders should expect a clear explanation of what was tested, what standard was used, what could not be tested, which issues block users, which systems are responsible, and what must happen next.
- An executive brief that explains risk without burying decision-makers in WCAG jargon.
- A technical audit that maps findings to WCAG 2.1 AA and flags relevant WCAG 2.2 considerations.
- A remediation backlog that engineering, content, procurement, and vendors can actually use.
- A document and PDF plan that separates high-use public files from low-risk archives.
- Vendor review notes for third-party systems and procurement renewals.
- A repeatable governance model for publishing, QA, release checks, and staff training.
How Pure Path helps public sector teams move
Pure Path is equipped for this work because accessibility is not isolated from the rest of digital delivery. We understand websites, front-end engineering, forms, documents, CMS behavior, analytics, design systems, cloud environments, vendor integrations, and the operational constraints that public sector teams live with.
That matters because the fix is rarely just a checklist. Some accessibility barriers are content problems. Some are component problems. Some are vendor problems. Some are procurement problems. Some are workflow problems. A good partner can tell the difference and help the organization move in the right order.
The deadline moved. The work did not.
The one-year extension gives public entities more room to plan, but it does not make accessibility optional. It gives teams time to do the work correctly: inventory the real surface area, test the paths people use, fix the issues that block access, bring vendors into the process, and leave behind a governance model that lasts.
For procurement teams, website managers, directors, CIOs, ADA coordinators, and agency leadership, the right move is to turn the deadline into an operating plan now. By the time April 26, 2027 arrives, accessibility should not be a scramble. It should be part of how the organization ships public services.
Pure Path can help public sector teams get there with accessibility audits, WCAG 2.1 AA remediation, document and PDF triage, vendor review, procurement support, and governance that fits the way real organizations work.