← Back to home

Accessibility: CleanPoker for inclusive teams

CleanPoker is a planning poker tool designed to be usable by everyone, including people with disabilities: screen reader users, keyboard-only users, people with low vision or motor impairments. It conforms to the WCAG 2.1 Level AA guidelines.

Who is it for?

CleanPoker is suitable for:

  • Blind or visually impaired people using a screen reader (NVDA, VoiceOver, JAWS)
  • People with motor impairments who navigate exclusively with a keyboard
  • People sensitive to animations (epilepsy, vestibular disorders)
  • People using browser zoom up to 200%
  • Agile teams wishing to include members with disabilities

Conformance status

CleanPoker is partially conformant with WCAG 2.1 AA criteria. Accessibility was integrated from the design stage, not added afterwards. The Lighthouse Accessibility score is 100/100.

Compatibility with assistive technologies

  • NVDA (Windows): tested with Firefox
  • VoiceOver (macOS / iOS): tested with Safari
  • JAWS (Windows): compatible via semantic HTML and ARIA
  • Full keyboard navigation: Tab, Shift+Tab, Enter, Space, arrow keys

Technical measures implemented

  • Skip link ("Skip to main content") at the top of the page
  • Full keyboard navigation (Tab, Enter, Space)
  • aria-live="polite" regions for real-time vote updates
  • aria-pressed states on voting cards
  • Contrast ratios meeting the 4.5:1 minimum
  • No user-scalable=no (free browser zoom)
  • prefers-reduced-motion support (no forced animations)
  • Dark mode support (prefers-color-scheme)
  • Semantic HTML5: <button>, <main>, <section>, <table>
  • rem units: browser zoom works correctly
  • Buttons and links with explicit labels (aria-label)

Technologies used

  • Semantic HTML5
  • CSS with rem units (zoom respected)
  • JavaScript (SvelteKit)
  • WebSocket for real-time
  • WAI-ARIA for interactive components

Known limitations

No major limitations identified to date. This site is actively maintained and regularly audited.

Report a problem

To report an accessibility issue or suggest an improvement: open a GitHub issue

Last updated

This declaration was established in June 2026.