TickYouOff
Sign in
Back
♿

Accessibility Audit Checklist

Hard 18 items · 2 hours
testuser's avatar
testuser Published 4 weeks ago
Technical

A practical WCAG 2.1 checklist for auditing web apps. It guides developers, designers, and QA through color contrast, keyboard support, ARIA, form labeling, focus management, and screen reader testing. Use it to find, fix, and document accessibility issues during development or before release.

Progress
0 / 18
  1. Run automated accessibility scan — Use tools like axe, Lighthouse, or WAVE to catch common WCAG issues
  2. Check color contrast ratios — Verify text and UI contrast meets WCAG AA (4.5:1) or project target
  3. Verify keyboard-only navigation — Ensure all functionality works without a mouse
  4. Tab through all interactive elements — Confirm focus order follows logical reading order
  5. Ensure visible focus indicators — Keep clear focus styles for links, buttons, and inputs
  6. Test skip links and logical tab order — Provide skip-to-content and avoid keyboard traps
  7. Provide descriptive alt text for images — Write functional alt for informative images; use empty alt for decorative
  8. Label form controls clearly — Associate <label> or aria-labelledby with each input
  9. Provide accessible names for custom controls — Add aria-label or aria-labelledby to icons and custom widgets
  10. Use semantic HTML headings and landmarks — Structure pages with h1-h6 and main/nav/header/footer
  11. Implement ARIA roles only when necessary — Prefer native elements; use ARIA for complex widgets
  12. Manage focus after DOM updates — Move focus into dialogs and to error summaries after actions
  13. Ensure dynamic content is announced — Use ARIA live regions or role=status for async updates
  14. Test with screen readers — Try key flows with NVDA, VoiceOver (mac/iOS), or TalkBack (Android)
  15. Conduct mobile accessibility testing — Test touch targets, zoom, contrast, and mobile screen readers
  16. Fix issues found by automated scan — Address high-severity defects first, then lower-priority items
  17. Re-run automated scan to verify fixes — Confirm automated tool reports cleared issues and no regressions
  18. Document remaining known issues and exceptions — Record WCAG waivers, outstanding bugs, and remediation plans
Sign in to save
📝 My Notes