Accessibility in Technology (a11y)

Section 1

Quick Answer

Designing products, devices, and environments so people with disabilities can use them effectively, often abbreviated a11y — covering features like screen readers, captions, keyboard navigation, high-contrast modes, and alt-text. In a classroom problem, reach for Accessibility when the question is whether a person with a visual, hearing, motor, or cognitive limitation can use a product, and what feature removes the barrier. Compliance is measured against WCAG's POUR principles. The nearest confusions are User Interface (general usability and layout for a typical user) and Ethics of Computing (broad fairness without a specific disability barrier).

Section 2

Why This Matters

About 15% of the world's population has some form of disability. Inaccessible technology excludes over a billion people. Moreover, accessible design benefits everyone—captions help in noisy environments, and voice control helps when your hands are full.

Section 3

Intuitive Explanation

Accessibility means designing technology so everyone can use it — not just people with perfect vision, hearing, and motor control. The key move is to spot a barrier that excludes someone with a disability, then identify the assistive feature that removes it: a screen reader for a blind user, captions for a deaf user, keyboard navigation for someone who can't use a mouse, a high-contrast mode for low vision.

The formal yardstick is WCAG (Web Content Accessibility Guidelines), with levels A, AA, and AAA and the four POUR principles — Perceivable, Operable, Understandable, Robust. When you meet a problem, check which principle is at risk: is the content perceivable (alt-text, captions), operable (keyboard, not mouse-only), understandable, and robust across assistive tools?

A weak answer treats accessibility as something to bolt on at the end, or considers only visual disability. A stronger answer designs for it from the start and remembers motor, hearing, and cognitive needs too — and notes that the same features help everyone, like captions in a noisy room. Don't confuse this with User Interface, which is about layout and usability for a typical user, or with the broad fairness questions of Ethics of Computing.

Core idea

Good accessibility design benefits everyone, not just people with disabilities. Captions help in noisy environments; voice control helps when your hands are full.

Section 4

When to Use

Use Accessibility when the task is about whether people with disabilities can use a product, and what features make that possible. Look for signals such as screen reader, captions, alt-text, keyboard navigation, high-contrast mode, a11y, or WCAG/POUR, then verify with this question: Can someone with a visual, hearing, motor, or cognitive limitation use this effectively? Do not pick it for any design question — if no disability barrier or assistive feature is at stake, the task is probably User Interface (general usability) or Ethics of Computing (broad fairness).

Pro tip

When designing for accessibility, follow the POUR principles: Perceivable (can users perceive all content?), Operable (can users navigate and interact?), Understandable (is the interface clear?), and Robust (does it work with assistive technologies?). Test with screen readers and keyboard-only navigation.

Section 5

How to Recognize It

Before using Accessibility, ask: does the prompt turn on whether someone with a disability can actually use the product?

Does the prompt name a disability or limitation — blindness, deafness, low vision, limited motor control, cognitive differences — and whether a product works for that person?

Yes means Accessibility is the concept; the issue is usability for people with disabilities. No disability and no barrier means look elsewhere.
Does the answer involve an assistive feature — screen reader, captions, alt-text, keyboard navigation, high-contrast mode, or voice control?

Those features are the signature of Accessibility. If the design question is purely about layout or look for a typical user, it's closer to User Interface.
Does a standard like WCAG or its POUR principles (Perceivable, Operable, Understandable, Robust) frame the requirement?

WCAG levels (A, AA, AAA) and POUR are the formal yardstick for Accessibility — a strong signal it's this concept.
Is the benefit framed as including everyone, not just disabled users — captions in a noisy room, voice control with full hands?

That 'good for all' framing is a hallmark of Accessibility; it's still the same concept, just showing why inclusive design helps broadly.
Could this be the nearest neighbor instead — User Interface (general usability) or Ethics of Computing (broad fairness)?

If no disability barrier or assistive feature is involved, reconsider those. Otherwise keep Accessibility and name the barrier you're removing.

Section 6

Accessibility vs User Interface vs Ethics of Computing vs Cybersecurity

Accessibility sits near design and fairness topics, so a problem can read like any of these. The deciding cue is a disability barrier and an assistive feature; the others are general usability, broad morality, or defending against an attacker.

Accessibility vs User Interface vs Ethics of Computing vs Cybersecurity
Type	Meaning	Key test	Formula	Example
Accessibility	Pick Accessibility when the task is whether people with disabilities can use a product, and what feature removes the barrier — screen readers, captions, alt-text, keyboard navigation, high-contrast, a11y, WCAG/POUR.	Can someone with a visual, hearing, motor, or cognitive limitation use this effectively?	$\text{WCAG: Perceivable, Operable, Understandable, Robust}$	Adding captions so a deaf user can follow a video, and alt-text so a blind user's screen reader can describe images.
User Interface	Pick User Interface when the task is how the screen and controls are laid out for a typical user — buttons, menus, fields, icons, layout — with no disability barrier at stake.	Is this about how a typical user interacts with the visible controls?	$\text{UI: buttons, menus, layout}$	A calculator app's number buttons, operation buttons, and display screen.
Ethics of Computing	Pick Ethics of Computing when the task is the broad right-and-wrong of a computing choice — not about a specific disability barrier or assistive feature.	Is this asking whether a computing choice is morally right, in general?	$\text{should we?}$	Should facial recognition be used for mass surveillance?
Cybersecurity	Pick Cybersecurity when the task is defending a system from a deliberate attacker — not about who can use the product.	Is someone trying to break in, and we are defending against them?	$\{\text{confidentiality}, \text{integrity}, \text{availability}\}$	Requiring two-factor login so a stolen password alone cannot unlock an account.

