📋 WCAG Vocabulary
Master core WCAG principles, conformance levels, and success criterion vocabulary. Intermediate
0 / 26 completed
1 / 26
The WCAG 2.1 guidelines are organised around four principles — POUR.
What does POUR stand for?
POUR describes the four foundational properties of accessible web content:
| Principle | Meaning |
|---|---|
| Perceivable | Users can sense content with available senses (vision, hearing, touch) |
| Operable | Can interact regardless of input device (mouse, keyboard, switch) |
| Understandable | Content and UI behaviour makes sense to users |
| Robust | Works with current and future assistive technologies |
All 78 WCAG 2.1 success criteria map to one of these four principles. Key vocabulary: "WCAG principle", "success criterion", "conformance level (A/AA/AAA)".
2 / 26
The accessibility audit found a Level AA violation.
What does WCAG Level AA conformance mean?
WCAG defines three conformance levels with increasing strictness:
| Level | Criteria count | Legal status |
|---|---|---|
| A (minimum) | 30 success criteria | Baseline — rarely sufficient alone |
| AA (standard) | A + 20 additional | Required by EU EAA, Section 508, UK PSBAR |
| AAA (enhanced) | AA + 28 additional | Not achievable for all content types |
Key vocabulary: "conformance level", "Level AA (standard requirement)", "WCAG 2.2 adds 9 new criteria vs. 2.1".
3 / 26
WCAG Success Criterion 1.4.3 requires a minimum contrast ratio of 4.5:1 for normal text.
What does this criterion address?
SC 1.4.3 Contrast Minimum (Level AA) ensures text is readable by users with low vision and colour vision deficiencies:
| Text type | Minimum contrast ratio |
|---|---|
| Normal text (under 18pt / 14pt bold) | 4.5:1 |
| Large text (18pt+ / 14pt+ bold) | 3:1 |
| UI components / graphical objects (SC 1.4.11) | 3:1 |
Tools: WebAIM Contrast Checker, Chrome DevTools, axe. Key vocabulary: "contrast ratio", "relative luminance", "large text exception", "1.4.11 Non-Text Contrast".
4 / 26
A developer argues: "Our users don't use screen readers, so we don't need to worry about accessibility."
Which WCAG principle does this argument misunderstand?
Accessibility serves a far wider group than screen reader users alone:
| User group | Accessibility need |
|---|---|
| Blind / low vision | Screen readers, contrast, zoom |
| Deaf / hard of hearing | Captions, transcripts, visual alerts |
| Motor impaired | Keyboard navigation, large targets |
| Cognitive differences | Plain language, consistent navigation |
| Situational (bright sun, one hand occupied) | Same accessibility features benefit all |
Most users don't disclose disabilities ("invisible disability"). Key vocabulary: "invisible disability", "situational disability", "spectrum of disability".
5 / 26
The page has a "conformance claim at WCAG 2.1 Level AA."
What is an Accessibility Conformance Report (ACR)?
The ACR / VPAT (Voluntary Product Accessibility Template) is a standard format for communicating product accessibility conformance:
| Term | Description |
|---|---|
| VPAT | US standard template (IT Industry Council); used in procurement |
| ACR | The completed VPAT document for a specific product |
| Accessibility Statement (EU) | Required under EU EAA / PSBAR for public sector sites |
| Self-attestation vs. third-party audit | Procurement teams prefer third-party validation |
Key vocabulary: "VPAT", "conformance claim", "procurement evaluation", "self-attestation".
6 / 26
git review -s my-feature-branch
Mark is misinterpreting the core principle of accessibility. WCAG isn't solely about screen readers; it's fundamentally about ensuring that content is perceivable to *all* users, regardless of their abilities or assistive technologies. Success Criterion 1.4.3 addresses color contrast specifically, but Mark's comment highlights a broader misunderstanding of equitable use and the need to consider diverse user needs – including those who may have difficulty perceiving visual cues like color.
7 / 26
PR Description:
"Implemented new user profile page. Includes a text field for 'Preferred Language'. Styling applied using CSS variables to ensure consistent color palettes across the application."
During a code review, Alex comments: 'I'm concerned that the label associated with the language selection doesn't have sufficient contrast against the background. This could violate WCAG 1.4.3.' Ben responds: 'We've used a very subtle gray for the labels – it looks fine to me.' Which statement best describes Ben's potential misunderstanding?Ben is prioritizing visual aesthetics over functional accessibility. WCAG 1.4.3 specifically addresses the need for sufficient color contrast between text and background—not just 'looks fine' to him. The guideline aims to ensure that users with low vision can comfortably read content, and Ben's response fails to acknowledge this critical requirement.
8 / 26
git review -s my-feature-branch During a code review of a new form, David points out: 'The form validation error message lacks sufficient color contrast against the background. This violates WCAG 1.4.3.' Emily responds: 'Users rarely read those messages anyway – it's just an aesthetic concern.' Which of the following best explains Emily's mistake?Emily's response fails to grasp the core principle of WCAG 1.4.3: ensuring sufficient contrast ratios for all text, including error messages, regardless of whether a user is visually impaired or using assistive technology. The guideline isn't just about aesthetics; it's about making information accessible to *all* users. Aesthetic concerns are valid, but shouldn't override the requirements of accessibility standards. She's conflating 'looks good' with 'is accessible.'
9 / 26
During a code review of a new navigation component, Chloe comments: 'The text color on the active menu item isn't sufficiently contrasting against the background. This is a violation of WCAG 1.4.3.' David replies, 'We've used a very light shade – it's just a subtle difference; most users won't notice it.' Which statement best describes David's potential misunderstanding regarding accessibility?
David mistakenly believes that his own perception of color contrast is sufficient. WCAG 1.4.3 isn't about whether *he* sees a problem; it's about ensuring sufficient contrast for users with visual impairments who may have different sensitivities. The goal is to meet a measurable standard, not rely on subjective judgment.
10 / 26
git review -s my-feature-branch
Mark is misinterpreting the core principle of accessibility. WCAG isn't solely about screen readers; it's fundamentally about ensuring that content is perceivable to *all* users, regardless of their abilities or assistive technologies. Success Criterion 1.4.3 addresses color contrast specifically, but Mark's comment highlights a broader misunderstanding of equitable use and the need to consider diverse user needs – including those who may have difficulty perceiving visual cues like color.
11 / 26
PR Description:
"Implemented new user profile page. Includes a text field for 'Preferred Language'. Styling applied using CSS variables to ensure consistent color palettes across the application."
During a code review, Alex comments: 'I'm concerned that the label associated with the language selection doesn't have sufficient contrast against the background. This could violate WCAG 1.4.3.' Ben responds: 'We've used a very subtle gray for the labels – it looks fine to me.' Which statement best describes Ben's potential misunderstanding?Ben is prioritizing visual aesthetics over functional accessibility. WCAG 1.4.3 specifically addresses the need for sufficient color contrast between text and background—not just 'looks fine' to him. The guideline aims to ensure that users with low vision can comfortably read content, and Ben's response fails to acknowledge this critical requirement.
12 / 26
git review -s my-feature-branch During a code review of a new form, David points out: 'The form validation error message lacks sufficient color contrast against the background. This violates WCAG 1.4.3.' Emily responds: 'Users rarely read those messages anyway – it's just an aesthetic concern.' Which of the following best explains Emily's mistake?Emily's response fails to grasp the core principle of WCAG 1.4.3: ensuring sufficient contrast ratios for all text, including error messages, regardless of whether a user is visually impaired or using assistive technology. The guideline isn't just about aesthetics; it's about making information accessible to *all* users. Aesthetic concerns are valid, but shouldn't override the requirements of accessibility standards. She's conflating 'looks good' with 'is accessible.'
13 / 26
During a code review of a new navigation component, Chloe comments: 'The text color on the active menu item isn't sufficiently contrasting against the background. This is a violation of WCAG 1.4.3.' David replies, 'We've used a very light shade – it's just a subtle difference; most users won't notice it.' Which statement best describes David's potential misunderstanding regarding accessibility?
David mistakenly believes that his own perception of color contrast is sufficient. WCAG 1.4.3 isn't about whether *he* sees a problem; it's about ensuring sufficient contrast for users with visual impairments who may have different sensitivities. The goal is to meet a measurable standard, not rely on subjective judgment.
14 / 26
git review -s my-feature-branch
Mark is misinterpreting the core principle of accessibility. WCAG isn't solely about screen readers; it's fundamentally about ensuring that content is perceivable to *all* users, regardless of their abilities or assistive technologies. Success Criterion 1.4.3 addresses color contrast specifically, but Mark's comment highlights a broader misunderstanding of equitable use and the need to consider diverse user needs – including those who may have difficulty perceiving visual cues like color.
15 / 26
PR Description:
"Implemented new user profile page. Includes a text field for 'Preferred Language'. Styling applied using CSS variables to ensure consistent color palettes across the application."
During a code review, Alex comments: 'I'm concerned that the label associated with the language selection doesn't have sufficient contrast against the background. This could violate WCAG 1.4.3.' Ben responds: 'We've used a very subtle gray for the labels – it looks fine to me.' Which statement best describes Ben's potential misunderstanding?Ben is prioritizing visual aesthetics over functional accessibility. WCAG 1.4.3 specifically addresses the need for sufficient color contrast between text and background—not just 'looks fine' to him. The guideline aims to ensure that users with low vision can comfortably read content, and Ben's response fails to acknowledge this critical requirement.
16 / 26
git review -s my-feature-branch During a code review of a new form, David points out: 'The form validation error message lacks sufficient color contrast against the background. This violates WCAG 1.4.3.' Emily responds: 'Users rarely read those messages anyway – it's just an aesthetic concern.' Which of the following best explains Emily's mistake?Emily's response fails to grasp the core principle of WCAG 1.4.3: ensuring sufficient contrast ratios for all text, including error messages, regardless of whether a user is visually impaired or using assistive technology. The guideline isn't just about aesthetics; it's about making information accessible to *all* users. Aesthetic concerns are valid, but shouldn't override the requirements of accessibility standards. She's conflating 'looks good' with 'is accessible.'
17 / 26
During a code review of a new navigation component, Chloe comments: 'The text color on the active menu item isn't sufficiently contrasting against the background. This is a violation of WCAG 1.4.3.' David replies, 'We've used a very light shade – it's just a subtle difference; most users won't notice it.' Which statement best describes David's potential misunderstanding regarding accessibility?
David mistakenly believes that his own perception of color contrast is sufficient. WCAG 1.4.3 isn't about whether *he* sees a problem; it's about ensuring sufficient contrast for users with visual impairments who may have different sensitivities. The goal is to meet a measurable standard, not rely on subjective judgment.
18 / 26
git review -s my-feature-branch
Mark is misinterpreting the core principle of accessibility. WCAG isn't solely about screen readers; it's fundamentally about ensuring that content is perceivable to *all* users, regardless of their abilities or assistive technologies. Success Criterion 1.4.3 addresses color contrast specifically, but Mark's comment highlights a broader misunderstanding of equitable use and the need to consider diverse user needs – including those who may have difficulty perceiving visual cues like color.
19 / 26
PR Description:
"Implemented new user profile page. Includes a text field for 'Preferred Language'. Styling applied using CSS variables to ensure consistent color palettes across the application."
During a code review, Alex comments: 'I'm concerned that the label associated with the language selection doesn't have sufficient contrast against the background. This could violate WCAG 1.4.3.' Ben responds: 'We've used a very subtle gray for the labels – it looks fine to me.' Which statement best describes Ben's potential misunderstanding?Ben is prioritizing visual aesthetics over functional accessibility. WCAG 1.4.3 specifically addresses the need for sufficient color contrast between text and background—not just 'looks fine' to him. The guideline aims to ensure that users with low vision can comfortably read content, and Ben's response fails to acknowledge this critical requirement.
20 / 26
git review -s my-feature-branch During a code review of a new form, David points out: 'The form validation error message lacks sufficient color contrast against the background. This violates WCAG 1.4.3.' Emily responds: 'Users rarely read those messages anyway – it's just an aesthetic concern.' Which of the following best explains Emily's mistake?Emily's response fails to grasp the core principle of WCAG 1.4.3: ensuring sufficient contrast ratios for all text, including error messages, regardless of whether a user is visually impaired or using assistive technology. The guideline isn't just about aesthetics; it's about making information accessible to *all* users. Aesthetic concerns are valid, but shouldn't override the requirements of accessibility standards. She's conflating 'looks good' with 'is accessible.'
21 / 26
During a code review of a new navigation component, Chloe comments: 'The text color on the active menu item isn't sufficiently contrasting against the background. This is a violation of WCAG 1.4.3.' David replies, 'We've used a very light shade – it's just a subtle difference; most users won't notice it.' Which statement best describes David's potential misunderstanding regarding accessibility?
David mistakenly believes that his own perception of color contrast is sufficient. WCAG 1.4.3 isn't about whether *he* sees a problem; it's about ensuring sufficient contrast for users with visual impairments who may have different sensitivities. The goal is to meet a measurable standard, not rely on subjective judgment.
22 / 26
During a code review of a modal window, Alex says: 'The modal's background isn't sufficient contrast against the main page. This could be a violation of WCAG 1.4.3.' Which response best addresses this concern?
// No relevant code here
Alex correctly identifies that sufficient color contrast is a core principle of accessibility under WCAG 1.4.3. The options highlight different misunderstandings: increasing font size isn't a direct solution for contrast issues, and Alex's comment needs to be more specific about the problematic area. The last option points to a vague statement without actionable information.
23 / 26
In a Slack channel discussing a new accessibility audit, Maria writes: 'We need to ensure all buttons have ARIA labels. This will help screen readers understand their purpose.' What does Maria primarily mean when referring to 'ARIA labels'?
// No relevant code here
Maria is correctly identifying that ARIA (Accessible Rich Internet Applications) labels are used to provide semantic information about interactive elements to screen readers. While ARIA labels are crucial for accessibility, they don't directly impact the user experience or automatically fix color contrast issues.
24 / 26
A PR description reads: 'Added a new form field with a placeholder text. The placeholder is styled to match the input field's background color.' Is this sufficient for WCAG compliance?
// No relevant code here
While using matching colors can be a helpful starting point, it is insufficient for WCAG compliance. Placeholder text needs to be visually distinct from the input field (e.g., different color, font weight, or size) to avoid confusion for users with screen readers. The description lacks critical information about contrast and readability.
25 / 26
"I'm working on improving the accessibility of our data tables. I've added headings to each column and row to help screen readers understand the structure." During a stand-up update, your team lead asks: 'Can you elaborate on how this improves accessibility?'
// No relevant code here
The team member's response is insufficient because it doesn't explain *how* using headings improves accessibility. Adding headings provides semantic information to assistive technologies, allowing them to correctly interpret and navigate the tabular data – this is key to WCAG compliance. The other options represent misunderstandings of how ARIA roles and attributes function.
26 / 26
During a code review, Ben remarks: 'The form field labels aren't properly associated with their input fields using the `for` attribute. This violates WCAG 1.4.3.' What is the primary issue Ben is highlighting?
// No relevant code here
Ben is correctly identifying that proper association of form field labels with their input fields using the `for` attribute is essential for screen reader navigation. Without this association, screen readers cannot accurately link the label to its corresponding input field, leading to a poor user experience and violating WCAG 1.4.3.
Frequently Asked Questions
What will I practice in "WCAG Vocabulary | Accessibility Exercises"?
This is an Accessibility Language exercise set. It walks through 26 scenario-based multiple-choice questions built around real usage of Accessibility Language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 26 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Accessibility Language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Accessibility Language exercises?
See the Accessibility Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Accessibility Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.