ACCESS BRIEF INSIGHTS — May 06, 2026
IT is Not the Owner of Your Content
The biggest digital accessibility challenge most public agencies have not yet addressed is not the agency website itself. It is the content being delivered by consulting firms every week under contracts that were written before the mandate existed.
​
A state DOT’s website may have dozens of pages maintained by internal staff. But behind those pages are hundreds or thousands of documents, project pages, public involvement materials, and planning deliverables produced by AEC consulting firms under contract. This is not a criticism of how those firms operate. The system was built before ADA Title II required WCAG 2.1 AA for digital content. Accessibility was never part of the scope of work, the QA/QC checklist, or the production workflow because the mandate did not require it.
​
Now it does. And the gap between how work has always been scoped and what the law now requires is real. Consulting firms are delivering exactly what was asked for. The problem is that what was asked for is no longer sufficient. The DOJ’s final rule changed what a complete deliverable looks like, but the procurement process, the scope templates, and the consultant’s understanding of the agency’s obligations have not caught up yet.
The Deadline Extension Does Not Pause the Content Pipeline
When the DOJ extended the ADA Title II compliance deadline by one year in April 2026, it gave agencies additional time to build capability. Some agencies are using that time well, investing in training, updating procurement language, and standing up accessibility programs. That is exactly what the extension was designed to support.
​
But the extension also creates a risk that is easy to overlook. The content pipeline does not pause because a deadline moved. Every week, consulting firms are delivering new documents to their DOT clients. Environmental assessments. Public involvement plans. Design reports. Project websites. Meeting materials. Every one of those deliverables produced under the existing process, without accessibility built in, is a document that will need to be remediated later or that will be non-conformant when the deadline arrives.
​
The agencies that use this runway to change how content is produced and procured will be in a strong position by April 2027. The agencies that continue to accept deliverables produced the same way they have always been produced will arrive at the deadline with a larger backlog than they have today. The extension is an opportunity, but only if it is used to change the process rather than extend the status quo.
Why IT Gets the Assignment
When a public agency learns that its digital content must conform to WCAG 2.1 AA, the first instinct is almost always the same: assign it to IT. This makes sense on the surface. Digital accessibility sounds like a technology problem. The word digital is right there in the name. IT manages the website, the servers, the content management system. It feels like their domain.
​
But IT does not produce the content. The environmental documents were written by consultants and reviewed by project managers. The public involvement materials were developed by a communications team or a public engagement firm. The design reports were assembled by engineers. The press releases, the project fact sheets, the board meeting agendas — none of this was produced by IT.
​
IT manages the infrastructure the content sits on. In most agencies, IT did not create the content, does not review it before it is posted, and has no authority over how it is formatted, structured, or exported. Digital accessibility needs IT as a partner, but assigning IT as the sole owner puts accountability with the one group that does not control the content production process.
Closing the Consultant Gap
The AEC firms producing content for public agencies are operating within the framework they have been given. A consulting firm’s project manager executes the scope they were contracted to perform. If the scope says deliver a public involvement plan, they deliver a public involvement plan. If the scope does not mention accessibility, accessibility is not part of the deliverable. The project manager is not making a judgment about the law. They are responding to the requirements in front of them.
​
This is why the solution is not training alone. Awareness helps, but until accessibility requirements appear in the scope of work, the contract language, and the deliverable acceptance criteria, consulting firms will continue to produce what they have always produced. The gap closes when the agency changes what it asks for, not when the consultant independently decides to add something the client did not request.
What This Looks Like When It Works
Agencies that are making progress on digital accessibility share a common characteristic: they distribute responsibility to the people who produce the content rather than centralizing it in a group that does not.
​
IT remains essential. IT ensures the CMS supports accessible publishing, configures templates that enforce structure, and implements automated testing tools that flag issues before content goes live. IT is a critical partner in the accessibility program. The shift is from sole owner to partner.
​
The organizational structure that works has three components. First, a named accessibility lead with authority that crosses departmental lines, someone who can set standards, review processes, and work with content producers across the organization and beyond it. Second, training and tools for every group that produces content, integrated into existing workflows rather than delivered as a one-time awareness session. Third, procurement language that extends accessibility requirements to consultants and vendors so that contractor-produced content arrives conformant rather than requiring remediation after delivery.
​
That third component is what closes the consultant gap. When accessibility is in the scope, it is in the budget. When it is in the contract, it is in the QA/QC process. When it is in the deliverable acceptance criteria, the project manager has a clear reason to build it into the production workflow. The standard for a complete deliverable changes at the point where the work is assigned, not after it is delivered.
Two Questions Worth Asking
If your agency has assigned digital accessibility to IT, it is worth asking: does IT produce the content that needs to be accessible? If the answer is no, the organizational model may need to evolve. Not because IT is doing something wrong, but because the challenge is bigger than any single department.
​
And if your agency is using the deadline extension to plan ahead, one more question is worth asking: how are the deliverables coming in from consultants this month being produced? If the answer is the same way they have always been produced, the extension is an opportunity to start that conversation now rather than later.
​
The agencies that use this time to change how content is produced and procured will be ready. That is the purpose of the runway.
​
If you are working through how to structure accessibility responsibility in your agency or firm, the ADA Title II Readiness Checklist covers 36 dimensions of preparedness, including organizational ownership, staff training, and procurement. You can download it using the button below.
​
This topic is covered in more depth in Real. Relevant. Required., a practitioner’s guide to ADA Title II digital accessibility for state and local government, coming soon from AOG.
​