DOJ’s 2016 web accessibility questions asked how to score compliance; the 2024 rule declined to set a score
On July 29, 2016, the Justice Department extended comments on 123 questions about state and local government websites, one of them how to measure compliance. The 2024 rule set no percentage. In our reading, user-task evidence became the record that counts.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
On July 29, 2016, the Justice Department extended comments on 123 questions about state and local government websites, one of them how to measure compliance. The 2024 rule set no percentage. In our reading, user-task evidence became the record that counts.
- The week The extension notice described the scale of the request.
- The standard: from WCAG 2.0 to WCAG 2.1 The May 2016 notice explained the choice.
- The scope: content, channels and exceptions That definition covered more than text.
- The measure: from percentages to minimal impact The 2016 notice explained why it raised the question.
- The timing: proposed, set and moved The notice recorded what commenters to the 2010 advance notice had said.
- How the outcome reached different governments A state with dozens of agencies faces scale and decentralization.
- Objections, in order DOJ heard this concern and answered that full conformance is the definitive path. [4] The objection has force for large sites that will always have some errors.
- Checks an agency digital or ADA lead could run List the top tasks residents complete online and in apps: apply, pay, renew, register, report, look up.
- With hindsight The 2016 rulemaking itself did not survive.
The week
On Friday, July 29, 2016, the Federal Register published a short notice from the Justice Department’s Civil Rights Division. [2] It extended the comment period on a supplemental advance notice of proposed rulemaking about the websites of state and local governments. [2] The notice was dated July 25, 2016. [2]
The underlying document had appeared on May 9, 2016. [2] It addressed the potential application of technical accessibility requirements to the websites of entities covered by title II of the Americans with Disabilities Act, meaning state and local governments. [2] Comments had been due August 8, 2016. [2] The extension moved the deadline by 60 days, to October 7, 2016. [2]
The extension notice described the scale of the request. It said the supplemental notice asked 123 multipart questions on a wide range of complex issues, including potential technical requirements and the costs and benefits of a title II web rule. [2] It said three commenters had asked for a 90-day extension, citing the complexity of the issues, the number of questions and the amount of data requested. [2]
The Department granted 60 days, not 90. [2] It explained why it did not want more delay. It said a title II web rule was likely to help create an infrastructure for web accessibility that would be important to its later title III proposal for public accommodations. [2] Further delay in the title II rulemaking, it said, would hinder the title III timeline as well. [2]
The May notice had its own history. It recounted that DOJ’s 1991 title II and title III rules did not mention the web, which was then in its infancy. [1] In 2003 the Department published guidance on accessible state and local government websites. [1] In September 2010, guidance accompanying the revised title II rule said title II covers public entities’ websites and that the Department enforced that coverage case by case. [1]
On July 26, 2010, the Department had published an advance notice covering both government and business websites. [1] The May 2016 notice said the Department received approximately 400 public comments on it and later decided to proceed with title II first. [1]
The supplemental notice set out what the Department was considering. It said the Department was considering proposing WCAG 2.0 Level AA, the World Wide Web Consortium’s guidelines, as the standard for title II websites and web content. [1] It described WCAG 2.0 as published in December 2008 and approved as an international standard in October 2012. [1]
It floated a timeline. The text under consideration would require compliance two years after publication of a final rule, except for live-audio captioning, unless the entity could show fundamental alteration or undue burdens. [1] It asked whether small public entities, those with a population of 50,000 or less, should get an additional year, three in total. [1] It asked whether very small entities or special district governments should meet only Level A. [1]
It considered exceptions. The Department listed four categories under consideration: archived web content, certain preexisting conventional electronic documents, third-party content linked from a government site, and certain content posted by third parties. [1] It also discussed password-protected content of public educational institutions. [1]
And it asked about measurement. Question 52 asked how compliance with WCAG 2.0 Level AA should be assessed or measured, particularly for minor or temporary noncompliance. [1] It asked whether the Department should consider percentages of content that need to be accessible, and whether there is a minimum threshold of acceptable noncompliance for complaints or enforcement. [1]
The July 2016 extension was a procedural notice. Its importance is in what it kept open: 60 more days for answers to 123 questions about how state and local government websites should be made accessible. [2] Of those questions, one asked whether the compliance model DOJ used for buildings would work for the web. [1]
Question 52 asked how compliance should be measured. [1] DOJ said its usual compliance model, under which a facility must meet the standards 100 percent of the time with few limitations, might not work well for the web. [1] It asked whether a percentage of accessible content, or a threshold of acceptable noncompliance, would be better. [1]
Our argument is that the answer DOJ gave in 2024 was no score at all. The final rule considered and rejected a numerical percentage, a policy-based approach and an organizational maturity approach. [4] Instead it adopted a narrow defense under which a government that is not in full conformance must demonstrate that the gap has only a minimal impact on access. [4] [7] In our reading, that made evidence of what users can actually do the record that counts.
We take the question in four parts:
- The standard: what technical benchmark DOJ proposed in 2016 and adopted in 2024.
- The scope: which content and which channels the rule reaches, and what it excepts.
- The measure: how DOJ moved from asking about percentages to adopting a minimal-impact defense.
- The timing: how compliance dates were proposed, set and then moved.
The parts do not overlap. The first is the benchmark, the second the boundary, the third the test of compliance and the fourth the clock. After them we look at how the outcome reached different governments, take the objections in order, and end with checks an agency’s digital, IT or ADA lead could run.
The standard: from WCAG 2.0 to WCAG 2.1
Why DOJ looked to WCAG
The May 2016 notice explained the choice. It said the 2010 advance notice had considered three options: WCAG 2.0, the federal section 508 standards and general performance-based standards. [1] DOJ said it was considering WCAG 2.0 Level AA. [1]
It gave reasons. It said WCAG 2.0 had become the internationally recognized benchmark for web accessibility. [1] It said several countries and some states used it, while other states based their standards on section 508, which was then based on the older WCAG 1.0. [1] It said WCAG 2.0 was designed to be technology neutral and that its success criteria are testable. [1]
Testable criteria and why they matter
The notice quoted WCAG’s own purpose for its testable criteria. It said they allow WCAG 2.0 to be used where requirements and conformance testing are necessary, such as in design specification, purchasing, regulation and contractual agreements. [1]
That sentence foreshadowed the problem question 52 raised. A standard made of testable criteria invites counting. A site has some number of pages, each page some number of elements, each element passing or failing each criterion. A percentage seems natural. DOJ’s later rejection of that approach is what makes the 2024 rule distinctive. [4]
States that started from section 508
The 2016 notice described a split among states. It said some states, including Alaska, Georgia, Hawaii and Minnesota, used WCAG 2.0 as their web standard. [1] It said others, such as California, Florida, Illinois, Maryland, New York and Texas, based their standards on the section 508 standards, then based on WCAG 1.0. [1]
For a state on the second path, the 2016 proposal implied a change of benchmark as well as of enforcement. In our reading, the agencies of such a state would have had to retrain developers and re-test content against a newer standard. The 2024 rule’s choice of WCAG 2.1 moved the benchmark again, for every state. [4]
The 2024 change to 2.1
The 2024 final rule adopted WCAG 2.1 Level AA. [4] The current regulation requires web content and mobile apps to comply with Level A and Level AA success criteria and conformance requirements in WCAG 2.1. [6]
The rule explained part of its reasoning. It said WCAG 2.1 Level AA requires, for example, that text be formatted so that it is easier to read when magnified, which matters for people with low vision who use magnification tools. [4] It said public entities were likely already familiar with WCAG 2.1, available since 2018 and built on WCAG 2.0. [4]
Live captions
The 2016 text under consideration excepted one Level AA criterion: Success Criterion 1.2.4, captions for live-audio content in synchronized media. [1] DOJ said some countries that adopted WCAG 2.0 Level AA, such as Canada and New Zealand, had exempted that requirement because of cost and immature technology. [1]
DOJ also said public entities were increasingly webcasting public hearings and committee meetings, and that people with disabilities needed real-time captions to participate more fully in civic life. [1] It asked whether to phase the requirement in. [1]
The 2024 rule did not carve the criterion out. It described Success Criterion 1.2.4 as requiring captions for live-audio content in synchronized media. [4] It said modern live captioning often can be created with the assistance of technology, such as conferencing software that integrates captioning with live meetings. [4] It declined to prescribe captioning requirements beyond WCAG 2.1 Level AA, such as a numerical accuracy standard. [4]
For a city council or a state board that streams meetings, that change is concrete. Live captions are part of the standard. A government that streams meetings without them has a gap on the day its compliance date arrives.
What did not change
The undue burden limitation carried through. The 2016 text under consideration would have excused compliance that would cause a fundamental alteration or undue financial and administrative burdens. [1] The current regulation contains the same limitation. [6]
The 2016 notice described how that limitation would work. The decision would have to be made by the head of the public entity or a designee, after considering all resources available, with a written statement of reasons. [1] The entity would still have to take other actions to ensure access to the maximum extent possible. [1] In our reading, that is a high bar, and a government should not plan on it as a routine exit.
The scope: content, channels and exceptions
Web content as DOJ defined it
The 2016 notice said DOJ was considering covering all web content public entities make available on their websites, whether viewed on desktop computers, notebooks, smartphones or other devices. [1] It offered a draft definition based on WCAG’s, covering information or sensory experience, including the encoding that defines structure, presentation and interactions. [1]
That definition covered more than text. It reached images, sounds, videos, controls and animations. [1] For a government, the inventory therefore includes every form, video, map and interactive tool on its sites.
Mobile apps
In 2016, mobile apps were a question. DOJ said its proposal under consideration would generally not cover software, but asked whether it should address mobile apps because public entities were turning to them. [1] It gave examples: apps for reporting graffiti or streetlight outages, and transit apps showing nearby stops and arrival times. [1]
By 2024 the answer was yes. The current regulation requires that mobile apps a public entity provides or makes available be readily accessible and usable, and meet WCAG 2.1 Level AA. [6] The 2024 rule described public entities using apps for services from traffic information to trash pickup scheduling to vaccination appointments. [4]
Social media
The 2024 rule addressed public entities’ use of social media platforms in a separate discussion. [4] Its exception covers a public entity’s social media posts made before the entity’s compliance date. [4] Posts after that date are not excepted. [4]
For a communications office, that means accessible posting practices, such as image descriptions and captioned video, become part of the compliance program from the compliance date forward. The platform’s own interface is the platform’s; the entity’s posts are the entity’s. That division is our reading of the exception’s wording.
Content provided through others
The current regulation covers web content and mobile apps a public entity provides or makes available directly or through contractual, licensing or other arrangements. [6] In our reading, that phrase reaches the payment portal run by a vendor, the permit system licensed from a software company and the app built by a contractor.
That is where scope meets procurement. A government that buys digital services without accessibility terms has bought a compliance gap. The rule does not tell agencies how to write contracts; it makes the content theirs regardless of who built it. [6]
Exceptions considered and adopted
The 2016 notice considered four categories of exceptions. [1] It said DOJ was concerned that public entities would need considerable resources to make large quantities of historic information accessible retroactively. [1] It noted commenters who said outdated documents were sometimes hundreds of pages long and scanned images. [1]
The 2024 rule adopted five exceptions. The first two cover archived web content and preexisting conventional electronic documents, unless those documents are used to apply for, access or participate in services. [4] The other three cover third-party content not posted under an arrangement with the entity, individualized password-protected documents, and preexisting social media posts. [4]
Two 2016 ideas did not survive. The 2024 rule did not include an exception for linked third-party content, which it said would have been redundant and could have caused confusion. [4] It also did not include an exception for password-protected course content in schools, which had been proposed in DOJ’s 2023 proposal. [4]
Conforming alternate versions
The 2016 notice addressed separate accessible versions of pages. [1] DOJ said it was concerned WCAG 2.0 could be read to permit two separate websites, one for people with disabilities and one for everyone else, even when unnecessary. [1] It considered allowing alternate versions only where technical or legal limitations prevent direct accessibility, or to provide access to conventional electronic documents. [1]
The 2024 rule kept the first limit. It said conforming alternate versions are permissible only when it is not possible to make web content directly accessible due to technical or legal limitations. [4] It explained its concern about a segregated approach and the difficulty of keeping two versions up to date. [4]
The 2024 rule also added a different flexibility. Under section 35.203, an entity may show that other designs, methods or techniques provide substantially equivalent or greater accessibility and usability than WCAG 2.1 Level AA. [4] The 2016 notice had discussed equivalent facilitation under its own heading. [1] In our reading, both the alternate-version rule and the equivalent-facilitation rule demand the same thing as the minimal-impact defense: evidence about what users experience.
Court and agency filings
The 2016 notice considered a specific problem for courts. It said courts and administrative agencies can receive vast amounts of filings from third parties, with exhibits such as maps or drawings that cannot easily be made accessible. [1] DOJ was considering placing such filings within the exception for third-party content. [1]
The 2024 rule’s third-party exception covers content posted by a third party unless the third party posts it under contractual, licensing or other arrangements with the entity. [4] How that applies to a particular court’s electronic filing system is a question for that court’s counsel. In our reading, the 2016 discussion shows DOJ understood court records as a distinct case from the start.
Dates as the boundary
Two of the 2024 exceptions turn on timing. Preexisting documents and preexisting social media posts are excepted if they were available or posted before the entity’s compliance date. [4] In our reading, that makes the compliance date a content-management boundary as well as an enforcement one. Every document after it must conform; documents before it are excepted unless used for current services.
The measure: from percentages to minimal impact
What DOJ asked in 2016
The 2016 notice explained why it raised the question. DOJ said the dynamic and interconnected nature of websites, and the large and varied amount of content on them, might make the building model a poor fit. [1] Under that model, facilities must be fully compliant at all times, subject to few limitations. [1]
Question 52 then asked four things. [1] It asked how compliance should be assessed or measured, particularly for minor or temporary noncompliance, and whether DOJ should consider percentages of content that must be accessible. [1] It asked whether there is an acceptable minimum threshold of noncompliance for complaints or enforcement, and whether some errors may not be significant barriers. [1]
What DOJ considered in 2024
The 2024 rule listed the alternatives it weighed. They included allowing isolated or temporary interruptions, requiring a numerical percentage of conformance, allowing entities to show compliance by following specified accessibility policies and practices, and allowing them to show organizational maturity. [4]
On percentages, DOJ’s answer was concern about users. It said even a very small share of nonconforming content could block an individual from a service, and that a single error could prevent someone from submitting an application for public benefits. [4] It said commenters agreed that percentages would be difficult to implement because they would be challenging to calculate. [4] It said it received a very small number of comments advocating a percentage approach, all from state and local government entities. [4]
On policies, DOJ said it had considered letting an entity show compliance by establishing and following policies for accessibility feedback, testing and remediation. [4] It described commenters’ disagreement over what policies should be required. [4] It declined that approach because, given the wide range of policies and practices commenters proposed, it found no sufficient rationale for adopting any specific set in a generally applicable regulation. [4] It said many of the suggested policies would require it to dictate particular details of public entities’ day-to-day operations. [4]
On maturity, DOJ said conformance testing evaluates a site at a point in time, while organizational maturity evaluates whether an entity has the infrastructure to produce accessible content consistently. [4] It declined that approach too. [4]
What DOJ adopted
The current regulation, section 35.205, says an entity not in full compliance will be deemed compliant in a limited circumstance. [7] The entity must demonstrate that the noncompliance has such a minimal impact on access that it would not affect what people with disabilities can do. [7] They must be able to access the same information, engage in the same interactions, conduct the same transactions and otherwise participate in the same services. [7]
The manner matters as much as the outcome. The use must provide substantially equivalent timeliness, privacy, independence and ease of use. [7] The 2024 rule gave an example of a person with a manual dexterity disability renewing a professional license online. [4] If that person takes significantly longer, needs help or endures a much more cumbersome process, the defense would not apply. [4]
Who carries the burden
The 2024 rule was explicit. It said the burden of demonstrating that section 35.205 applies is on the public entity. [4] It said a public entity must provide evidence that all of the criteria are satisfied. [4]
It said what would not be enough. Showing only that the entity received no complaints would not suffice, nor would pointing to a few individuals with disabilities who were unaffected. [4] The entity must show that the nonconformance would not affect people whose disabilities are pertinent to it. [4]
The rule also set expectations about frequency. DOJ said section 35.205 is intended to apply in rare circumstances and will require detailed analysis of each alleged instance. [4] It said full conformance to WCAG 2.1 Level AA is the only definitive way to guarantee compliance. [4]
What the defense does not do
The defense does not create a grace period. DOJ said it is not a blanket justification for avoiding conformance from the outset. [4] It said it does not expect or intend that section 35.205 will excuse most nonconformance. [4] It also said the provision does not alter existing enforcement: individuals can still file complaints and agencies can still investigate. [4]
Some commenters asked DOJ to add a notice-and-cure provision to help protect small entities from liability, and DOJ said it did not believe that approach was appropriate. [4] In our reading, that choice keeps the burden of finding problems on the government, not on residents who encounter them.
Why that makes task evidence the record
In our reading, the structure of section 35.205 points to a particular kind of evidence. A percentage would have called for an automated scan. A policy approach would have called for a policy manual. The minimal-impact defense calls for proof about tasks: whether a person using assistive technology can find the information, complete the form and finish the payment as quickly, privately and independently as anyone else. [7]
That is evidence a government can only produce by testing tasks, ideally with people who use assistive technology. Automated scans remain useful for finding failures. They cannot show that a failure has minimal impact, because impact is about the person, not the page.
Building an evidence program
An evidence program for the defense would have a few parts. In our reading, it starts with a list of the tasks that matter, tested with a defined set of assistive technologies: screen readers, magnification, voice control and keyboard-only use. Each test would record whether the task was completed, how long it took, whether help was needed and whether the tester had to share personal information with anyone.
Those four records map to the four qualities section 35.205 names: timeliness, privacy, independence and ease of use. [7] A government that records them for each task, on each release, has the material to show minimal impact if it ever needs to. One that records only automated scan scores does not.
The program would also run on change. Sites and apps are updated constantly; a task that passed last quarter may fail after a vendor release. In our reading, testing tied to releases, rather than annual audits alone, is what keeps the evidence current. The rule does not prescribe this method; it is our inference from the burden it places on the entity. [4]
The building analogy revisited
DOJ’s 2016 concern was that the 100-percent model for buildings might not suit the web. [1] The 2024 rule kept full conformance as the requirement and added a narrow defense. [4] It also noted that its title II regulation already recognizes that mechanical devices will sometimes fail, in the context of isolated or temporary interruptions. [4]
In our reading, DOJ kept the building model’s demand for full conformance. It added a narrow tolerance for real-world failure, available only where the entity can prove the failure did not matter to users.
The timing: proposed, set and moved
The 2016 proposal
The 2016 text under consideration would have required compliance two years after a final rule. [1] Question 3 asked whether that struck the right balance and whether DOJ should consider phasing, with frequently used or necessary pages first. [1] Question 4 asked for data on whether there would be a shortage of professionals proficient in web accessibility. [1]
The notice recorded what commenters to the 2010 advance notice had said. Proposals ranged from compliance on publication to a five-year window, with no consensus. [1] Commenters representing public entities cited budgets and staffing, and some said they lacked qualified personnel. [1]
The 2024 dates
The 2024 rule set two tiers. Public entities with a population of 50,000 or more, other than special district governments, were to comply beginning April 24, 2026. [4] Entities under 50,000 and special district governments were to comply beginning April 26, 2027. [4] The tiers drew the line at a population of 50,000, the figure the 2016 notice had used to describe small public entities. [1] [4]
The 2026 extension
On April 20, 2026, DOJ published an interim final rule extending both dates. [5] The date for entities of 50,000 or more moved from April 24, 2026, to April 26, 2027. [5] The date for smaller entities and special districts moved from April 26, 2027, to April 26, 2028. [5] The rule took effect April 20, 2026, with comments due June 22, 2026. [5]
The current regulation reflects the new dates, as checked on November 16, 2026. [6] As checked on the same date, the current text still requires WCAG 2.1 Level AA and still contains the minimal-impact defense. [6] [7]
The workforce question
The 2016 notice asked for data on whether there would be a shortage of professionals proficient in web accessibility. [1] It recorded commenters’ concerns that public entities lacked qualified personnel and would need time to train staff or hire professionals. [1]
That question has a management answer. A government cannot buy compliance once; it must build the capacity to keep content conforming as it changes. In our reading, the workforce question in 2016 was among the most practical DOJ asked, because the minimal-impact defense later assumed an entity able to test and document its own services.
Dates and budgets
A compliance date shapes a budget cycle. Governments plan spending in fiscal years, and a date that moves by a year can move work into a different budget. The 2026 extension moved both tiers to later dates. [5] In our reading, the risk is that a moved date reads as a reprieve, when the standard and the defense’s evidence burden are unchanged. [6] [7]
Phasing that did not happen
The 2016 question about phasing pages by importance did not become a rule. [1] The 2024 rule set one date per tier for all covered content and apps. [4] In our reading, a government can still phase its own work by task importance; the rule simply does not give later deadlines to lower-priority pages.
How the outcome reached different governments
A large state
A state with dozens of agencies faces scale and decentralization. Each agency may run its own sites and vendors. The rule makes all of them the state’s content. [6] Task-based evidence must be gathered agency by agency for the services residents use: benefits, licensing, taxes, courts and vehicle services.
A county
A county runs services residents need on deadlines: property tax payment, court records, elections information, health services. Each is a task the minimal-impact defense would test against timeliness. [7] A county that relies on a vendor’s portal for tax payment would need the vendor’s testing evidence as well as its own.
Counties also publish large numbers of documents: agendas, minutes, budgets and notices. The preexisting-document exception helps with the archive. [4] It does not help with the agenda posted next week, which must conform from the compliance date. A county clerk’s office is therefore part of the accessibility program alongside its web team.
A small town
A town under 50,000 has the later date. [6] It may have no web staff. The 2016 notice had recorded commenters’ concern that small entities may lack a dedicated webmaster and use templates that may not be accessible. [1] For such a town, the template and its vendor are the program.
A special district
Special district governments share the later date regardless of size. [6] The 2016 notice had defined special districts and asked whether they should meet only Level A. [1] The final rule applied Level AA to them as to everyone else. [6]
A public university
A public university is a title II entity. The 2016 notice discussed an exception for password-protected course content of public educational institutions. [1] The 2024 rule did not adopt the course content exception that had been proposed in 2023. [4] In our reading, that brings learning management content within the rule’s reach, subject to the remaining exceptions.
A state court system
Courts are title II entities with large volumes of documents filed by others. The 2016 notice treated judicial filings as a special case. [1] Court systems would need to separate their own content, such as forms, calendars and payment portals, which falls under the standard, from third-party filings, whose status depends on the exception’s terms. [4]
A transit agency
A transit agency’s app showing arrival times was one of the 2016 notice’s own examples. [1] Under the current regulation, that app must meet WCAG 2.1 Level AA. [6] Real-time information is a timeliness question: a rider who learns about a bus later than others has not had substantially equivalent timeliness. [7]
Objections, in order
1. Without a percentage, governments cannot know if they comply
DOJ heard this concern and answered that full conformance is the definitive path. [4] The objection has force for large sites that will always have some errors. The minimal-impact defense is the rule’s response, and it requires evidence, not a number. [7]
2. Testing with users is too expensive
Task-based testing costs more than automated scans. But the 2024 rule said that an absence of complaints, or a few unaffected users, would not prove minimal impact. [4] A government relying on the defense would need stronger evidence. The cost of producing it is part of the cost of relying on it.
3. Vendors control the content
The rule assigns the content to the government whatever the arrangement. [6] That shifts the problem to procurement and contract management. It does not remove it.
4. The delay shows the rule will change
The 2026 Unified Agenda says DOJ is considering whether to extend deadlines and then propose changes that could make some provisions less burdensome. [8] That is a real signal. But the current regulation, as checked on November 16, 2026, still requires WCAG 2.1 Level AA by fixed dates. [6] A plan that waits for changes that have not been proposed bets on an outcome no document yet describes.
5. Title II already required access before any rule
DOJ said in 2010 and in 2016 that title II covers public entities’ websites. [1] The rule added a technical standard and dates; the underlying duty was older. That cuts against waiting: the obligation to provide equal access did not begin with the rule.
6. Old documents will swamp the program
The exceptions for archived content and preexisting documents address this. [4] Their limits matter: a preexisting document used to apply for or access a current service is not excepted. [4] An inventory that separates live forms from archives makes the workload visible.
7. Automated scanning is enough
Automated tools can detect some WCAG failures quickly and cheaply. They cannot show whether a person using a screen reader completed a benefits application with substantially equivalent timeliness and independence. [7] Under a percentage rule, scans might have sufficed. Under the rule DOJ adopted, they are a starting point. [4]
8. Residents can call instead
The 2016 notice recalled DOJ’s 2003 guidance, which said governments might meet title II obligations through an alternative such as a staffed telephone line. [1] The same guidance said such alternatives were unlikely to provide an equal degree of access in hours and range of options. [1] DOJ said in 2016 that this was even more true as websites had grown in information and complexity. [1] In our reading, the 2024 rule leaves no room for a phone line to substitute for conforming web content, because its requirement attaches to the content itself. [6]
Checks an agency digital or ADA lead could run
Task list
List the top tasks residents complete online and in apps: apply, pay, renew, register, report, look up. For each, name the system and the owner.
Task testing
Test each task with assistive technology, and where possible with users who rely on it. Record time taken, help needed, any personal information shared with a helper, and failures. Those are the dimensions section 35.205 names. [7]
Vendor inventory
List every vendor-provided site, portal and app, with the contract and its accessibility terms. The rule reaches content provided through contractual, licensing or other arrangements. [6]
Document inventory
Separate documents used for current services from archives. Date each one. Preexisting documents used to apply for or participate in services are not excepted. [4]
Remediation log
Keep a dated log of each defect found, its effect on tasks and its fix. If the entity ever needs the minimal-impact defense, this log is where its evidence starts.
Live captions
List every public meeting the entity streams and confirm live captions are provided. The 2024 rule treats live captions as part of WCAG 2.1 Level AA. [4]
Alternate versions
Find every separate text-only or accessible version of a page. Confirm each exists because of a technical or legal limitation, as section 35.202 requires, and that it stays current. [4]
Agenda watch
Check the Unified Agenda and the Federal Register for DOJ’s next action under RIN 1190-AA82. [8]
With hindsight
The 2016 rulemaking itself did not survive. The extension notice of July 2016 had tied the title II rule to a later title III rule for businesses. [2] DOJ withdrew both rulemakings in 2017. On December 26, 2017, DOJ formally withdrew four advance notices, including the title II web accessibility rulemaking under RIN 1190-AA65 and its May 2016 supplemental notice. [3] DOJ said it was evaluating whether regulations on the accessibility of web information and services were necessary and appropriate. [3]
The withdrawal notice said DOJ would continue to assess whether specific technical standards were necessary to help covered entities comply with the ADA. [3] It did not say title II stopped covering websites. [3]
The withdrawal also stated that DOJ had not published any rulemaking document on title III web accessibility since the 2010 advance notice. [3] The title II rule that came later stood alone.
DOJ returned to the subject later. The 2024 final rule said DOJ received more than 200 public comments on the 2016 supplemental notice. [4] It said DOJ published a proposed rule on August 4, 2023, which included more than 60 questions and drew approximately 345 comments. [4]
The final rule was published April 24, 2024, and took effect June 24, 2024. [4] It adopted WCAG 2.1 Level AA for web content and mobile apps, five exceptions and the minimal-impact defense. [4] It set compliance dates of April 24, 2026, and April 26, 2027. [4]
Those dates did not hold. The April 20, 2026 interim final rule moved them to April 26, 2027, and April 26, 2028. [5] As checked on November 16, 2026, the current regulation shows the later dates. [6]
More change may come. The 2026 Unified Agenda lists the rulemaking under RIN 1190-AA82 at the Final Rule Stage. [8] Its abstract says DOJ is considering whether to extend the deadlines and then publish a proposed rule to reconsider whether some provisions could be made less burdensome. [8] Its timetable shows an interim final rule dated 07/00/2026 and a proposed rule To Be Determined. [8] Those are the agency’s projections, as checked on November 16, 2026.
What held up from 2016 was the standard family and the population line. DOJ proposed WCAG 2.0 Level AA and adopted its successor, WCAG 2.1 Level AA. [1] [4] It discussed a 50,000 population line for small entities and used it for the compliance tiers. [1] [4]
What changed was the answer to question 52. In 2016, DOJ asked whether a percentage or threshold could measure compliance. [1] In 2024, it rejected percentages and adopted a defense that turns on the experience of people with disabilities doing real tasks. [4] [7] As checked on November 16, 2026, section 35.205 is unchanged in the current text. [7]
The questions DOJ asked in 2016 about live captions, mobile apps and alternate versions were all answered in the 2024 text. [4] The 2026 interim final rule extended dates, and the current regulation still applies WCAG 2.1 Level AA to web content and apps, as checked on November 16, 2026. [5] [6]
What remains uncertain is everything the 2026 agenda entry leaves open. [8] A government that builds task-based testing and vendor accountability now will have evidence useful under any version of the rule, because the duty to provide equal access predates every version. [1]
Spotted an error? Tell us and we will check it and correct the article where needed.