Accessibility Testing Vocabulary Quiz
Learn the vocabulary of accessibility testing: screen readers, keyboard navigation, and automated tools like axe and Lighthouse.
0 / 25 completed
1 / 25
A developer says 'I tested with NVDA'. What is NVDA?
NVDA (NonVisual Desktop Access) is a free, open-source screen reader for Windows widely used to test how web content is announced to blind and low-vision users.
2 / 25
What does 'keyboard-only navigation testing' involve?
Keyboard-only testing means navigating the entire interface using only the keyboard to verify all interactive elements are reachable, operable, and have a visible focus indicator.
3 / 25
A QA engineer says 'the axe scan found 3 violations'. What is axe?
axe (by Deque) is a widely used automated accessibility testing engine available as a browser extension, CLI tool, and testing library integration that flags WCAG violations.
4 / 25
When a tester says 'this fails the accessibility audit in Lighthouse', what does that mean?
Lighthouse is a Chrome tool that runs automated audits including accessibility checks. An accessibility audit failure means the page has detectable WCAG issues such as missing labels, poor contrast, or inaccessible forms.
5 / 25
What is 'VoiceOver' in the context of accessibility testing?
VoiceOver is the built-in screen reader on Apple devices (macOS, iOS, iPadOS) and is essential for testing accessibility on Apple platforms alongside NVDA/JAWS on Windows.
6 / 25
Sarah: 'Hey team, I ran a contrast check on the primary button using WebAIM's Contrast Checker. The results show it's significantly below WCAG AA standards – we need to address this immediately!'. What does 'WCAG' stand for in this context?WCAG stands for Web Content Accessibility Guidelines. It's a set of internationally recognized standards that define how web content should be structured and presented to ensure it is accessible to people with disabilities. Sarah is referencing the specific guidelines within WCAG concerning color contrast ratios, which are crucial for users with visual impairments. Using 'WebAIM's Contrast Checker' indicates she's utilizing a tool based on these established guidelines.7 / 25
// API Response (Partial)
The API response highlights a critical accessibility issue: low contrast between the button's background and text. This directly relates to WCAG AA standards, which mandate sufficient contrast ratios for readability. The option correctly identifies this as a 'critical' violation because insufficient color contrast can make the button difficult or impossible to see for users with visual impairments, representing a significant usability problem. Option A is incorrect because while an aria-label is important, the core issue is the low contrast itself.
8 / 25
John: 'I'm running a screen reader test on the login form. I've been using VoiceOver on iOS and it's highlighting all the elements correctly.'
Maria (a senior developer) replies in Slack: 'That's great, but are you specifically testing for *logical reading order*? VoiceOver reads content sequentially, but some components might be presented in an unexpected order that confuses users with disabilities.'This question focuses on a crucial aspect of screen reader testing beyond just visual element highlighting. Logical reading order dictates how assistive technologies like VoiceOver navigate and announce content – if elements are presented in an illogical sequence, the user experience will be significantly impaired. Option A is incorrect as HTML source code isn't *the* sole determinant; options B and D misrepresent the role of VoiceOver, and option C accurately describes the concept.
9 / 25
PR Description:
@johndoe - Please review this PR. The new form has a prominent submit button and a complex validation process. I've focused on ensuring it's accessible for users with screen readers, but could use a fresh pair of eyes to confirm everything is working correctly. (Note: Accessibility testing included VoiceOver navigation and contrast checks.)
This question tests understanding of accessibility testing within a code review context. The correct answer focuses on verifying core accessibility features like VoiceOver announcements and keyboard navigation – these are fundamental checks. Options A is too rigid, B misrepresents the scope, and C is an unrelated technical detail. D highlights a specific aspect (contrast), but doesn't encompass the broader goal of ensuring usability for screen reader users.
10 / 25
David: 'I've just sent this PR with the new modal window. I ran a Lighthouse audit and it flagged a few issues – specifically around keyboard focus management and color contrast. It also suggested adding `aria-label` attributes to all interactive elements within the modal. Should I prioritize addressing these Lighthouse findings, or is that a secondary concern after ensuring basic accessibility functionality?'Lighthouse provides valuable automated checks, but it's not a substitute for manual testing. While the Lighthouse findings highlight areas needing attention – keyboard focus and color contrast – they don't guarantee a fully accessible experience. Manually verifying these issues with tools like VoiceOver is crucial to ensure the modal truly works for users with disabilities, confirming that `aria-label` attributes are correctly implemented and keyboard navigation behaves as expected.
11 / 25
Sarah: 'Hey team, I ran a contrast check on the primary button using WebAIM's Contrast Checker. The results show it's significantly below WCAG AA standards – we need to address this immediately!'. What does 'WCAG' stand for in this context?WCAG stands for Web Content Accessibility Guidelines. It's a set of internationally recognized standards that define how web content should be structured and presented to ensure it is accessible to people with disabilities. Sarah is referencing the specific guidelines within WCAG concerning color contrast ratios, which are crucial for users with visual impairments. Using 'WebAIM's Contrast Checker' indicates she's utilizing a tool based on these established guidelines.12 / 25
// API Response (Partial)
The API response highlights a critical accessibility issue: low contrast between the button's background and text. This directly relates to WCAG AA standards, which mandate sufficient contrast ratios for readability. The option correctly identifies this as a 'critical' violation because insufficient color contrast can make the button difficult or impossible to see for users with visual impairments, representing a significant usability problem. Option A is incorrect because while an aria-label is important, the core issue is the low contrast itself.
13 / 25
John: 'I'm running a screen reader test on the login form. I've been using VoiceOver on iOS and it's highlighting all the elements correctly.'
Maria (a senior developer) replies in Slack: 'That's great, but are you specifically testing for *logical reading order*? VoiceOver reads content sequentially, but some components might be presented in an unexpected order that confuses users with disabilities.'This question focuses on a crucial aspect of screen reader testing beyond just visual element highlighting. Logical reading order dictates how assistive technologies like VoiceOver navigate and announce content – if elements are presented in an illogical sequence, the user experience will be significantly impaired. Option A is incorrect as HTML source code isn't *the* sole determinant; options B and D misrepresent the role of VoiceOver, and option C accurately describes the concept.
14 / 25
PR Description:
@johndoe - Please review this PR. The new form has a prominent submit button and a complex validation process. I've focused on ensuring it's accessible for users with screen readers, but could use a fresh pair of eyes to confirm everything is working correctly. (Note: Accessibility testing included VoiceOver navigation and contrast checks.)
This question tests understanding of accessibility testing within a code review context. The correct answer focuses on verifying core accessibility features like VoiceOver announcements and keyboard navigation – these are fundamental checks. Options A is too rigid, B misrepresents the scope, and C is an unrelated technical detail. D highlights a specific aspect (contrast), but doesn't encompass the broader goal of ensuring usability for screen reader users.
15 / 25
David: 'I've just sent this PR with the new modal window. I ran a Lighthouse audit and it flagged a few issues – specifically around keyboard focus management and color contrast. It also suggested adding `aria-label` attributes to all interactive elements within the modal. Should I prioritize addressing these Lighthouse findings, or is that a secondary concern after ensuring basic accessibility functionality?'Lighthouse provides valuable automated checks, but it's not a substitute for manual testing. While the Lighthouse findings highlight areas needing attention – keyboard focus and color contrast – they don't guarantee a fully accessible experience. Manually verifying these issues with tools like VoiceOver is crucial to ensure the modal truly works for users with disabilities, confirming that `aria-label` attributes are correctly implemented and keyboard navigation behaves as expected.
16 / 25
Sarah: 'Hey team, I ran a contrast check on the primary button using WebAIM's Contrast Checker. The results show it's significantly below WCAG AA standards – we need to address this immediately!'. What does 'WCAG' stand for in this context?WCAG stands for Web Content Accessibility Guidelines. It's a set of internationally recognized standards that define how web content should be structured and presented to ensure it is accessible to people with disabilities. Sarah is referencing the specific guidelines within WCAG concerning color contrast ratios, which are crucial for users with visual impairments. Using 'WebAIM's Contrast Checker' indicates she's utilizing a tool based on these established guidelines.17 / 25
// API Response (Partial)
The API response highlights a critical accessibility issue: low contrast between the button's background and text. This directly relates to WCAG AA standards, which mandate sufficient contrast ratios for readability. The option correctly identifies this as a 'critical' violation because insufficient color contrast can make the button difficult or impossible to see for users with visual impairments, representing a significant usability problem. Option A is incorrect because while an aria-label is important, the core issue is the low contrast itself.
18 / 25
John: 'I'm running a screen reader test on the login form. I've been using VoiceOver on iOS and it's highlighting all the elements correctly.'
Maria (a senior developer) replies in Slack: 'That's great, but are you specifically testing for *logical reading order*? VoiceOver reads content sequentially, but some components might be presented in an unexpected order that confuses users with disabilities.'This question focuses on a crucial aspect of screen reader testing beyond just visual element highlighting. Logical reading order dictates how assistive technologies like VoiceOver navigate and announce content – if elements are presented in an illogical sequence, the user experience will be significantly impaired. Option A is incorrect as HTML source code isn't *the* sole determinant; options B and D misrepresent the role of VoiceOver, and option C accurately describes the concept.
19 / 25
PR Description:
@johndoe - Please review this PR. The new form has a prominent submit button and a complex validation process. I've focused on ensuring it's accessible for users with screen readers, but could use a fresh pair of eyes to confirm everything is working correctly. (Note: Accessibility testing included VoiceOver navigation and contrast checks.)
This question tests understanding of accessibility testing within a code review context. The correct answer focuses on verifying core accessibility features like VoiceOver announcements and keyboard navigation – these are fundamental checks. Options A is too rigid, B misrepresents the scope, and C is an unrelated technical detail. D highlights a specific aspect (contrast), but doesn't encompass the broader goal of ensuring usability for screen reader users.
20 / 25
David: 'I've just sent this PR with the new modal window. I ran a Lighthouse audit and it flagged a few issues – specifically around keyboard focus management and color contrast. It also suggested adding `aria-label` attributes to all interactive elements within the modal. Should I prioritize addressing these Lighthouse findings, or is that a secondary concern after ensuring basic accessibility functionality?'Lighthouse provides valuable automated checks, but it's not a substitute for manual testing. While the Lighthouse findings highlight areas needing attention – keyboard focus and color contrast – they don't guarantee a fully accessible experience. Manually verifying these issues with tools like VoiceOver is crucial to ensure the modal truly works for users with disabilities, confirming that `aria-label` attributes are correctly implemented and keyboard navigation behaves as expected.
21 / 25
Sarah: 'Hey team, I ran a contrast check on the primary button using WebAIM's Contrast Checker. The results show it's significantly below WCAG AA standards – we need to address this immediately!'. What does 'WCAG' stand for in this context?WCAG stands for Web Content Accessibility Guidelines. It's a set of internationally recognized standards that define how web content should be structured and presented to ensure it is accessible to people with disabilities. Sarah is referencing the specific guidelines within WCAG concerning color contrast ratios, which are crucial for users with visual impairments. Using 'WebAIM's Contrast Checker' indicates she's utilizing a tool based on these established guidelines.22 / 25
// API Response (Partial)
The API response highlights a critical accessibility issue: low contrast between the button's background and text. This directly relates to WCAG AA standards, which mandate sufficient contrast ratios for readability. The option correctly identifies this as a 'critical' violation because insufficient color contrast can make the button difficult or impossible to see for users with visual impairments, representing a significant usability problem. Option A is incorrect because while an aria-label is important, the core issue is the low contrast itself.
23 / 25
John: 'I'm running a screen reader test on the login form. I've been using VoiceOver on iOS and it's highlighting all the elements correctly.'
Maria (a senior developer) replies in Slack: 'That's great, but are you specifically testing for *logical reading order*? VoiceOver reads content sequentially, but some components might be presented in an unexpected order that confuses users with disabilities.'This question focuses on a crucial aspect of screen reader testing beyond just visual element highlighting. Logical reading order dictates how assistive technologies like VoiceOver navigate and announce content – if elements are presented in an illogical sequence, the user experience will be significantly impaired. Option A is incorrect as HTML source code isn't *the* sole determinant; options B and D misrepresent the role of VoiceOver, and option C accurately describes the concept.
24 / 25
PR Description:
@johndoe - Please review this PR. The new form has a prominent submit button and a complex validation process. I've focused on ensuring it's accessible for users with screen readers, but could use a fresh pair of eyes to confirm everything is working correctly. (Note: Accessibility testing included VoiceOver navigation and contrast checks.)
This question tests understanding of accessibility testing within a code review context. The correct answer focuses on verifying core accessibility features like VoiceOver announcements and keyboard navigation – these are fundamental checks. Options A is too rigid, B misrepresents the scope, and C is an unrelated technical detail. D highlights a specific aspect (contrast), but doesn't encompass the broader goal of ensuring usability for screen reader users.
25 / 25
David: 'I've just sent this PR with the new modal window. I ran a Lighthouse audit and it flagged a few issues – specifically around keyboard focus management and color contrast. It also suggested adding `aria-label` attributes to all interactive elements within the modal. Should I prioritize addressing these Lighthouse findings, or is that a secondary concern after ensuring basic accessibility functionality?'Lighthouse provides valuable automated checks, but it's not a substitute for manual testing. While the Lighthouse findings highlight areas needing attention – keyboard focus and color contrast – they don't guarantee a fully accessible experience. Manually verifying these issues with tools like VoiceOver is crucial to ensure the modal truly works for users with disabilities, confirming that `aria-label` attributes are correctly implemented and keyboard navigation behaves as expected.
Frequently Asked Questions
What will I practice in "Accessibility Testing Vocabulary Quiz"?
This is an Accessibility Language exercise set. It walks through 25 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 25 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.