Paper Boat Media / Public services & digital access

04 / 05

Public service.
Public access.

The updated ADA Title II deadlines and the operating plan that turns a date into completed work.

01Confirm the date
02Inventory the services
03Assign the repairs
04Verify access

01

The deadline moved. The work still needs an owner.

A resident needs to pay a bill, apply for a permit, register a child for a program or understand a public notice. The service exists online, but one part of the process does not work with the technology they use. The problem may sit in a city page, an old document, a department’s form or a vendor platform bought several years ago.

For a public organization, website accessibility reaches well beyond the communications department. It involves the people who publish information, buy software, manage records, deliver services and respond when someone needs help.

The ADA Title II web rule requires covered state and local government web content and mobile apps to meet WCAG 2.1 Level AA, subject to the rule’s conditions and exceptions. In April 2026, DOJ extended the technical compliance dates to April 26, 2027 or April 26, 2028, depending on the entity. The current DOJ fact sheet explains the revised schedule.

The useful response is a coordinated implementation program with a confirmed deadline, an inventory, named owners and evidence that repairs work. This guide explains how I would organize that program. Legal counsel or the entity’s ADA lead should confirm applicability and any exception being relied upon.

02

Which date applies?

Use the entity classification and population rules, not the size of the website or the number of people on the web team. Record the basis for the decision so departments and vendors are working from the same date.

Entity category Revised technical compliance date Planning reference
State/local government with 50,000 or more people April 26, 2027 Confirm the applicable population measure.
State/local government with fewer than 50,000 people April 26, 2028 Document the entity and population used.
Special district government April 26, 2028 Confirm that the entity meets the rule’s classification.

Schools deserve particular care. A school district is not automatically a special district government under this rule. DOJ explains that city and county school districts use the relevant city or county population; independent school districts use the applicable Small Area Income and Poverty Estimates population estimate. Do not substitute enrollment or staff count. A department or library that is part of a larger government generally follows that government’s population. See the DOJ small entity guide.

Existing obligations concerning effective communication and equal access continue before these dates. The extension concerns the specific technical requirements. A resident facing a barrier today still needs an appropriate response.

03

What belongs in the inventory?

Start with the services residents use, then identify the systems that deliver them. A URL export is useful, but it will not explain the whole operating environment.

List the main website, department sites, microsites, web applications and mobile apps. Identify forms, payment services, registration systems, agendas, notices, reports, videos and documents. Include services delivered through contractual or licensing arrangements. The Title II rule addresses content provided through those arrangements; outsourcing is not a reason to omit it from the review.

For each item, record a business owner, a technical owner, the audience, the task supported and the person who can approve a change. Add the platform, vendor, contract renewal date and any known accessibility evidence.

The inventory becomes more useful when it distinguishes a shared template from unique content. A department may own hundreds of pages that share one layout, while a single permit application contains a complicated sequence of controls. Both need attention, but counting them as equivalent units obscures the effort.

Inventory field Why I would collect it
Public service or task Connects the asset to what a resident needs to do
Content and technical owners Identifies who can authorize and implement repairs
Platform or vendor Reveals shared dependencies and access limitations
Active use Helps distinguish current service material from historical records
Existing evidence Avoids losing prior audits, issue reports or vendor responses
Next action and date Turns the inventory into a working program

Do not require perfect data before making progress. Begin with essential services and expand the inventory systematically. Mark uncertainty honestly rather than filling a spreadsheet with confident guesses.

04

Treat documents as a publishing system.

Public websites accumulate documents because documents are how organizations work. Meeting packets, notices, applications, reports and instructions often begin in different departments using different software.

If the only intervention is to repair the current PDF collection, the next publishing cycle can recreate the same problems. I would examine the source templates and the people producing them.

Which documents are still used to obtain a service? Which should be web pages? Which are retained for historical reference? Which have an accessible source file? Which are scans? These questions help determine the work and the skills needed.

An exception may apply to certain older material, but age alone is not enough. The rule has defined categories and conditions. Do not assume that renaming a folder “archive” or moving a file off the main navigation changes its legal status.

For new documents, establish a practical publication route. Use structured source templates, assign review responsibility and check the exported result. Someone should confirm reading order, headings, tables, links and other relevant features rather than assuming the export button preserves everything correctly.

