Screen Reader Testing Workflows
Learn the IT-English vocabulary engineers use when testing applications with screen readers like NVDA, JAWS and VoiceOver.
0 / 25 completed
1 / 25
A QA engineer says: 'The screen reader doesn't announce the error when the field becomes invalid.' Which term describes the screen reader speaking content aloud?
Screen readers 'announce' content — reading it aloud or sending it to a braille display.
2 / 25
What is the 'virtual cursor' (or 'browse mode') in screen reader testing?
Browse/virtual cursor mode lets screen reader users read through content independently of the focused element.
3 / 25
A tester reports: 'In forms mode the reader passes keystrokes straight to the input.' What does 'forms mode' (focus mode) do?
Forms/focus mode passes keystrokes to the control so users can type, rather than intercepting keys for navigation.
4 / 25
Which sentence correctly uses 'verbosity' in a screen reader context?
Verbosity controls how much detail (punctuation, roles, states) the screen reader announces.
5 / 25
A bug report says the button is 'unlabelled'. What problem is being described?
An 'unlabelled' control lacks an accessible name, so assistive tech can't tell users what it does.
6 / 25
Sarah, during a code review of the React component for our mobile app, flagged that the `TextInput` wasn't announcing its placeholder text. She said, 'The screen reader isn't reading out the "Enter your email" placeholder.' Which term best describes what Sarah is referring to when she mentions the screen reader 'not reading out' the placeholder? A) Accessibility Audit
B) Screen Reader Output
C) Semantic HTML Validation
D) Keyboard Navigation
Sarah is describing the process of the screen reader vocalizing content – specifically, the placeholder text within the `TextInput` component. 'Screen Reader Output' is the most accurate term here; it directly refers to the audible presentation of information by assistive technology. Options A and C relate to broader accessibility practices, while option D describes how a user navigates using keyboard controls, not the actual output of the screen reader itself.
7 / 25
David: 'I've just reviewed this PR. The screen reader isn't announcing the `aria-label` on the primary action button. It's a critical usability issue!'
Which of the following best describes David's concern regarding the missing `aria-label`?David is highlighting a problem related to semantic accessibility. The `aria-label` attribute is specifically designed to provide textual descriptions for UI elements when screen readers cannot determine the meaning from the element's content or associated HTML structure. Misinterpreting this as a contrast issue, keyboard focus problem, or JavaScript error would miss the core point of using `aria-label` to improve accessibility for users with disabilities. It's crucial to ensure that assistive technologies correctly interpret and announce these labels.8 / 25
During a code review for a new e-commerce feature, Maria points out that the 'Add to Cart' button isn't announcing any text when focused with VoiceOver. She says, 'The screen reader isn't saying anything about the button.' Which of these statements best captures Maria's observation and its significance?
Maria's comment highlights a problem with 'screen reader output.' While a missing title attribute or semantic issues can contribute to accessibility problems, the core issue here is that VoiceOver (or another screen reader) simply isn't announcing any text related to the button when it receives focus. This means users relying on screen readers are unable to understand the button's purpose—a critical usability failure. The correct answer focuses on the lack of audible feedback from the screen reader itself, not a specific underlying HTML problem.
9 / 25
John: 'I just reviewed this pull request. VoiceOver isn't announcing the `aria-describedby` attribute on the product image. It's a potential issue for screen reader users who rely on image descriptions.' What is John primarily concerned about in his feedback?John is correctly identifying a problem related to accessibility. The
aria-describedby attribute is used to link an element to another element that provides more detailed information – in this case, likely a description of the product image for screen reader users. Simply having an alt text isn't sufficient; `aria-describedby` allows for richer descriptions and ensures the screen reader can effectively convey the image's meaning. The other options relate to different aspects of code review but don't directly address the core issue of providing accessible information for visually impaired users via a screen reader.10 / 25
Alex's comment indicates a problem with screen reader output. Specifically, he's pointing out that VoiceOver (a common screen reader) isn't providing any textual information about the 'Remember Me' checkbox. This typically happens when the checkbox lacks an appropriate
aria-label attribute, which is crucial for screen readers to announce its purpose and value to the user. The other options represent different accessibility issues – contrast, code errors, or overall form compliance – but don't directly address the issue of missing screen reader output.11 / 25
Sarah, during a code review of the React component for our mobile app, flagged that the `TextInput` wasn't announcing its placeholder text. She said, 'The screen reader isn't reading out the "Enter your email" placeholder.' Which term best describes what Sarah is referring to when she mentions the screen reader 'not reading out' the placeholder? A) Accessibility Audit
B) Screen Reader Output
C) Semantic HTML Validation
D) Keyboard Navigation
Sarah is describing the process of the screen reader vocalizing content – specifically, the placeholder text within the `TextInput` component. 'Screen Reader Output' is the most accurate term here; it directly refers to the audible presentation of information by assistive technology. Options A and C relate to broader accessibility practices, while option D describes how a user navigates using keyboard controls, not the actual output of the screen reader itself.
12 / 25
David: 'I've just reviewed this PR. The screen reader isn't announcing the `aria-label` on the primary action button. It's a critical usability issue!'
Which of the following best describes David's concern regarding the missing `aria-label`?David is highlighting a problem related to semantic accessibility. The `aria-label` attribute is specifically designed to provide textual descriptions for UI elements when screen readers cannot determine the meaning from the element's content or associated HTML structure. Misinterpreting this as a contrast issue, keyboard focus problem, or JavaScript error would miss the core point of using `aria-label` to improve accessibility for users with disabilities. It's crucial to ensure that assistive technologies correctly interpret and announce these labels.13 / 25
During a code review for a new e-commerce feature, Maria points out that the 'Add to Cart' button isn't announcing any text when focused with VoiceOver. She says, 'The screen reader isn't saying anything about the button.' Which of these statements best captures Maria's observation and its significance?
Maria's comment highlights a problem with 'screen reader output.' While a missing title attribute or semantic issues can contribute to accessibility problems, the core issue here is that VoiceOver (or another screen reader) simply isn't announcing any text related to the button when it receives focus. This means users relying on screen readers are unable to understand the button's purpose—a critical usability failure. The correct answer focuses on the lack of audible feedback from the screen reader itself, not a specific underlying HTML problem.
14 / 25
John: 'I just reviewed this pull request. VoiceOver isn't announcing the `aria-describedby` attribute on the product image. It's a potential issue for screen reader users who rely on image descriptions.' What is John primarily concerned about in his feedback?John is correctly identifying a problem related to accessibility. The
aria-describedby attribute is used to link an element to another element that provides more detailed information – in this case, likely a description of the product image for screen reader users. Simply having an alt text isn't sufficient; `aria-describedby` allows for richer descriptions and ensures the screen reader can effectively convey the image's meaning. The other options relate to different aspects of code review but don't directly address the core issue of providing accessible information for visually impaired users via a screen reader.15 / 25
Alex's comment indicates a problem with screen reader output. Specifically, he's pointing out that VoiceOver (a common screen reader) isn't providing any textual information about the 'Remember Me' checkbox. This typically happens when the checkbox lacks an appropriate
aria-label attribute, which is crucial for screen readers to announce its purpose and value to the user. The other options represent different accessibility issues – contrast, code errors, or overall form compliance – but don't directly address the issue of missing screen reader output.16 / 25
Sarah, during a code review of the React component for our mobile app, flagged that the `TextInput` wasn't announcing its placeholder text. She said, 'The screen reader isn't reading out the "Enter your email" placeholder.' Which term best describes what Sarah is referring to when she mentions the screen reader 'not reading out' the placeholder? A) Accessibility Audit
B) Screen Reader Output
C) Semantic HTML Validation
D) Keyboard Navigation
Sarah is describing the process of the screen reader vocalizing content – specifically, the placeholder text within the `TextInput` component. 'Screen Reader Output' is the most accurate term here; it directly refers to the audible presentation of information by assistive technology. Options A and C relate to broader accessibility practices, while option D describes how a user navigates using keyboard controls, not the actual output of the screen reader itself.
17 / 25
David: 'I've just reviewed this PR. The screen reader isn't announcing the `aria-label` on the primary action button. It's a critical usability issue!'
Which of the following best describes David's concern regarding the missing `aria-label`?David is highlighting a problem related to semantic accessibility. The `aria-label` attribute is specifically designed to provide textual descriptions for UI elements when screen readers cannot determine the meaning from the element's content or associated HTML structure. Misinterpreting this as a contrast issue, keyboard focus problem, or JavaScript error would miss the core point of using `aria-label` to improve accessibility for users with disabilities. It's crucial to ensure that assistive technologies correctly interpret and announce these labels.18 / 25
During a code review for a new e-commerce feature, Maria points out that the 'Add to Cart' button isn't announcing any text when focused with VoiceOver. She says, 'The screen reader isn't saying anything about the button.' Which of these statements best captures Maria's observation and its significance?
Maria's comment highlights a problem with 'screen reader output.' While a missing title attribute or semantic issues can contribute to accessibility problems, the core issue here is that VoiceOver (or another screen reader) simply isn't announcing any text related to the button when it receives focus. This means users relying on screen readers are unable to understand the button's purpose—a critical usability failure. The correct answer focuses on the lack of audible feedback from the screen reader itself, not a specific underlying HTML problem.
19 / 25
John: 'I just reviewed this pull request. VoiceOver isn't announcing the `aria-describedby` attribute on the product image. It's a potential issue for screen reader users who rely on image descriptions.' What is John primarily concerned about in his feedback?John is correctly identifying a problem related to accessibility. The
aria-describedby attribute is used to link an element to another element that provides more detailed information – in this case, likely a description of the product image for screen reader users. Simply having an alt text isn't sufficient; `aria-describedby` allows for richer descriptions and ensures the screen reader can effectively convey the image's meaning. The other options relate to different aspects of code review but don't directly address the core issue of providing accessible information for visually impaired users via a screen reader.20 / 25
Alex's comment indicates a problem with screen reader output. Specifically, he's pointing out that VoiceOver (a common screen reader) isn't providing any textual information about the 'Remember Me' checkbox. This typically happens when the checkbox lacks an appropriate
aria-label attribute, which is crucial for screen readers to announce its purpose and value to the user. The other options represent different accessibility issues – contrast, code errors, or overall form compliance – but don't directly address the issue of missing screen reader output.21 / 25
Sarah, during a code review of the React component for our mobile app, flagged that the `TextInput` wasn't announcing its placeholder text. She said, 'The screen reader isn't reading out the "Enter your email" placeholder.' Which term best describes what Sarah is referring to when she mentions the screen reader 'not reading out' the placeholder? A) Accessibility Audit
B) Screen Reader Output
C) Semantic HTML Validation
D) Keyboard Navigation
Sarah is describing the process of the screen reader vocalizing content – specifically, the placeholder text within the `TextInput` component. 'Screen Reader Output' is the most accurate term here; it directly refers to the audible presentation of information by assistive technology. Options A and C relate to broader accessibility practices, while option D describes how a user navigates using keyboard controls, not the actual output of the screen reader itself.
22 / 25
David: 'I've just reviewed this PR. The screen reader isn't announcing the `aria-label` on the primary action button. It's a critical usability issue!'
Which of the following best describes David's concern regarding the missing `aria-label`?David is highlighting a problem related to semantic accessibility. The `aria-label` attribute is specifically designed to provide textual descriptions for UI elements when screen readers cannot determine the meaning from the element's content or associated HTML structure. Misinterpreting this as a contrast issue, keyboard focus problem, or JavaScript error would miss the core point of using `aria-label` to improve accessibility for users with disabilities. It's crucial to ensure that assistive technologies correctly interpret and announce these labels.23 / 25
During a code review for a new e-commerce feature, Maria points out that the 'Add to Cart' button isn't announcing any text when focused with VoiceOver. She says, 'The screen reader isn't saying anything about the button.' Which of these statements best captures Maria's observation and its significance?
Maria's comment highlights a problem with 'screen reader output.' While a missing title attribute or semantic issues can contribute to accessibility problems, the core issue here is that VoiceOver (or another screen reader) simply isn't announcing any text related to the button when it receives focus. This means users relying on screen readers are unable to understand the button's purpose—a critical usability failure. The correct answer focuses on the lack of audible feedback from the screen reader itself, not a specific underlying HTML problem.
24 / 25
John: 'I just reviewed this pull request. VoiceOver isn't announcing the `aria-describedby` attribute on the product image. It's a potential issue for screen reader users who rely on image descriptions.' What is John primarily concerned about in his feedback?John is correctly identifying a problem related to accessibility. The
aria-describedby attribute is used to link an element to another element that provides more detailed information – in this case, likely a description of the product image for screen reader users. Simply having an alt text isn't sufficient; `aria-describedby` allows for richer descriptions and ensures the screen reader can effectively convey the image's meaning. The other options relate to different aspects of code review but don't directly address the core issue of providing accessible information for visually impaired users via a screen reader.25 / 25
Alex's comment indicates a problem with screen reader output. Specifically, he's pointing out that VoiceOver (a common screen reader) isn't providing any textual information about the 'Remember Me' checkbox. This typically happens when the checkbox lacks an appropriate
aria-label attribute, which is crucial for screen readers to announce its purpose and value to the user. The other options represent different accessibility issues – contrast, code errors, or overall form compliance – but don't directly address the issue of missing screen reader output.Frequently Asked Questions
What will I practice in "Screen Reader Testing Workflows"?
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.