Accessible design ensures that products are usable by people across the full range of human ability, including those with visual, auditory, motor, and cognitive differences. The Web Content Accessibility Guidelines (WCAG) define measurable standards: minimum contrast ratios of 4.5:1 for normal text (AA compliance), text alternatives for all non-text content, keyboard navigability for all interactive elements, and no seizure-inducing animations. Accessibility is not a feature added after design — it must be built into the design system from the beginning. The curb-cut effect demonstrates that accessibility improvements almost universally benefit all users: captions help noisy-environment viewers, high contrast helps outdoor screen users, keyboard navigation helps power users.
Audit an existing website using a contrast checker (e.g., WebAIM) and a screen reader (NVDA or VoiceOver). Document every accessibility failure, then redesign the color palette and component specifications to meet WCAG AA compliance. Compare the before/after and note which improvements also enhanced the experience for non-disabled users.
You have already learned that contrast is one of the primary tools designers use to create emphasis and guide attention. Accessibility in design is, at its core, the discipline of ensuring that the contrast, structure, and interactivity of a design work not just for the average user under ideal conditions, but for the full range of human ability and circumstance. The transition from "contrast as aesthetic tool" to "contrast as measurable accessibility standard" is one of the key intellectual moves this topic asks you to make.
The Web Content Accessibility Guidelines (WCAG) translate accessibility into engineering constraints. The most directly applicable one you will encounter is the contrast ratio requirement: at least 4.5:1 between text and its background for normal-sized text at AA compliance level. This is not an arbitrary threshold — it is derived from human vision research on the minimum contrast needed for people with moderately reduced contrast sensitivity, such as the elderly or those with low vision. When you run a color pair through a contrast checker and see a ratio, you are measuring something real about legibility, not just aesthetics. A design that looks "readable enough" to a designer with perfect vision in a dim office may be unreadable to a significant portion of its intended audience.
The curb-cut effect is the single most important concept for overcoming resistance to accessibility work. Designers sometimes experience accessibility requirements as constraints that force compromises — "I wanted soft gray text but had to use dark text for contrast." The curb-cut effect reframes this: accessible choices almost always improve the experience for everyone. High-contrast text is easier to read for everyone. Captions, added for deaf users, are used constantly by hearing users in noisy environments. Large click targets, added for users with motor difficulties, make interfaces less frustrating for everyone on mobile. Building accessibility in makes the design better, not just more compliant.
Typography fundamentals you have already studied — type size, weight, spacing, and hierarchy — connect directly to accessibility. Text sized below 18pt requires the full 4.5:1 contrast ratio; large text (18pt or 14pt bold) has a more lenient 3:1 requirement because its size compensates for reduced contrast. Font weight affects readability for users with dyslexia or low vision. Line length and line height affect cognitive load for users with attention or reading disorders. None of these are special exceptions — they are the same typographic principles, made explicit as requirements.
Keyboard navigability is the accessibility requirement that most directly connects to interaction design and UI fundamentals. Every interactive element — button, link, form field, modal — must be reachable and activatable without a mouse. This matters for users with motor disabilities who cannot use pointing devices, but also for power users who prefer keyboard shortcuts and for assistive technologies like screen readers that navigate the DOM sequentially. Ensuring keyboard access means making decisions about focus order, focus indicators (visible outlines), and the semantic structure of your HTML — which is why accessibility cannot be retrofitted after the layout is built.
The deepest principle behind accessibility design is that "normal use" is not a stable category. Any user can become situationally impaired: using a phone in sunlight, holding a baby with one arm, wearing gloves in winter, or simply aging. Designing for the edges of human ability is designing for reality — the full, varied, context-dependent reality of how people actually encounter your work.
Topics in reflective domains aren't scored by quiz answers. Read, reflect, and mark when you've thought it through.