What an accessibility maturity model is
An accessibility maturity model is a staged framework describing different levels of organizational capability in accessibility. Each stage is defined by what the organization knows, what it does, and what processes and tools it has in place. It is a diagnostic tool, not a scorecard for compliance, but a map for planning.
The most widely referenced model is the W3C’s Model for Accessible Technology in the Field of Accessibility (MATF). Most variants share a five-stage arc.
The five stages
- Stage 1 – Unaware: No dedicated accessibility effort, no policy, no systematic approach. Issues are identified reactively, if at all.
- Stage 2 – Reactive: Accessibility enters awareness through a legal demand, complaint, or customer escalation. Efforts are ad hoc. There may be a one-time audit or tool deployment, but no sustained program.
- Stage 3 – Structured: An accessibility program exists with defined policies, designated ownership, and systematic tooling. Accessibility is included in project plans. Progress is tracked, though unevenly.
- Stage 4 – Integrated: Accessibility is embedded in standard workflows: development, design, content, procurement, and vendor management. It is not a separate workstream but part of how work gets done.
- Stage 5 – Optimized: Accessibility is a strategic priority reflected in leadership commitment, budget, and culture. Programs are continuously improved based on data and user feedback.
Why maturity level matters for tool and service selection
An organization at Stage 1 or 2 typically needs to establish basic monitoring and address visible barriers on the live site; runtime remediation and an initial scan are the right starting point. Deploying a full audit program prematurely is counterproductive if the organization lacks internal capacity to act on the findings.
An organization at Stage 3 or 4 is ready for development-time testing tools, formal audit documentation, and procurement requirements. An organization at Stage 5 typically needs program management support, ongoing user testing, and periodic third-party audit validation. Understanding maturity level prevents both over-investment and under-investment relative to regulatory risk.
