A public-sector accessibility plan can fail before the first audit begins if the inventory is too narrow. Many teams start with the main website because it is visible and easy to scan. The real accessibility surface is usually larger: department pages, forms, PDFs, payment flows, mobile apps, authenticated portals, embedded dashboards, maps, procurement systems, agenda platforms, document libraries, and third-party services.
The goal of an accessibility inventory is not to create a perfect spreadsheet. The goal is to build a shared map of digital services, ownership, public impact, vendor dependency, and remediation priority. Without that map, teams end up fixing low-risk pages while high-impact journeys remain inaccessible.
Start with service journeys, not page counts
Page counts can be useful, but they do not tell leadership where people get blocked. A five-page permit flow can matter more than five thousand archived news posts. A public benefits application, emergency notice, meeting agenda, payment form, document packet, or complaint workflow may carry more service risk than a high-traffic landing page.
- What task is the public trying to complete?
- Who owns the content, code, system, vendor contract, and support process?
- What formats are involved: web pages, forms, PDFs, video, maps, dashboards, or mobile screens?
- How often is the journey used and how critical is it to public service delivery?
- What is already known from complaints, support tickets, analytics, or staff experience?
Include vendor systems early
Vendor platforms can become the hidden risk in accessibility planning. A public entity may control the main website but depend on external systems for permits, licensing, agendas, payments, learning, public records, resident portals, chatbot support, or document workflows. Those systems need owners, evidence, known exceptions, and a path for remediation.
The inventory should capture contract owner, renewal date, vendor contact, accessibility conformance report status, known issues, support commitments, and whether the public entity has acceptance criteria for future releases.
Documents need their own triage model
Public-sector document libraries can be enormous. Treating every PDF as equal creates paralysis. The inventory should separate high-use, current, legally or operationally required documents from low-risk historical archives. That makes it easier to focus remediation on documents people actually need to use now.
- Current forms, applications, notices, agendas, minutes, policies, and public reports.
- Documents required to complete a service journey.
- Document templates that generate repeated accessibility problems.
- Archived files that need a reasonable policy, request path, or replacement approach.
What a useful inventory should contain
- Asset name, URL, system, department, owner, vendor, audience, and service purpose.
- Format type: website, app, portal, document, video, dashboard, map, form, or embedded tool.
- Public impact, traffic, legal or operational importance, and known complaints.
- Testing status, standard used, issue severity, and remediation owner.
- Vendor evidence, contract notes, renewal date, and support path.
- Next action, due date, and validation method.
From inventory to action
Once the inventory exists, accessibility work can move in a smarter order. Teams can test the highest-impact journeys, group recurring template issues, identify document remediation patterns, ask vendors for evidence, and build a backlog that reflects public impact instead of page volume.
That shift matters. Accessibility compliance becomes more manageable when the organization understands its real digital surface area and can explain why the work is sequenced the way it is.