An accessibility roadmap is a sequenced plan that moves your organization from its current state to WCAG conformance. It assigns ownership, sets timelines, and breaks the work into phases your team can complete without stalling. Without one, accessibility work tends to drift into a backlog no one touches.
The roadmap itself is not complicated. It follows a predictable sequence: inventory, audit, prioritize, remediate, validate, maintain. What separates teams that reach WCAG 2.1 AA or WCAG 2.2 AA conformance from those that do not is execution discipline at each phase.
| Phase | Primary Activity | Outcome |
|---|---|---|
| Inventory | Catalog all digital assets (websites, web apps, mobile apps, documents) | Complete list of what needs evaluation |
| Audit | Evaluate each asset against WCAG 2.1 AA or 2.2 AA | Audit report identifying all accessibility issues |
| Prioritize | Rank issues by user impact and risk | Sequenced remediation queue |
| Remediate | Developers and content authors fix issues | Conformance gaps closed |
| Validate | Re-evaluate fixes to confirm conformance | Verified WCAG conformance |
| Maintain | Ongoing monitoring, periodic re-evaluation | Conformance sustained over time |
Why Most Accessibility Projects Stall
Teams stall when the scope feels undefined or when no one owns the next step. A common pattern: an organization gets an audit report, circulates it internally, and then nothing happens for months. The report loses freshness, the product changes, and the issues documented no longer match what is live.
The fix is structural. Every phase of the roadmap needs an owner, a deadline, and a clear deliverable. Accessibility is not a single event. It is a project with multiple stages, and each stage requires follow-through before the next one begins.
Start with a Digital Asset Inventory
Before you can scope an audit, you need to know what you have. This means cataloging every digital asset your organization operates: marketing websites, web apps, mobile apps, SaaS products, PDFs, multimedia content, and internal tools that fall under compliance requirements.
For organizations subject to ADA compliance (Title II or Title III), Section 508, or the European Accessibility Act (EAA), the inventory determines which assets carry legal or procurement obligations. The inventory also sets your budget. Audit pricing is driven by the number and complexity of pages or screens being evaluated.
How Does the Audit Fit Into the Roadmap?
The audit is the foundation. A manual accessibility audit is the only way to determine WCAG conformance. Automated scans are a separate activity and only flag approximately 25% of issues. They are useful for monitoring between audits, but they cannot replace human evaluation.
Accessible.org audits are always fully manual, meaning a trained evaluator goes through each page or screen against the applicable WCAG standard. The audit report identifies every accessibility issue, maps it to the relevant WCAG criterion, and includes enough detail for a developer to act on it.
When scoping your accessibility audit with expert evaluators, determine whether you are targeting WCAG 2.1 AA or WCAG 2.2 AA. Most organizations default to 2.1 AA, though procurement requirements and newer regulations increasingly reference 2.2 AA.
Prioritizing Issues After the Audit
An audit report for a mid-size website can identify dozens or hundreds of issues. Fixing them all at once is rarely realistic. Prioritization gives your team a sequence that maximizes impact early.
Two frameworks work well here: Risk Factor and User Impact prioritization formulas. Risk Factor weighs legal exposure and the likelihood of a complaint. User Impact weighs how many users are affected and how severely the issue blocks access. Many teams use both, addressing high-risk and high-impact issues in the first sprint.
The Accessibility Tracker Platform supports both prioritization approaches and can sequence your remediation queue automatically based on audit data. For teams managing multiple projects, this prevents the common problem of decision-makers spending weeks deciding what to fix first.
Remediation: Assigning the Work
Remediation is where roadmaps succeed or fall short. The audit report tells you what is wrong. Remediation is the process of fixing it. This work typically falls to front-end developers, content authors, and design teams depending on the type of issue.
Assign each issue to a specific person with a deadline. Vague ownership like “the dev team will look at this” produces delays. Clear assignment looks like: “Issue #47, missing form labels on the checkout page, assigned to Sarah, due Friday.”
Accessible.org provides guided remediation services for organizations that need developer support or want expert guidance on complex fixes. For teams working independently, the audit report itself serves as the remediation playbook.
Validation and Re-Evaluation
After fixes are applied, each one needs to be re-evaluated to confirm it resolves the issue without introducing new ones. This is validation. Skipping it means you may believe you have reached conformance when you have not.
Validation is typically performed by the same auditor or team that conducted the original evaluation. They re-evaluate the specific pages or components where issues were identified and confirm whether the fix meets the WCAG criterion.
Maintaining Conformance Over Time
WCAG conformance is not a one-time achievement. Every content update, feature release, or design change can introduce new accessibility issues. A sustainable roadmap includes a maintenance phase: periodic re-evaluation, scan monitoring between audits, and training for content authors and developers.
Accessible.org recommends annual manual re-evaluation at minimum, with automated scan monitoring in between. The Accessibility Tracker Platform tracks conformance status across all your projects in one place, so teams can see when an asset starts to drift from its last evaluated state.
Organizations pursuing ADA compliance, EAA compliance, or Section 508 conformance should also maintain documentation: an accessibility statement, an accessibility policy, and for SaaS products entering procurement, a current ACR based on the VPAT template.
What Does a Realistic Timeline Look Like?
For a single website with 20 to 50 pages, a typical timeline from inventory to validated WCAG 2.1 AA conformance is 8 to 16 weeks. Larger projects with multiple digital assets or complex web apps can take 6 months or longer. The key variable is remediation speed, which depends on team capacity and issue volume.
Breaking the roadmap into 2-week sprints keeps momentum visible. Each sprint should close a defined set of issues and produce a measurable reduction in the total issue count.
| Weeks | Phase | Key Deliverable |
|---|---|---|
| 1-2 | Inventory and Scoping | Complete asset list and audit scope defined |
| 3-4 | Audit | Full audit report delivered |
| 5 | Prioritization | Sequenced remediation queue with assignments |
| 6-12 | Remediation | Issues fixed in priority order across sprints |
| 13-14 | Validation | Fixes re-evaluated and confirmed |
| Ongoing | Maintenance | Monitoring, periodic re-evaluation, training |
Frequently Asked Questions
How much does it cost to build and execute an accessibility roadmap?
Cost depends on the number of digital assets, their complexity, and whether you need external audit and remediation services. A single-website project with a manual WCAG 2.1 AA audit, remediation guidance, and validation typically ranges from a few thousand dollars to mid-five figures. Larger portfolios with multiple web apps or mobile apps cost more. Accessible.org publishes transparent pricing for audit and accessibility consulting services.
Can our internal team conduct the audit ourselves?
Internal teams with WCAG expertise can evaluate their own assets, but independently issued audit reports carry more weight in procurement and legal contexts. An external auditor brings objectivity and is less likely to overlook issues that internal teams have normalized. For organizations that need an ACR based on the VPAT template, an independent evaluation is the market standard.
What WCAG version should we target for our roadmap?
WCAG 2.1 AA remains the most widely referenced standard in contracts, regulations, and procurement. WCAG 2.2 AA is gaining traction, particularly in government and enterprise procurement. If your compliance obligations reference a specific version, use that one. If you have flexibility, 2.1 AA is the safest default with an eye toward adopting 2.2 AA criteria in your next evaluation cycle.
How do we keep conformance from slipping after the roadmap is complete?
Build accessibility into your development and content workflows. Train developers on WCAG criteria relevant to their work. Train content authors on accessible document and media practices. Conduct automated scans monthly for early detection. Schedule a full manual re-evaluation annually or after major product changes.
An accessibility roadmap works when it is specific, sequenced, and owned. The phases are well-established. The difference between organizations that reach conformance and those that do not comes down to whether someone is accountable for moving through each phase on schedule.
Contact Accessible.org to start your accessibility roadmap with a manual WCAG audit.
