Not sure which lesson to do first? Find your level and get a plan →

CS Thinking · Systems, Networks & Impact · Grade 6-8

Accessibility

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.


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. You use it whenever you build or check something people will use: a website, an app, a game, a video, a sign-up form. It works by finding the spot where a design demands one particular ability, such as seeing color, hearing speech or steering a mouse, and adding a second way through: a word beside the color, captions under the speech, a keyboard route beside the mouse.

Why This Matters

About 1.3 billion people, roughly 1 in 6, live with a significant disability. If you can spot barriers, you catch them while a design is still a sketch, when adding a label to a button takes a minute. If you can't, a school form that only works with a mouse quietly shuts a student out, and the team finds out after launch, when fixing it means rebuilding pages.

Intuitive Explanation

Picture a school entrance with only stairs. A student who uses a wheelchair can do schoolwork perfectly well; the stairs are what stop her at the door. Build a ramp and the barrier is gone. Accessibility in computing starts from the same view: the problem sits in the design, so the fix goes in the design too.

Digital stairs are everywhere once you look. A photo with no alt-text is a blank to a screen reader, which can only speak text aloud. A video with no captions tells a deaf viewer nothing. A menu that opens only when a mouse hovers over it can't be reached by someone who moves through a page with the Tab key or a single switch. Each fix gives a second route to the same content: describe the photo in words, write the speech as text, make every control reachable from the keyboard. The POUR checklist sorts these routes: can people take the content in (Perceivable), work the controls (Operable), follow it (Understandable), and use it with their assistive tools (Robust)?

Not every complaint about a design is an accessibility problem. If a checkout has seven steps and every shopper finds it slow, that is a user-interface problem, because it hits everyone the same way. It becomes accessibility when the design blocks someone because of how they see, hear, move or think, such as a Pay button that a screen reader announces only as "button". Ask whether the problem bothers only people who lack a particular ability, such as sight, hearing or fine hand control.

Fixes built for one group usually help many more. Curb cuts made for wheelchairs also serve strollers and rolling suitcases, and captions help everyone in a loud cafeteria.

Think of it like this. Accessibility is the ramp beside the stairs. The stairs still work for most people, the ramp lets everyone else in, and strollers and delivery carts end up using it too. Like a ramp, it is far cheaper to draw into the plans than to add after the building is finished. Unlike a ramp, many digital fixes are invisible, such as alt-text only a screen reader speaks.

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.


When to Use

