---
title: 'Knowledge check | Accessibility Testing Tutorial: WCAG 2.2'
description: Nine questions on the decisions that come up in real accessibility testing
  work. Each answer has a short explanation, so a wrong answer points you back to…
source_url:
  html: https://testingbot.com/resources/courses/accessibility-testing/knowledge-check
  md: https://testingbot.com/resources/courses/accessibility-testing/knowledge-check.md
---

Course

[Accessibility Testing Tutorial: WCAG 2.2](https://testingbot.com/resources/courses/accessibility-testing)

Chapter 10 of 10

1. [1 Accessibility Testing Tutorial: WCAG 2.2 in Practice](https://testingbot.com/resources/courses/accessibility-testing)
2. [2 Manual Accessibility Checks You Still Need](https://testingbot.com/resources/courses/accessibility-testing/manual-accessibility-checks)
3. [3 axe-core with Playwright: Your First Scan](https://testingbot.com/resources/courses/accessibility-testing/axe-core-with-playwright)
4. [4 axe-core with Selenium in Java](https://testingbot.com/resources/courses/accessibility-testing/axe-with-selenium-java)
5. [5 Scoping Scans, Rules and a Baseline of Known Issues](https://testingbot.com/resources/courses/accessibility-testing/scoping-rules-and-baselines)
6. [6 Fixing Common Violations: Contrast, Forms and ARIA](https://testingbot.com/resources/courses/accessibility-testing/fixing-common-violations)
7. [7 Running Accessibility Checks in CI](https://testingbot.com/resources/courses/accessibility-testing/accessibility-checks-in-ci)
8. [8 Accessibility Testing on TestingBot](https://testingbot.com/resources/courses/accessibility-testing/accessibility-testing-on-testingbot)
9. [9 What Automated Accessibility Testing Cannot Catch](https://testingbot.com/resources/courses/accessibility-testing/what-automation-cannot-catch)
10. [10 Knowledge check](https://testingbot.com/resources/courses/accessibility-testing/knowledge-check)

[Exit course](https://testingbot.com/resources/courses)

 Chapter 10 of 10 Intermediate 7 min read Updated Nov 2026 

# Knowledge check

Nine questions on the decisions that come up in real accessibility testing work. Each answer has a short explanation, so a wrong answer points you back to the right chapter.

1. A product owner asks you to "make sure the site meets WCAG 2.2 AA with automated tests". What is the accurate response?

 Add an axe scan of every page; a green scan proves conformance Automated scans cover part of WCAG; conformance also needs manual keyboard, screen reader and zoom checks WCAG cannot be tested at all, only audited by lawyers Only Level A criteria can be tested automatically, so test those and skip AA

Rules engines are good at mechanical criteria such as contrast, names and labels, but many criteria need human judgement: alt text quality, focus order, meaningful link text. Automation and manual checks complement each other (chapters 1 and 8).

2. A scan written two years ago uses `withTags(['wcag2a', 'wcag2aa'])`. What does it miss?

 Nothing, `wcag2aa` includes every later version Only best-practice rules All contrast rules Rules for criteria added in WCAG 2.1 and 2.2, which carry tags such as `wcag21aa`, `wcag22a` and `wcag22aa`

Each WCAG version's criteria have their own tags. Without `wcag21a`, `wcag21aa`, `wcag22a` and `wcag22aa`, rules like `target-size` (2.5.8, new in 2.2) never run (chapters 2 and 3).

3. A test opens a settings dialog, then immediately calls `analyze()`. The dialog's contrast results vary between runs. What is the best fix?

 Wait for the dialog's final state with a web-first assertion (or reduce motion) before scanning Add `retries: 3` to the config Disable `color-contrast` for dialogs Move the dialog scan to a nightly job

axe measures what is rendered when it runs. A dialog still animating in has partial opacity, which lowers contrast. Scan the settled state; retries and disabled rules only hide the timing problem (chapter 6).

4. An embedded third-party map widget fails `aria-allowed-attr`, and your team cannot change its markup. The vendor has a ticket. What is the most defensible setup?

 Disable `aria-allowed-attr` in the shared fixture Stop scanning pages that contain the map Exclude the widget's container in the shared fixture, with a comment naming the owner and ticket Remove `wcag2a` from the tag list

A scoped, documented exclusion keeps the rule active for everything you own and makes the vendor issue visible. Disabling the rule or a whole tag would also hide your own future violations (chapter 4).

5. A pull request adds three lines to `a11y-baseline/checkout.json` and nothing else changes in the checkout code. What should the reviewer do?

 Approve it; baseline files are generated and do not need review Ask why; adding baseline lines accepts new violations, and an unrelated selector change may only need the old entry renamed Delete the baseline so all violations fail Approve it, since axe fingerprints never change

A baseline entry is permission for a violation to exist. New entries are either newly introduced bugs or selector churn after a markup change; both deserve a look before they are accepted (chapter 4).

6. A custom toggle is `<span role="switch" tabindex="0">` and axe reports `aria-required-attr`. What is the most robust fix?

 Add `aria-checked="false"` and leave it at that Remove the role so the rule no longer applies Add `aria-hidden="true"` to the span Use a native `<input type="checkbox">` (styled as a switch, or with `role="switch"`) so state and keyboard handling come from the browser

A static `aria-checked` silences axe but lies about state as soon as the user toggles it. Native inputs bring focus, Space handling and real checked state; removing the role or hiding the control makes it worse (chapter 5).

7. Your suite passes in Chromium. On a Safari run, a button fails `target-size`. What is the right reading of that result?

 The button renders smaller in WebKit, so Safari users really get a target under 24 pixels Safari results are unreliable and should be ignored The baseline was generated in the wrong browser and only needs regenerating `target-size` only applies to mobile browsers

axe measures the layout each engine produces. Different default control sizes are a real difference for real users, which is one reason to run accessibility scans in more than one browser (chapters 5 and 7).

8. Which problem is a scheduled scan of production URLs most likely to catch that pull-request tests miss?

 A focus order that does not match the visual layout Alt text that does not describe the image A CMS editor publishing a banner with low-contrast text between deploys A screen reader not announcing a toast message

Scheduled scans re-check pages that change without a code change, such as CMS content and third-party scripts. The other three need human judgement, which no scan provides (chapters 7 and 8).

9. A designer swaps a visible "Email" label for a placeholder. axe stays green. Which test would catch the change?

 A reflow test at 320 CSS pixels An accessibility tree assertion, such as `toMatchAriaSnapshot`, that expects the textbox's name to come from the label A second axe scan with `best-practice` rules A colour contrast check

axe accepts a placeholder as an accessible name, so the rules stay green. A snapshot of the accessibility tree, or a test that checks the visible label, encodes the decision that the field must keep a real label (chapter 8).

Check answers

## Where to go next[#](https://testingbot.com#where-to-go-next)

Put the four layers from chapter 8 in place on one real page of your own product this week: an axe scan with a baseline, one keyboard journey, one accessibility tree snapshot of its most important form, and a fifteen-minute manual pass with a screen reader. Then grow from there.

For reference, keep the [W3C WCAG 2.2 quick reference](https://www.w3.org/WAI/WCAG22/quickref/) and TestingBot's [accessibility rules overview](https://testingbot.com/support/accessibility/web/rules) open while you fix issues. To run your checks across more browsers, or to scan production pages on a schedule, see [automated accessibility testing on TestingBot](https://testingbot.com/features/accessibility-testing). If you want to know more about the test runner used throughout this course, the [Playwright tutorial](https://testingbot.com/resources/courses/playwright) goes deeper.

[Previous · Chapter 9 What Automated Accessibility Testing Cannot Catch](https://testingbot.com/resources/courses/accessibility-testing/what-automation-cannot-catch)
## You finished Accessibility Testing Tutorial: WCAG 2.2

Put what you learned into practice. Run your tests on 6100+ real browsers and physical iOS and Android devices.

[Start free trial](https://testingbot.com/users/sign_up) [See pricing](https://testingbot.com/pricing) [Browse other courses](https://testingbot.com/resources/courses)

## TestingBot Accessibility Testing Certification

Turn this course into a free, resume-worthy credential: pass the exam, run the course suite on TestingBot, and get a verifiable certificate for your LinkedIn profile.

[How it works](https://testingbot.com/resources/courses/accessibility-testing/certification)
