Master vocabulary for inclusive design principles, persona spectrum, and accessibility advocacy. Advanced
0 / 22 completed
1 / 22
Microsoft's Inclusive Design framework describes "permanent, temporary, and situational" disability.
How does this model change how teams approach accessibility?
The persona spectrum model expands who benefits from accessibility features:
Disability type
One arm example
Permanent
Born with one arm
Temporary
Arm in a cast after injury
Situational
Holding a baby, carrying shopping
Curb cut effect: features designed for permanent disabilities benefit far more poeple — curb cuts designed for wheelchair users also help cyclists, parents with strollers, and delivery workers. Key vocabulary: "persona spectrum", "curb cut effect", "situational disability", "design for the margins benefits the mainstream".
2 / 22
"We should design for the margins, not the average user."
What does this principle mean in product design?
"Design for the margins" (Kat Holmes, Mismatch) — excluding people reveals design rigidity:
Structural rework of component tree, DOM, interaction model
If a component tree was built with div-based interactions, retrofitting ARIA and keyboard handling requires structural changes. Key vocabulary: "accessibility debt", "shift-left accessibility", "component API contract for accessibility", "retrofit cost".
5 / 22
The design system team is building an accessible-by-default component library.
What does "accessible by default" mean for a component library?
An accessible-by-default component library encapsulates accessibility complexity so feature teams don't have to re-implement it:
Component
Built-in accessibility
<Button />
Correct role, keyboard activation, focus ring, disabled state
<Modal />
ARIA dialog pattern, focus trap on open, Escape to close, returns focus on close
Benefits: accessibility at scale, reduced individual team expertise requirement, consistent screen reader experience. Key vocabulary: "WAI-ARIA Authoring Practices", "design system accessibility contract", "accessibility token".
6 / 22
Reviewer: 'The button's color contrast isn't ideal. Users with low vision might struggle to see it.'
You (as the UI designer) respond in a Slack message to the reviewer: 'Got it. I'll adjust the color palette and check the WCAG compliance levels for that button.'
Which of the following best describes the core issue being raised, and your response's focus?
The reviewer correctly identifies that the button's color contrast ratio falls short of accessibility standards (WCAG). This isn't simply about aesthetics; it addresses a core barrier for users with visual impairments. Your response demonstrates an understanding of this specific issue and a proactive step toward remediation – focusing on WCAG compliance is key to ensuring usability for everyone. The other options misinterpret the problem, suggesting aesthetic concerns or a broader UI redesign without addressing the fundamental accessibility gap.
7 / 22
Sarah, a senior developer, is drafting a PR description for a new data visualization component. She writes: 'This chart displays sales figures – it's pretty and easy to understand!'
Which of the following best describes the potential issue with Sarah's statement, and what should she add to improve accessibility?
Sarah's statement prioritizes aesthetics and perceived ease of understanding over accessibility. A crucial element of accessible design is providing alternative text descriptions (alt attributes) for all visual elements, including charts, so screen readers can convey the information to users who are visually impaired. Simply stating it's 'pretty and easy to understand' doesn't address the needs of diverse users.
8 / 22
Mark, a junior developer, is discussing accessibility with his team during a standup meeting. He says: 'We should focus on making this feature accessible *after* we've finished building it.'
Which of the following best explains why this approach is typically less effective and more costly?
Retrofitting accessibility after a feature is complete almost always involves substantial rework. It necessitates modifying existing code, potentially altering the application's architecture, and re-testing – all of which dramatically increase development time and cost compared to integrating accessibility considerations from the initial design phase.
9 / 22
Reviewer: 'The button's color contrast isn't ideal. Users with low vision might struggle to see it.'
You (as the UI designer) respond in a Slack message to the reviewer: 'Got it. I'll adjust the color palette and check the WCAG compliance levels for that button.'
Which of the following best describes the core issue being raised, and your response's focus?
The reviewer correctly identifies that the button's color contrast ratio falls short of accessibility standards (WCAG). This isn't simply about aesthetics; it addresses a core barrier for users with visual impairments. Your response demonstrates an understanding of this specific issue and a proactive step toward remediation – focusing on WCAG compliance is key to ensuring usability for everyone. The other options misinterpret the problem, suggesting aesthetic concerns or a broader UI redesign without addressing the fundamental accessibility gap.
10 / 22
Sarah, a senior developer, is drafting a PR description for a new data visualization component. She writes: 'This chart displays sales figures – it's pretty and easy to understand!'
Which of the following best describes the potential issue with Sarah's statement, and what should she add to improve accessibility?
Sarah's statement prioritizes aesthetics and perceived ease of understanding over accessibility. A crucial element of accessible design is providing alternative text descriptions (alt attributes) for all visual elements, including charts, so screen readers can convey the information to users who are visually impaired. Simply stating it's 'pretty and easy to understand' doesn't address the needs of diverse users.
11 / 22
Mark, a junior developer, is discussing accessibility with his team during a standup meeting. He says: 'We should focus on making this feature accessible *after* we've finished building it.'
Which of the following best explains why this approach is typically less effective and more costly?
Retrofitting accessibility after a feature is complete almost always involves substantial rework. It necessitates modifying existing code, potentially altering the application's architecture, and re-testing – all of which dramatically increase development time and cost compared to integrating accessibility considerations from the initial design phase.
12 / 22
Reviewer: 'The button's color contrast isn't ideal. Users with low vision might struggle to see it.'
You (as the UI designer) respond in a Slack message to the reviewer: 'Got it. I'll adjust the color palette and check the WCAG compliance levels for that button.'
Which of the following best describes the core issue being raised, and your response's focus?
The reviewer correctly identifies that the button's color contrast ratio falls short of accessibility standards (WCAG). This isn't simply about aesthetics; it addresses a core barrier for users with visual impairments. Your response demonstrates an understanding of this specific issue and a proactive step toward remediation – focusing on WCAG compliance is key to ensuring usability for everyone. The other options misinterpret the problem, suggesting aesthetic concerns or a broader UI redesign without addressing the fundamental accessibility gap.
13 / 22
Sarah, a senior developer, is drafting a PR description for a new data visualization component. She writes: 'This chart displays sales figures – it's pretty and easy to understand!'
Which of the following best describes the potential issue with Sarah's statement, and what should she add to improve accessibility?
Sarah's statement prioritizes aesthetics and perceived ease of understanding over accessibility. A crucial element of accessible design is providing alternative text descriptions (alt attributes) for all visual elements, including charts, so screen readers can convey the information to users who are visually impaired. Simply stating it's 'pretty and easy to understand' doesn't address the needs of diverse users.
14 / 22
Mark, a junior developer, is discussing accessibility with his team during a standup meeting. He says: 'We should focus on making this feature accessible *after* we've finished building it.'
Which of the following best explains why this approach is typically less effective and more costly?
Retrofitting accessibility after a feature is complete almost always involves substantial rework. It necessitates modifying existing code, potentially altering the application's architecture, and re-testing – all of which dramatically increase development time and cost compared to integrating accessibility considerations from the initial design phase.
15 / 22
Reviewer: 'The button's color contrast isn't ideal. Users with low vision might struggle to see it.'
You (as the UI designer) respond in a Slack message to the reviewer: 'Got it. I'll adjust the color palette and check the WCAG compliance levels for that button.'
Which of the following best describes the core issue being raised, and your response's focus?
The reviewer correctly identifies that the button's color contrast ratio falls short of accessibility standards (WCAG). This isn't simply about aesthetics; it addresses a core barrier for users with visual impairments. Your response demonstrates an understanding of this specific issue and a proactive step toward remediation – focusing on WCAG compliance is key to ensuring usability for everyone. The other options misinterpret the problem, suggesting aesthetic concerns or a broader UI redesign without addressing the fundamental accessibility gap.
16 / 22
Sarah, a senior developer, is drafting a PR description for a new data visualization component. She writes: 'This chart displays sales figures – it's pretty and easy to understand!'
Which of the following best describes the potential issue with Sarah's statement, and what should she add to improve accessibility?
Sarah's statement prioritizes aesthetics and perceived ease of understanding over accessibility. A crucial element of accessible design is providing alternative text descriptions (alt attributes) for all visual elements, including charts, so screen readers can convey the information to users who are visually impaired. Simply stating it's 'pretty and easy to understand' doesn't address the needs of diverse users.
17 / 22
Mark, a junior developer, is discussing accessibility with his team during a standup meeting. He says: 'We should focus on making this feature accessible *after* we've finished building it.'
Which of the following best explains why this approach is typically less effective and more costly?
Retrofitting accessibility after a feature is complete almost always involves substantial rework. It necessitates modifying existing code, potentially altering the application's architecture, and re-testing – all of which dramatically increase development time and cost compared to integrating accessibility considerations from the initial design phase.
18 / 22
Reviewer: 'The form field lacks a clear label. Screen reader users need to understand what information is expected.' You are the UI developer responding to this comment. Which of the following best describes your next action?
// Example code - does not need to be functional
The correct approach is to use `aria-labelledby` which provides a semantic link between the visible label and the input element for screen readers. Placeholder text isn't reliable for conveying required information, and changing the input type doesn't automatically create proper labels. Ignoring accessibility feedback will lead to usability issues for users with disabilities.
19 / 22
A teammate sends a Slack message: 'Just added some dynamic content to the page – it's really engaging!' You're responsible for ensuring this content is accessible. Which response best addresses their comment while advocating for accessibility?
Consider the potential impact on users who rely on assistive technologies.
The best response acknowledges their enthusiasm but immediately raises accessibility concerns regarding color contrast and alternative text (alt text). These are crucial elements for users with visual impairments. The other options either ignore the accessibility need or express a purely aesthetic focus, which is unacceptable in inclusive design.
20 / 22
Sarah, a senior developer, is drafting a PR description for a new API endpoint. She writes: 'This endpoint returns JSON data representing product information – it's well-structured and easy to parse.' What key aspect of accessibility should Sarah *specifically* address in her PR description?
Developers often focus on the technical structure of APIs, but accessibility requires more than just data formatting.
While JSON validity, HTTPS security, and error handling are important API considerations, Sarah's primary responsibility is to highlight how *users* with disabilities will interact with the data. Specifically mentioning access via assistive technologies demonstrates a commitment to inclusive design and directs attention to the necessary accessibility aspects of the endpoint.
21 / 22
Mark, a junior developer, is discussing accessibility with his team during a standup meeting. He says: 'I'm working on the new search component – I'll make sure it's accessible.' Which of the following best describes what Mark should be doing to *demonstrate* this commitment?
Don't just state intent; provide concrete actions.
Mark should be actively researching and applying relevant accessibility standards (WCAG) to his work. Reviewing guidelines provides a framework for understanding requirements. The other options represent vague intentions or delegation of responsibility – Mark needs to take ownership and demonstrate practical knowledge.
22 / 22
An API returns the following JSON response:
{
"status": "success",
"data": {
"productName": "Laptop X",
"price": 1299.99,
"description": "A powerful laptop for professionals."
}
}
You need to ensure this response is accessible. Which of the following actions would *most* directly contribute to accessibility?
Focus on providing semantic information that assistive technologies can interpret.
The most effective way to make this API response accessible is to provide descriptive labels and alternative text for each data field. This allows screen readers to accurately convey the meaning of the information to users with visual impairments. Formatting as currency and using numeric values are important but don't directly address accessibility.
What will I practice in "Inclusive Design Language | Accessibility Exercises"?
This is an Accessibility Language exercise set. It walks through 22 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 22 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.