Use accessibility thinking whenever people will see, hear, click or read what you made: a website, app, game, video or document. Strong signals are a named user (a blind student, a deaf viewer, someone who can't use a mouse) or an assistive tool such as a screen reader, captions, keyboard-only use or zoom. If a complaint affects every user the same way, like a confusing menu, it is a User Interface question; if it asks whether a technology is fair or right in general, use Ethics of Computing.

Tip. Ask: Does the design depend on one ability, such as seeing color, hearing sound or using a mouse, that some users do not have?

How to Recognize It

Before you treat it as an accessibility problem, picture the product in the hands of someone who cannot see, hear, move or read the way the designer expected.

  1. Is information given only one way, such as only by color, only by sound or only in an image?

    Yes is an accessibility gap; add a second way, like a label, captions or alt-text. If every user can perceive it but finds it clumsy, that is Usability.

  2. Can every action be done without a mouse or a precise tap, for example with a keyboard or voice?

    No is an accessibility gap. If the question is only about where buttons go and how screens look, it points to User Interface.

  3. Does a screen reader, switch control or other assistive tool need to work with the product?

    Yes makes it accessibility, because those tools rely on labels and headings being built in. If no one is shut out at all, look at User Interface or Usability.

  4. Is the question whether excluding some users is fair, weighed alongside cost, privacy or jobs?

    Yes widens it to Ethics of Computing. Accessibility is the practical design work that removes the barrier.

Accessibility vs User Interface vs Usability vs Ethics of Computing

Accessibility, interface design and ease of use overlap, because a good interface does all three. Ask whether anyone is completely blocked, or whether everyone is merely slowed down.

Accessibility

Meaning
Accessibility is designing a product so people with disabilities can use it fully, often by offering a second way through.
Key test
Someone with a disability is blocked unless the design changes.
Example
A video with captions can be followed by a deaf viewer.

User Interface

Meaning
A user interface is the screens, controls and feedback a person uses to operate a program or device.
Key test
You are describing what the controls are, not who is shut out.
Example
A music app's play button, volume slider and song list make up its interface.

Usability

Meaning
Usability is how quickly and easily typical users can get a task done with a product.
Key test
Everyone can use it, but some designs take more effort than others.
Example
A checkout that needs five taps instead of twelve has better usability.

Ethics of Computing

Meaning
Ethics of computing weighs whether a technology treats all the people it affects fairly.
Key test
It asks whether leaving people out is right, not how to fix the design.
Example
Debating whether a government service may be offered only through an app.

Formula & Notation

Worked Examples

Example 1 — Audit a lunch-order page

Easy

A school's lunch-order page has four features: (1) each meal is shown by a photo with no alt-text; (2) sold-out meals are marked only by turning their name red; (3) the Order button works only with a mouse click; (4) prices are light gray (#999999) on white, which a contrast checker rates 2.8:1. For each feature, say who is blocked and give a fix.
Show the steps and the answer
  1. Feature 1: a screen reader reaches each photo and can announce only "image" or a file name such as "IMG_2041.jpg".

    A blind student never learns what the meal is. Fix: alt-text such as "Cheese pizza with side salad". This is a Perceivable problem: the content can't be taken in.

  2. Feature 2: red versus black is the only clue that a meal is sold out.

    About 1 boy in 12 has red-green color blindness and may see the two colors as the same. Fix: add the words "Sold out", so color is an extra signal, not the only one.

  3. Feature 3: press Tab to move through the page and notice that the Order button is skipped.

    Students who use a keyboard, a switch or voice control can't press it. Fix: build it as a real button that Tab reaches and Enter presses. This is an Operable problem.

  4. Feature 4: compare the 2.8:1 contrast with the WCAG minimum of 4.5:1 for normal-size text.

    The gray fails, so students with low vision, and anyone reading in bright sun, struggle with the prices. Fix: darker text; #595959 on white measures about 7:1.

Answer: Four barriers, four fixes: alt-text on the photos (blind users), the words "Sold out" beside the red (color-blind users), a keyboard-reachable button (keyboard and switch users), and darker price text (low-vision users).

Takeaway: For each feature, ask which ability it demands, such as seeing color or steering a mouse, and add a second route that doesn't need it.

Example 2 — Accessibility or user interface?

Standard

Two complaints arrive about the same lunch app. A: "Everyone orders for the wrong day, because the calendar starts on Sunday but the menu week starts on Monday." B: "I use voice control. I say 'click Order' and nothing happens, because the button is just a fork icon with no name." Which is an accessibility problem and which is a user-interface problem?
Show the steps and the answer
  1. Ask who complaint A affects: every user, whether they use a mouse, a keyboard or a screen reader.

    No particular ability makes the confusion go away; the layout itself misleads. That makes it a User Interface fix: start the calendar on Monday.

  2. Ask who complaint B affects: a user who speaks commands, and also anyone using a screen reader.

    A sighted mouse user can see the fork and click it, so the barrier exists only for people relying on assistive tools. That makes it accessibility: the button has no name those tools can find (Robust).

  3. Fix B by giving the button the text label "Order".

    Voice control matches spoken words to button names, and a screen reader reads the same name aloud. The visible word also helps new users who don't know that the fork means order.

Answer: A is a User Interface problem; B is an accessibility problem.

Takeaway: If a problem hits every user the same way, redesign the interface; if it blocks only people who see, hear, move or think differently, it is accessibility.

Example 3 — Find the mistake: only checking for blindness

Application

Maya's class video project has spoken narration, photos, and a drag-and-drop quiz at the end that must be finished in 10 seconds. She adds alt-text to every photo and writes: "Done. Blind viewers can follow it, so the project is accessible." Find the mistake and correct it.
Show the steps and the answer
  1. List everything the project asks of a viewer: seeing the photos, hearing the narration, dragging with a mouse, and answering within 10 seconds.

    Every demand is a possible barrier, not only the visual ones Maya checked.

  2. Hearing: the narration has no captions.

    A deaf or hard-of-hearing viewer sees the photos but misses every word of explanation. Fix: add captions.

  3. Movement: the quiz needs a mouse drag.

    A viewer with a hand tremor, or one who uses only a keyboard, can't drag. Fix: let answers be chosen with Tab and Enter as well.

  4. Time: the whole quiz lasts 10 seconds.

    A slow reader, a viewer with a learning disability, or someone using a switch device runs out of time. Fix: let viewers turn the timer off or extend it.

  5. Name the error: Maya checked one kind of disability.

    Accessibility covers hearing, movement and thinking as well as sight, and her project still blocks three groups.

Answer: Not yet accessible. Keep the alt-text, and add captions, a keyboard way to answer the quiz, and a timer that can be extended or switched off.

Takeaway: Check every sense and movement your design asks for, not only sight.

Where You'll See It

  • Turning on captions to watch a video in a loud room

    Captions were built for deaf and hard-of-hearing users, but they help everyone in a noisy bus or quiet library — a clear case of accessible design benefiting all users.

  • Navigating a website with only the keyboard

    Someone who can't use a mouse relies on keyboard navigation (Tab and Enter) to reach every button; if a site only works by clicking, it locks those users out.

  • Adding alt-text to a photo you post

    Alt-text is a written description that a screen reader speaks aloud, so a blind classmate can understand the image instead of hearing a blank or 'image' with no meaning.

Common Mistakes

  1. The slip: Accessibility is something you add at the end if there's time.

    Why it's tempting: It feels like a finishing touch, like polish, rather than part of the core build.

    Instead: Accessibility should be designed in from the start; bolting it on later is harder, costlier, and usually leaves gaps.

  2. The slip: Accessibility is only about helping blind users.

    Why it's tempting: Screen readers and alt-text are the most famous features, so it seems vision-only.

    Instead: Accessibility also covers hearing, motor, cognitive, and neurological needs — captions, keyboard control, simple layouts, and more.

  3. The slip: Accessible design only benefits people with disabilities.

    Why it's tempting: The features are labeled as 'assistive,' so they seem to help only a small group.

    Instead: Many accessibility features help everyone — captions in noisy places, voice control when hands are full, high contrast in bright sunlight.


Mini Practice

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

  1. A web page shows a bar chart: 12 students walk to school and 8 take the bus. Write alt-text that a screen reader could read to a blind user.

    Hint: Say what information the picture gives, not just what kind of picture it is.

  2. Normal text needs a contrast ratio of at least 4.5:1. Grey on white measures 2.8:1, dark blue on white 8.6:1, and black on white 21:1. Which pass?

    Hint: Compare each first number with 4.5.

  3. A form has four parts: Name, Email, a fancy dropdown that only opens with a mouse click, and a Submit button. A user moves through it using only the Tab key. Where do they get stuck, and which POUR principle fails?

    Hint: Picture moving through the form without a mouse, one part at a time.

  4. Match each feature to who it mostly helps: captions, keyboard shortcuts, simple step-by-step instructions, screen reader labels. Choose from: deaf users, users with limited hand movement, users with cognitive disabilities, blind users.

    Hint: Think about which sense or ability each feature replaces or supports.

  5. One team moves the Save button to the top of the screen because most users look there first. Another team adds voice control so people who cannot use their hands can save. Which change is user interface design, and which is accessibility?

    Hint: Which change removes a barrier for people with a disability?

  6. A team says: "We'll finish the app first and add accessibility in the last week, since only a few users need it." Name two problems with this plan.

    Hint: Think about the cost of changing finished screens, and about who else uses captions.

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.

Frequently Asked Questions

How does a blind person use a smartphone?

Phones have built-in screen readers, VoiceOver on iPhone and TalkBack on Android. With one turned on, the phone reads aloud whatever is under your finger, and you double-tap to choose it. Many blind users set the speech to a very fast rate. It only works well if app makers label their buttons; an unlabeled button is read out as just the word button, which tells the user nothing.

Is accessibility required by law?

In many places, yes, at least for some organizations. In the United States, courts have applied the Americans with Disabilities Act to websites, and federal government websites must meet accessibility rules. The European Accessibility Act requires many products and online services sold in the EU to be accessible from June 2025. Most of these rules point to the WCAG guidelines as the standard to meet.

What does contrast mean, and why do designers check it?

Contrast is how different the text color is from the background color. Light gray text on a white page may look stylish but is hard to read for people with low vision. WCAG asks for a contrast ratio of at least 4.5 to 1 for normal-sized text. Free online checkers will tell you the ratio for any two colors, so designers test it before choosing a palette.

Do video games need accessibility too?

Yes, and many now include it. Common options are remapping buttons so players can use whatever controls they can reach, subtitles that name the speaker, color-blind modes, and settings that slow the game down or skip hard sections. Microsoft makes a controller with large programmable buttons for players with limited movement. These options also help players who are tired, injured or new to games.

Learning Path

← Before

No prerequisites
Accessibility

You are here

No earlier lesson is needed; it helps to have used a website or app and noticed what it asks of you. This lesson adds a way to find barriers (each place a design demands one particular ability) and to fix them with a second route. Next, User Interface covers how screens and controls are laid out for everyone, and Ethics of Computing widens the question to who benefits and who is harmed by a technology.

See Also