The 2018 Section 508 refresh made WCAG the federal test and the first edit to old content the trigger
From January 18, 2018, federal agencies had to meet the revised Section 508 Standards, built on WCAG 2.0 Level AA. Unaltered legacy content was exempt, so the first change to an old page, form or system became the moment it had to conform.
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
From January 18, 2018, federal agencies had to meet the revised Section 508 Standards, built on WCAG 2.0 Level AA. Unaltered legacy content was exempt, so the first change to an old page, form or system became the moment it had to conform.
- The week Thursday, January 18, 2018, was the compliance date for the revised Section 508 Standards.
- The test: one external standard for content, documents and software The first part was the test itself.
- The scope: public content and nine kinds of internal communication The second part was what had to conform.
- The trigger: when the legacy safe harbor ended The third part was the safe harbor in E202.2.
- The purchase: standards ahead of the acquisition rules The fourth part was procurement.
- How this differed across agencies and their partners The four parts applied to every agency covered by Section 508.
- Objections, in order We take five objections, numbered in the order we address them.
- Checks a program director could run These checks follow from the four parts.
- With hindsight The standards themselves were corrected almost at once.
The week
Thursday, January 18, 2018, was the compliance date for the revised Section 508 Standards. Section 508 of the Rehabilitation Act requires federal agencies to make the information and communication technology they develop, procure, maintain or use accessible to people with disabilities. The United States Access Board writes the standards that give that duty its technical content.
The Board had published the revision in a final rule in the Federal Register on January 18, 2017. The rule took effect on March 20, 2017. Its dates section said compliance with the section 508-based standards was not required until January 18, 2018. The same rule revised the Board’s guidelines for telecommunications equipment under Section 255 of the Communications Act, which applied only once the Federal Communications Commission adopted them.
The rule replaced standards in force since 2000. The Board described those older standards as product-based, with requirements grouped by product type: software and operating systems, web content, telecommunications products, closed products, and computers. Commenters, it said, agreed with its approach of addressing accessibility through functionality rather than product types. The new standards were organized by function and by kind of technology, with a scoping chapter that said what had to conform.
The central technical change was to adopt the Web Content Accessibility Guidelines. Section E205.4 required electronic content to conform to Level A and Level AA success criteria and conformance requirements in WCAG 2.0, incorporated by reference. The same level applied to non-web documents, with four success criteria excepted. Section E207.2 applied WCAG 2.0 Level A and AA to software user interfaces and to the content of platforms and applications.
The rule also set out what content was covered. Public-facing content had to conform. Content that was not public facing had to conform when it was official agency business in one of nine categories. They were emergency notifications, decisions adjudicating an administrative claim, program or policy announcements, and notices of benefits, eligibility, employment opportunity or personnel action. They also included formal acknowledgments of receipt, surveys, templates and forms, educational and training materials, and intranet content designed as a web page.
A safe harbor covered existing technology. Section E202.2, titled Legacy ICT, covered any component or portion of existing ICT that complied with the earlier standard. If it had not been altered on or after January 18, 2018, it did not have to be modified to conform. The rule defined alteration as a change to existing ICT that affects interoperability, the user interface, or access to information or data. It defined existing ICT as ICT procured, maintained or used on or before January 18, 2018.
The rule kept and refined two other exceptions. Where conformance would impose an undue burden or a fundamental alteration, an agency had to conform to the extent it could, document the basis in writing and provide an alternative means of access. Where conforming ICT was not commercially available, the agency had to procure the product that best met the standards and document the market research behind that judgment.
The rule also said how it would reach purchasing. It said the Board’s 508 Standards were not self-enforcing for procurement. They would take legal effect for procurement when adopted by the Federal Acquisition Regulatory Council, and agencies would incorporate them into their own acquisition rules and policies.
Accessibility standards are easy to treat as a design checklist. We read the revised Section 508 Standards, as they applied from January 18, 2018, as something closer to a change-control rule. They gave agencies a single external test, WCAG 2.0 Level AA. They spread that test across documents, forms and software as well as web pages. And through the legacy safe harbor, they tied the duty to conform to the moment an agency changed something.
That last point is easy to miss. On January 18, 2018, an agency did not have to fix every old page, form or system that met the earlier standard. It had to make sure that whatever it built, bought or altered from that day on met the new one. The compliance date did not start a remediation project. It started a rule that applied to every future change.
We take the standards in four parts. Each is a separate question an agency had to answer, and together they cover what the compliance date demanded:
- The test: what conformance meant, now that it pointed to WCAG.
- The scope: which content had to conform, public and internal.
- The trigger: when existing technology lost the safe harbor.
- The purchase: how the standards reached contracts before the acquisition rules caught up.
Our argument is that the refresh moved accessibility compliance into the agency’s change processes. Because the safe harbor ended at the first alteration, every content edit, form update and software release became a compliance event. Agencies whose publishing, forms and release processes carried the test would comply as a by-product of normal work. Agencies that treated accessibility as a periodic audit would find the gap growing with every change they made. After the four parts, we look at how this differed across agencies and their partners, at objections, and at what a program director could check.
This matters for citizen experience because the public meets an agency through its changes. A new benefits form, a redesigned eligibility screen, a revised notice, an updated help page: each is a moment when a person with a disability either can or cannot complete a task. The refresh put the test at exactly those moments. An agency that met it at each change would improve its services for disabled users as a matter of course.
A note on our reading. We describe the standards from the Access Board’s own rule and the current Code of Federal Regulations. How provisions apply to a particular agency or product is our reading, and agencies should rely on their own counsel and Section 508 program managers.
The test: one external standard for content, documents and software
The first part was the test itself. Before 2018, the Section 508 Standards had their own technical provisions. From January 18, 2018, the core test for content and software interfaces was WCAG 2.0 at Level A and Level AA, a standard published by the World Wide Web Consortium and incorporated by reference.
Why an external standard mattered
An external standard changed who could check compliance. WCAG has published success criteria, techniques and testing methods that developers, testers and vendors already used outside government. A federal agency could now ask for the same thing a commercial customer or a foreign government might ask for. The Board said its rule aimed to harmonize with standards organizations worldwide, including the European standard for public procurement of ICT, EN 301 549.
For an agency, that meant the market could supply testing. It also meant an agency’s own staff needed to know WCAG itself, rather than an agency-specific list. Developers, content authors and testers each needed training aimed at their part of the work.
Documents as well as web pages
The test applied to non-web documents too. The rule defined a document broadly. Its examples included letters, email messages, spreadsheets, presentations, podcasts, images and movies. Non-web documents had to meet WCAG 2.0 Level A and AA, with four success criteria excepted because they assume a set of web pages: bypass blocks, multiple ways, consistent navigation and consistent identification.
For a benefits agency, that covered the notices and forms that reach the public as attachments, PDFs and printouts produced from electronic files. It also covered the spreadsheets and presentations that circulate among staff when they fall in a covered category. A conforming website could still host non-conforming documents, and each document was its own test.
Software interfaces
E207.2 applied the same WCAG levels to software user interfaces and to the content of platforms and applications. Chapter 5 added software-specific requirements, such as interoperability with assistive technology. E207.3 said that where non-web software needs several steps to accomplish an activity, all the software related to that activity had to conform.
That last provision matters for case management and enterprise systems. A process that runs through several screens or modules, some built in-house and some bought, conforms only if every step does. One inaccessible step blocks the whole activity for a user who relies on assistive technology.
Functional performance criteria as a backstop
E204.1 said that where the technical requirements did not address a function of the technology, that function had to meet the functional performance criteria in Chapter 3. Those criteria describe modes of operation: without vision, with limited vision, without perception of color, without hearing, with limited hearing, and others. They are written in terms of what a user must be able to do.
The backstop matters for new kinds of technology that the technical chapters do not describe. It also means an agency cannot treat a passing automated scan as the end of the question. A function a scanner does not test still has to work for the people the criteria describe.
Equivalent facilitation
E101.2 allowed an alternative design or technology where it gave substantially equivalent or greater accessibility and usability than conformance to the hardware and software requirements. The functional performance criteria were the measure of equivalence. That gave agencies room to meet the purpose of a requirement another way. It also put the burden of showing equivalence on the agency, against criteria written in terms of what users can do.
Training by role
A single external test made role-based training practical. Content authors needed to know how to write headings, link text and alternative text, and how to produce documents that keep their structure. Developers needed to know how to build interfaces that work with screen readers and keyboards. Testers needed to know how to check both. Contracting staff needed to know enough to write requirements and evaluate claims. Each role touched a different part of WCAG.
Mobile apps and data
The rule defined an application as software designed to help the user perform a task, and the software provisions applied to it. A mobile app an agency published for the public was software with a user interface, so E207 and Chapter 5 reached it. The same WCAG levels applied to its screens and its content.
The rule’s definition of content took in electronic information and data, including the encoding that defines its structure and presentation. A public data download is content. A spreadsheet of program statistics, published for the public, had to meet the document requirements: a structure that assistive technology can read, with headers marked as headers.
Testing as a capability
All of this made testing an agency capability. Automated tools catch some WCAG failures and miss others that need a human tester. Manual testing with assistive technology takes trained staff and time. An agency that wanted conforming output had to decide who tested, at what point in the work, and with what evidence recorded.
The scope: public content and nine kinds of internal communication
The second part was what had to conform. The Board’s rule said all public-facing content, and nine categories of non-public-facing content that communicate official business, had to be accessible. It defined public facing as content an agency makes available to members of the public, such as a website, blog post or social media page.
Public-facing content
Public-facing content was simple to scope and large in volume. Websites, social media posts, public documents, data downloads and online forms all qualified. For an agency with a very large number of public pages and documents, the volume alone made a one-time audit impractical as a means of keeping content conforming. Content was published every day.
Internal content that still had to conform
The nine categories brought internal content into scope. Emergency notifications, decisions on administrative claims, program and policy announcements, notices about benefits, eligibility, jobs and personnel actions, and formal acknowledgments of receipt were all covered. So were surveys, templates and forms, training materials, and intranet content designed as a web page.
That list touches a wide range of an agency’s operations. Human resources sends personnel action notices. Training offices publish courses. Program offices issue policy announcements. Adjudication offices issue decisions. Each of those offices produced covered content, whether or not it thought of itself as a publisher.
Social media and outside platforms
The rule’s definition of public-facing content gave social media pages as an example. Agencies publish on platforms they do not control. The platform’s interface belongs to its owner. The agency’s posts, images, captions and videos belong to the agency. An image posted without a text description, or a video without captions, was the agency’s content and the agency’s gap.
That divided the work in a familiar way. The agency could not fix the platform. It could fix what it posted, and choose formats that carry descriptions and captions. A social media team that published from a checklist covering those points would meet much of the requirement for its own content.
Email and office documents
The rule’s definition of a document included email messages, spreadsheets and presentations. Agencies communicate internally by email. An email announcing a policy, or notifying an employee of a personnel action, fell in a covered category. So did the attachments.
That reached every employee who sends official communications. Office software has accessibility checking features, and templates can carry correct structure. Training for all staff on a short list of practices, such as real headings, meaningful link text and alternative text for images, would cover a good part of everyday covered content.
Employees as users
E203.1 tied the rule to both audiences. Agencies had to ensure that federal employees with disabilities had comparable access to information and data, and that members of the public with disabilities did too. Internal systems used only by staff were therefore in scope, through the software provisions, as well as public systems.
For an agency, that meant hiring and accommodating employees with disabilities depended partly on its internal tools. A case management system that a blind employee could not use was a barrier to employment as well as a compliance gap.
User needs as a planning step
E203.2 required agencies to identify the needs of users with disabilities when they procured, developed, maintained or used ICT. It asked how those users would perform the functions the technology supported, and how it would be developed, installed, configured and maintained to support them. That is a requirements step. It belongs at the start of a project, not at acceptance testing.
Templates and forms
Templates and forms were one of the nine categories in their own right. They were also the source of other covered content. A conforming letter template produces conforming letters, if authors use it as designed. A conforming form produces a conforming experience for every person who fills it in. That made the template and forms owners a small group whose work multiplied across the agency.
Records and the archive exception
The rule excepted records maintained by the National Archives and Records Administration under federal recordkeeping statutes, unless public facing. Agency records still in agency hands were not covered by that exception. An agency’s own document management system, holding covered content, remained in scope.
The trigger: when the legacy safe harbor ended
The third part was the safe harbor in E202.2. Any component or portion of existing technology that met the earlier standard, and had not been altered on or after January 18, 2018, did not have to be modified to meet the new standards.
Alteration as the trigger
The rule defined alteration as a change to existing ICT that affects interoperability, the user interface, or access to information or data. That definition is broad. Editing the text of a page affects access to information. Redesigning a form affects the user interface. Changing an integration affects interoperability.
So the safe harbor was narrow in operation. In our reading, it protected content and systems that agencies left alone. Anything an agency touched in the ordinary course of work moved, at least in part, into the new standards. The phrase “component or portion” suggests the trigger applied at that level, so a change to one part need not bring the whole system into scope.
Who decides what counts as an alteration
The definition left room for judgment at the margins. A security patch that changes nothing a user sees may not affect the interface or access to information. A content correction that changes one word does. Someone had to make those calls consistently, and the call had consequences for what had to be tested.
We would put that decision in the agency’s written Section 508 policy, with examples. A rule that any change a user can see, or any change to how data is reached, counts as an alteration is simple to apply. Leaving the call to each team invites inconsistent answers and, over time, a body of changes that no one tested because each team decided its change did not count.
What the trigger did to maintenance
For content teams, the trigger meant every edit was a compliance event. An agency updating an old program page had to bring the changed portion up to WCAG 2.0 Level AA. A policy office revising a guidance document had to produce a conforming revision. A forms office updating a form had to make the new version conform.
For software teams, every release that changed an interface or data access was in scope for the changed portions. A legacy system under active maintenance would move toward conformance one release at a time, if the release process tested for it. If it did not, the agency would be shipping non-conforming changes into a system that had lost the safe harbor for those parts.
Proving the earlier standard
The safe harbor protected only technology that met the earlier standard. In our reading, an agency relying on it needed to be able to show that the legacy content or system had conformed to the 2000 standards. Without that evidence, the safe harbor gave no protection, because there was nothing to keep.
That made old test records valuable. An agency with accessibility testing records for its legacy systems could rely on the safe harbor for unaltered parts. One without them could not show that the parts it left alone had ever conformed.
Retiring content instead of altering it
The trigger gave agencies a third option besides leaving content alone or bringing it up to standard: retiring it. Old pages and documents that no longer served a purpose did not need to be fixed. They could be removed or moved to an archive under recordkeeping rules. For a large site, pruning outdated content shrank both the public’s search problem and the agency’s conformance problem.
That decision needs an owner who knows the content and the records rules. Removing content that the public still needs, or that the agency must keep available, would trade one problem for another.
Systems that mix old and new
After January 18, 2018, a system under active maintenance would contain unaltered legacy parts and altered or new parts. Users experience the system as a whole. A person who can complete the new steps of a process but not the old ones still cannot complete the process. E207.3’s rule on complete processes for non-web software points the same way.
For a program office, that argued for planning conformance by user task, not by code module. The question was whether a person using assistive technology could complete each task the system supported, from start to finish. The answer told the agency where its legacy parts blocked a task that its new parts had made accessible.
Inventory and change control
The trigger also made inventory a compliance tool. An agency needed to know which content and systems existed on January 18, 2018, which met the earlier standard, and which had changed since. Content management systems record edit dates. Software release records show what changed. Linking those records to accessibility testing let an agency show which parts were in which state.
The purchase: standards ahead of the acquisition rules
The fourth part was procurement. The Board’s rule said its standards were not self-enforcing for procurement-related matters. They would take legal effect for procurement when adopted by the Federal Acquisition Regulatory Council. Agencies were also to incorporate them into their own acquisition regulations and policies.
A gap between two dates
On January 18, 2018, the compliance date for the standards had arrived. The Federal Acquisition Regulation had not yet been amended to reference them. In our reading, that left agencies to decide, contract by contract, how to write the revised standards into solicitations through their own policies and requirements documents. We read the standards as applying to what agencies developed, maintained and used regardless of what the acquisition rules said.
For a contracting officer, the practical answer was to specify the revised standards in the statement of work and the evaluation criteria. That needed the program office to know which provisions applied to the product being bought. It also needed evaluators who could judge a vendor’s claims of conformance.
Best meets, documented
E202.7 covered the case where conforming technology was not commercially available. The agency had to procure the technology that best met the standards consistent with its business needs. It had to document in writing the non-availability, including the market research performed and which provisions could not be met, and the basis for its best-meets determination.
That turned market research into a compliance record. An agency buying a product that did not fully conform needed a file showing it had looked for one that did, and why it chose what it chose. E202.7.2 also required the agency to provide an alternative means of access where the product it bought did not conform.
Undue burden, documented
E202.6 allowed an agency to conform only to the extent that full conformance did not impose an undue burden or a fundamental alteration. The responsible official had to document the basis in writing, explaining why and to what extent compliance would create the burden. The agency still had to provide an alternative means of access. That was a record with a named official behind it.
Contractor tools and incidental technology
E202.4 said ICT acquired by a contractor incidental to a contract did not have to conform. A contractor’s own office equipment, used to perform the work, was not the agency’s ICT. But technology the contractor delivered to the agency, or operated on the agency’s behalf for the public, was a different matter. Drawing that line belonged in the contract.
Support documentation and help desks
E208.1 required support documentation and services the agency provided for ICT to meet Chapter 6. Electronic documentation, including web-based self-service support, had to conform to WCAG 2.0 Level A and AA. Help desks, call centers, training services and automated self-service technical support had to give information on accessibility features and accommodate users’ communication needs.
That reached service contracts as well as product purchases. An outsourced help desk serving agency employees or the public was part of the agency’s support services. Its scripts, its knowledge base and its channels had to work for users with disabilities. A help desk contract that did not say so left the agency to fix the gap later.
Cloud services the agency uses
Section 508 covers technology an agency uses as well as what it buys or builds. A software service hosted by a vendor, used by agency staff or offered to the public, is ICT the agency uses. The vendor controls the product’s interface. The agency controls its configuration, its content and its choice of product. Each of those choices could improve or worsen conformance, and the agency answered for the result.
Vendor claims as evidence
A vendor’s report on its own product’s conformance is a claim, not a test. An agency that accepted a vendor’s report without checking had evidence of what the vendor said, not of what the product did. Spot testing key functions with assistive technology before award, or during acceptance, gave the agency its own evidence.
Acceptance and remedies
A contract that specified the standards also needed a way to enforce them. Acceptance criteria could include conformance testing of delivered work. Remedies could include correction at the contractor’s cost when delivered work failed. Without those terms, an agency that found a failure after acceptance would pay to fix it, or live with it. The time to write those terms was before award, when the agency had its strongest position.
How this differed across agencies and their partners
The four parts applied to every agency covered by Section 508. They landed differently by size, mission and how much an agency published or built.
Large departments
Large departments had volume and decentralization. Hundreds of offices published content and ran systems. A department-level accessibility office could set policy, but the trigger fired in every office that edited anything. Departments that built the test into shared content platforms and release pipelines had a way to scale. Those that relied on a central team to review content before publication had a bottleneck.
Small agencies and commissions
Small agencies had less content and fewer systems, and also fewer specialists. One person might be the Section 508 coordinator alongside other duties. For them, the procurement part carried more weight, because they bought rather than built. Specifying the standards in each purchase, and checking vendor claims, was within their reach. A small agency can also share work with others: common contract language, shared testing services and shared training reduce the cost of doing each piece alone. The standards are the same for every agency, so the materials one agency builds can serve another with little change.
Benefits and adjudication programs
Programs that issue notices and decisions had a direct exposure through the nine categories. Benefit notices, eligibility decisions and adjudication rulings had to conform. Those documents are produced by systems, from templates. Fixing the templates fixed every document produced from them afterward, which made template owners an important control point.
Agencies that work through grantees and states
Section 508 applies to federal agencies. Grantees, states and local governments are not covered by it as such. But a federal agency that provides a system or content to the public through a partner, or procures a system that partners use, remains responsible for its own ICT. Agencies needed to be clear in agreements about whose technology was whose.
Field offices, kiosks and shared equipment
The rule gave information kiosks and transaction machines as examples of ICT, and multi-function copy machines as examples of hardware. Agencies with public counters, visitor centers or field offices may use self-service machines. Chapter 4 applied hardware requirements to them. A kiosk replaced after January 18, 2018, was new ICT and had to conform.
Regulators and filing systems
Regulatory agencies run electronic systems through which companies and individuals file applications, reports and complaints. Those systems are public-facing ICT. A filer with a disability who cannot complete a required filing faces a compliance problem created by the agency’s own system. For regulators, conformance of filing systems is part of fair access to the process they administer.
Contractors and integrators
For contractors, the refresh changed what conformance meant in proposals and deliverables. A contractor that built agency systems needed WCAG testing in its own process, and records to show the agency. Contractors that maintained legacy systems faced the trigger directly: each change they made moved part of the system into the new standards.
Objections, in order
We take five objections, numbered in the order we address them.
1. The safe harbor protected agencies from a remediation burden
The first objection is that E202.2 let agencies leave old content alone. It did, for content that met the earlier standard and was never touched. But content and systems that matter are the ones agencies keep changing. The safe harbor shrank with every edit, so an agency’s active estate moved into the new standards whether or not it planned a remediation project. The safe harbor reduced the cost of the transition. It did not remove the cost of change from that day on.
2. WCAG is a web standard and fits documents and software poorly
The second objection is that applying web criteria to documents and software is awkward. The Board recognized that, with four exceptions for non-web documents and software and a word substitution for “page.” The awkwardness is real at the edges. It does not change the core requirement that content and interfaces work with assistive technology. The alternative, separate agency-specific rules for each kind of technology, was what the Board replaced, after commenters supported the shift.
3. Until the FAR changed, procurement was not covered
The third objection is that the standards did not bind procurement until the acquisition rules adopted them. That is a reading of the Board’s own text for procurement-related matters. In our reading, it did not change an agency’s duty for the technology it developed, maintained and used. An agency that bought a non-conforming product would still be using non-conforming technology. The procurement gap affected how an agency wrote contracts. It did not suspend the standards for what the agency put in front of users.
4. Automated testing makes conformance cheap
The fourth objection is that tools can test conformance at scale. Tools help with volume and catch some failures. Several WCAG criteria, and the functional performance criteria, need human judgment. An agency that relied only on tools would have evidence of what the tools checked. That is useful evidence. It is not evidence that a person using a screen reader can complete a task, which is what the functional performance criteria ask.
5. Accessibility is a niche concern for a small population
The fifth objection is that the requirement serves few users. The rule covers federal employees and members of the public with disabilities, and the functional performance criteria include limited vision and limited hearing. Those categories are not small or fixed. The same practices, such as clear structure, captions and keyboard access, also help users on small screens and slow connections. Disability can also arrive with age, injury or illness, for employees and for members of the public. A system built to the standard serves people whose needs change while they use it.
Checks a program director could run
These checks follow from the four parts. They are our suggestions, not requirements.
- Do content, forms and software release processes include a WCAG 2.0 Level AA check before publication or release, with the result recorded?
- Does the agency know which of its covered internal communications fall in the nine categories, and who produces each?
- Can the agency show, for legacy content it relies on the safe harbor for, that it met the earlier standard and has not been altered?
- Do solicitations specify the revised standards, and do evaluators test key functions rather than accept vendor claims alone?
- Are best-meets and undue burden determinations documented in writing, with the alternative means of access named?
The checks also produce figures a program director can track: the share of releases with a recorded accessibility check, the number of determinations on file, the number of complaints and their resolution. None of those figures proves conformance by itself. Together they show whether the change-control logic is running.
The checks need owners. Release checks belong to content and software teams, with the Section 508 program setting the test. The nine categories belong to the offices that produce them. Safe harbor records belong to the Section 508 program and the system owners. Solicitations belong to contracting officers and program offices together. Determinations belong to the responsible officials the rule names.
With hindsight
The standards themselves were corrected almost at once. On January 22, 2018, the Access Board published a direct final rule correcting what it called inadvertent drafting errors in the 2017 rule. It said the corrections fixed two typographical errors and restored longstanding requirements for TTY compatibility and functionality that had been unintentionally deleted. It said the changes established no new substantive requirements and imposed no costs. The rule took effect March 23, 2018, absent adverse comment.
The acquisition rules caught up on August 11, 2021. That day, the Department of Defense, the General Services Administration and NASA published a final rule amending the Federal Acquisition Regulation to incorporate the Access Board’s revised standards. It took effect September 10, 2021. From that date, the gap our fourth part described was closed in the government-wide acquisition rules.
The technical test has not moved. The current Code of Federal Regulations text of the revised 508 Standards still incorporates WCAG 2.0 by reference, the W3C Recommendation of December 11, 2008. The legacy safe harbor in E202.2 still reads as it did, keyed to alterations on or after January 18, 2018. So the change-control logic of our third part remains the operating rule for federal agencies.
Congress added a reporting duty. GSA’s Section 508 site says the Consolidated Appropriations Act, 2023, signed December 29, 2022, amended Section 508 to require agencies to assess and report their efforts annually. OMB, in consultation with GSA and the Access Board, must issue criteria and instructions, and agencies submit responses to OMB and GSA. GSA then publishes a report with a governmentwide and agency-by-agency assessment of compliance and recommendations to Congress. The site lists reports for fiscal years 2023, 2024 and 2025, the last submitted and published on March 2, 2026.
That reporting gives agencies a yearly occasion to account for their compliance, and GSA publishes the results. In our view, an agency whose change processes carry the test can report from its own records. One that relies on periodic audits has to reconstruct its position each year.
A similar approach later reached state and local governments, under a different law. On April 24, 2024, the Department of Justice published a final rule under title II of the Americans with Disabilities Act for state and local governments. Its abstract says it adopted specific technical standards for web content and mobile apps. The current rule text requires conformance with WCAG 2.1 Level A and AA, a later version than the federal agencies’ own standard.
The Department extended that rule’s compliance dates in an interim final rule effective April 20, 2026. Public entities with a population of 50,000 or more now have until April 26, 2027. Smaller entities and special district governments have until April 26, 2028.
For a program director today, the practical lesson is that the trigger never expires. Every change made since January 18, 2018, has been a compliance event for the changed part. An agency that has run that rule through its release processes for years should have an estate that has moved toward conformance. One that has not has an estate whose changed parts may fail a standard that has applied to them all along.
What held up, in our reading, is that an external test, applied at the point of change, made accessibility part of ordinary operations for those who built it in. What did not hold up was any sense that January 18, 2018, finished the job. The acquisition rules needed more time, reporting came later, and the test for states and localities moved to a newer version of WCAG than the one federal agencies still apply.
Spotted an error? Tell us and we will check it and correct the article where needed.