CPACC vs WAS — which certification should you go for

Two certifications, one organisation, and a question that comes up in almost every accessibility Slack channel: should I start with CPACC or go straight for WAS? Here is a practical comparison to help you decide.

The short answer

If you are unsure, start with CPACC. It is broader, more universally useful, and serves as a foundation for everything that follows — including WAS. If you already implement WCAG daily and can audit a page against every success criterion from memory, WAS may be the better first move.

What each certification covers

CPACC — Certified Professional in Accessibility Core Competencies

CPACC is the generalist credential. It covers the full landscape of accessibility: disability models, assistive technologies, accessibility standards (WCAG, ATAG, UAAG), and legal frameworks (EAA, Section 508, EN 301 549). It tests breadth of understanding rather than depth of technical skill.

Think of it as proving you can navigate the entire map — standards, laws, disabilities, and technology — at a confident, professional level.

WAS — Web Accessibility Specialist

WAS is the technical credential. It goes deep into WCAG success criteria, testing techniques, ARIA implementation, and remediation strategies. It assumes you already understand the foundations that CPACC covers and asks you to apply them at the code and audit level.

Think of it as proving you can do the work — find issues, explain why they fail, and fix them in markup and code.

Side-by-side comparison

	CPACC	WAS
Focus	Broad foundations	Technical depth
Audience	Designers, PMs, QA, compliance, developers	Developers, auditors, QA specialists
WCAG depth	Principles, structure, conformance levels	Individual success criteria, techniques, failures
Legal content	Significant — laws and policies are a major section	Minimal — assumes you already know the legal context
Disability knowledge	Major section — models, types, AT	Assumes prior knowledge
Code and ARIA	Not tested directly	Tested in depth
Questions	100 multiple-choice	75 multiple-choice
Duration	2 hours	1.5 hours
Passing score	~65–70%	~65–70%
Validity	3 years	3 years
Prerequisite	None	None (but CPACC knowledge is assumed)

The hidden third option: CPWA

If you earn both CPACC and WAS, IAAP automatically grants you the CPWA — Certified Professional in Web Accessibility. There is no separate exam. CPWA signals that you have both the strategic overview and the technical depth — it is the strongest credential in the IAAP ecosystem.

Many professionals plan for CPWA from the start: CPACC first, WAS six to twelve months later.

Which one matches your role?

Choose CPACC first if you are:

• A designer, product manager, or content strategist who shapes decisions but does not write code.
• A developer or QA who is relatively new to accessibility and wants the full picture before going technical.
• In a compliance, legal, or procurement role where understanding the regulatory landscape matters more than writing ARIA.
• Building a career pivot into accessibility and need the most broadly recognised entry point.

Choose WAS first if you are:

• A developer or auditor who already has deep WCAG knowledge and implements accessibility daily.
• Confident you could explain every WCAG 2.2 AA success criterion, its intent, and at least one sufficient technique.
• Primarily interested in proving technical audit capability to clients or employers.

“If you have to look up what 1.4.11 Non-text Contrast requires before you can explain it, you are not ready for WAS — and that is fine. Start with CPACC.”

Difficulty and preparation time

Both exams are challenging, but in different ways:

• CPACC is wide. The difficulty is covering all the domains — disability models, AT, standards, and law — without leaving gaps. Candidates with a technical background often underestimate the legal and disability sections.
• WAS is deep. The difficulty is knowing the precise intent and testing methods for dozens of success criteria. Candidates who passed CPACC sometimes assume WAS will feel similar — it does not. It is a different kind of exam.

Certification	Typical preparation (with prior experience)	From scratch
CPACC	20–40 hours	70–100 hours
WAS	30–50 hours	Not recommended without CPACC-level knowledge first

Can I study for both at the same time?

Technically, yes. Practically, most people do better focusing on one at a time. The knowledge overlaps — WCAG principles, conformance, and basic AT knowledge appear in both — but the way you are tested is different. Splitting your attention risks underperforming on both.

The most common successful pattern is: CPACC → two to three months of practical work applying what you learned → WAS.

How this platform helps

A11yPrep’s flashcards and practice questions are aligned with the CPACC Body of Knowledge. The spaced repetition system is designed to cover the full breadth of CPACC domains — disabilities, standards, law, and AT — in the time window most candidates have. If you are aiming for WAS after CPACC, the foundation you build here carries directly into your technical preparation.