🔍 Accessibility Audit Vocabulary
Master the language of accessibility audits: findings, severity, VPAT, and remediation vocabulary. Intermediate
0 / 45 completed
1 / 45
The audit report cites WCAG 2.1 SC 2.4.7 — Focus Visible.
What does a success criterion citation in an accessibility audit mean?
Each WCAG success criterion citation in an audit report gives the finding a traceable, normative reference:
| Citation component | Example | Purpose |
|---|---|---|
| SC number | 2.4.7 | Unique identifier — enables lookup |
| SC name | Focus Visible | Human-readable label |
| Level | AA | Indicates compliance priority |
Citing the SC separates normative violations (must fix for legal compliance) from best-practice recommendations (should fix). Key vocabulary: "success criterion reference", "normative requirement", "understanding SC", "sufficient technique".
2 / 45
The automated scan found 12 violations using axe-core.
What is the key limitation of automated accessibility testing?
Automated accessibility tools are fast and consistent but cover only a portion of WCAG requirements:
| Testing type | Finds | Misses |
|---|---|---|
| Automated (axe-core) | Missing alt text, contrast failures, missing labels, duplicate IDs | Wrong alt text, cognitive accessibility, keyboard flow quality |
| Manual review | Context-dependent issues, logical structure, reading order | Comprehensive AT experience |
| AT testing | Screen reader comprehension, forms mode, focus management | Efficiency — requires AT expertise |
Key vocabulary: "automated + manual testing requirement", "false negative", "automated audit coverage (30–40%)", "expert review".
3 / 45
The audit finding has severity: Critical.
What does severity in an accessibility audit typically mean?
Severity classification helps teams prioritise remediation regardless of WCAG level:
| Severity | User impact | Example |
|---|---|---|
| Critical | Access completely blocked for a user group | Keyboard trap, form with no labels |
| Major | Significantly impairs but does not block | Poor focus management in modal |
| Minor | Friction — user can work around it | Heading level skipped in one section |
Severity is independent of WCAG level — a Level A issue can be Minor in context; a Level AA issue can be Critical if it blocks screen reader users. Key vocabulary: "access blocker", "remediation priority", "user impact vs. WCAG level".
4 / 45
The VPAT shows "Supports with Exceptions" for SC 1.4.11.
What does "Supports with Exceptions" in a VPAT mean?
VPAT conformance level designations communicate the product's accessibility status for each success criterion:
| VPAT designation | Meaning |
|---|---|
| Supports | Fully meets the success criterion |
| Partially Supports / Supports with Exceptions | Some components do not conform; known gaps documented in notes |
| Does Not Support | The criterion is not met |
| Not Applicable | The criterion does not apply to this product type |
Key vocabulary: "VPAT conformance claim", "exception documentation", "remediation roadmap in VPAT notes", "honest self-assessment".
5 / 45
The remediation recommendation is to add a visible focus indicator to all interactive elements.
What SC does this recommendation address and why is it important?
Focus visible requirements ensure sighted keyboard users can navigate without a mouse:
| Criterion | Requirement | WCAG version |
|---|---|---|
| SC 2.4.7 Focus Visible | Any keyboard-operable UI must have a visible focus indicator | 2.1 — Level AA |
| SC 2.4.11 Focus Appearance | Stricter: focus indicator must have minimum area and contrast | 2.2 — Level AA |
outline: none in CSS = accessibility failure. Key vocabulary: "focus indicator", "focus ring", "outline: none anti-pattern", "keyboard navigation baseline", "focus management in SPAs".
6 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
7 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
8 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
9 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
10 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
11 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
12 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
13 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
14 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
15 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
16 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
17 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
18 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
19 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
20 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
21 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
22 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
23 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
24 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
25 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
26 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
27 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
28 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
29 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
30 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
31 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
32 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
33 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
34 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
35 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
36 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
37 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
38 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
39 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
40 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
41 / 45
Sarah: "Hey team, I've just run the accessibility audit on the new payment API. Axe-core flagged 37 violations related to insufficient color contrast in the form fields and missing ARIA labels for several buttons. Should we prioritize fixing these based on the report?"This scenario highlights a common situation in code reviews. While all violations deserve attention, the report's designation of 'critical' issues – like insufficient color contrast – often represents a significant barrier for users with visual impairments. Prioritizing these high-severity items ensures immediate improvements to core functionality and demonstrates commitment to accessibility best practices. Focusing solely on ARIA labels without addressing contrast could still lead to usability problems, so a balanced approach is key.
42 / 45
PR Description: 'Implemented minor styling changes to the user interface. Added some padding and adjusted font sizes for better readability.' Reviewer Alex comments: 'This looks good, but have you considered running an accessibility audit? Specifically, are you ensuring sufficient color contrast between text and background elements according to WCAG guidelines?'Alex's comment highlights the critical connection between UI styling and accessibility. WCAG 1.4.3 specifically addresses sufficient color contrast as a requirement for readability – failing to meet this criterion can make content inaccessible to users with low vision. The PR description focuses solely on aesthetic changes without considering their impact on user experience and, crucially, adherence to accessibility standards. This demonstrates the importance of proactively incorporating accessibility considerations during development.
43 / 45
During a code review for a new e-commerce checkout flow, Developer Ben notes in the comment: 'I've run an automated accessibility scan using Lighthouse. It highlighted several issues related to keyboard navigation – specifically, missing `tabindex` attributes on some interactive elements and inconsistent focus order.' What is Ben primarily referring to when discussing these Lighthouse findings?
Ben is focusing on 'keyboard navigation' which relates to WCAG success criterion 2.1.2 No Keyboard Input Component Removed. The scan identified problems with how users navigate a website using only the keyboard, such as missing `tabindex` attributes or an inconsistent focus order, directly impacting those who rely on keyboards for interaction – a key accessibility consideration. These issues often cause significant difficulty for users with motor impairments.
44 / 45
Alex, the lead developer on the project, sends this Slack message to the team: 'Just finished a quick accessibility audit of the new admin dashboard. Axe-core reported 23 violations primarily relating to low color contrast and missing alternative text for images. Should we focus our immediate efforts on addressing these findings, or are there other issues we should prioritize based on the severity?' What is Alex most concerned about when requesting this review?Alex is rightly concerned about the high number of violations reported by Axe-core. While low color contrast can be a factor, multiple violations point to a systemic issue requiring immediate attention. The key takeaway here is that automated scans like Axe-core often highlight areas needing focused investigation – it's not simply about resolving every single flagged item immediately but understanding the overall accessibility status and prioritizing based on severity. The other options misinterpret the role of automated testing or assume low color contrast automatically represents a critical failure.
45 / 45
During a standup update, David says: 'We've just completed an accessibility audit of the new data visualization tool using Lighthouse. The scan identified several issues related to screen reader compatibility – specifically, missing or poorly implemented `aria-*` attributes on charts and graphs, and insufficient semantic HTML.' What is David primarily raising concern about in this statement?
David is highlighting the lack of keyboard navigation support, which directly relates to screen reader accessibility. The `aria-*` attributes and semantic HTML are often used to provide assistive technologies with information needed to interpret and interact with complex UI elements like charts and graphs. A failure in these areas significantly impacts users who rely on screen readers for access.
Frequently Asked Questions
What will I practice in "Accessibility Audit Vocabulary | Accessibility Exercises"?
This is an Accessibility Language exercise set. It walks through 45 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 45 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.