Accessibility acceptance criteria

These accessibility acceptance criteria ensure compliance with WCAG (Web Content Accessibility Guidelines) and improve usability for screen readers, keyboard users, and other assistive technologies.

Keyboard Accessibility

  • All interactive elements (links, buttons, forms) are focusable and can be navigated using Tab and Shift + Tab.
  • Focusable elements have a visible focus indicator (e.g., outline or underline).
  • Keyboard users can fully operate all site functions (e.g., menus, modals, dropdowns, sliders)
  • Skip to main content" link is available and works

Screen Reader Support

  • All non-text content (images, icons, SVGs) has meaningful alt text.
  • Headings (h1-h6) are hierarchical and convey structure.
  • Live announcements provide necessary updates to screen reader
  • Form errors are announced when invalid input occurs.

Color & Contrast

  • Text meets contrast requirements (4.5:1 for normal text, 3:1 for large text).
  • Color is not the only way to convey information errors should have an icon or text, not just red color.
  • Links are distinguishable from surrounding text not just by color—underline or bold is preferred.

Forms & Inputs

  • Each form field has an associated
  • Error messages are clear and announced by screen readers.
  • Required fields are explicitly marked.
  • autocomplete attributes help users fill out forms faster.
    Keyboard users can reach and interact with dropdowns, radio buttons, and checkboxes without a mouse.

Error Handling & Feedback

  • Error messages are descriptive (e.g., "Enter a valid email" instead of just "Invalid input").
  • Errors are associated with form fields.
  • Confirmation messages are announced when actions are completed.
  • Users can undo destructive actions (e.g., "Undo" button for deletions).
  • Logical tab order (keyboard navigation follows the same visual order).
  • No keyboard traps (users can navigate freely without getting stuck).
  • Custom components should behave like native elements for assistive tech.

Multimedia & Motion

  • Videos should have captions embedded subtitles
  • Audio content has transcripts for users who cannot hear.
  • No auto-playing media unless user-initiated or can be stopped.
  • Animations do not trigger seizures. Flashing elements should follow the 3 flashes per second rule.
  • Reduced motion preference is respected

Performance & Loading

  • Pages are fully accessible before JavaScript loads gracefully.
  • Lazy-loaded content is announced to screen readers
  • Loading indicators are present when fetching data.
GitHub Storybook Figma library Version 3 release guide Release history BAgel helper QA process