Accessibility

Accessibility

Kenshiki is built to be usable without relying on a single sense, input method, or color cue. This page documents the accessibility support we currently provide and the improvements we are still auditing.

Kenshiki Pulse app

Current accessibility support

VoiceOver. The primary Pulse surfaces expose labels for tabs, settings, status cards, Defense actions, Live sensor actions, and interactive trace targets. Decorative icons are hidden from VoiceOver where they repeat visible text.

Voice Control. Common tasks use named buttons and controls, including check-in, Settings, Defense actions, phone-number verification, Live diagnostics, and appearance selection.

Dark interface. Pulse supports System, Light, and Dark appearance modes in Settings. Dark mode is available for common tasks.

Differentiate without color alone. Statuses are paired with text labels, icons, and pills. Color is used as reinforcement, not as the only source of meaning.

Sufficient contrast. Text, cards, and state labels use theme tokens selected for strong contrast in light and dark modes. We continue to review edge cases as new surfaces are added.

Reduced motion. Motion is not required to complete common tasks. The main Pulse ring respects the iOS Reduce Motion setting.

Ongoing work

What we are still improving

Larger Text. Pulse uses readable fixed type sizes today, but we are still auditing full Dynamic Type behavior across dense cards, graphs, and diagnostic panels. We will not claim full Larger Text support until common tasks have been tested at larger accessibility sizes.

Captions and audio descriptions. Pulse does not currently include video, audio narration, or time-based media that requires captions or audio descriptions.

Feedback. If an accessibility issue blocks a common task, email hello@kenshikilabs.com. Please include the device model, iOS version, the task you were trying to complete, and the accessibility feature you were using.

Public site

Website accessibility

The Kenshiki public site uses semantic HTML, visible focus states, text links, and responsive layouts. We avoid requiring the interactive demo to understand legal, privacy, or accessibility notices.

Some demo and chart surfaces are more complex than static pages. We treat accessibility issues there as product bugs and prioritize fixes that affect common navigation, reading, and support tasks.