Accessibility Testing Methodology: WAS Practice Questions

Introduction: Why Testing Methodology Dominates the WAS Exam

If you're preparing for the Web Accessibility Specialist (WAS) certification from IAAP, one thing becomes immediately clear when you review the October 2024 Body of Knowledge: testing and evaluation is the heart of this exam. Domain 2 - Testing and Evaluation of Web Accessibility - accounts for a full 60% of your total score. That means if you're skimping on testing methodology in your WAS exam prep, you're leaving the majority of the exam underprepared.

This article delivers targeted WAS certification practice questions focused specifically on accessibility testing methodology, paired with in-depth explanations to reinforce your understanding. Whether you're taking your first WAS practice test or drilling a specific weak area, these questions are designed to mirror the complexity and style of real IAAP WAS exam items.

Unlike the foundational CPACC credential, the WAS is a deeply technical certification. If you're unsure which exam to tackle first, check out our comparison article on WAS vs CPACC: Which IAAP Accessibility Certification First? to align your learning path with your career goals. For those who are ready to go deep on testing methodology right now, let's dive in.

Domain 2 Deep Dive: Testing and Evaluation (60%)

The October 2024 IAAP Body of Knowledge organizes Domain 2 into several major competency areas. Understanding the scope of this domain is the first step in effective WAS exam study. The domain covers:

• Assistive Technology Testing - evaluating with screen readers (NVDA, JAWS, VoiceOver, TalkBack), switch access, magnification software, and voice control
• Manual Evaluation Methods - keyboard-only testing, focus order inspection, color contrast analysis, and cognitive walkthroughs
• Automated Evaluation - using tools like axe, WAVE, Lighthouse, and understanding their limitations
• Testing Methodology and Process - defining scope, selecting test cases, sampling strategies, and conformance testing
• Reporting - writing Accessibility Conformance Reports (ACRs), VPATs, issue severity ratings
• Remediation Strategies - prioritizing fixes, communicating with developers, re-testing after remediation

For a broader overview of exam structure and scoring, our WAS Certification Exam Guide: Format, Topics, Pass Rate and Tips is an essential companion resource.

15 WAS Practice Questions on Accessibility Testing Methodology

The following web accessibility specialist exam questions are designed to test your understanding of Domain 2 concepts at the depth required by the actual IAAP WAS exam. Read each question carefully before reviewing the explanations in the next section.

Questions 1-5: Automated and Manual Testing

Question 1. A development team runs an automated accessibility scan using the axe-core engine and receives zero violations. What should the accessibility specialist conclude?

1. The page is fully WCAG 2.2 conformant
2. Automated testing is complete; no further testing is needed
3. Automated testing has passed; manual and assistive technology testing must still be performed
4. The page passes EN 301 549 requirements

Question 2. Which of the following accessibility issues CANNOT be reliably detected by automated testing tools?

1. Missing alt attributes on images
2. Insufficient color contrast ratio
3. Whether an image's alt text accurately describes the image's content
4. Form inputs lacking associated labels

Question 3. When testing a single-page application (SPA) with dynamic content loaded via AJAX, what is the PRIMARY concern for an accessibility tester?

1. Whether the page uses semantic HTML5 elements
2. Whether focus management and status announcements are correctly implemented after dynamic updates
3. Whether the page has a valid DOCTYPE declaration
4. Whether the page loads within three seconds

Question 4. A tester is evaluating keyboard accessibility. Which sequence best describes a complete keyboard navigation test?

1. Tab through all interactive elements, verify visible focus indicators, confirm logical focus order, test all functionality without a mouse
2. Tab through the page once and check that no errors appear in the browser console
3. Use an automated tool to scan for tabindex values greater than 0
4. Verify that all links open in the same tab

Question 5. Which WCAG 2.2 success criterion is specifically relevant when a keyboard user finds that pressing Tab moves focus to an element but the focus indicator is not visible?

