Grades 3–9 · STEM & Computer Science
Accessibility in computer science class: audits, alerts and tactile maps
Short answer: Teach accessibility in computer science by having students test designs against specific users and record what fails. Good tasks include auditing a mock web page for keyboard access and labels, comparing alert prototypes for someone facing away from the board, redesigning a tactile map key, and adding a visible cue to a Scratch game that only beeps.
- Grades3–9
- Units5 accessibility-focused STEM units
- Devices neededOptional; most tasks run on paper mockups
- Assessment20-point learning check, 100-point scoring sheet
Accessibility is often taught as a checklist at the end of a project. Students learn more when it is the project: they meet a design that fails one user, describe the failure precisely, and propose a repair they can test. That is also how professional accessibility work runs, which makes it a strong fit for computer science and engineering classes.
TeachLessons has five units that approach accessibility from different angles, from a Grade 3 Scratch game to a Grade 9 web audit. They share a format of four 90-minute double lessons, five worksheets with answer keys, and a 20-point learning check.
Units for this topic
Website Accessibility Audit Lab
Lead unit: a structured audit of keyboard access, labels and perceivable cues on a mock interface.
Design an Accessible Emergency Alert
Compares single- and multi-channel alert prototypes against specific user tests.
Design a Better Tactile Map
Redesigns a tactile map key and tests it with a partner's feedback.
Accessible Game Design in Scratch
Brings accessibility into a younger Scratch class with keyboard input and visible success cues.
Repair a Broken Web Form
Practices error messages and labels that help users recover, tested with the keyboard only.
Test an Evacuation Route with a Paper Simulation
Adds bottleneck modeling and a clear discussion of what a classroom simulation cannot establish.
Why accessibility belongs in the CS curriculum
Computing students are building things other people use. Asking who cannot use a design, and why, sharpens the same skills you already teach: tracing behavior, writing a reproducible bug report, defining a test and checking whether a fix worked. Accessibility simply gives those skills a human reason.
It also gives quieter students a way in. A student who is not yet confident writing code can still find that a red error border carries no text, or that Tab skips a custom control.
Four project types that work in middle school
Each of these runs as a full unit, but you can also borrow a single case as a warm-up.
- Web audits: in Website Accessibility Audit Lab, a local mockup has a search box labeled only by placeholder, a green outline for selection and red for errors with no text. Students log three issues with reproduction steps and propose one testable repair each.
- Alert design: Design an Accessible Emergency Alert compares a siren alone with a flashing icon plus vibration puck, tested against hearing protection and a learner facing away from the board.
- Tactile maps: Design a Better Tactile Map starts with a draft where the desk and exit use identical raised dots. Students design a distinct key and test it with a partner.
- Game design: Accessible Game Design in Scratch begins with a game that advances only on a sprite click and announces success with sound alone.
Teaching students to write testable repairs
The hardest shift for students is moving from a complaint to a test. 'The form is confusing' cannot be checked. 'When the email field is empty, the form shows a red border but no message, and the name field is erased' can. Repair a Broken Web Form practices this directly: students write one persistent label, one visible error message and a corrected user path, then test the whole thing with the keyboard only.
A useful classroom rule is that every repair needs a matching test, written before the fix. In the alert unit, for example, a student who adds vibration also has to say how they would check a user who cannot reliably feel vibrations.
Keeping the work grounded and safe
The emergency alert unit models alerts in a classroom setting. It does not ask students to design a real school procedure, and the related Test an Evacuation Route with a Paper Simulation unit explicitly asks what token results fail to establish for a real corridor. That habit of naming limits is part of good accessibility reasoning too: a fix that works for one tester has not been shown to work for everyone.
A five-step sequence
-
Introduce a user, not a rule
Start with a tester profile, such as a keyboard-only user or a learner facing away from the board.
-
Run the design as it is
Have students try the mockup, prototype or map and record exactly where it fails.
-
Log the issue precisely
Write reproduction steps and the expected versus actual result for each issue.
-
Propose a repair with a test
Pair every fix with a check that would show whether it worked for that user.
-
Retest and report limits
Retest, note any remaining barrier, and state what the classroom test cannot show.
Common mix-ups and what to try
Accessibility is a final polish step.
Design choices like color-only errors or click-only input are hard to fix late. Testing early with a user profile catches them.
Adding a second cue always fixes the problem.
Two cues with opposite meanings for different learners can make things worse. Each change needs its own test.
If one tester succeeds, the design is accessible.
Record results per user. A label that works for one person may not work for another, as the tactile map unit shows.
More STEM & Computer Science units
Related teaching guides
Frequently asked questions
What grades are these accessibility units for?
The Scratch game unit fits Grades 3–6, the tactile map Grades 4–7, and the web audit, web form and alert units Grades 6–9.
Do students need computers?
Most cases run on paper mockups and models. Scratch is used in the game unit if available, and the web units can be done with printouts and a keyboard walk-through.
Do the units teach a specific accessibility standard?
They teach the testing habits behind accessible design: keyboard access, text labels, more than one cue, and clear error recovery. You can connect these to any standard you already use.
How are students assessed?
Each unit has mini-checks, a 20-point learning check with model responses and a 100-point scoring sheet, plus peer review and revision pages.
What if a unit does not fit my CS standards?
Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.
Where are the other STEM units?
The STEM and computer science collection includes unplugged debugging, search algorithms, sensor calibration and data bias labs.
Ready for your next lesson?
Pick one tester profile this week and let students find out where a familiar design stops working for that person.
View Website Accessibility Audit LabInstant digital download. Every resource is built around the curriculum you teach – and if something doesn't fit your standards, the TeachLessons Guarantee applies: we adapt it for you.

