True story: I discovered a new website published by a Fortune 200 employer while listening to the radio during my work commute. Needless to say, it wasn’t accessible.
Ask most organizations to provide a complete list of their web content, and you’ll get one of two responses: either a spreadsheet that’s three years old or a long pause. If you then ask who is responsible for accessibility on each of those pages, documents, videos, and social media accounts, the pause becomes even longer.
This is a key issue in digital accessibility compliance, and it’s not discussed enough. The conversation often jumps straight to WCAG conformance levels, audit scope, and remediation timelines. But all that depends on a core assumption that most organizations cannot meet: that they know what they have.
The Ownership Vacuum
Digital content in most organizations accumulates without any clear management.
- A department posts a PDF to the website because it is quicker than contacting IT.
- A communications staffer publishes a page for a past event and then changes roles.
- A consultant creates a microsite for a campaign that ends when the contract finishes.
- A social media manager uploads graphics daily with no review process.
- A mobile app group switches their terms and conditions page to a webview because it changes so often, and they don’t want to have to republish the app every time.
No single person has a full picture of what exists, where it is stored, who created it, or whether or not accessibility was a consideration.
When an accessibility audit is commissioned in this context, negotiating the scope becomes a project in itself. Which URLs are included? Which PDFs are current versus which are claimed in archived status? Who has authority to remove outdated content or suggest fixes? The typical answers are: nobody knows, nobody is certain, and nobody can make that decision quickly.
The ownership vacuum created by not knowing any of this information is not a technology issue; it’s a governance issue. Content management systems, link crawlers, and sitemap generators can identify existing URLs, but they cannot determine who is responsible for them, whether they are still necessary, or if anyone will take action when a barrier is encountered. Human accountability is needed for this, and establishing that requires a process that assigns responsibility at the point of publication, before the content is published.
Why an Inventory Cannot Solve a Governance Problem
Organizations that recognize the problem often turn to an inventory as the solution. They hire a vendor to crawl multiple sites, create a list of barriers, and develop a remediation backlog. This approach is a sensible starting point, but it only addresses the symptom. Inventories become outdated the moment the next unreviewed piece of content goes live. Organizations that continually publish content without a gatekeeping process don’t have an accessibility issue with a clear endpoint. Instead, they have a pipeline that creates new problems faster than a remediation team can fix old ones.
The audit-and-remediate cycle is costly because it happens after the fact. Detecting a barrier once content has been published, added to a backlog, prioritized, sent to a developer or content owner, and fixed takes significantly more time and money than preventing the barrier before publication. Often, the content owner who created the issue is no longer in the role. The institutional knowledge of why a page exists, what it is supposed to say, and who it serves is frequently long gone.
Gatekeeping as Governance Infrastructure
An “accessibility gate” is a specific checkpoint in the publication workflow where two key things occur: accessibility requirements are checked, and ownership is assigned. Both are equally important.
When content passes through a gate before publication, the organization knows who published it, when, under what review process, and who is responsible for maintaining it. That is the metadata an inventory actually needs and rarely has. It transforms an unorganized collection of content into a managed asset register because each new item is added as soon as it is created, instead of being discovered later by a crawler.
Gatekeeping also alters the compliance posture in a way that retroactive remediation cannot. An organization that can demonstrate a documented, enforced review process for new content deployments is in a fundamentally different legal position than one that only responds when there is a complaint. The former has a program. The latter merely reacts.
Where to Start
The gate does not need to be elaborate to be effective. There are three simple core requirements:
- Every piece of content published to a digital channel must have a named owner before it goes live.
- That owner must confirm, in some documented form, that basic accessibility requirements have been met.
- Content that cannot be assigned an owner is not published.
This is not a technical requirement. It is a policy requirement. It asks organizations to treat digital publication the same way they treat other operational decisions that carry legal consequences: with a designated responsible party and a documented process.
Organizations that face the biggest challenges with accessibility compliance are rarely those lacking technical skills. They are usually the ones where anyone can publish content to a public channel without a second signature, checklist, review, or question. Fixing that isn’t an accessibility project; it’s a governance project. Addressing this governance issue is essential for giving the rest of the accessibility program a real chance to succeed.
