IAAP CPACC Foundations
The Certified Professional in Accessibility Core Competencies (CPACC) exam tests your understanding of disability, accessibility, and universal design. It’s the foundation credential — and the one NZ government tenders increasingly ask for.
1 The Hook
A Wellington digital agency bids for an AoG contract to redesign a Ministry website. The procurement criteria include: “evidence of accessibility expertise — IAAP certification preferred.” The agency has testers who know how to run axe and NVDA. None are IAAP certified.
They lose the bid to a competitor with one CPACC-certified tester on the team.
The CPACC takes 6 months to study for and $520 USD to sit. The contract was worth $380,000. The arithmetic is obvious.
This is not a hypothetical. AoG procurement panels are increasingly specifying IAAP credentials alongside ISTQB qualifications. For government-facing digital work in NZ, CPACC is fast becoming a table-stakes credential.
Senior engineer insight
When I first studied for CPACC, I assumed the hard part would be learning WCAG success criteria — I already knew those. The hard part was the disability models and AT pairings: the exam expects you to map a disability category to its primary AT and explain why that AT addresses the specific barrier. That conceptual precision is what separates people who understand accessibility from people who just run audits.
Six months after passing, I reviewed a government tender where our team was scored on "accessibility expertise." The evaluators cited the CPACC as evidence we understood disability as a rights issue, not just a compliance checkbox — which influenced our weighting on the governance criteria, not the technical ones.
Most common mistake: teams treat CPACC prep like WCAG study — they practice running axe and NVDA for months, then fail Domain 1 because they can't name the AT for cognitive disabilities or explain the Social model in their own words.
From the field
A Wellington GovTech team had two testers with strong WCAG 2.2 practical experience — they could find and fix colour contrast, keyboard trap, and screen reader issues fluently. When an AoG contract asked for IAAP certification, they self-assessed as "basically certified" and included that claim in their tender response. The evaluation panel came back with a clarification request: "Please list your IAAP member numbers." Neither tester had ever joined IAAP, let alone sat the exam.
They withdrew the claim, lost the criterion weighting, and came second. The team lead studied for and passed CPACC over the following four months — about 14 weeks at three hours a week. The next AoG bid they submitted listed a current IAAP member number. They won. The lesson that generalises: practical skill and formal credential are not interchangeable in procurement contexts; NZ government panels increasingly treat IAAP membership as a verifiable signal, not a proxy for self-assessed competence.
2 The Rule
IAAP CPACC certification proves you understand accessibility as a discipline, not just as a tool. It covers disability models, legal frameworks, assistive technologies, and universal design — knowledge that goes far beyond running automated scans.
3 The Analogy
CPACC is to accessibility what ISTQB Foundation is to testing.
It’s the baseline credential that says “I understand the fundamentals, not just the practice.” Most jobs don’t require it — but the ones that do, really do. An ISTQB Foundation certificate doesn’t prove you can write great tests. It proves you understand what testing is for. CPACC is the same signal for accessibility: you understand the why, the who, and the legal weight behind it.
4 Watch Me Do It
The CPACC exam is 100 multiple-choice questions, 2 hours, passing score 65%. It covers three content domains.
Domain 1: Disabilities, Challenges, and Assistive Technologies (40%)
Disability models — the exam tests whether you understand both:
- Medical model: disability is a deficiency in the person, to be fixed or accommodated through clinical intervention.
- Social model: disability is society’s failure to design environments that work for everyone. The barrier is the environment, not the person.
NZ context: The Social model underpins the NZ Disability Strategy 2016–2026 and the Human Rights Act 1993 (s.21 lists disability as a prohibited ground of discrimination).
Disability categories and assistive technologies:
- Visual: screen readers (NVDA, JAWS, VoiceOver), refreshable braille displays, screen magnification
- Auditory: captions, transcripts, sign language video, visual alert systems
- Motor/Physical: switch access, eye-tracking, mouth sticks, voice control (Dragon NaturallySpeaking)
- Cognitive: text-to-speech, simplified language tools, reading mode, AAC devices
- Speech: augmentative and alternative communication (AAC) devices, text input
- Seizure disorders: animation control, flicker detection tools
Domain 2: Accessibility and Universal Design (40%)
The 7 Principles of Universal Design (Mace, 1997) — memorise these for the exam:
- Equitable Use — useful to everyone, regardless of ability
- Flexibility in Use — accommodates a wide range of preferences and abilities
- Simple and Intuitive — easy to understand regardless of experience or language
- Perceptible Information — communicates necessary information effectively regardless of conditions
- Tolerance for Error — minimises hazards and adverse consequences of unintended actions
- Low Physical Effort — can be used efficiently and comfortably with minimal fatigue
- Size and Space for Approach and Use — appropriate for any user’s size, posture, or mobility
WCAG 2.2 — the four POUR principles:
- Perceivable — content must be presentable in ways users can perceive
- Operable — interface components must be operable by all users
- Understandable — content and operation must be understandable
- Robust — content must be interpreted reliably by assistive technologies
NZ Web Accessibility Standard 1.2 mandates WCAG 2.2 AA for all NZ government agency websites. Made under the Crown Entities Act 2004.
Domain 3: Standards, Laws, and Management Strategies (20%)
- UN CRPD: NZ ratified the Convention on the Rights of Persons with Disabilities in 2008. Article 9 requires accessible ICT.
- Human Rights Act 1993: s.21(1)(h) — disability is a prohibited ground of discrimination. Applies to digital services.
- NZ Web Accessibility Standard 1.2: The domestic technical standard, mandating WCAG 2.2 AA for government agencies.
- Section 508 (US) / EN 301 549 (EU): Comparable international standards. The exam expects you to understand how they relate to WCAG without confusing them with NZ law.
5 When to Use It
Pursue CPACC when:
- You are targeting NZ government or enterprise digital services work and want to differentiate in procurement
- Your organisation bids for AoG contracts and wants to formally claim accessibility expertise
- You want a formal credential to pair with your ISTQB qualification when moving into senior or specialist roles
- You work in a sector with legal accessibility obligations (government, health, education) and need to understand the legal framework, not just the technical standard
CPACC alone does not qualify you to conduct WCAG audits. That is WAS territory. CPACC establishes the conceptual and legal foundation — WAS proves the technical competence.
6 Common Mistakes
🚫 “I used to think: CPACC is a technical exam about automated testing tools.”
Actually: CPACC is mostly conceptual. Disability models, AT categories, legal frameworks, and universal design principles make up around 80% of the content. Less than 20% touches specific tools. Testers who train by running axe for six months are preparing for the wrong exam.
🚫 “I used to think: practical NVDA and axe experience is enough to pass CPACC.”
Actually: Practical experience helps, but the exam tests knowledge you won’t encounter just by running automated scans. You need to know the six disability categories, the AT for each, the two disability models, the 7 Universal Design principles, and the structure of the NZ and international legal frameworks. This is study content, not hands-on content.
🚫 “I used to think: NZ law doesn’t directly mandate WCAG compliance.”
Actually: The NZ Web Accessibility Standard 1.2, made under the Crown Entities Act 2004, requires government agencies to meet WCAG 2.2 AA. The Human Rights Act 1993 creates additional legal exposure for digital services that exclude people with disabilities. Non-compliance is a legal risk, not just a best-practice gap.
7 Now You Try
Explain the difference between the Medical and Social models of disability, and explain why the Social model is the basis for NZ’s Web Accessibility Standard. Give a concrete example showing how each model would approach a website that deaf users cannot use.
Why teams fail here
- Preparing for CPACC as a WCAG exam — the majority of the content is conceptual (disability models, AT categories, legal frameworks) and candidates who only practise technical testing are underprepared for Domain 1 and Domain 3.
- Confusing NZ law with international standards — candidates mix up the NZ Web Accessibility Standard 1.2, the Human Rights Act 1993, Section 508 (US), and EN 301 549 (EU); the exam expects you to distinguish them cleanly.
- Underestimating the Universal Design principles — the 7 principles by Mace (1997) are directly testable; candidates who skim them and rely on POUR instead are caught out by questions that use the UD terminology, not the WCAG terminology.
- Not joining IAAP before studying — IAAP membership gives access to the Body of Knowledge (the official study guide) and the candidate handbook; candidates who study from unofficial materials often encounter terminology mismatches on exam day.
Key takeaway
CPACC certifies that you understand accessibility as a civil rights discipline — not a tooling skill — and in NZ government procurement that distinction is increasingly worth more than any amount of unprovable practical experience.
Interview Questions
What NZ hiring managers ask about IAAP CPACC certification foundations.
Q1. What does CPACC stand for and what does it cover?
Strong answer: CPACC is the Certified Professional in Accessibility Core Competencies, offered by IAAP. It covers three domains: disabilities, challenges, and assistive technology (the breadth of disability types and how AT helps); accessibility and universal design (WCAG, ATAG, UAAG, WAI-ARIA principles); and standards, laws, and management strategies. CPACC is the entry-level IAAP certification — it validates broad knowledge without requiring technical implementation skills. Relevant for NZ testers, project managers, and content authors who need to demonstrate accessibility competency without writing code.
Q2. Name three disability categories covered by CPACC and a web accessibility implication of each.
Strong answer: Visual (blindness, low vision, colour blindness): screen readers cannot access images without alt text (WCAG 1.1.1); colour-blind users cannot rely on colour alone to convey information (WCAG 1.4.1). Auditory (deafness, hard of hearing): video content needs captions (WCAG 1.2.2); audio-only content needs a text transcript (WCAG 1.2.1). Motor/mobility (limited hand function, spinal injury): all functionality must be keyboard-operable (WCAG 2.1.1); click targets must be sufficiently large (WCAG 2.5.8). CPACC expects you to connect disability characteristics to specific access barriers.
Q3. What is the difference between CPACC and WAS and who should pursue each?
Strong answer: CPACC validates broad accessibility knowledge — principles, standards, disability types, assistive technologies. It does not require technical skills. WAS (Web Accessibility Specialist) validates technical implementation: WCAG implementation, ARIA patterns, HTML/CSS accessibility, and technical audits. For NZ QA professionals: CPACC suits testers involved in accessibility methodology, project management, or client communication. WAS suits those conducting technical audits, writing ARIA code, or evaluating complex interactive components. Many accessibility specialists hold both — CPACC provides the conceptual foundation that makes WAS study more effective.
8 Self-Check
Click each question to reveal the answer.
What does CPACC stand for, and what are the three exam domains?
Certified Professional in Accessibility Core Competencies. The three domains are: (1) Disabilities, Challenges, and Assistive Technologies (40%); (2) Accessibility and Universal Design (40%); (3) Standards, Laws, and Management Strategies (20%). Exam: 100 questions, 2 hours, 65% to pass.
What NZ legislation makes WCAG 2.2 AA mandatory for government websites?
The NZ Web Accessibility Standard 1.2, made under the Crown Entities Act 2004. It mandates WCAG 2.2 AA for all NZ government agency websites. The Human Rights Act 1993 (s.21) also prohibits disability-based discrimination, creating additional legal exposure for inaccessible digital services.
Name 3 assistive technologies used by people with visual impairments.
Screen readers (NVDA, JAWS, VoiceOver), refreshable braille displays (connected to a computer, they convert on-screen text to braille in real time), and screen magnification software (ZoomText, Windows Magnifier, macOS Zoom). Each serves different needs within the visual impairment category.
9 ISTQB Mapping
CPACC is an IAAP credential — not an ISTQB qualification. The two are complementary, not competing.
CTFL v4.0 Section 4.1.1 covers non-functional testing, which includes accessibility testing as a category. CTFL does not go into accessibility depth — it acknowledges it as a testable quality characteristic. CPACC provides the conceptual depth that CTFL leaves to specialists.
For NZ government work: ISTQB CTFL establishes general testing competence; CPACC establishes accessibility-specific competence. Senior testers targeting government accessibility roles increasingly need both.