A department that publishes weekly should have a repeatable process. A specialist can address a difficult document, but the everyday workflow should make routine publication more reliable. Budget for training and template repair alongside the backlog.

05

Exceptions need a record and a reason.

The rule identifies limited exceptions involving archived content, certain preexisting documents, specified third-party content, certain individualized password-protected documents and preexisting social media posts. Each has conditions. Content used for current access to a service may be treated differently from material retained only for reference.

I would maintain an exception register rather than leaving these decisions in email. Record the item, the category being considered, the factual basis, the reviewer and what happens if someone requests accessible information. Have the responsible legal or compliance lead confirm the interpretation.

The register is also a maintenance tool. If archived content is revised or repurposed, the earlier reasoning may no longer apply. If a previously historical document becomes part of an active application process, the team needs to revisit it.

Exceptions should help the organization apply the rule accurately. They should not become a strategy for hiding difficult work. A resident does not benefit from a technically clever filing arrangement that leaves an essential instruction unusable.

06

Procurement can prevent the next backlog.

Accessibility problems are often purchased before they are published. A department selects a registration platform, payment tool or document system, and the web team discovers its limitations after the contract is signed.

I would bring accessibility questions into product selection. Ask for current evidence relevant to the version and configuration being purchased. If a vendor supplies an Accessibility Conformance Report, examine its scope, date, methods and unresolved findings. A report is useful evidence to evaluate, not a reason to skip testing the intended service.

Demonstrations should include actual tasks. Ask the vendor to show how a person completes registration using a keyboard, corrects an error and receives confirmation. Test the deployed configuration where feasible, because an accessible product can still be configured poorly.

Contracts should address responsibilities, issue reporting, repair expectations and changes over time. The exact terms belong with procurement and counsel. From an implementation perspective, the organization needs a route for escalating barriers and a plan when the vendor cannot resolve them promptly.

Track renewal dates. A platform due for renewal in three months presents a different decision from one with a long remaining term. That does not remove the need to address a barrier, but it affects the practical choices available.

07

Give the program a small, accountable team.

The most common organizational problem is a task that crosses departments without belonging to anyone. Communications can change copy but cannot alter the payment system. IT can contact the vendor but does not own the public service. Records staff manage files but may not control the original templates.

Assign an executive sponsor who can resolve competing priorities. Identify the ADA or compliance lead, the web or IT lead, procurement and the content owners for major services. Give the group a shared issue register and a regular decision meeting.

The meeting should resolve specific questions: who owns a repair, what dependency is blocking it, what help a resident needs now and what evidence will close the finding. It should not become a recurring presentation of the same percentage-complete chart.

Responsibility Practical output
Executive sponsor Decisions about resources and unresolved ownership
ADA/compliance lead and counsel Confirmed obligations and reviewed exception decisions
Web and IT team Technical inventory, implementation and release controls
Department content owners Accurate content, accessible source documents and publication practices
Procurement Vendor evidence, contractual responsibilities and escalation routes
Service staff Immediate assistance and feedback from affected residents

One person may hold several roles in a small entity. The responsibilities still need to be explicit. A small team benefits from fewer handoffs, but cannot rely on assumptions about who is watching the inbox.

08

Test a public service from beginning to end.

Consider an illustrative recreation registration process. A resident finds a class, checks eligibility, creates an account, selects a date, requests an accommodation, pays a fee and receives confirmation. The main website may control only the first two steps.

A useful review follows the whole sequence. It checks the information, navigation, account controls, errors, payment handoff and confirmation. It also examines what happens when the class is full or the resident needs to correct an entry.

Automated scanning can help identify recurring technical issues across many pages. Manual evaluation investigates interaction and context. W3C’s WCAG-EM methodology is a useful reference for defining and documenting an evaluation. The report should state the scope and methods rather than imply that an automated score covers every process.

Use an agreed test environment or controlled production procedure. Do not create real permits, charges or official submissions accidentally. Involve the service owner so the test follows the actual process and the team can distinguish a technical failure from an intentional business rule.

After repairs, repeat the original steps and check related behavior. A change to a shared date picker might affect several services. Testing only the page where the issue was first reported can leave the same component broken elsewhere.

