Home / Accessibility

Accessibility statement

We want everyone on the team to be able to estimate with PointHuddle, whatever device, input or assistive technology they use. We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

Where we are

Partially conformant with WCAG 2.2 AA: the parts listed below are tested on every release, but the whole app hasn’t been reviewed by an outside accessibility expert yet, and some limitations are known.

What we test on every release

• Automated checks (axe-core, WCAG 2.0, 2.1 and 2.2 A and AA rules, every impact level) on the room while idle, voting and revealed, every side panel and settings section, the async-round vote on a phone, the join dialog, these content pages and every theme in light and dark mode.
• Keyboard: every control can be reached and used with the keyboard; number keys pick a card and revealing and accepting have shortcuts; the story list can be reordered with the keyboard; dialogs keep focus inside and give it back when they close.
• Screen readers: the reveal and other changes are announced in a live region, and each seat says whether that person has voted and, after the reveal, their card.
• Motion: card flips, confetti and other animation are turned off when your system asks for reduced motion.
• Zoom and small screens: rooms work at 320 pixels wide without scrolling sideways, which is what a 1280-pixel window looks like at 400% zoom (WCAG 1.4.10, Reflow).
• Colour: text meets the 4.5:1 contrast ratio in every theme, and nothing is shown by colour alone: lowest and highest votes are also labelled.

Known limitations

• Charts in the Stats tab (trends and the per-card ranges) are drawn as images with a short text summary; the full numbers are in Copy table and the Summary tab rather than in an accessible table on the chart itself.
• Inside Microsoft Teams, Google Meet and Zoom, the meeting app around PointHuddle is outside our control.
• Card decks you make yourself can contain emoji or symbols that some screen readers read in an unexpected way.

Tell us about a barrier

If something gets in your way, write to [email protected] with what you were trying to do, the browser and any assistive technology you use. We reply within two business days and treat barriers as bugs.

This statement was last reviewed on 14 October 2026.