Study the three official domains (40% creating accessible solutions, 40% identifying issues, 20% remediating them), rehearse decisions between competing techniques rather than reciting rules, and plan logistics around the handbook's scoring, session, and renewal rules. Anything this guide cannot verify, such as question count and fees, comes straight from IAAP's own pages.
What the WAS credential covers
The IAAP Web Accessibility Specialist designation certifies an intermediate level of web accessibility skill, and its Body of Knowledge (BoK) lists the categories the exam draws from.
The BoK is a starting point for study, not an exhaustive account of every question, and IAAP states plainly that using it does not guarantee a pass. It describes web accessibility theory, principles, and fundamentals pitched at an intermediate level of skill and experience.
The designation expects three to five years of hands-on work in or with a web accessibility team, and your application must document skills linked to the certification's domains. Content comes from WCAG 2.0, 2.1, and 2.2 plus the European standard EN 301 549. Note one scope boundary: user agent accessibility guidelines (UAAG), which cover browsers and media players, sit outside the WAS certification.
Official sources: IAAP Web Accessibility Specialist Body of Knowledge, version 2.3, October 2024 — Content outline, domains one to three; IAAP Professional Certification Handbook, January 2026 Edition #2 — Applications, exam rules, results, retakes, and renewal sections
The three tested domains at a glance
The exam splits into three domains: 40% creating accessible web solutions, 40% identifying issues, and 20% remediating them.
The table below compresses the official content outline. Treat it as a map, not a substitute: the BoK expands each area into study tasks and resource lists, and IAAP links the current outline from the WAS pages. The outline's subheadings are your preparation priorities; the official document is where the exhaustive detail lives.
| Domain | Weight | Focus |
|---|---|---|
| Domain One: Creating accessible web solutions | 40% | WCAG 2.2, WAI-ARIA 1.2, ATAG 2.0, and EN 301 549; semantic HTML, custom controls, focus and state management; strategies of users with different disabilities |
| Domain Two: Identifying accessibility issues | 40% | Conformance checking, testing with assistive technologies, keyboard and touch testing, automated tools and ACT Rules, accessibility quality assurance |
| Domain Three: Remediating accessibility issues | 20% | Prioritizing and communicating issues, fixes versus redesign, and accessibility in procurement and conformance reports |
Official sources: IAAP Web Accessibility Specialist Body of Knowledge, version 2.3, October 2024 — Content outline, domains one to three
Applying, scheduling, and accommodations
You apply through IAAP, pay by the session deadline, then schedule with Pearson; the handbook lists the exact sequence.
Applications are made on the IAAP site, not Pearson's. After the certification team approves your application, which can take up to three business days, you pay and then receive scheduling instructions. Applications and education-credit submissions must be completed in English, though supporting documents may be in any language.
Exam sessions run six times a year, each with its own application, payment, and scheduling deadlines. Payment dates close one week after applications close, and late invoice payments push your application to the next session. Three delivery options exist, and candidates cannot use Pearson remote proctoring in China, Cuba, Iran, North Korea, Russia, the Russian Federation, Sudan, or Syria.
- Create an IAAP account and submit your application through the Certification Portal.
- Choose a delivery option: Pearson remote proctoring, a Pearson test center, or a hosted exam event.
- Pay by the session's payment due date; scheduling instructions follow within about five business days of payment.
- Request accommodations during the application. IAAP works on an honor system and needs no disability proof, but test-center accommodations beyond extra time need roughly ten business days to arrange.
- Applications are often rejected when experience prerequisites or documented roles are missing, so align your application with the BoK's domain descriptions.
Official sources: IAAP Professional Certification Handbook, January 2026 Edition #2 — Applications, exam rules, results, retakes, and renewal sections
Scoring, results, and retakes
IAAP reports a scale score from 200 to 800 with a passing mark of 600, plus domain-level feedback rather than percentage scores.
Results appear in your Certification Portal four to six weeks after the exam session ends, not on the exam day itself. You will not see which answers were right or wrong; feedback comes as above-standard, near-standard, or below-standard per domain.
If you do not pass, retake rules apply: you must wait two exam sessions before reapplying, and you can retake at a reduced rate once within a year of your first attempt, up to two retakes in that year. Retakes require a new application for the session you target. If you want a second look at your score, a rescoring costs $50 and a manual review $150, completed within thirty business days. Exam fees are non-refundable, and canceling does not entitle you to a refund.
- Wait two exam sessions before reapplying after a failed attempt.
- One reduced-rate retake is available within a year of the first attempt, up to two retakes total in that year.
- Rescoring costs $50; a manual review costs $150.
Official sources: IAAP Professional Certification Handbook, January 2026 Edition #2 — Applications, exam rules, results, retakes, and renewal sections
Success criteria, sufficient techniques, and failures
Success criteria state the testable outcome, sufficient techniques show one way to meet it, and failures document patterns that break it. Techniques themselves are not normative.
WCAG separates what must be true from how you might make it true. A criterion defines the outcome; a sufficient technique is one documented path that satisfies it; an advisory technique goes beyond the minimum as optional best practice; a failure is a specific pattern that causes the criterion to be unmet. The techniques are vetted by accessibility professionals, but they are informative, not required, and they age: the BoK notes some sufficient techniques now look dated as better implementations emerge.
This distinction pays off in scenario questions. An answer option can invoke a technique name incorrectly, and you only catch that if you know what outcome the criterion actually demands. Practicing failures trains a complementary skill: looking at a snippet and naming the concrete harm, rather than vaguely sensing something is wrong.
Practice exercise
A WCAG supporting document says a particular markup pattern, when present, satisfies a success criterion. A second document describes a coding mistake that makes that same criterion fail. Classify each document, and state whether an author must use the first document's pattern to conform.
Show answer
The first is a Sufficient Technique and the second is a Failure. The author does not have to use that pattern: techniques are non-normative, so conformance is judged against the success criterion itself, and any accessibility-supported way of meeting it works.
The BoK defines the three technique kinds exactly this way and states that published techniques are not normative; the WCAG 2.2 recommendation likewise describes sufficient and advisory techniques as informative. This is a pure classification from the sourced definitions, which is why the mandatory-versus-optional part of the answer follows.
- Success criterion: the testable, technology-neutral outcome.
- Sufficient technique: one documented way to satisfy it, not the only way.
- Advisory technique: optional best practice beyond the requirement.
- Failure: a specific pattern that causes the outcome to be unmet.
Official sources: IAAP Web Accessibility Specialist Body of Knowledge, version 2.3, October 2024 — Content outline, domains one to three; Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation — Introduction, layers of guidance, comparison with WCAG 2.1, new features
Choosing native HTML or ARIA
Native HTML elements bring roles, states, and keyboard behavior with them; ARIA exists to fill in missing semantics for dynamic content and custom widgets. When a standard element fits, use it.
The BoK makes the decision rule explicit: know when and why to use WAI-ARIA 1.2, and when to use standard HTML instead. ARIA supplies attributes that fill missing semantics, particularly for dynamic content and custom widgets where no native equivalent exists, and it must be used carefully because the behavior still has to be implemented and verified. The ARIA Authoring Practices Guide documents how roles, states, and properties apply to common design patterns, including the keyboard support those patterns expect.
Build the contrast with paired examples. An accordion built from headings and native elements gives you structure for free; a genuinely custom widget, such as a complex grid, is where ARIA becomes necessary along with an interaction pattern you must implement. The exam-relevant skill is recognizing which situation you are in.
Practice exercise
Assume a control behaves exactly like a standard push button that can be toggled: it activates with a click or keyboard, and it carries a pressed or not-pressed state. Two implementations are proposed: (a) a div element with role="button", a tabindex attribute, and a click handler; (b) a native button element that toggles the aria-pressed attribute. Which implementation matches the guidance for when ARIA is appropriate, and why?
Show answer
Option (b). The native button already provides the button role and keyboard activation, so nothing is missing for ARIA to fill; adding aria-pressed to it expresses the toggle state. Rebuilding a button from a div and ARIA means reimplementing behavior the platform would supply, which the guidance says to avoid when standard HTML fits.
The BoK directs candidates to know when to use standard HTML instead of WAI-ARIA, and describes ARIA as filling in missing semantics for dynamic content and custom widgets. The stated assumption that the control behaves like a standard push button is what makes the native element the correct fit; with genuinely custom behavior, the analysis would differ.
Official sources: IAAP Web Accessibility Specialist Body of Knowledge, version 2.3, October 2024 — Content outline, domains one to three; ARIA Authoring Practices Guide (APG), W3C WAI — Home page: patterns, landmarks, accessible names and descriptions
Knowing your WCAG versions
Study WCAG 2.2 as the current target, but understand what 2.1 and 2.2 each added and that 2.2 removed one criterion.
The BoK expects you to know the release history: WCAG 2.0 in 2008, 2.1 in 2018, and 2.2 in 2023. WCAG 2.1 added success criteria for new input modes such as touch and speech, plus more coverage of low vision and cognitive disabilities. WCAG 2.2 added requirements on authentication, form entry, and help, and keyboard- or pointer-focused criteria such as Focus Not Obscured, Target Size, and Dragging Movements.
One structural change matters for conformance questions: WCAG 2.2 removed success criterion 4.1.1 Parsing. Content conforming to 2.2 also conforms to 2.0 and 2.1, but authors bound by policy to the older versions may still need to test and report 4.1.1. WCAG 3.0 is in early development and likely years from completion, so do not expect its conformance model on this exam.
Official sources: IAAP Web Accessibility Specialist Body of Knowledge, version 2.3, October 2024 — Content outline, domains one to three; Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation — Introduction, layers of guidance, comparison with WCAG 2.1, new features
Matching testing methods to defects
Domain Two expects you to combine methods: automated tools, manual keyboard and assistive technology passes, and code-level inspection. Each catches a different defect class, so no single pass is complete.
The BoK dedicates several Domain Two sections to this: testing with assistive technologies for different user groups, keyboard testing, content and usability testing, ACT Rules, and automated tools, plus WCAG-EM for evaluation methodology. The table below is an editorial study aid built on that structure; use it to answer questions of the form 'which verification step is missing?'
It also works as a review index. After finishing a topic, ask which testing row would catch a defect in that topic and which rows would not. An unlabeled form field is caught by several methods, while a tab order that only makes sense visually is mainly a manual keyboard finding.
| Method | Tends to catch | Tends to miss | Best use |
|---|---|---|---|
| Automated scanning | Missing labels, absent alt text, some structural and markup problems | Anything needing judgment: focus order, announcement clarity, meaningful alt text | Fast baseline sweep and regression checks |
| Keyboard-only inspection | Traps, missing focus indicators, illogical tab order, unreachable controls | Whether announcements make sense when read aloud | Verifying the interaction of every custom widget |
| Code inspection | Incorrect roles, states, and name associations before users see them | Real-world usability of a technically correct component | Root-causing issues found by other methods |
| Assistive technology pass | End-to-end announcements, state changes, comprehension | Technology combinations you did not test | Final confirmation that the experience works |
Official sources: IAAP Web Accessibility Specialist Body of Knowledge, version 2.3, October 2024 — Content outline, domains one to three
Keeping the credential after you pass
WAS certification is valid for three years and renewing requires 35 education credits documented in the certification portal.
Credits come from three categories: professional development (the primary route, such as qualifying webinars, workshops, and courses aligned with the content outline), sharing your knowledge (unpaid, structured teaching or writing aimed at other accessibility professionals), and structured volunteering. Short content under 15 minutes earns nothing, repeats do not count, and podcasts and books are currently not approved.
Timing matters as much as totals: credits must be earned before the expiration date, and a 30-day grace period afterwards lets you complete the renewal form without retaking the exam. With an active IAAP membership maintained for the full three-year period, renewal costs nothing; otherwise a renewal fee applies.
Practice exercise
During one renewal cycle you attend two qualifying professional-development webinars aligned with the WAS content outline: one runs 50 minutes, the other 90 minutes. How many credits do these two activities earn, and what fraction of the WAS three-year requirement do they cover?
Show answer
The 50-minute webinar falls in the 45-60 minute band and earns 1.0 credit. The 90-minute webinar falls in the 76-90 minute band and earns 1.5 credits. Together they earn 2.5 credits, which is 2.5 of the 35 required, or one fourteenth of the three-year requirement.
The handbook's calculation table assigns 1.0 credit to 45-60 minutes and 1.5 credits to 76-90 minutes, and the WAS requirement is 35 credits per three-year period. The arithmetic is 1.0 + 1.5 = 2.5 and 2.5/35 = 1/14. Check that each activity otherwise qualifies: content must run at least 15 minutes, align with the content outline, and count only the first time viewed.
Official sources: IAAP Professional Certification Handbook, January 2026 Edition #2 — Applications, exam rules, results, retakes, and renewal sections
A study sequence and final checklist
Work from the official BoK as your topic map, rehearse decisions rather than reciting rules, and confirm logistics on IAAP's own pages before your session.
One optional routine that fits the material: rotate through the domains in short cycles, pairing each topic with a decision you write down and justify. For a component, decide native element versus ARIA and name the governing criterion. Then test it three ways in your own authorized environment: keyboard only, name/role/value inspection, and a screen reader pass. Depth with one screen reader teaches you what announcements should sound like; you can then reason about other combinations. Adjust the pace to your schedule rather than skipping phases.
This routine is study advice, not an official requirement, and it cannot predict your result. Before exam day, close out the administrative loop: application approved, payment made, session selected, delivery option and accommodations arranged, and the Pearson system check completed if you are testing remotely.
- Download the current Body of Knowledge and work its study tasks domain by domain.
- Use How to Meet WCAG 2.2 as your filterable quick reference for criteria and techniques.
- Log one written decision per studied component: the choice made, the governing concept, and the alternative rejected.
- Verify question count, duration, and fees on IAAP's official WAS pages, since the BoK and handbook do not state them.
- Book through the Certification Portal and keep payment and scheduling deadlines for your chosen session.
Official sources: IAAP Web Accessibility Specialist Body of Knowledge, version 2.3, October 2024 — Content outline, domains one to three; IAAP Professional Certification Handbook, January 2026 Edition #2 — Applications, exam rules, results, retakes, and renewal sections
Official sources
Facts checked against official documents: