Accessibility

Panoptik should be usable by everyone in the group, on the app and on this website. Accessibility is treated as part of the product rather than a later pass over it, and the commitments below describe what is built today, not what is planned.

Dynamic Type is supported through the Accessibility 3 size. Layouts reflow rather than truncate at large text sizes, including the capture countdown and the develop flow.

VoiceOver is supported. Controls expose meaningful labels, values, and traits, and interactive targets meet Apple's minimum hit-target size.

Colour is never the only signal. Status is always paired with text or an icon, which matters in an interface that is deliberately near-monochrome.

Reduced Motion is respected. When it is enabled in iOS Settings, animated transitions are replaced with static state changes.

Capture prompts allow two minutes to respond, and a missed prompt has no penalty. Nobody is disadvantaged for needing longer.

The site uses semantic HTML structure, landmark regions, and a logical heading order, and every page is fully keyboard navigable with a visible focus ring.

Meaningful images carry alternative text, and decorative images are hidden from assistive technology.

All animation and smooth scrolling is disabled when the operating system reports a reduced-motion preference.

Body text is set in ivory (18.8:1) or muted (9.3:1) against the near-black background, both comfortably above the WCAG AA threshold.

Lower-contrast tones are reserved for large text and non-essential metadata such as indices and timestamps, and are never used for body copy.

Panoptik is a video app. Clips are recorded by members, so Panoptik cannot guarantee captions, audio description, or the visual clarity of what anyone records.

The interface is dark only. This is a deliberate product decision carried over from the app rather than an oversight, and there is no light theme.

If you hit an accessibility problem, email support@panoptikapp.com with the page or screen, your device, your iOS or browser version, and a description of what went wrong. Accessibility reports are treated as bugs, not suggestions.