Accessibility

Meaning: Pick Accessibility when the task is whether people with disabilities can use a product, and what feature removes the barrier — screen readers, captions, alt-text, keyboard navigation, high-contrast, a11y, WCAG/POUR.
Key test: Can someone with a visual, hearing, motor, or cognitive limitation use this effectively?
Formula: $\text{WCAG: Perceivable, Operable, Understandable, Robust}$
Example: Adding captions so a deaf user can follow a video, and alt-text so a blind user's screen reader can describe images.

User Interface

Meaning: Pick User Interface when the task is how the screen and controls are laid out for a typical user — buttons, menus, fields, icons, layout — with no disability barrier at stake.
Key test: Is this about how a typical user interacts with the visible controls?
Formula: $\text{UI: buttons, menus, layout}$
Example: A calculator app's number buttons, operation buttons, and display screen.

Ethics of Computing

Meaning: Pick Ethics of Computing when the task is the broad right-and-wrong of a computing choice — not about a specific disability barrier or assistive feature.
Key test: Is this asking whether a computing choice is morally right, in general?
Formula: $\text{should we?}$
Example: Should facial recognition be used for mass surveillance?

Cybersecurity

Meaning: Pick Cybersecurity when the task is defending a system from a deliberate attacker — not about who can use the product.
Key test: Is someone trying to break in, and we are defending against them?
Formula: $\{\text{confidentiality}, \text{integrity}, \text{availability}\}$
Example: Requiring two-factor login so a stolen password alone cannot unlock an account.

Section 7

Formula & Notation

Section 8

Worked Examples

Example 1 — Recognize the model

Easy

Problem

A class sees this computing situation: students evaluate a school app that collects data and decide what benefits, risks, accessibility needs, and safeguards matter. How should a student decide whether Accessibility is the right model?

Solution

Identify the target of the reasoning.

The target might be a problem, data representation, code state, system component, user need, or stakeholder.
List the process or relationship that matters.

Accessibility is useful when the problem asks for an impact analysis with stakeholders, benefit, risk, evidence, safeguard, and tradeoff stated.
Apply the recognition test: Am I evaluating a computing choice by naming stakeholders, benefits, harms, data use, and responsible safeguards?

This separates accessibility from technical feature only and personal opinion.
State the evidence that would prove the answer.

A trace, test, diagram, input-output pair, or impact argument prevents a vague answer.

Answer

Use Accessibility only if the task is asking for an impact analysis with stakeholders, benefit, risk, evidence, safeguard, and tradeoff stated and the situation passes the recognition test. Otherwise, choose the nearby model that better matches the computing structure.

Takeaway: Model choice comes before definitions. The same words can belong to different CS ideas depending on the problem structure.

Example 2 — Avoid the vocabulary trap

Standard

Problem

A student says, "This prompt contains the word privacy, so I should use accessibility." Explain why that shortcut is risky.

Solution

Treat the word as a clue, not proof.

CS vocabulary overlaps across problem solving, programming, data, systems, design, and impact questions.
Check whether the target and process match Accessibility.

The computing structure decides the model.
Compare with Technical feature only and Personal opinion.

A feature may work technically while still creating social, privacy, access, or fairness concerns. Impact analysis must name stakeholders, evidence, tradeoffs, and safeguards, not just preference.
State what the final result would mean.

If the final result would not mean an impact analysis with stakeholders, benefit, risk, evidence, safeguard, and tradeoff stated, the model is probably wrong.

Answer

The shortcut is risky because privacy can appear in several related CS models. The student must first show that the task answers "Am I evaluating a computing choice by naming stakeholders, benefits, harms, data use, and responsible safeguards?" with yes.

Takeaway: A CS thinking concept is a reasoning tool, not just a vocabulary match.

Example 3 — Write the computing conclusion

Application

Problem

After solving a Accessibility problem, a student writes only a definition. What should be added to make the answer useful?

Solution

Name the specific case.

The answer should identify the input, data, program state, system component, user, or stakeholder being described.
Show the process or evidence.

A trace, test, example, diagram, or tradeoff explains why the concept applies.
Connect the result to the goal.

The final sentence should say how the concept helps solve, test, design, represent, protect, or evaluate the computing situation.
Mention limits or edge cases.

Computing answers are stronger when they state where the method might fail, scale poorly, exclude users, or require a different design.

