The IAAP Web Accessibility Specialist (WAS) certification covers the technical skills needed to evaluate and remediate web content against WCAG. The exam targets practitioners who work directly with code, audit reports, and assistive technology behavior. Topics include WCAG 2.1 success criteria interpretation, ARIA roles and properties, semantic HTML, keyboard interaction patterns, screen reader behavior, and remediation methods across common content types. WAS is positioned as the credential for people doing hands-on accessibility work, not policy or program management. It sits alongside CPACC in the IAAP framework, with CPACC covering foundational knowledge and WAS covering technical practice.
| Area | Detail |
|---|---|
| Full name | Web Accessibility Specialist |
| Issuing body | International Association of Accessibility Professionals (IAAP) |
| Focus | Technical evaluation and remediation of web content |
| Primary standard | WCAG 2.1 Level A and AA |
| Format | Multiple-choice exam, proctored online or in person |
| Audience | Developers, auditors, QA engineers, accessibility consultants |
What is the IAAP WAS certification?
WAS is a technical credential from IAAP that signals a person can evaluate web content for WCAG conformance and recommend accurate remediation. It is not a program-level certification. It is a practitioner credential.
The exam draws from a published Body of Knowledge that IAAP updates periodically. Candidates are expected to know WCAG success criteria by number, understand the intent behind each one, and apply them to real code patterns.
Core content areas the exam covers
The WAS Body of Knowledge organizes content into a few practical domains. Each one maps to work an auditor or accessibility developer does day to day.
Creating accessible web content using WCAG. Applying success criteria to text, images, forms, tables, multimedia, and structure.
Identifying accessibility issues using WCAG. Evaluating existing pages against Level A and AA criteria with code inspection and assistive technology.
Remediating accessibility issues using WCAG. Recommending fixes that meet the success criteria without introducing new issues.
Within those domains, the exam evaluates knowledge of semantic HTML, ARIA 1.1, keyboard interaction, focus management, color and contrast, name and role exposure, and how assistive technology interprets the DOM.
WCAG knowledge evaluated in depth
WAS candidates need more than familiarity with WCAG. The exam expects you to know which criterion applies to a given issue and why.
Examples of what you should be able to do: identify the correct success criterion for a missing form label (1.3.1 or 4.1.2 depending on context), distinguish between 1.4.3 Contrast (Minimum) and 1.4.11 Non-text Contrast, apply 2.4.7 Focus Visible and 2.4.11 Focus Not Obscured correctly, and recognize when 2.1.1 Keyboard versus 2.1.2 No Keyboard Trap is the right reference.
The exam favors precision. Two issues that look similar may map to different criteria, and the credential rewards practitioners who understand the distinction.
ARIA and assistive technology
A meaningful portion of the exam covers ARIA. Candidates should know the difference between roles, states, and properties, when ARIA is appropriate versus when native HTML is the better choice, and how common patterns like menus, dialogs, and tabs are constructed.
Assistive technology knowledge is also evaluated. Expect questions about how screen readers announce headings, landmarks, form controls, and live regions. NVDA, JAWS, and VoiceOver behavior all fall within scope.
Remediation methods
The remediation portion covers how to correct issues identified during an evaluation. This includes writing accurate alternative text, fixing heading order, restructuring forms for proper label association, and choosing between native elements and ARIA patterns.
The exam does not evaluate a specific framework or library. It covers the underlying accessibility principles that apply regardless of the tech stack.
Who the WAS certification is for
WAS suits people who write code, conduct audits, or validate fixes. Developers building accessible components, QA engineers evaluating products, and consultants delivering audit reports all benefit from the credential.
It is less useful for policy writers, program managers, or procurement teams. Those roles align more closely with CPACC, the foundational IAAP credential.
How WAS compares to other accessibility credentials
CPACC covers disability concepts, standards, and universal design at a conceptual level. WAS goes deeper on the technical side of web content. The two are designed to complement each other, and many practitioners earn both to qualify for the CPWA designation.
Outside of IAAP, the DHS Trusted Tester certification covers a structured evaluation methodology rooted in Section 508. Trusted Tester is procedural. WAS is principles-based. Both have value, but they cover different skills.
Frequently Asked Questions
Does the IAAP WAS certification qualify me to conduct accessibility audits?
The credential signals technical competence and is widely recognized in procurement and hiring. Many auditors hold WAS, and clients often look for it. That said, conducting accurate audits also takes practice with real products and audit report writing, which the exam does not directly evaluate.
What is the difference between IAAP WAS and CPACC?
CPACC is the foundational credential covering disability awareness, accessibility standards, and universal design principles. WAS is the technical credential covering WCAG application, ARIA, and remediation. CPACC is broader. WAS is deeper on web technology.
Which WCAG version does the WAS exam use?
The current exam targets WCAG 2.1 Level A and AA. IAAP updates the Body of Knowledge as standards mature, so candidates should confirm the current version on the IAAP site before preparing.
Is WAS recognized by employers and clients?
Yes. WAS is one of the most recognized technical accessibility credentials in the industry. It appears frequently in job descriptions for accessibility engineers, consultants, and auditors, and procurement teams often reference it when evaluating vendors.
How long does it take to prepare for the WAS exam?
Preparation time varies by background. Practitioners already working in accessibility full time often prepare in a few months. Developers new to WCAG typically need longer to work through the Body of Knowledge and practice with assistive technology.
WAS rewards people who have done the work. The exam is not a shortcut into the field, but for practitioners already evaluating and remediating web content, it puts a recognized credential next to the skill.
Looking for accessibility professionals who hold the WAS credential? Contact AccessibilityBase to browse the directory.