Accessibility

Accessible design is mostly good design applied consistently. This is the baseline every design should meet (WCAG 2.2 AA).

Visual

  • Text contrast: 4.5:1 for body text, 3:1 for large text (24px, or 19px bold). This includes placeholder text that carries meaning, secondary text and text on images.
  • Non-text contrast: 3:1 for input borders, focus rings, icons that convey meaning, chart lines and the selected state of controls.
  • Color isn't the only signal: pair status colors with text or an icon; underline links in body text, or make them distinct in more than hue.
  • Text over images: use a scrim (a gradient or a solid band) so contrast holds wherever the text lands.
  • Zoom and reflow: layouts survive 200% text zoom and a 320px-wide viewport without horizontal scrolling or overlapping text.

Interaction

  • Targets: at least 24×24px with spacing, and 44×44px on touch screens.
  • Focus: every interactive element shows a visible focus ring (:focus-visible), at least 2px, in a color that contrasts with both the element and the background. Never remove it.
  • Keyboard: everything clickable is reachable and operable with the keyboard, in a logical order. Dialogs trap focus and return it when closed.
  • Motion: respect prefers-reduced-motion; avoid large parallax and autoplaying motion; nothing flashes more than three times a second.
  • Time: avoid time limits, or let people extend them.

Structure

  • Use real elements: button for actions, a for navigation, label linked to inputs, headings in order (one h1, then h2, …), lists for lists, table for tabular data.
  • Landmarks: header, nav, main, footer.
  • Images that carry meaning have alt text that says what matters about them; decorative images have empty alt.
  • Icon-only buttons have an accessible name (aria-label).
  • Form errors are linked to their fields and announced, not only colored.

Content

  • Plain language; front-load the key words.
  • Link text that makes sense out of context ("Read the pricing details", not "Click here").
  • Don't write instructions that depend only on shape, color or position ("click the green button on the right").