Answer

A complete answer should say what accessibility controls in the specific situation, include evidence such as a trace or test, and state any condition needed for the model to apply.

Takeaway: The final explanation is part of CS thinking, not an optional sentence after the term.

Section 9

Common Mistakes

Common slip-up

Treating accessibility as an afterthought to add at the end instead of designing for it from the start

The right idea

Fix this by naming the input, process, output, evidence, and checking "Am I evaluating a computing choice by naming stakeholders, benefits, harms, data use, and responsible safeguards?" before using the concept.

Common slip-up

Only considering visual disabilities—accessibility also covers hearing, motor, cognitive, and neurological disabilities

The right idea

Fix this by naming the input, process, output, evidence, and checking "Am I evaluating a computing choice by naming stakeholders, benefits, harms, data use, and responsible safeguards?" before using the concept.

Common slip-up

Assuming accessibility only benefits disabled users—features like captions, voice control, and responsive design improve the experience for everyone

The right idea

Fix this by naming the input, process, output, evidence, and checking "Am I evaluating a computing choice by naming stakeholders, benefits, harms, data use, and responsible safeguards?" before using the concept.

Common slip-up

Using accessibility from a keyword alone

The right idea

Signal words like privacy, security, ethics only point to a possible model; the computing structure must match too.

Section 10

Mini Practice

Try these on your own. Tap Reveal when you want to check.

What clue tells you this is Accessibility: A video platform adds captions so that deaf and hard-of-hearing users can follow the audio.

Hint: Which disability barrier is being removed, and how?
Why is this User Interface, not Accessibility: A designer rearranges a calculator app's buttons so the most-used operations sit closer to the display.

Hint: Is a disability barrier at stake, or general layout for a typical user?
Why is this Ethics of Computing, not Accessibility: A company debates whether it is fair to release a product that excludes users in low-income regions.

Hint: A disability/assistive-feature question, or a broad fairness debate?
Which concept fits: A website is redesigned so every interactive element can be reached and activated with the keyboard alone, for users who cannot use a mouse.

Hint: Who is being enabled, and against what barrier?
What clue tells you this is Accessibility: An image gallery is updated so every photo has alt-text that a screen reader can read aloud to blind users.

Hint: What feature serves which group, and which WCAG principle?
Spot the mismatch: A student labels 'making login require two-factor authentication' as an Accessibility improvement. Is that right?

Hint: Defending against an attacker, or removing a disability barrier?

Want the full set?

50 practice questions for this concept — free to try, every one with a complete worked solution showing the why, not just the answer.

Practice this concept → Take a mastery check

Section 11

Frequently Asked Questions

What is Accessibility in simple terms?

Accessibility (often abbreviated a11y) is designing products, devices, and environments so people with disabilities can use them effectively. In short: design so everyone can use it. It includes features like screen readers, captions, keyboard navigation, high-contrast modes, and alt-text for images.

How do I recognize an Accessibility problem?

Ask: can someone with a visual, hearing, motor, or cognitive limitation use this effectively? Strong signals are screen reader, captions, alt-text, keyboard navigation, high-contrast mode, a11y, or WCAG/POUR. If the problem is about removing a disability barrier with an assistive feature, it is Accessibility.

How is Accessibility measured?

Compliance is measured against standards such as WCAG (Web Content Accessibility Guidelines), which define levels A, AA, and AAA across four principles known as POUR: Perceivable, Operable, Understandable, and Robust. Pointing to a POUR principle or a WCAG level is a sign you are in an accessibility problem.

How is Accessibility different from User Interface?

User interface is how the screen and controls are laid out for a typical user — buttons, menus, layout. Accessibility asks whether people with disabilities can use those controls, and what features remove barriers. A UI can look clean yet be inaccessible (for example, images with no alt-text for screen readers). If a disability barrier or assistive feature is at stake, it is Accessibility; otherwise it is User Interface.

What is the most common mistake with Accessibility?

Two mistakes. First, treating accessibility as an afterthought bolted on at the end, instead of designing for it from the start. Second, considering only visual disabilities; accessibility also covers hearing (captions), motor (keyboard navigation), and cognitive limitations.

Does Accessibility only mean features for blind users?

No. Accessibility spans many disabilities: screen readers and high-contrast modes for visual limitations, captions for deaf users, keyboard navigation for people who cannot use a mouse, and clear, simple design for cognitive needs. Limiting it to one group is a common misconception.

Section 12

Learning Path

← Before

No prerequisites

Accessibility

You are here

Next →

Ethics of Computing User Interface

Before this, students should be able to identify inputs, outputs, data, processes, users, and system parts in a computing situation. This page focuses on the recognition cue: Am I evaluating a computing choice by naming stakeholders, benefits, harms, data use, and responsible safeguards? That cue connects earlier computing descriptions to later problem solving because students first choose the model, then choose the representation, code, test, diagram, or explanation. After this, Ethics of Computing and User Interface become easier to recognize.

Section 13