100+ Free WAS Practice Questions

Prepare for the IAAP Web Accessibility Specialist (WAS) exam with instant access — no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately

Not published by IAAP Pass Rate

100+ Questions

100% Free

Loading practice questions...

Same family resources

Explore More IAAP Accessibility Professional Certifications

Continue into nearby exams from the same family. Each card keeps practice questions, study guides, flashcards, videos, and articles in one place.

IAAP Accessible Document Specialist (ADS)

Practice Questions100 questions

IAAP Certified Professional in Accessibility Core Competencies (CPACC)

Practice Questions100 questions

2026 Statistics

Key Facts: WAS Exam

75 Qs

Exam Questions

Multiple choice

2 hrs

Time Limit

Closed book

600/800

Passing Score

Scaled score

$555

Exam Fee

$455 for IAAP members

40/40/20

Domain Weights

Official outline

3-5 yrs

Experience Expected

Hands-on web a11y

The WAS exam has 75 multiple-choice questions with a 2-hour time limit in a closed-book, computer-based format delivered by Pearson VUE. The passing mark is a scaled score of 600 on a 200-800 scale. The exam fee is $555 standard, $455 for IAAP members, and $225 for Emerging and Developing Economy candidates. Content is weighted 40% Creating Accessible Web Content, 40% Identify Accessibility Issues, and 20% Remediate Accessibility Issues, covering WCAG 2.0/2.1/2.2, WAI-ARIA, EN 301 549, and assistive technology testing. IAAP expects 3-5 years of hands-on web accessibility experience.

Sample WAS Practice Questions

Try these sample questions to test your WAS exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1What does the "first rule of ARIA" advise developers to do?

A.Use native HTML elements with built-in accessibility semantics before adding ARIA roles, states, or properties

B.Add a role attribute to every interactive element so assistive technologies can identify it

C.Apply aria-label to every element that contains visible text

D.Avoid ARIA entirely because it is no longer valid in HTML5

Explanation: The first rule of ARIA is to prefer native HTML elements (such as <button>, <a>, <input>) because they carry built-in roles, keyboard behavior, and focusability. ARIA should only fill gaps that native HTML cannot express. Adding ARIA on top of working native semantics often creates conflicts or redundant announcements.

2Which HTML element provides keyboard focusability, Enter and Space activation, and correct role exposure to assistive technologies with no additional scripting?

A.<div onclick="save()">Save</div>

B.<span role="button">Save</span>

C.<button type="submit">Save</button>

D.<a href="#" onclick="save()">Save</a>

Explanation: A native <button> is focusable by default, activates with both Enter and Space, and is exposed with the button role automatically. Custom elements require tabindex, keyboard event handlers, and ARIA to approximate even part of this behavior. This is why native elements are the foundation of accessible interfaces.

3Which WCAG conformance level do most accessibility laws, regulations, and organizational policies require as their target?

A.Level A

B.Level AA

C.Level AAA

D.There are no levels; a site either conforms or it does not

Explanation: Level AA is the standard target referenced by regulations such as the ADA Title II rule, Section 508, EN 301 549, and the European Accessibility Act, because it balances meaningful accessibility with feasibility across most content. Level A alone leaves significant barriers, while Level AAA is not achievable for all content types.

4Given <img src="logo.png" alt="Acme Corporation" aria-label="Acme home page">, what accessible name will assistive technologies compute for the image?

A.Acme Corporation

B.logo.png

C.Acme Corporation Acme home page

D.Acme home page

Explanation: In the accessible name computation, author-supplied ARIA labeling wins over native labeling: aria-labelledby takes precedence over aria-label, which in turn takes precedence over native mechanisms such as the alt attribute. Here aria-label is present, so the name is "Acme home page" and the alt text is ignored.

5A purely decorative border image is embedded with an <img> element. What is the correct way to make screen readers ignore it?

A.Remove the alt attribute entirely

B.Give it an empty alt attribute: alt=""

C.Give it alt="decorative border image"

D.Wrap it in an element with aria-live="off"

