6 min read

CPACC - Module 13: integrating ICT accessibility organization-wide

A study summary of integrating ICT accessibility across an organization for the CPACC exam — the W3C's four steps, maturity models, and management champions.

  • #accessibility
  • #cpacc
  • #study-notes

This is Module 13 of the CPACC (Certified Professional in Accessibility Core Competencies) Body of Knowledge — the fourth module of Domain 3, Standards, Laws, and Management Strategies. Module 12 covered which laws and standards apply to ICT; this module is about operationalizing accessibility — turning it into an ongoing organizational capability rather than a one-off fix.

The W3C WAI four-step approach #

The W3C’s Web Accessibility Initiative frames an organizational program as four phases — Initiate → Plan → Implement → Sustain.

| Step | Purpose | Key activities | |---|---|---| | 1. Initiate | Ground the effort in culture & secure buy-in | Learn the basics · explore the current environment · set objectives · develop the business case · raise awareness · gather support | | 2. Plan | Assess the work and assign it | Create an accessibility policy · assign responsibilities · set budget/resources · review environment & websites · establish a monitoring framework · engage stakeholders | | 3. Implement | Weave accessibility through the work | Build skills & expertise · integrate goals into policies · assign tasks · evaluate early and regularly · prioritize issues · track & communicate | | 4. Sustain | Keep momentum after launch | Monitor websites · engage stakeholders · track standards & legislation · adapt to new tech · incorporate user feedback |

Maturity models (don’t mix them up) #

A maturity model lets an organization benchmark where it stands. The exam references two five-level models — and their level names are different, which is exactly what gets tested.

| Level | Business Disability Forum (BDF) | Capability Maturity Model (Carnegie Mellon) | |---|---|---| | 1 | Informal — no documentation or process | Initial — ad hoc, unpredictable | | 2 | Defined — documented, not yet actioned | Repeatable — policies & procedures in place | | 3 | Repeatable — established & actioned consistently | Defined — standard processes, integrated whole | | 4 | Managed — monitored & improved; business as usual | Managed — quantitative quality goals & measurement | | 5 | Best practice — innovate, improve, share | Optimizing — continuous, proactive improvement |

Management champions #

Launching and sustaining a program needs champions from key areas across the organization — people who understand accessibility in their own area and lead improvement there.

Evaluating for accessibility #

Test early and throughout the design/development lifecycle — it’s easier and cheaper to find and fix issues early. Recommendations:

  • Ensure the product/service is fit for purpose and usable by people with disabilities.
  • Take a “born accessible” approach; build reusable design & code libraries.
  • Use QA tools and human evaluation; perform formative, summative, and continuous evaluations.
  • Include people with disabilities in evaluations; bring in outside experts where in-house capability has gaps.

The supporting practices #

Beyond the core loop, the module lists organizational practices you should recognize:

  • Recruiting & including people with disabilities — disability inclusion statement in postings, accessible recruitment site, accessible facilities + reasonable accommodations, educate managers on their obligations.
  • Recruiting digital-accessibility skills — e.g. HTML/CSS/JS, screen-reader testing, knowledge of WCAG and PDF/UA; post on the IAAP Career Center, a11yjobs, and professional networks.
  • Communication management — publish comms standards, train on people-first and plain language, caption & describe time-based media, design for assistive tech.
  • Legal & public relations — assess legal liability; PR should consult legal / risk & compliance before publishing accessibility claims.
  • Procurement best practices — verify product accessibility claims, verify vendor expertise, require accessibility in contracts, review the vendor’s accessibility roadmap, and leverage procurement policy to influence the market.

Quick self-check #

  1. “Accessibility must be a ___, not a ___.” Fill in the blanks.
  2. Name the W3C WAI four steps in order.
  3. Which maturity model’s top level is “Best practice”? Which is “Optimizing”?
  4. Name three things management champions help with.
  5. What percentage of defects do automated checkers catch, and what does that imply?
  6. Which step does “develop the business case” belong to?

Knowledge check #

Answer each question, then check answers — the feedback explains every choice.

Knowledge check

1. In which ways do management champions help launch and sustain an accessibility program? Select all that apply.
2. To succeed, ICT accessibility efforts must be well grounded in the organization's culture, process, and practices.
3. The BDF Accessibility Maturity Model has five levels — which is the highest (level 5)?
4. A website owner asks, "How are we going to handle accessibility on this project?" What are the best responses? Select all that apply.
5. What are two reasons automated testing can't be the only method of evaluating accessibility? Select all that apply.
6. ICT accessibility must be approached strategically and operationally as an integral and ongoing activity.
7. Per the W3C, which are three ways to implement an organizational ICT accessibility program? Select all that apply.
8. The W3C recommends evaluating early and throughout the design process because it's easier and less costly to address issues early.

Study tip: this module is mostly lists, so anchor the two “spines.” First, the W3C loop: Initiate → Plan → Implement → Sustain. Second, the two maturity models side by side — remember only the endpoints: BDF runs Informal → Best practice, CMM runs Initial → Optimizing. Then keep three sound-bites ready: program not project, champions ≠ outsourcing, and automated tools catch ~25%, so humans test too.