The Digital Accessibility Time Bomb: Navigating Institutional Barriers

Planners who've assessed their department's web accessibility situation face a familiar challenge: Knowing what's wrong is easier than getting the organization to act. Digital accessibility sits in an uncomfortable institutional space — not clearly owned by IT, legal, communications, or any single department — which often means no one owns it at all.

Part 1 of "The Digital Accessibility Time Bomb" highlighted the looming deadlines for Web Content Accessibility Guidelines (WCAG) 2.1 AA compliance and shared tips to help planners assess the scope of the problem. This second part addresses the barriers planners will encounter when raising accessibility concerns, offers talking points for conversations with decision-makers, and suggests contract provisions that can prevent accessibility problems in future vendor relationships.

Common Barriers to Action

There are four barriers planners should be prepared for.

1. Diffused Responsibility

IT manages the servers but doesn't create content. Communications may oversee the website, but doesn't control what planning uploads. Legal understands the liability but lacks the technical capacity to remediate. Planning generates documents, but considers the website someone else's domain. This fragmentation means accessibility complaints circulate without landing anywhere.

2. Compliance as a Project Instead of a Function

Decision-makers often frame accessibility as something to be achieved and then checked off — allocate budget this year, fix the problems, move on. But municipal websites aren't static. New content appears daily, staff turns over, and compliance drifts away because it isn't embedded in ongoing workflows. When leadership treats this as a project rather than a function, they set up the organization for repeated failure.

3. Misplaced Faith in Vendors

Many municipalities have already purchased accessibility tools or services, and decision-makers may believe the problem is handled. But overlay widgets don't fix underlying structural problems; automated remediation produces malformed tagging, and audits without remediation capacity become shelfware. Planners who raise concerns may encounter resistance from colleagues who feel their previous purchase decisions are being criticized.

4. Resource Competition

Accessibility competes with every other priority for limited staff time and budget. Without a forcing function like active litigation or a federal deadline, it loses. The WCAG mandate changes this calculus — April 2026 creates urgency — but even with a deadline, accessibility may be deprioritized in favor of more visible projects.

Talking Points for Decision-Makers

When raising accessibility concerns with supervisors, department heads, or agency leadership, planners should frame the issue in terms that resonate institutionally.

On Legal Exposure

"The DOJ's WCAG mandate takes effect in April 2026 (or April 2027) for municipalities of our size. Noncompliance exposes us to complaints, investigations, and potential litigation under Title II of the ADA. Overlay widgets and automated tools don't provide legal protection, according to the courts. We need to understand our actual exposure before the deadline arrives."

On Equity and Mission Alignment

"Planning's core function is inclusive public engagement. When our documents aren't accessible to residents using screen readers or other assistive technologies, we're excluding community members with disabilities from the planning process. This undermines our comprehensive plan goals around equity and public participation."

On the Scope of the Problem

"I assessed a sample of our department's online documents using standard accessibility checkers. The majority failed basic WCAG criteria. We don't have an inventory of our digital assets, we don't have a process for ensuring new documents are accessible before publication, and we don't have staff trained in accessibility requirements. This isn't a problem we can solve with a single purchase — it requires building ongoing capacity."

On False Solutions

"Some vendors promise turnkey compliance, but the technology doesn't deliver what they claim. Automated tagging produces documents that pass automated checkers but fail actual users. Overlays have been widely condemned by disability advocates and don't address underlying structural problems. Before we spend money, we need to understand what actually works."

On the Opportunity

"Accessible documents are structured documents — machine-readable, searchable, ready for integration with modern information systems. If we build the capacity to manage our digital assets properly, we're not just achieving compliance. We're laying the groundwork for better public information systems overall."

Contract Provisions for Vendor Agreements

Planners often procure external services for plan development, environmental review, website components, public engagement platforms, and other work that generates digital content. These contracts are an opportunity to prevent accessibility problems rather than inherit them.

Include explicit WCAG 2.1 AA requirements in the scope of work. Don't assume vendors know or will follow accessibility standards — state the requirement clearly: "All deliverables, including PDFs, web pages, interactive features, and multimedia content, shall conform to WCAG 2.1 Level AA success criteria."

Require accessibility documentation. Vendors should provide a Voluntary Product Accessibility Template (VPAT) or equivalent documentation demonstrating how their deliverables meet WCAG criteria. For documents, require an accessibility check report from a tool like PAC 2026 or Adobe Acrobat's built-in checker.

Specify testing with assistive technologies. Automated checkers catch some problems but miss many others. Contract language should require that deliverables be tested with screen readers (such as NVDA or JAWS) and keyboard-only navigation before acceptance.

Include remediation obligations. If deliverables fail accessibility review, the vendor should be contractually obligated to remediate at no additional cost. Without this provision, agencies often face a choice between accepting noncompliant work or paying twice.

Build accessibility review into the payment schedule. Tie the final payment to successful accessibility verification. This creates an incentive for vendors to deliver compliant work rather than treating accessibility as an afterthought.

Require source files. For documents that may need future updates, ensure the contract requires delivery of editable source files (Word, InDesign, etc.), not just final PDFs. Remediating a PDF is significantly harder than fixing the source document and re-exporting.

The Limits of Individual Action

These talking points and contract provisions can help planners advocate within their organizations and prevent some future problems. But they don't solve the underlying challenge: Municipalities lack the institutional infrastructure to manage digital accessibility at scale.

The backlog remains. Ongoing production workflows remain unchanged. The capacity to remediate thousands of documents before April 2026 didn't materialize because a planner raised concerns in a meeting.

What these actions accomplish is positioning. Planners who've documented the problem, advocated for resources, and built accessibility requirements into their own procurement practices have done what's within their power. When the deadline arrives, and the organization isn't ready, the path forward will be clearer — and the relationships needed to pursue real solutions will already exist.

Preview of Part 3

The final part of this series tackles how AI tools may be necessary to scale up web accessibility efforts. It deals frankly with current capabilities and limitations and offers experiments planners can start running now.

Top image: ©Aliaksandra Salalaika / Dreamstime.com