checklist: Check Accessibility

As a baseline, at least 4.5:1 for normal text and 3:1 for large text; assess exceptions and text in images separately.

Describe informative images, hide decorative images from assistive technology and give functional icons an understandable name.

Use a logical heading hierarchy; add ARIA only when native HTML semantics are insufficient.

Provide captions, transcripts and audio description as required by the content and conformance target.

Check at 200% zoom and reflow at 320 CSS pixels; consider exceptions for content requiring two-dimensional layout.

Keep focus order meaningful, avoid keyboard traps and ensure focused content is not obscured.

Check WCAG 2.2 success criterion 2.5.8; consider its exceptions and 24 by 24 CSS pixel minimum.

Allow users to extend, adjust or turn off limits where no exception applies.

Provide pause, stop or hide controls where required and account for reduced-motion preferences.

e.g. hover menus need focus alternative

Mark the primary language and relevant changes of language.

e.g. same behavior for buttons, menus, forms

e.g. specific instructions for form entries

e.g. <label for="...">, aria-describedby

Offer plain-language explanations where useful; a separate simplified-language version is not universally required.

e.g. no <div> for buttons or headings

For example, test screen readers with supported browser and device combinations; automated checks alone are not sufficient.

e.g. no redundancy, no false role

Use validators and accessibility tools as supplements; valid code alone does not demonstrate WCAG conformance.

e.g. in the context of releases or maintenance cycles