Web Accessibility Specialist (WAS)

1. Review the Body of Knowledge (BoK): Download and study the IAAP WAS Body of Knowledge document, which outlines all four exam content domains and the specific competencies tested. This is your primary study guide.

1. Assess your prerequisites: Confirm you have practical experience with HTML, CSS, JavaScript, and assistive technologies (screen readers, keyboard navigation). If gaps exist, complete foundational web development or accessibility training first.

1. Study WCAG 2.x and WAI-ARIA: Work through the W3C's Web Content Accessibility Guidelines (WCAG 2.1/2.2) and WAI-ARIA specifications in detail, as these form the technical backbone of the exam.

1. Use IAAP-recommended study resources: Explore IAAP's official study guide, practice exams, and member-discounted training courses. Third-party resources such as Deque University, WebAIM, and the A11y Project are widely used by candidates.

1. Practice hands-on accessibility testing: Use assistive technologies (NVDA, JAWS, VoiceOver) and automated tools (axe, WAVE) to audit real websites. Practical experience is critical for the "Identify and Remediate" exam domains.

1. Apply for the exam: Create an IAAP account at accessibilityassociation.org, complete the application, attest to your professional experience or education, and pay the exam fee ($385 for non-members, reduced for IAAP members).

1. Schedule and sit the proctored exam: Book your online proctored exam session through IAAP's testing platform. The exam is 75 multiple-choice questions in 2 hours.

1. Earn and maintain your credential: Upon passing, download your digital badge and add it to LinkedIn. Track your 45 CEUs over the 3-year renewal cycle to maintain your certification.

The WAS exam is organized around four core content domains, each reflecting a distinct phase of accessibility work in professional practice.

Domain 1 – Creating Accessible Web Content: This domain covers the technical skills required to build accessibility into web content from the ground up. Topics include proper use of semantic HTML, ARIA roles and attributes (WAI-ARIA), accessible forms, keyboard operability, focus management, color contrast, multimedia alternatives (captions, transcripts, audio descriptions), and responsive/adaptive design considerations. Candidates are expected to know how to implement WCAG 2.x success criteria at the code level.

Domain 2 – Identify Accessibility Issues: This domain tests the ability to detect accessibility barriers using a combination of automated tools (such as axe, WAVE, or Lighthouse) and manual testing techniques, including keyboard-only navigation and screen reader testing (NVDA, JAWS, VoiceOver, TalkBack). Candidates must understand the limitations of automated testing and know when manual evaluation is required.

Domain 3 – Remediate Accessibility Issues: Building on identification skills, this domain assesses the ability to prioritize, document, and fix accessibility defects. Candidates must understand how to communicate issues to development teams, recommend appropriate code-level fixes, and verify that remediations meet WCAG conformance requirements.

Domain 4 – Conformance Evaluation: This domain covers formal accessibility auditing methodologies, including the W3C's Website Accessibility Conformance Evaluation Methodology (WCAG-EM). Candidates must understand how to scope an evaluation, select representative samples, document findings, and produce a conformance report. Knowledge of relevant legal frameworks (ADA, Section 508, EN 301 549) and their relationship to WCAG is also assessed.

The WAS certification has established itself as the leading technical credential in the digital accessibility space since its launch in 2016. As of the mid-2020s, IAAP reports thousands of certified professionals globally, with the WAS being the most technically rigorous of IAAP's credential offerings. Demand has grown substantially in response to increasing legal enforcement of web accessibility requirements — particularly ADA Title III litigation in the United States, the European Accessibility Act (EAA) mandating compliance by 2025, and ongoing enforcement of Section 508 for federal contractors. Organizations under legal pressure to demonstrate accessibility competence increasingly look for WAS-certified staff or contractors as evidence of due diligence.

In terms of market positioning, WAS occupies the technical practitioner tier of the accessibility credential landscape. It is vendor-neutral and technology-agnostic, making it applicable across all web stacks and platforms. Its closest companion credential is the CPACC (Certified Professional in Accessibility Core Competencies), which covers conceptual and policy knowledge, while WAS focuses on hands-on technical implementation. Together, they form the CPWA (Certified Professional in Web Accessibility), IAAP's combined credential. The WAS is widely recognized by major technology employers, federal agencies, and accessibility consulting firms, and is increasingly listed as a preferred or required qualification in job postings for accessibility engineer and auditor roles.

Regional adoption is strongest in North America and Europe, where legal frameworks create the most direct compliance pressure. Growth in Asia-Pacific is emerging, particularly in Australia (DDA compliance) and Japan. The broader trend toward inclusive design, WCAG 2.2 adoption, and AI-generated content accessibility is expanding the relevance of WAS beyond traditional web development into product management, content strategy, and DevOps roles. The main competitive pressure comes from employer-specific programs (such as DHS Trusted Tester) and free/low-cost training platforms, but WAS remains the most widely recognized third-party credential for technical web accessibility expertise.

The Web Accessibility Specialist (WAS) certification was launched in 2016 by the International Association of Accessibility Professionals (IAAP), a nonprofit professional association founded in 2014 to formalize and advance the accessibility profession globally. IAAP was established in response to a recognized gap: while web accessibility standards (WCAG) had existed since 1999, there was no standardized way for professionals to demonstrate verified competency in implementing them. The WAS was developed through a rigorous job task analysis process involving accessibility practitioners from across the industry, resulting in a Body of Knowledge that maps directly to real-world accessibility work.

Since its launch, the WAS has undergone periodic updates to its Body of Knowledge to reflect evolving standards, including the incorporation of WCAG 2.1 (2018) and WCAG 2.2 (2023) criteria, as well as expanded coverage of WAI-ARIA and mobile accessibility. IAAP also introduced the CPWA (Certified Professional in Web Accessibility) as a combined credential for professionals who hold both the CPACC and WAS, recognizing that the most effective accessibility professionals need both conceptual and technical expertise. The program has grown from a North American focus to a genuinely global credential, with candidates and certified professionals in over 50 countries, reflecting the worldwide expansion of web accessibility legislation and inclusive design mandates.