Accessibility Statement

Version 1.0 · KJN

What we have built

• Screen reader support. Interactive controls carry accessible names, landmark and widget roles are set, and status changes (connection state, captions, room events) are announced through polite live regions rather than appearing silently.
• Keyboard access. The interface is built from native buttons, labelled form fields, and links, so it follows the browser's own focus order, and focus indicators are styled to stay visible for keyboard users rather than being removed.
• Reduced motion. We honour your system "reduce motion" setting and drop non-essential animation when it is on.
• Fixed dark canvas and increased contrast. The main app uses a fixed dark green canvas (the Wall and chat panel inside a room is light) and does not currently switch with your system's light or dark-mode preference. It does respond to the system's increased-contrast setting and forced-colors mode.
• Decorative images are hidden from screen readers. Avatars sit beside the person's name in text, so they are marked decorative instead of read out as noise.
• Text, not just video. Every room has a text chat, so a conversation can be held entirely in writing.
• Skip link. The first thing a keyboard user reaches is a “Skip to main content” link that jumps past the rail and sidebar — in the lobby and inside a room alike.
• Measured contrast, entry screen and room. Not judged by eye: the colours are computed against the WCAG formula — alpha overlays composited over their base — and a regression test fails the build if a palette change drops any pairing below the threshold.

Known gaps — the honest list

• Captions cover your own speech only. This is the most important limitation on this page. Live captions come from your browser's own speech recognition and transcribe only your device. KJN does not caption other participants. If you are Deaf or hard of hearing, KJN does not currently give you a transcript of what other people are saying, and you should not rely on it for that. Room text chat is the working alternative today.
• No captions or transcripts are stored. Nothing is kept that you could read back after a call.
• Not tested with assistive technology — the gap we would most like closed. We have not run KJN through a screen reader end to end, nor tested it with voice control or a switch device. Everything above is built to the standard and measured against it; none of it is proven in use by someone who depends on it. Those are different things, and the difference is where the real problems usually are.
• Video calling has an unavoidable floor. Real-time video demands sustained attention and fast reactions. Some of that is intrinsic to the medium, and text chat is there for when it is not workable.

Tell us what breaks

If any part of KJN is unusable for you, email hello@kjn.app. Tell us what you were trying to do, what happened, and the assistive technology, browser, and operating system you were using if you can — it makes the problem far easier to reproduce. Accessibility reports are treated as defects, not as feature requests.

We aim to acknowledge accessibility reports within five business days. That is a commitment to answer you, not a commitment to a fix date; when something will take a while, we will say so and tell you what we know.

How this page stays honest

This statement describes the software as it actually ships. It is reviewed when the interface changes, and the gap list above is meant to shrink. If you find a claim here that does not match what you experience, that is a defect in this page and we want to hear about it at the same address.