09

A practical 90-day starting plan

This is an example of how to organize the first phase, not a promise that every entity can complete all remediation in ninety days. Large inventories and complex vendor systems can require a longer program.

Days 1–30: establish the facts and ownership.

Confirm the entity’s deadline and target requirements. Assemble the core team. Identify high-value public services, major vendors and the known document backlog. Review existing complaints and audits. Agree on how urgent access problems will reach someone able to help.

By the end of this phase, leadership should have a realistic inventory outline, a list of immediate barriers and clear owners. It should also know which facts remain unresolved and who is finding them.

Days 31–60: evaluate representative services and begin shared repairs.

Assess important journeys and shared components. Create reproducible repair tickets. Fix high-impact problems within the team’s control and raise vendor issues with clear evidence. Begin correcting source templates so new content does not add to the backlog.

Use findings to improve the budget. The initial inventory may reveal that document remediation needs a separate workstream or that one vendor dependency affects several departments. That is useful information, even when it complicates the original estimate.

Days 61–90: verify, expand and make the routine sustainable.

Retest completed work, review unresolved barriers and extend the assessment to the next group of services. Finalize publishing guidance and procurement requirements. Give leadership a report of verified repairs, remaining risks, dependencies and next decisions.

The program should now have a rhythm that can continue toward the applicable deadline and beyond. Accessibility will remain part of operating the services after the initial compliance project closes.

10

Measure progress in ways that inform decisions.

Page counts and scan scores can be useful, but they do not tell the whole story. A team can close many low-impact findings while the main application remains unusable.

I would track essential journeys reviewed, critical barriers unresolved, shared components repaired, vendor issues awaiting action, active documents remediated and new content passing the publication check. Include the age of open items and the next decision needed.

Report the scope of those measures. “All priority journeys retested” means something only when the priority journeys are named. “No critical issues” should identify the evaluation and the definition of critical used.

Keep a concise evidence record. It should be possible to explain which version was tested, when the repair was released and what the retest showed. That record helps new staff, vendors and leadership understand the program without reconstructing it from old conversations.

Questions & answers

Questions public organizations ask

Is the deadline still April 2026 for larger governments?

No. DOJ’s April 2026 extension moved the technical compliance date for entities with populations of at least 50,000 to April 26, 2027. Smaller entities and special district governments have an April 26, 2028 date under the revised schedule. Confirm your entity’s classification.

Are school districts automatically in the 2028 group?

No. DOJ distinguishes school districts from special district governments. The relevant population rules determine a school district’s date. Use the DOJ guidance rather than assuming that the word district means the same thing in both categories.

Does the extension mean we can wait to help someone?

No. Existing duties concerning effective communication, reasonable modifications and equal opportunity continue. Establish a way to address an individual’s access problem while the technical remediation program proceeds.

Is WCAG 2.2 required by this rule?

The rule specifies WCAG 2.1 Level AA. An organization can choose a broader 2.2 AA target for new work while documenting how it addresses the actual requirement. WCAG 3 remains a draft and should not be substituted as a current compliance standard.

Can a vendor's accessibility statement close our review?

It can provide useful information, but evaluate its scope and the behavior of the service you deploy. Request relevant evidence, test important tasks and keep unresolved issues assigned. A general statement is not the same as verification of your implementation.

Do we have to repair every historical file immediately?

The rule contains defined exceptions, but each requires a fact-specific review. Inventory active and historical material, confirm any exception with the appropriate lead and preserve a process for accessible information requests. Do not assume every old PDF qualifies.

Who should lead the project?

Use a designated program owner supported by leadership, the ADA/compliance function, IT, content owners and procurement. The exact structure can be small. What matters is that repair decisions, vendor issues and resident requests have clear routes to action.

Sources & scope

Sources and further reading

Reviewed October 20, 2026. This implementation guide is not legal advice. Confirm applicability and current requirements with the responsible legal or compliance lead.

Work with Rob

Turn the deadline into an operating plan.

If your organization has a deadline but no clear inventory, repair ownership or vendor plan, I can help organize the work and connect the website decisions to the public services they support.

Explore website accessibility consulting and how to prioritize repairs, or contact Rob Urban at 407-227-0741.

Scroll to Top