The WCAG AA standard requires a minimum contrast ratio of 4.5:1 for normal body text. A designer proposes light gray text (#999999) on a white background, which has a contrast ratio of approximately 2.8:1. What is the most direct consequence of this choice?
AThe design will fail validation but remain legally compliant in most jurisdictions
BThe text will be unreadable only for users with complete color blindness
CThe design fails WCAG AA compliance, making text difficult to read for users with low vision, the elderly, and anyone in bright light
DThe design automatically fails WCAG AAA but may still pass WCAG AA
A 2.8:1 ratio falls well below the 4.5:1 AA minimum for normal text. This primarily affects users with low vision, but the curb-cut effect means it also degrades readability for the elderly (whose contrast sensitivity declines with age), users on low-quality screens, and anyone reading in bright sunlight. WCAG AA is the widely adopted compliance baseline; the design as proposed fails it.
Question 2 True / False
The curb-cut effect in accessibility design means that features built specifically for disabled users almost generally create a worse experience for non-disabled users who are forced to encounter them.
TTrue
FFalse
Answer: False
The curb-cut effect is the opposite: accessibility improvements consistently benefit a much wider user base than the specific disability they target. Captions benefit users in noisy environments. High contrast benefits outdoor mobile users. Keyboard navigation benefits power users who prefer not to use a mouse. The name comes from sidewalk curb cuts, designed for wheelchair users, which turned out to benefit parents with strollers, delivery workers, and cyclists. Accessibility and usability are aligned, not in tension.
Question 3 Short Answer
A design team is building a web application and says they will 'add accessibility features in a final pass before launch.' Why is this approach fundamentally flawed, and what should they do instead?
Think about your answer, then reveal below.
Model answer: Accessibility cannot be reliably retrofitted because it depends on foundational design decisions — color palette, typography scale, interaction patterns, component structure — that are made early and are expensive to change later. For example, a color palette chosen without contrast analysis may require wholesale redesign to reach 4.5:1. Keyboard navigability requires HTML structure decisions made during component architecture. Accessibility must be a constraint built into the design system from the start, not an audit checklist at the end.
The 'add it later' approach consistently fails in practice because the cost of rework grows exponentially with how late the fix is applied. The correct approach is to treat WCAG compliance as a design requirement equivalent to visual aesthetics — evaluated at every design decision, not just the last one.