1. 1.4.3 Contrast (Minimum)
2. 2.4.7 Focus Visible
3. 2.4.11 Focus Appearance (new in WCAG 2.2)
4. Both B and C are relevant

Questions 6-10: Assistive Technology and Screen Reader Testing

Question 6. When testing with JAWS on Windows, which browser pairing is considered the standard recommended combination for WCAG conformance testing?

1. JAWS + Firefox
2. JAWS + Chrome
3. JAWS + Internet Explorer 11
4. JAWS + Safari

Question 7. A screen reader announces a button as "button" with no accessible name. What is the most likely cause and the correct WCAG failure?

1. The button has no href attribute; fails 2.4.4 Link Purpose
2. The button contains only an icon with no text alternative; fails 4.1.2 Name, Role, Value
3. The button uses the wrong HTML element; fails 1.3.1 Info and Relationships
4. The button color does not contrast sufficiently; fails 1.4.3 Contrast (Minimum)

Question 8. When using VoiceOver on macOS to test a data table, which VoiceOver behavior indicates the table is properly marked up?

1. VoiceOver reads all cell contents sequentially without headers
2. VoiceOver announces column and row header information when navigating individual cells
3. VoiceOver skips the table entirely
4. VoiceOver reads the table caption only

Question 9. A tester discovers that a modal dialog does not trap focus - pressing Tab from the last element in the dialog moves focus to elements behind the dialog. Which WCAG criterion is violated?

1. 1.3.2 Meaningful Sequence
2. 2.1.2 No Keyboard Trap (in reverse - focus escapes when it should not)
3. 2.1.1 Keyboard
4. 4.1.3 Status Messages

Question 10. Which assistive technology is MOST appropriate for evaluating whether a mobile web application meets WCAG 2.2 success criteria on iOS?

1. NVDA with Chrome
2. VoiceOver with Safari on iOS
3. JAWS with Edge
4. Narrator with Edge on Windows

Questions 11-15: Methodology, Reporting, and Remediation

Question 11. An organization needs to produce a formal report of WCAG 2.2 conformance for procurement purposes. What document format is most appropriate?

1. A GitHub issues list
2. An Accessibility Conformance Report (ACR) using the VPAT® template
3. A PDF of automated scan results
4. An internal bug tracking spreadsheet

Question 12. When determining the scope of an accessibility audit for a large e-commerce website, what is the most defensible sampling strategy?

1. Test only the homepage and contact page
2. Test all pages automatically and none manually
3. Select a representative sample including common page templates, high-traffic pages, and pages covering critical user journeys
4. Test only pages that have received user complaints

Question 13. When writing remediation recommendations, which approach best supports effective developer communication?

1. Describing barriers in legal language only
2. Providing specific code examples, the relevant WCAG success criterion, and the expected user impact
3. Listing only the WCAG criterion number without explanation
4. Sending developers a link to the full WCAG specification

Question 14. A site owner asks you to assign a severity rating to each issue found during an audit. Which factor is MOST important when determining issue severity?

1. How long the issue has existed in the codebase
2. The frequency of the page in the sitemap
3. The degree to which the issue blocks a user with a disability from completing a task
4. The complexity of the fix for the development team

Question 15. Under the European Accessibility Act (EAA), which of the following products and services must meet accessibility requirements by June 28, 2025?

1. Only government websites
2. Consumer products and services including e-commerce, banking, transport, and e-books
3. Only mobile applications developed after 2020
4. Only products sold to organizations with more than 500 employees

Detailed Answer Explanations

Answers 1-5

Answers 6-10

Answers 11-15

Key Testing Frameworks You Must Know

The IAAP WAS exam expects you to understand not just what to test, but how to systematically approach accessibility evaluation. Several frameworks underpin professional accessibility testing methodology.

WCAG-EM (Website Accessibility Conformance Evaluation Methodology)

