
evaluate a game for motor, vision, hearing and cognitive accessibility using a structured checklist, and recommend specific, feasible fixes.
Instruction
Many players have a disability, whether permanent, temporary (a broken wrist) or situational (a noisy bus, bright sunlight on a phone). Accessible design widens who can play, and many accessibility features, such as subtitles and remappable controls, are used by players who do not have a disability at all. Accessibility is a design quality, not an add-on.
Four areas.
- Motor. Can the game be played with limited strength, speed or dexterity, or with one hand? Barriers: rapid button mashing, holding buttons for long periods, precise timing with no alternative, controls that cannot be changed. Fixes: remappable controls, toggle instead of hold, adjustable game speed, assist options, support for different controllers.
- Vision. Can players with low vision or color-vision deficiency read the game? Barriers: small text, low contrast, information shown only by color (red enemy, green friend). Fixes: scalable text, high contrast between the player, hazards and background, shapes or symbols alongside color, and clear audio cues.
- Hearing. Can deaf or hard-of-hearing players get every important piece of information? Barriers: dialogue without subtitles, warnings given only by sound (an enemy behind you). Fixes: subtitles with speaker names and a readable size and background, captions for important sounds, and visual indicators for off-screen sounds.
- Cognitive. Can players who need more time or clearer information follow the game? Barriers: walls of instructions, strict time limits, no reminder of the current goal. Fixes: teach one thing at a time, show the current objective on request, allow pauses at any time, and offer adjustable or removable timers.
Photosensitivity. Rapid flashing can trigger seizures in people with photosensitive epilepsy. The W3C’s web accessibility guidelines (WCAG) use a threshold of no more than three flashes in any one-second period. Treat it as a hard rule for your games: no rapid full-screen flashes, and a setting to reduce screen shake and flashing.
The law and the industry. In the United States, the 21st Century Communications and Video Accessibility Act requires communication features in games, such as voice and text chat, to be accessible to people with disabilities. Beyond legal requirements, many studios publish accessibility guidelines, and players and disability advocates review games’ accessibility. The Game Accessibility Guidelines (gameaccessibilityguidelines.com) group recommendations into basic, intermediate and advanced; start with the basic ones, which are cheap to add early and expensive to retrofit.
Accessible is not the same as easy. Options let each player find the challenge that suits them. A hard game can offer remapping, subtitles and color-safe design without becoming less hard; an assist mode can be optional and never forced. Players with disabilities are not a single group, so offer options rather than one “accessible version”.
Running the audit. You will audit your own level, which is hard because you already know where everything is. So leave it alone for a day, then play it for five minutes normally. For practice first, you can run the same checklist on the first level of a published game you already own: judging someone else’s choices sharpens your eye for your own. Then replay it under constraints that simulate barriers, done respectfully, for a few minutes each: one hand only; sound muted; the screen in greyscale (many operating systems have a color-filter setting) or at reduced brightness. Complete the checklist, rating each item met, partly met or not met, with evidence. Let measured numbers, such as contrast ratios and flashes per second, do the judging where they can; a family member playing under the same constraints can add evidence you cannot see yourself. Simulations help you notice problems, but they are not the experience of disabled players; nothing replaces testing with disabled players and listening to them.
Recommendations must be specific and feasible: “Add a shape to the red hazards, since in greyscale they match the floor” beats “make it more accessible”. Prioritize by impact and cost.
📖 Read for this lesson
The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.
Formative check
Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.
In your game, enemies are red and friendly characters are green, with the same shape. What is the best fix?
Adding accessibility options always makes a game easier for everyone.
Which U.S. law requires in-game voice and text chat features to be accessible to people with disabilities?
Complete the audit of your own level after a day away from it: for each of the four areas, rate one item met, partly met or not met with evidence. Then write your three top recommendations in priority order, each specific and feasible, and for each say how you will check that the fix worked.
How confident are you that you can audit a game’s accessibility and recommend specific, feasible fixes?
Practice
Work these on paper or in your notebook, then open Check your answer. Aim for all of Fluency and Application; try at least one Challenge.
Printable version: this unit’s practice workbook (PDF)
Fluency
Build speed and accuracy with the core skill.
- Name the four areas of the accessibility audit and one barrier in each.
Check your answer
Answer: Motor (rapid button mashing or long holds); vision (information shown only by color, small text); hearing (dialogue without subtitles, warnings only by sound); cognitive (walls of instructions, strict time limits).Any correct barrier per area from the lesson is fine. - Give the photosensitivity threshold the lesson uses and its source.
Check your answer
Answer: No more than three flashes in any one-second period, from the W3C’s web accessibility guidelines (WCAG).Treat it as a hard rule, and offer a setting to reduce screen shake and flashing. - Define situational disability and give two examples.
Check your answer
Answer: A temporary limitation caused by circumstances. Examples: a noisy bus, bright sunlight on a phone, holding a baby in one arm.Many accessibility features, such as subtitles, are used by players without a disability.
Application
Use the skill in context. Show your reasoning.
- A power-up effect flashes the whole screen every 0.25 seconds for two seconds. Does it meet the threshold? What if it flashed every 0.5 seconds?
Check your answer
Answer: Every 0.25 s is 4 flashes per second, which fails (more than 3). Every 0.5 s is 2 per second, which is within the threshold.1 ÷ 0.25 = 4 and 1 ÷ 0.5 = 2 flashes per second. - Write one specific, feasible fix for each barrier: (a) a boss fight requires holding a button for 10 seconds; (b) an alarm warns only by sound that a guard is behind you; (c) the current goal is shown once and never again.
Check your answer
Answer: (a) Offer toggle instead of hold, or remappable controls. (b) Add a visual indicator for the off-screen sound, plus a caption. (c) Show the current objective on request (for example, in the pause menu).Specific and feasible beats “make it more accessible.” - A classmate says adding subtitles and remappable controls will make your hard game too easy. Answer using the lesson.
Check your answer
Answer: Accessible is not the same as easy. Remapping, subtitles and color-safe design remove barriers without changing the challenge; an assist mode can be optional and never forced. Options let each player find the challenge that suits them.Players with disabilities are not a single group, so offer options rather than one “accessible version.” - Describe how to self-audit your own level fairly, including the constraints you would simulate, and one limit of this method.
Check your answer
Answer: Leave it a day, play five minutes normally, then replay for a few minutes each with one hand only, sound muted and the screen in greyscale or reduced brightness; rate each checklist item met, partly met or not met with evidence. Limit: simulations help you notice problems but are not the experience of disabled players; nothing replaces testing with them.Let measured numbers such as flashes per second do the judging where they can. - In which group do the Game Accessibility Guidelines’ cheapest recommendations sit, and why add them early?
Check your answer
Answer: The basic group. They are cheap to add early and expensive to retrofit.The guidelines group recommendations into basic, intermediate and advanced.
Review
Keep earlier skills sharp.
- Review (Lesson 1.4): an audit finds that nobody notices the exit sign in greyscale. Is this a functionality bug or a usability issue, and why?
Check your answer
Answer: A usability issue: the exit works, but players struggle to notice it.Usability issues are fixed by design (contrast, shape, placement), not by code.
Accessibility Audit: Thresholds, the Contrast Formula and a Completed Audit
SLS original checklist and invented level; thresholds paraphrased from W3C WCAG 2.2 (Recommendation 12 December 2024, W3C Document License), retrieved 2026-11-10; FCC CVAA guide as read 2026-09-26 · SLS original, with paraphrase of W3C WCAG 2.2 (W3C Document License) and a U.S. FCC public-domain summary
Why this reading. The lab asks you to audit your own level with a checklist, after a day away from it, and write prioritized fixes. Because you already know your level, measured numbers such as contrast ratios and flash counts matter even more: they judge the level for you. Here is the checklist with the thresholds explained, the contrast formula worked, and a completed audit of an invented level so you can see what evidence for each rating looks like. Checklist wording and the audit are SLS original; the numeric thresholds are paraphrased from WCAG 2.2, cited below.
Thresholds you can test (from WCAG 2.2, a web standard used here by analogy)
- Success criterion 1.4.3: text needs a contrast ratio of at least 4.5 to 1 (3 to 1 for large text).
- 1.4.11: interface components and meaningful graphics need at least 3 to 1 against neighboring colors.
- 1.4.1: color must not be the only way to tell things apart.
- 2.3.1: nothing flashes more than three times in any one second, unless below the flash thresholds.
- 2.2.1: a time limit can be turned off, adjusted or extended.
Contrast ratio = (L1 + 0.05) / (L2 + 0.05), where L1 is the lighter color’s relative luminance and L2 the darker’s. Luminance = 0.2126 R + 0.7152 G + 0.0722 B after each channel c (0 to 1) is converted: c / 12.92 if c is at most 0.04045, otherwise ((c + 0.055) / 1.055) raised to 2.4. Example: dark text has L = 0.0219 and sky has L = 0.5529, so the ratio is (0.5529 + 0.05) / (0.0219 + 0.05) = 8.38.
The level under audit: Kelp Hollow 2 (invented)
| Pair | Contrast ratio (computed) |
|---|---|
| Hazard (#C0392B) on floor (#6B7A5A) | 1.18 to 1 |
| Hazard on friendly character (#2E8B57) | 1.28 to 1 |
| White text on sky (#87CEEB) | 1.74 to 1 |
| Dark text (#1B2A3A) on sky | 8.38 to 1 |
| Coin (#F2C230) on sky | 1.04 to 1 |
| Coin on dark cave wall (#1B2A3A) | 8.71 to 1 |
Completed audit (SLS original)
| Area | Item | Rating | Evidence |
|---|---|---|---|
| Vision | Hazards distinguishable from floor | Not met | 1.18 to 1; under a greyscale filter hazards vanish into the floor |
| Vision | Enemy versus friend not by color alone | Not met | Same shape; 1.28 to 1 in luminance |
| Vision | Text readable | Partly met | Dark text 8.38 to 1 passes; white title text on sky is 1.74 to 1 |
| Motor | Controls remappable | Not met | Jump fixed to one key |
| Hearing | Important sounds also visible | Met | Urchin warning flashes an icon |
| Cognitive | Pause anywhere, current goal on request | Partly met | Pause works; no goal reminder |
| Photosensitivity | No more than 3 flashes per second | Partly met | Victory strobe flashes 5 times per second |
Top recommendations, in priority order (each with how to check the fix)
- Add spikes to hazards and outline them in dark blue: fixes two failures for about an hour of work. Check: rerun the greyscale filter and recompute the hazard-on-floor ratio.
- Replace the victory strobe with a 2-per-second pulse: a safety issue and a five-minute change. Check: count flashes in one second of a screen recording.
- Add remappable jump: medium cost, high benefit. Check: remap jump and finish the level one-handed.
About law: the FCC states that the Twenty-First Century Communications and Video Accessibility Act applies to games’ communication features, such as voice and text chat, and does not cover other parts of gameplay (FCC guide, as read on 2026-09-26). The Game Accessibility Guidelines (CC BY-SA, not reproduced here) are a good source of further ideas.