Accessibility

Popnin aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA on every page and every screen of a meeting. Meetings themselves carry what the people in them say, show and share; the limits that follow from that are set out below.

What that means in practice

• Everything works from a keyboard: signing in, setting up a meeting, joining, every control in a meeting, chat, polls and the menus. Focus is always visible, follows you to each new screen, and comes back to where you were when a menu or dialog closes. Escape closes them.
• Buttons, toggles and menus are named for screen readers and say whether they are on or off. Each video tile is named after the person in it, and each screen has a title of its own.
• Text is at least 4.5 to 1 against its background, and the edges of fields and controls at least 3 to 1, in both the light and the dark theme, which follow your device.
• Pages work at 400% zoom, on a screen 320 pixels wide, and with wider letter, word and line spacing, without content being cut off or needing sideways scrolling. Long names, titles and links wrap rather than being cut short.
• Buttons and links are at least 24 by 24 pixels.
• Signing in uses a code sent by email: no puzzles and nothing to remember, and the code can be pasted or filled in by your device.
• Animation is reduced when your device asks for reduced motion.
• Keyboard shortcuts in a meeting: Ctrl (⌘ on a Mac) + D for the microphone, + E for the camera, and Ctrl/⌘ + Alt + H, C or P to raise your hand, open chat or open People.

How we check

Every proposed change is tested automatically with axe-core against the WCAG 2.0, 2.1 and 2.2 Level A and AA rules, on every page and on the screens of a meeting with a host and a guest (lobby, chat, polls, People, menus, the whiteboard), in light and dark, at desktop and phone widths, and for reflow at 320 pixels and a title per screen. Focus order, focus visibility, text spacing and target sizes have also been checked by hand.

Known limitations

• What people say and share. Audio, video, shared screens, documents, files and chat messages come from the people in a meeting, not from us, and we cannot make them accessible. This is a statement of partial conformance for that content.
• Live captions are machine-generated on your own device (nothing is uploaded) and need a browser that can transcribe a call, currently recent versions of Chrome. Elsewhere the captions option says it isn't supported. Machine captions make mistakes; for a meeting where accurate captions matter, add a human captioner as a participant.
• Drawing on a presentation or the whiteboard is freehand by nature, so it needs a pointer or touch. Presenting, turning pages and everything else about a presentation work from the keyboard.

Tell us about a problem

If something gets in your way, please tell us with "Report a bug" at the foot of the home page. Say what you were trying to do and, if you use one, which browser and assistive technology. We read every report and treat accessibility problems as bugs to fix.

Last reviewed October 2026.