WCAG-EM is W3C's official methodology for evaluating the accessibility of websites. It defines a five-step process: define scope, explore the website, select a representative sample, evaluate the sample, and report the findings. The WAS exam tests your knowledge of each step, particularly sample selection criteria and conformance reporting formats.

ACT Rules (Accessibility Conformance Testing)

ACT Rules provide standardized, machine-readable test rules that map directly to WCAG success criteria. Understanding ACT Rules helps WAS candidates understand why automated tools give specific results and how to interpret edge cases. The IAAP Body of Knowledge includes ACT Rules as a testable topic.

Manual vs. Automated Testing: What the Exam Tests

One of the most nuanced topics in the IAAP WAS exam is the relationship between automated and manual testing. The exam does not ask you to memorize tool interfaces - it tests your ability to reason about when and why each approach is appropriate.

Testing Approach	What It Detects	What It Misses	WCAG Areas
Automated Tools (axe, WAVE, Lighthouse)	Missing attributes, contrast ratios, structural errors, duplicate IDs	Meaningful alt text, logical focus order, cognitive usability, context-dependent failures	1.1.1, 1.4.3, 4.1.1, some 4.1.2
Manual Keyboard Testing	Focus trapping, skip links, logical tab order, custom widget behavior	Screen reader announcements, visual-only issues	2.1.1, 2.1.2, 2.4.3, 2.4.7
Screen Reader Testing	Accessible names, roles, states, live region announcements, reading order	Color contrast, layout issues	1.3.1, 4.1.2, 4.1.3, WAI-ARIA usage
Visual / Cognitive Inspection	Reading level, consistent navigation, error identification, instructions	Programmatic structure, AT compatibility	3.1.5, 3.2.3, 3.3.1, 3.3.2

For deeper practice on ARIA specifically - a critical sub-topic within both domains - explore our dedicated article on ARIA Roles and Attributes: WAS Exam Practice Questions.

Remediation Strategies and Reporting

The final cluster of Domain 2 competencies covers what happens after testing. The WAS exam expects candidates to understand how to communicate findings effectively and support teams in fixing issues.

Writing Effective Accessibility Reports

A professional accessibility report includes: issue title and location, steps to reproduce, WCAG success criterion violated, severity rating, user impact statement, and recommended fix with code examples. VPATs (Voluntary Product Accessibility Templates) follow a structured format that maps findings to WCAG 2.x, Section 508, and EN 301 549 criteria.

Prioritizing Remediation

Not all issues are equal. The WAS exam tests your understanding of prioritization frameworks: critical issues (blocking task completion for AT users) take highest priority, followed by serious issues (significant barriers), moderate issues (workarounds exist), and minor issues (low impact). This framework helps organizations allocate limited development resources effectively.

Study Tips for Testing Methodology Questions

Candidates who score highest on Domain 2 consistently report a hands-on study approach. Here's what works based on WAS exam prep best practices:

• Practice with real tools. Install NVDA (free), axe DevTools browser extension (free tier), and practice testing real websites. The exam tests conceptual understanding, which is reinforced by actual experience.
• Study AT pairings. Know which screen reader + browser combinations are current standards: NVDA+Chrome, JAWS+Chrome, VoiceOver+Safari (macOS/iOS), TalkBack+Chrome (Android).
• Map failures to criteria. For every WCAG 2.2 success criterion you study, ask: "How would I test this? What does a pass look like? What does a failure look like?"
• Practice writing bug reports. Write sample accessibility issues in the format: location → steps to reproduce → failure → criterion → severity → recommendation.
• Take WAS mock exams. Timed practice under exam conditions is irreplaceable. Visit our WAS practice test hub for free and premium question sets.

For a structured 40-80 hour study plan, our WAS Exam Study Guide: How to Prepare in 40-80 Hours walks you through exactly how to allocate your preparation time across both domains. And for a comprehensive question bank covering all WAS topics, check out the WAS Practice Test: Free Web Accessibility Specialist Questions 2026.

Frequently Asked Questions