Example 1 — Audit a lunch-order page
Show the steps and the answer
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.
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.
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.
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.