Explanation: An empty alt attribute (alt="") signals that the image is decorative and should be skipped by assistive technologies, satisfying SC 1.1.1 for non-informative content. The alt attribute must still be present so the image is not announced by its filename instead.

6Why is <div class="btn" onclick="save()">Save</div> inaccessible to keyboard-only users by default?

A.The onclick attribute is not valid on div elements

B.Screen readers refuse to announce the contents of div elements

C.A div is not focusable and click handlers do not fire from the keyboard

D.The text "Save" must be wrapped in a <label> element to be activated

Explanation: Generic containers like div are not in the tab order and have no built-in keyboard interaction, so a click handler is only reachable with a mouse. Making this pattern accessible requires tabindex="0", a button role, and Enter/Space key handlers — or simply using a native <button>, which is the recommended fix.

7According to the ARIA Authoring Practices Guide tabs pattern, how should keyboard users move focus among the tabs in a tab list?

A.With the Left and Right Arrow keys, while the Tab key moves focus from the tab list into the tab panel

B.By pressing the Tab key repeatedly to cycle through every tab one at a time

C.By pressing Enter to enter navigation mode and then using the arrow keys

D.Each tab must be reached only through sequential Tab presses so the order stays predictable

Explanation: The APG tabs pattern treats the tab list as a composite widget: Left/Right Arrow keys move focus between tabs (typically with roving tabindex and aria-selected updates), and a single Tab press moves focus out of the tab list into the active panel. This keeps the tab list to one stop in the page's Tab sequence.

8Which set of behaviors describes correct focus management for a modal dialog?

A.Focus stays on the triggering button while the dialog opens so the user keeps their place

B.Focus moves into the dialog, and pressing Tab at the last element leaves the dialog open but moves focus to the page behind it

C.Focus is not moved at all; users can press Tab until they reach the dialog

D.Focus moves into the dialog on open, is contained within it while open, and returns to the triggering element on close

Explanation: A modal dialog must receive focus when it opens (usually on the dialog container or its first focusable element), trap Tab and Shift+Tab within the dialog while it is open, and restore focus to the element that opened it when closed. Without these steps, keyboard and screen reader users can lose context or interact with obscured background content.

9What minimum target size does WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum) require for pointer inputs, absent an exception?

A.44 by 44 CSS pixels

B.24 by 24 CSS pixels

C.16 by 16 CSS pixels

D.48 by 48 CSS pixels

Explanation: WCAG 2.2 SC 2.5.8 (Level AA) requires pointer targets to be at least 24 by 24 CSS pixels, with exceptions such as inline targets in sentences, user-agent-controlled sizes, essential presentation, and an equivalent 24-pixel spacing circle. The older 44 by 44 pixel figure comes from the Level AAA SC 2.5.5 and from platform guidelines, not from 2.5.8.

10A container with aria-hidden="true" contains a focusable link. What problem does this create?

A.None; aria-hidden is ignored by screen readers when content is focusable

B.None; aria-hidden automatically removes descendants from the tab order

C.The content is hidden from the accessibility tree but remains keyboard-focusable, so focus can land on content that assistive technologies cannot perceive

D.aria-hidden is invalid on container elements and will be stripped by the browser

Explanation: aria-hidden="true" removes an element and its descendants from the accessibility tree, but it does not change keyboard focusability. A focusable element inside an aria-hidden subtree creates a 'ghost stop': keyboard users can land on it, but screen reader users hear nothing. The rule is that aria-hidden must never be used on focusable content or on ancestors of focusable content.

About the WAS Exam

The IAAP Web Accessibility Specialist (WAS) is an intermediate-level technical certification from the International Association of Accessibility Professionals for people who design, develop, implement, evaluate, or manage accessible web-based content. It validates the ability to recognize and identify accessibility issues in programmatic content, explain what is missing or incorrect, apply WCAG 2.0/2.1/2.2 and WAI-ARIA, and test with assistive technologies. The closed-book, computer-based exam has 75 multiple-choice questions in 2 hours and is delivered by Pearson VUE. Holding both the WAS and the CPACC awards IAAP's highest credential, the Certified Professional in Web Accessibility (CPWA).

