Score Your Accessibility Program: A Practical Maturity Model for 2025
TABLE OF CONTENTS
An accessibility maturity model helps organizations understand where they stand and where they need to go. Without a clear framework for assessment, accessibility efforts become scattered—reactive fixes here, occasional audits there, but no coherent strategy connecting the pieces.
Most organizations don't know if they're beginners or advanced. They have some accessible components and some glaring gaps. They've done an audit but aren't sure if it made lasting difference. They want to improve but don't know what "better" looks like in concrete terms.
A maturity model provides that clarity. It defines stages of accessibility program development, identifies signals that indicate current position, and maps the path forward. For 2025, with regulations tightening and digital experiences expanding, understanding your accessibility maturity isn't optional—it's essential for planning, budgeting, and risk management.
Know Where You Stand Before You Plan Where to Go
Why Maturity Assessment Matters
What is an accessibility maturity model? An accessibility maturity model is a framework that defines stages of organizational accessibility capability, from reactive (fixing issues only when complaints arise) to strategic (accessibility embedded in business strategy, metrics, and culture).
Without maturity assessment, organizations face:
Resource misallocation: Investing in advanced tooling when basic processes are missing, or vice versa.
Unrealistic expectations: Leadership expecting rapid transformation without understanding the journey required.
Repeated failures: Trying the same approaches without understanding why they haven't worked.
Compliance gaps: Thinking you're compliant when systemic issues persist.
Maturity models originated in software development (CMMI) and have been adapted for security, DevOps, and now accessibility. They acknowledge that capability develops through stages—you can't skip from crisis mode to excellence without building intermediate capabilities.
The Accessibility Maturity Landscape
Several accessibility maturity models exist, including the W3C Accessibility Maturity Model which provides a comprehensive framework. The Business Disability Forum offers assessment tools for UK organizations. Many consultancies have developed proprietary models.
The model presented here synthesizes common patterns into a practical four-level framework applicable to organizations of any size, focusing on observable behaviors and measurable outcomes rather than abstract capabilities.
The Four Levels of Accessibility Maturity
Level 0: Reactive
How do you know if your accessibility program is reactive? Reactive organizations address accessibility only when forced to—lawsuits, complaints, or public incidents. There's no budget, no owner, and no systematic approach. Each issue is handled as a one-off crisis.
Characteristics of Level 0:
- Accessibility work triggered only by complaints or legal action
- No designated accessibility owner or responsibility
- No policies, guidelines, or standards documented
- No regular testing or auditing
- No accessibility requirements in procurement or vendor contracts
- Fixes are band-aids applied to individual pages
- No training or awareness programs
- Accessibility seen as legal risk, not business priority
Common triggers for change: A demand letter, lawsuit, or public complaint forces attention. A new hire with disability can't use internal tools. A major client requires VPAT documentation.
Risk profile: High legal exposure. Significant technical debt accumulating. Reputation vulnerable to public incidents.
Level 1: Structured
Characteristics of Level 1:
- Designated accessibility owner or point person
- Basic policy exists (even if incomplete or not enforced)
- Annual or periodic audits conducted
- Some developers trained on basics
- Accessibility mentioned in some documentation
- Testing is manual and sporadic
- Fixes happen after audits, then drift
- No integration with development workflow
What Level 1 looks like in practice: The organization knows accessibility matters. They've done an audit and fixed critical issues. Someone "owns" accessibility (often alongside other responsibilities). But accessibility isn't embedded—it's a project that runs periodically rather than a continuous practice.
Challenges at Level 1: Audit-fix-drift cycle continues. Fixes don't stick because nothing prevents new issues. The accessibility owner is overwhelmed. Metrics focus on issues found, not issues prevented. Progress feels like treading water.
Level 2: Integrated
Characteristics of Level 2:
- Accessibility embedded in SDLC (development lifecycle)
- Automated testing in CI/CD pipelines
- Design systems include accessibility requirements
- QA includes accessibility verification
- Training provided to designers, developers, and content creators
- Procurement includes accessibility requirements
- Regular (not just annual) testing cadence
- Metrics track prevention, not just detection
- Cross-functional accessibility working group
What Level 2 looks like in practice: Accessibility is built in, not bolted on. New features ship with accessibility considered from design through deployment. Automated tests catch regressions. The design system encodes accessible patterns. Multiple team members share accountability.
According to Forrester research on digital accessibility, organizations at this level see significant reductions in remediation costs and legal exposure compared to reactive approaches.
Level 3: Strategic
Characteristics of Level 3:
- Accessibility tied to business KPIs and executive scorecards
- Dedicated accessibility budget (not borrowed from other initiatives)
- Proactive roadmaps, not just reactive fixes
- Accessibility informs product strategy and market positioning
- User research includes people with disabilities
- Supplier accessibility requirements enforced
- Public accessibility commitment and transparency
- Continuous improvement based on user feedback
- Accessibility expertise distributed across organization
- Advocacy and thought leadership externally
What Level 3 looks like in practice: Accessibility isn't just compliance—it's competitive advantage. Leadership discusses accessibility in strategy meetings. Product managers consider accessibility when prioritizing features. The organization publishes accessibility statements and tracks public commitments.
Signals You're at Each Level
Organizational Behaviors
| Signal | Level 0 | Level 1 | Level 2 | Level 3 |
|---------------------|----------------------|----------------------------------------------------------|---------------------------------|-------------------------------------------|
| Accessibility owner | None | Part-time, often designer or developer with other duties | Dedicated role or team | Executive sponsor + distributed ownership |
| Trigger for work | Complaints, lawsuits | Audits, compliance deadlines | Release cycles, sprint planning | Product roadmaps, business strategy |
| Executive awareness | Crisis only | Annual report | Quarterly metrics | Strategic planning integration |
| Developer knowledge | Minimal | Some trained | Training required for new hires | Continuous learning culture |
| User involvement | None | Occasionally for audits | Regular testing | Ongoing research and co-design |Tooling and Processes
| Signal | Level 0 | Level 1 | Level 2 | Level 3 |
|-------------------|-------------------------------|-------------------|----------------------------------------------|-------------------------------------------|
| Testing approach | None or occasional manual | Periodic audits | Automated + manual, continuous | Predictive, proactive monitoring |
| CI/CD integration | None | None | Automated checks block deploys | Quality gates with accessibility criteria |
| Design system | No accessibility requirements | Basic guidelines | Accessibility encoded in tokens and patterns | Continuous refinement based on testing |
| Issue tracking | Spreadsheets or nothing | Dedicated backlog | Integrated with sprint work | Trend analysis and prevention metrics |Metrics and Governance
| Signal | Level 0 | Level 1 | Level 2 | Level 3 |
|----------------|-----------------|------------------------|------------------------------------|--------------------------------------------|
| Primary metric | None | Issues found in audits | Issues prevented, fix velocity | Business impact, user satisfaction |
| Reporting | None | After audits | Ongoing dashboards | Board-level reporting |
| Budget | None | Project-based | Operational budget | Strategic investment |
| Procurement | No requirements | Basic language | Detailed requirements, VPAT review | Supplier certification, ongoing monitoring |Moving Up the Maturity Ladder
From Reactive to Structured
Immediate priorities:
- Designate an owner: Someone must be accountable. Even part-time ownership is better than none.
- Conduct baseline audit: You need to know your current state. A comprehensive accessibility audit reveals the scope of work ahead.
- Document basic policy: Even a one-page statement of intent creates foundation for accountability.
- Address critical issues: Fix the most severe barriers—keyboard traps, missing form labels, inaccessible navigation.
- Establish basic training: Ensure teams understand what accessibility means and why it matters.
Investment required: Minimal budget for initial audit and basic tooling. Primary investment is time and attention.
Timeline indicators: Most organizations can reach Level 1 within 3-6 months with focused effort.
From Structured to Integrated
Key transitions:
- Shift left in SDLC: Move accessibility from "check at the end" to "consider at the start."
- Implement automated testing: Integrate accessibility checks into CI/CD pipelines. As the Deque axe-core documentation explains, automated tests catch 20-50% of issues automatically.
- Embed in design systems: Build accessibility into components so developers get it by default.
- Expand training: Move beyond awareness to practical skills for designers, developers, and content creators.
- Establish metrics: Track not just issues found but issues prevented, fix velocity, and trend direction.
- Create working group: Cross-functional team ensures accessibility spans silos.
Investment required: Tooling costs, training programs, design system updates. May require dedicated accessibility role.
Challenges to expect: Resistance from teams who see accessibility as "extra work." Tooling integration complexity. Maintaining momentum after initial improvements.
From Integrated to Strategic
Key transitions:
- Connect to business metrics: Demonstrate accessibility impact on revenue, risk, and reputation.
- Secure executive sponsorship: Accessibility needs champion at senior level.
- Establish dedicated budget: Moving from project-based to operational funding provides stability.
- Include in product strategy: Accessibility becomes factor in feature prioritization and market positioning.
- Engage users with disabilities: Move from testing to co-design and ongoing relationship.
- Publish commitments: Transparency through accessibility statements and public reporting.
Investment required: Dedicated resources, user research programs, external communications.
What success looks like: Microsoft's accessibility evolution demonstrates strategic maturity—accessibility influences product strategy, informs hiring, and shapes public identity.
Mapping TestParty to Each Maturity Stage
Entry Use Cases (Level 0-1)
For organizations beginning their accessibility journey, TestParty provides:
Baseline discovery: Comprehensive scanning reveals current state across digital properties. Understanding scope of issues is first step toward addressing them.
Prioritized remediation: AI-powered analysis identifies critical issues and generates code-level fixes, helping teams address the most impactful problems first.
Progress tracking: Dashboards show improvement over time, demonstrating value to stakeholders and maintaining momentum.
Growth Use Cases (Level 1-2)
As organizations mature, TestParty supports integration:
CI/CD integration: Automated accessibility checks in build pipelines prevent regressions before deployment.
Continuous monitoring: Ongoing scanning catches issues introduced by content changes, third-party updates, or code modifications.
Team enablement: Issue context and fix suggestions help developers learn accessibility while resolving problems.
Advanced Use Cases (Level 2-3)
Mature organizations leverage TestParty for strategic visibility:
Multi-property oversight: Dashboard views across brands, regions, and platforms provide enterprise-wide visibility.
Trend analysis: Historical data reveals patterns—which types of issues recur, which teams ship cleaner code, where investment is needed.
Compliance documentation: Automated reporting supports regulatory requirements and demonstrates due diligence.
Vendor management: Scanning third-party integrations and vendor-provided experiences identifies supply chain accessibility risks.
Self-Assessment Checklist
Use these questions to evaluate your current maturity level:
Level 0 indicators:
- [ ] No designated accessibility owner
- [ ] Last audit was more than 2 years ago (or never)
- [ ] Accessibility work only happens after complaints
- [ ] No accessibility policy exists
- [ ] No developers have accessibility training
Level 1 indicators:
- [ ] Someone owns accessibility (even part-time)
- [ ] Policy exists (even if incomplete)
- [ ] Audits happen periodically
- [ ] Some training has occurred
- [ ] Known issues are tracked somewhere
Level 2 indicators:
- [ ] Accessibility included in SDLC from design phase
- [ ] Automated tests in CI/CD
- [ ] Design system includes accessibility requirements
- [ ] Training is ongoing, not one-time
- [ ] Cross-functional accountability exists
Level 3 indicators:
- [ ] Executive sponsor champions accessibility
- [ ] Dedicated budget exists
- [ ] Users with disabilities involved in research
- [ ] Accessibility in product strategy discussions
- [ ] Public commitments published
Frequently Asked Questions
How long does it take to move between maturity levels?
Progression depends on organizational size, complexity, and investment. Moving from Level 0 to Level 1 typically takes 3-6 months with focused effort. Level 1 to Level 2 often requires 12-18 months as it involves process and culture change, not just policy. Level 2 to Level 3 may take years and requires executive commitment and cultural shift.
Can we skip maturity levels?
Attempting to skip levels usually fails. Organizations that try to implement strategic accessibility without integrated foundations end up with impressive policies but continuing failures in execution. Each level builds capabilities that support the next. The progression is sequential, even if the pace varies.
How do we convince leadership to invest in maturity advancement?
Connect accessibility to business outcomes: legal risk reduction, market expansion (disabled consumers and aging populations), brand reputation, and employee productivity (internal tools). The Disability:IN business case provides data on financial performance of disability-inclusive companies.
What's the biggest obstacle to maturity advancement?
Most organizations stall at Level 1—they've acknowledged accessibility matters but haven't embedded it operationally. The transition to Level 2 requires changing how teams work, not just adding accessibility as a checkpoint. This requires sustained leadership attention and willingness to modify established processes.
Should we get certified at each level?
External certification (like IAAP organizational membership or third-party assessments) provides validation and accountability. However, certification isn't required for progress. Focus on actual capability improvement; certification can follow as documentation of achievement.
Conclusion: Make Maturity a Journey, Not a Label
An accessibility maturity model provides a roadmap, not a destination. No organization achieves perfect accessibility—technology changes, standards evolve, and new challenges emerge. The goal is continuous improvement, not a final score.
Advancing accessibility maturity requires:
- Honest assessment of current state without defensiveness
- Incremental progress building on each level's foundation
- Sustained investment beyond one-time projects
- Distributed ownership across functions and teams
- Measurable goals tracking both compliance and outcomes
- User perspective grounding work in actual impact
The organizations that succeed treat accessibility maturity as an ongoing journey. They celebrate progress without declaring victory. They learn from setbacks without abandoning effort. They connect accessibility to broader organizational values and business objectives.
Where does your organization stand? And more importantly, what will it take to move forward?
Want a data-backed maturity score for your org? Start by scanning your key properties and reviewing them with our team.
Related Articles:
Stay informed
Accessibility insights delivered
straight to your inbox.
Automate the software work for accessibility compliance, end-to-end.
Empowering businesses with seamless digital accessibility solutions—simple, inclusive, effective.
Book a Demo