5 exercises — Master the vocabulary for making the business case for accessibility: ROI arguments, legal risk, roadmap framing, and responding to stakeholder objections.
0 / 18 completed
1 / 18
A product manager asks: "Why should we prioritise accessibility now? Our analytics don't show many disabled users."
Which response is the most effective business case argument?
Effective accessibility advocacy combines three business arguments:
1. Market size (the analytics problem):
• ~1.3 billion people globally have some form of disability (WHO)
• Analytics under-count them — users with assistive technologies often block JavaScript, skew session data
• The "disability" label misses situational disability: someone using the app one-handed while commuting
2. Total user benefit (the curb-cut effect):
• Captions benefit: deaf users + non-native speakers + noisy environments + silent commuters
• High contrast benefits: users with low vision + people in bright sunlight
• Keyboard navigation benefits: power users, developers, enterprise users
3. Cost of retrofitting:
• Research shows post-launch accessibility fixes cost 5–10× more than building in during design
• Every sprint that ships inaccessible features adds to the debt
Key vocabulary:
• addressable market — the total potential customers for a product
• curb-cut effect — accessibility features that benefit a broader population than originally intended
• retrofit — adding accessibility to existing code after the fact
• analytics under-counting — when tracking tools miss segments of users who use workarounds
2 / 18
A legal team asks you to explain the difference between ADA, WCAG, and EAA. Which explanation is correct?
Understanding the legal landscape is essential for accessibility advocacy:
ADA (Americans with Disabilities Act) — 1990, US:
• Civil rights law prohibiting discrimination against people with disabilities
• Courts have repeatedly held that websites are "places of public accommodation" covered by the ADA
• No specific technical standard mandated, but WCAG 2.1 AA is the de facto standard used in settlements
• Thousands of ADA web accessibility lawsuits filed annually
WCAG (Web Content Accessibility Guidelines) — W3C:
• Technical standard, not a law itself
• Levels: A (minimum), AA (standard), AAA (enhanced)
• WCAG 2.1 AA is the most widely required level in law and procurement
• WCAG 2.2 published October 2023 with new criteria
EAA (European Accessibility Act) — EU Directive 2019/882:
• Became enforceable June 28, 2025 in EU member states
• Requires WCAG conformance for digital products and services sold in the EU
• Penalties vary by member state; significant fines possible
Other laws to know:
• Section 508 (US federal procurement), EN 301 549 (EU standard for public procurement), AODA (Canada/Ontario)
Key vocabulary:
• conformance — meeting all requirements of a standard (WCAG conformance)
• AA (Double-A) — the intermediate WCAG conformance level required by most laws
• procurement requirement — an accessibility condition that must be met for a product to be purchased by government
3 / 18
An engineer pushes back: "Accessibility is a niche concern — our users are developers, they don't have disabilities."
How do you respond most effectively?
Countering the "our users don't have disabilities" myth requires facts and concrete examples:
Reality check on developer disability rates:
• The Stack Overflow Developer Survey consistently shows ~13-20% of developers report some form of disability
• Developer tools (IDEs, dashboards, CLI tools, web portals) are used by people with visual, motor, and cognitive disabilities
• Companies: Salesforce, Microsoft (VS Code), GitHub, GitLab all have dedicated accessibility programs for developer tools
The power user argument:
• Keyboard navigation = faster for all developers, not just those who need it
• Screen reader-compatible tables = better semantic structure for all users
• High-contrast themes = already a popular feature in every major IDE
The inclusive team argument:
• When you build inaccessible tools, you can't hire disabled developers (your users become your colleagues)
• Cognitive accessibility (clear error messages, predictable navigation) reduces cognitive load for everyone under stress
Key vocabulary:
• DX (Developer Experience) — the overall experience of developers using a tool or platform
• keyboard-first — design approach that ensures full functionality via keyboard before adding mouse interactions
• cognitive load — the mental effort required to use a system; accessibility reduces cognitive load for all users
4 / 18
A CFO asks: "What's the ROI on accessibility? Give me a number."
Which response most effectively answers the question?
CFOs respond to numbers — accessibility advocacy must speak the language of risk and return:
Quantifiable legal risk (most compelling for CFOs):
• ADA Title III web accessibility lawsuits: 4,000+ filed in US in recent years
• Average settlement: $25,000–$90,000 (small companies) to multi-million (large brands)
• Court-ordered remediation: often requires external audit + redesign under monitoring
• Repeat plaintiff risk: serial litigants file hundreds of cases — once flagged, you may face multiple suits
Revenue argument:
• Accessible e-commerce sites report higher conversion from users with disabilities
• Click-Away Pound Report (UK): disabled users spend £420 billion annually; inaccessible sites lose this revenue
• Forrester Research: accessible sites have lower bounce rates and higher overall usability scores
Cost avoidance (proactive vs reactive):
• IBM research: fixing a bug during design = $1; during testing = $15; post-release = $100
• Accessibility debt compounds just like technical debt
Key vocabulary:
• ROI (Return on Investment) — the financial return relative to the cost of an investment
• remediation cost — the expense of fixing accessibility issues after they've been shipped
• legal exposure — the potential financial liability from lawsuits or regulatory fines
• proactive vs reactive — building in vs. fixing after the fact
5 / 18
You are presenting an accessibility roadmap to leadership. Which framing is most likely to secure budget approval?
Roadmap framing that wins budget approval uses: phased approach, cost quantification, and risk comparison.
Why "phased investment" framing works:
• Leadership can approve a manageable Phase 1 without committing to full compliance upfront
• Each phase shows measurable progress (fewer violations, design system integration)
• Risk reduction provides justification even without revenue lift numbers
Structure of a persuasive accessibility roadmap:
1. Current state audit: # WCAG AA violations, severity, affected flows
2. Legal risk quantification: probability × typical settlement cost
3. Phase 1 — P0 remediation: critical path violations; cost + timeline
4. Phase 2 — Design system integration: prevents future debt; shift-left
5. Phase 3 — Certification: VPAT, external audit, compliance statement
Language patterns for leadership presentations:
• "This investment reduces our legal exposure from X to Y"
• "Remediating post-launch costs 5× more than integrating into the design system now"
• "Phase 1 targets the flows most vulnerable to litigation: checkout, authentication, forms"
Key vocabulary:
• VPAT (Voluntary Product Accessibility Template) — a document that describes how a product meets accessibility standards; often required for enterprise/government procurement
• P0 violation — a critical accessibility barrier that prevents a user from completing a core task
• shift-left — integrating accessibility (or any quality concern) earlier in the development process
• compliance statement — a public declaration of a product's WCAG conformance level
6 / 18
// API Response (Partial)
```json
{
"status": "error",
"code": 400,
"message": "Invalid request: Missing required parameter 'label'. Ensure label is a string and has a maximum length of 64 characters.",
"details": {
"field": "label",
"reason": "invalid_value"
}
}
```
During a code review, your colleague points out this API response. You need to explain to the team why this specific error is significant from an accessibility perspective. Which comment best captures the issue?
The correct response highlights the direct impact on screen readers and WCAG compliance. The API's rejection of the `label` field because it's missing or improperly formatted demonstrates a failure to provide accessible text for assistive technology users – specifically violating guideline 1.4.1 (Info and Relationships). Options A and D are too dismissive, while option C is a general statement without referencing accessibility standards. It's crucial to translate technical errors into their implications for user experience, particularly for those with disabilities.
7 / 18
Sarah, a junior developer on your team, writes this PR description for a new form input field:
```html
```
During a code review, you notice the label associated with this input is missing. Which of the following responses would be most effective in communicating the importance of accessibility to Sarah?
This question assesses the ability to advocate effectively with a less experienced developer. Option B provides the correct technical solution – using `aria-label` or the `
8 / 18
// API Response (Partial)
```json
{
"status": "error",
"code": 400,
"message": "Invalid request: Missing required parameter 'label'. Ensure label is a string and has a maximum length of 64 characters.",
"details": {
"field": "label",
"reason": "invalid_value"
}
}
```
During a code review, your colleague points out this API response. You need to explain to the team why this specific error is significant from an accessibility perspective. Which comment best captures the issue?
The correct response highlights the direct impact on screen readers and WCAG compliance. The API's rejection of the `label` field because it's missing or improperly formatted demonstrates a failure to provide accessible text for assistive technology users – specifically violating guideline 1.4.1 (Info and Relationships). Options A and D are too dismissive, while option C is a general statement without referencing accessibility standards. It's crucial to translate technical errors into their implications for user experience, particularly for those with disabilities.
9 / 18
Sarah, a junior developer on your team, writes this PR description for a new form input field:
```html
```
During a code review, you notice the label associated with this input is missing. Which of the following responses would be most effective in communicating the importance of accessibility to Sarah?
This question assesses the ability to advocate effectively with a less experienced developer. Option B provides the correct technical solution – using `aria-label` or the `
10 / 18
// API Response (Partial)
```json
{
"status": "error",
"code": 400,
"message": "Invalid request: Missing required parameter 'label'. Ensure label is a string and has a maximum length of 64 characters.",
"details": {
"field": "label",
"reason": "invalid_value"
}
}
```
During a code review, your colleague points out this API response. You need to explain to the team why this specific error is significant from an accessibility perspective. Which comment best captures the issue?
The correct response highlights the direct impact on screen readers and WCAG compliance. The API's rejection of the `label` field because it's missing or improperly formatted demonstrates a failure to provide accessible text for assistive technology users – specifically violating guideline 1.4.1 (Info and Relationships). Options A and D are too dismissive, while option C is a general statement without referencing accessibility standards. It's crucial to translate technical errors into their implications for user experience, particularly for those with disabilities.
11 / 18
Sarah, a junior developer on your team, writes this PR description for a new form input field:
```html
```
During a code review, you notice the label associated with this input is missing. Which of the following responses would be most effective in communicating the importance of accessibility to Sarah?
This question assesses the ability to advocate effectively with a less experienced developer. Option B provides the correct technical solution – using `aria-label` or the `
12 / 18
// API Response (Partial)
```json
{
"status": "error",
"code": 400,
"message": "Invalid request: Missing required parameter 'label'. Ensure label is a string and has a maximum length of 64 characters.",
"details": {
"field": "label",
"reason": "invalid_value"
}
}
```
During a code review, your colleague points out this API response. You need to explain to the team why this specific error is significant from an accessibility perspective. Which comment best captures the issue?
The correct response highlights the direct impact on screen readers and WCAG compliance. The API's rejection of the `label` field because it's missing or improperly formatted demonstrates a failure to provide accessible text for assistive technology users – specifically violating guideline 1.4.1 (Info and Relationships). Options A and D are too dismissive, while option C is a general statement without referencing accessibility standards. It's crucial to translate technical errors into their implications for user experience, particularly for those with disabilities.
13 / 18
Sarah, a junior developer on your team, writes this PR description for a new form input field:
```html
```
During a code review, you notice the label associated with this input is missing. Which of the following responses would be most effective in communicating the importance of accessibility to Sarah?
This question assesses the ability to advocate effectively with a less experienced developer. Option B provides the correct technical solution – using `aria-label` or the `
14 / 18
During a Slack conversation with the design team about a new UI component, Alex says: 'Just make it look good – accessibility is for lawyers.' Which response best communicates the importance of considering accessibility from a development perspective?
The correct answer emphasizes the core principle of equal user experience. The misconception is that accessibility is solely a legal matter or a task for specialists. Options B and D downplay the importance of inclusive design, while option C correctly frames it as a fundamental usability concern. Option A provides a more detailed explanation and justification.
15 / 18
You're reviewing a code change that implements a new API endpoint. The documentation for the endpoint includes this JSON response:
```json
{
"status": "success",
"data": {
"userId": 123,
"userName": "John Doe"
}
}
```
The API client is experiencing issues and reporting a '400 Bad Request' error. Which of the following best describes how you should communicate this issue to the backend team?
The correct response acknowledges that while the *status* field indicates success, the *data* is missing. This suggests a problem with data handling on the client side (serialization, mapping). Options A and D deflect responsibility or suggest inappropriate troubleshooting steps. Option C misinterprets the meaning of a 400 error – it's a general indication of an invalid request, not necessarily a specific field being missing.
16 / 18
During a standup meeting, your team lead asks: 'Can you explain how our new mobile app's screen reader support aligns with WCAG 2.1 guidelines?' Which of the following is the MOST effective way to answer this question?
The best answer demonstrates a practical understanding of WCAG 2.1's success criteria, specifically Level AA color contrast and keyboard navigation. Options A is too vague, B focuses on a specific technique without context, and D is an insufficient justification for accessibility compliance.
17 / 18
You're writing a PR description for a new form field. What's the *most* important thing to include regarding accessibility?
The correct answer highlights the crucial role of labels in accessibility. Labels provide context for screen readers and allow users with disabilities to understand the purpose and value of each input field. Options A, B, and C are irrelevant to accessibility considerations.
18 / 18
A stakeholder asks: 'How much will making our website accessible cost us?' Which response demonstrates a strategic understanding of the investment?
The correct response frames accessibility as an investment rather than just a cost. It acknowledges potential legal and reputational benefits alongside the direct impact on user experience. Options A and B provide vague or transactional answers, while option C focuses solely on basic remediation, neglecting the broader strategic value.
What will I practice in "Accessibility Advocacy Language — English for IT Professionals"?
This is an Accessibility Language exercise set. It walks through 18 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 18 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.