Questions

75 scored questions

Time Limit

2 hours

Passing Score

600 out of 800 (scaled score; scale runs 200-800)

Exam Fee

$555 ($455 members; $225 EDE) (IAAP (delivered by Pearson VUE))

WAS Exam Content Outline

40%

Creating Accessible Web Content

WCAG 2.x standards, WAI-ARIA, accessible JavaScript, APG widget patterns, product life cycle integration, and compatibility with user strategies

40%

Identify Accessibility Issues

User-needs analysis, WCAG conformance determination, automated testing tools, assistive technology testing, and end-user impact evaluation

20%

Remediate Accessibility Issues

Communicating issues, prioritizing by severity, and recommending remediation strategies and techniques

How to Pass the WAS Exam

What You Need to Know

Passing score: 600 out of 800 (scaled score; scale runs 200-800)
Exam length: 75 questions
Time limit: 2 hours
Exam fee: $555 ($455 members; $225 EDE)

Keys to Passing

Complete 500+ practice questions
Score 80%+ consistently before scheduling
Focus on highest-weighted sections
Use our AI tutor for tough concepts

WAS Study Tips from Top Performers

1Learn WCAG 2.2 success criteria by conformance level — know which requirements are Level A (keyboard access, no keyboard trap, name/role/value), Level AA (contrast minimum 4.5:1, focus visible, target size minimum 24x24), and Level AAA

2Apply the first rule of ARIA: prefer native HTML semantics over ARIA; only add roles, states, and properties when native elements cannot do the job, and never change native semantics away from their defaults

3Master accessible name computation order (aria-labelledby, then aria-label, then native labeling such as label elements and alt attributes) — name/role/value questions appear throughout the exam

4Practice focus management scenarios: modal dialogs must trap focus and return it on close, dynamic content changes need live regions or focus moves, and skip links support keyboard users

5Know the major assistive technology pairings — JAWS and NVDA on Windows, VoiceOver on macOS/iOS with Safari, TalkBack on Android — and remember automated tools catch only a fraction of issues, so manual and AT testing are essential

Frequently Asked Questions

What score do I need to pass the WAS exam?

The WAS exam is scored on a scale of 200 to 800, and the passing mark is a scaled score of 600. IAAP reports scaled outcomes rather than percentage scores, so 600 does not convert directly into a raw percentage of the 75 questions. IAAP does not publish official pass rates.

How technical is the WAS exam?

The WAS is IAAP's intermediate technical credential. It is not a coding exam, but you must recognize accessibility issues in programmatic content — semantic HTML, WAI-ARIA roles, states, and properties, accessible name computation, keyboard interaction, focus management, and dynamic content — and explain what is missing or incorrect. IAAP expects 3-5 years of first-person, hands-on experience in web accessibility work.

How much does the WAS exam cost?

The standard WAS exam fee is $555 USD. IAAP members pay $455, and candidates from Emerging and Developing Economy (EDE) countries pay $225. Retake fees apply per attempt, with discounted member and EDE rates available once within one year of the first attempt. All fees are non-refundable.

What is the format of the WAS exam?

The WAS is a closed-book, computer-based exam with 75 multiple-choice questions and a 2-hour time limit. It is delivered at Pearson VUE test centers in over 130 countries or via Pearson OnVUE remote proctoring. No reference materials, calculators, or devices are permitted during the exam.

How does the WAS relate to the CPWA credential?

The Certified Professional in Web Accessibility (CPWA) is IAAP's highest credential and is awarded automatically to candidates who hold both the CPACC and the WAS while both are valid. There is no separate CPWA exam — you earn it by passing and maintaining the two underlying certifications.

How do I maintain the WAS certification?

The WAS is valid for 3 years. Renewal requires 35 Education Credits directly related to the WAS Content Outline plus a renewal form. The renewal fee is waived for IAAP members in good standing; non-members pay $200 ($75 for EDE candidates). You do not retake the exam unless the certification lapses.