Accessibility as a program: initiate, plan, implement, sustain

7 min read · BoK 3F· p. 64–66

Learning objectives (3)

Sequence the four phases of the W3C WAI Planning and Managing Accessibility framework
Explain why accessibility requires ongoing program management rather than a single project
Describe the purpose and content of an organizational accessibility statement

Why it matters

Organizations routinely treat accessibility as a project — something to fix once and then close. This approach fails because digital products change, organizations grow, staff turn over, and new technologies emerge. Sustainable accessibility requires an ongoing program embedded in organizational culture, processes, and governance. The W3C WAI Planning and Managing framework provides a practical model for building that program. (BoK p. 64)

Program vs. project thinking

A project has a start, an end, and a defined deliverable. A program is a permanent organizational capability. The distinction matters for accessibility because:

A project might audit and remediate a website; a program ensures the next redesign is built accessibly from the start.
A project might train a team once; a program ensures new staff are trained, refreshers occur, and training evolves with technology.
A project has a budget line; a program has ongoing resource allocation.

(BoK p. 64)

The W3C WAI Planning and Managing phases

The W3C Web Accessibility Initiative (WAI) describes four phases for managing organizational accessibility. (BoK p. 64)

1. Initiate

The Initiate phase is about creating the conditions for success. It involves:

Building the business case — articulating the legal, reputational, market, and social reasons to invest in accessibility.
Securing leadership commitment — without executive support, accessibility programs stall.
Reviewing the current state — understanding where the organization is today through an initial assessment of its digital assets. (BoK p. 64)

2. Plan

The Plan phase translates commitment into structure:

Establishing an accessibility policy — a formal statement of the organization’s obligations and standards.
Assigning roles and responsibilities — naming who owns accessibility across departments.
Allocating resources — budget, staff time, tools, and training.
Setting milestones — measurable targets for compliance levels and timelines. (BoK p. 65)

3. Implement

The Implement phase is where accessibility work happens in practice:

Training developers, designers, content authors, and procurement officers.
Integrating accessibility into the development lifecycle — requirements, design, coding, testing, and release.
Beginning remediation of existing inaccessible content, prioritized by impact.
Embedding accessibility into procurement criteria for third-party tools and platforms. (BoK p. 65)

4. Sustain

The Sustain phase ensures that gains are not lost over time:

Continuous monitoring — regular audits, automated scanning, and user feedback.
Policy review — updating the policy when laws, standards, or organizational priorities change.
Reporting — measuring and reporting progress to leadership.
Celebrating success — recognizing teams and individuals who advance accessibility, reinforcing the culture. (BoK p. 65)

Organizational accessibility statement

The BoK references the accessibility statement as an important output of the program. An organizational accessibility statement (distinct from the per-website statement required by the EU WAD) declares:

The organization’s accessibility commitment and the standards it aims to meet.
Its current conformance level.
Known gaps and the plan for addressing them.
A contact point for users who experience barriers. (BoK p. 66)

Publishing an accessibility statement demonstrates accountability and gives users actionable information.

European Agency guidelines

The BoK also references guidance from the European Agency for Special Needs and Inclusive Education, which publishes recommendations on making digital learning resources accessible. These guidelines are directed primarily at educational institutions and member-state agencies responsible for inclusive education, offering practical checklists and criteria for accessible digital content in learning environments. (BoK p. 66)

Real-world example

A regional bank treats accessibility as a project for the first time after receiving a complaint: it audits its website, fixes the issues reported, and closes the ticket. Two years later, after a website redesign, the same barriers are back. The bank hires an accessibility consultant who recommends moving to a program model. The consultant helps the bank Initiate (build a business case and secure board support), Plan (write a policy, assign an accessibility lead), Implement (train developers and integrate testing into the CI/CD pipeline), and Sustain (set quarterly audits and report to the board). Accessibility is now a standing item on the governance agenda.

Key terms

W3C WAI Planning and Managing: A W3C resource providing guidance on managing web accessibility within organizations across four phases. (BoK p. 64)
Initiate: The first WAI phase: secure leadership buy-in, assess current state, and establish the business case for accessibility. (BoK p. 64)
Plan: The second WAI phase: set goals, assign responsibilities, allocate resources, and create an accessibility policy. (BoK p. 65)
Implement: The third WAI phase: train staff, integrate accessibility into development workflows, and begin remediation. (BoK p. 65)
Sustain: The fourth WAI phase: monitor conformance continuously, review and update the policy, and maintain progress over time. (BoK p. 65)
European Agency guidelines: Guidance from the European Agency for Special Needs and Inclusive Education on accessible digital learning resources. (BoK p. 66)
Accessibility statement: A public declaration of an organization's accessibility commitment, conformance level, known gaps, and contact for feedback. (BoK p. 66)

Check yourself

.cy-island-wrapper { display: none; }JavaScript is required for the interactive quiz. Here are the questions for reference:

Which correctly states the four phases of the W3C WAI Planning and Managing Accessibility framework in order?

a) Plan → Initiate → Implement → Sustain
b) Initiate → Plan → Implement → Sustain — correct answer
c) Implement → Plan → Initiate → Sustain
d) Initiate → Implement → Plan → Sustain

Explanation: The W3C WAI Planning and Managing Accessibility framework describes four phases in a specific sequence: (1) **Initiate** — make the business case and secure leadership commitment before anything else; (2) **Plan** — define policies, assign roles, allocate resources; (3) **Implement** — train, integrate accessibility into development, remediate; (4) **Sustain** — monitor, review, report, and continually improve. The order matters: each phase builds on the previous one (BoK p. 64–65).

A company remediates its website after receiving an accessibility complaint, closes the remediation ticket, and considers the work complete. Eighteen months later, after a major redesign, the same accessibility barriers are back. Which management approach would best prevent this outcome?

a) Conducting a more thorough remediation audit so that every barrier is caught in a single pass
b) Transitioning from a project-based approach to an ongoing accessibility program with embedded processes — correct answer
c) Hiring an external accessibility consultant to manage all future website updates
d) Publishing an accessibility statement after each redesign to notify users of any new barriers

Explanation: The BoK's core message in 3F is that accessibility requires a **program**, not a project. A project has a defined end; once closed, the organization reverts to its previous patterns. An accessibility program embeds processes, training, governance, and monitoring into the organization's ongoing operations. When accessibility is part of the design specification and development workflow, new features and redesigns are built accessibly from the start — a concept the BoK calls **born accessible** — preventing the cycle of build → remediate → regress (BoK p. 69).

A government department's digital team argues that publishing an accessibility statement is useful only as a legal compliance checkbox and adds no value for users. Which statement best challenges this view based on the BoK?

a) An accessibility statement is only required for websites with more than 10,000 users per month
b) An accessibility statement provides users with actionable information about known barriers and how to request accessible alternatives, reducing exclusion for users with disabilities — correct answer
c) Accessibility statements are only useful in the Initiate phase; they become redundant once the organization reaches the Sustain phase
d) An accessibility statement eliminates an organization's legal liability for any accessibility barriers it discloses

Explanation: An accessibility statement is more than a compliance checkbox. When it honestly reports an organization's conformance status, lists known barriers, and provides a contact for feedback or to request accessible alternatives, it gives users with disabilities practical options. Instead of encountering an inaccessible page with no explanation and no recourse, a user can read the statement, understand what is and is not accessible, and request an alternative format. This transparency and provision of alternatives directly reduces exclusion — a genuine user benefit (BoK p. 66).

Sources

BoK references

Section 3F — IAAP CPACC Body of Knowledge v4.0 (Oct 2023), p. 64–66