12 items2 sectionsFor Designers, frontend developers learning accessibility

ARIA Cheatsheet for Designers

The first rule of ARIA: don't use ARIA when a native HTML element does the job. A button is more accessible than a div with role="button" + tabindex + key handlers. This cheatsheet covers the few cases where ARIA is genuinely required and the patterns that get them right.

References: WAI-ARIA Authoring Practices Guide, W3C ARIA 1.2, First rule of ARIA use (No ARIA is better than bad ARIA)

014 items

When NOT to Use ARIA

  1. 01
    Native HTML works — use <button>, <a>, <select>, <input>, <details>, <dialog> instead of div+ARIA
  2. 02
    role="button" on a div without keyboard handlers — actively makes things worse
  3. 03
    Redundant ARIA — <button aria-label="Submit">Submit</button> announces "Submit Submit"
  4. 04
    role="presentation" or role="none" on interactive elements (kills accessibility)

028 items

When YOU NEED ARIA

These are the cases where native HTML doesn't cover the pattern.

  1. 05
    Custom widgets without HTML equivalent — combobox, treegrid, slider (use APG patterns exactly)
  2. 06
    Live regions — aria-live="polite" for status updates, "assertive" for errors
  3. 07
    Labeling icon-only buttons — aria-label="Search" on icon button
  4. 08
    Hiding decorative content from screen readers — aria-hidden="true" on visual-only items
  5. 09
    Linking labels to inputs when <label for=> isn't possible — aria-labelledby
  6. 10
    Marking required fields — aria-required="true" (along with visual + text indicator)
  7. 11
    Disclosure widgets — aria-expanded on the trigger, aria-controls pointing at the panel
  8. 12
    Modal dialogs — role="dialog" + aria-modal="true" + aria-labelledby pointing at the title

AccessAudit AI for iPhone

Run this on your phone.

Point your iPhone camera at any color pair to see its WCAG contrast ratio and whether it passes, in real time, on the device.

More for AccessAudit AI users