# Accessibility Source: https://docs.gryt.chat/docs/guide/accessibility Our commitment and roadmap toward full accessibility Gryt is not fully accessible yet. This page says what works, what does not, and what is being done about it, because a page that only listed the good parts would be worse than nothing to somebody deciding whether they can use this. ## Why accessibility matters Voice chat platforms are inherently social tools. If they aren't accessible, they exclude the very people who could benefit most from low-friction, real-time communication. We believe everyone deserves equal access to online communities regardless of visual, motor, auditory, or cognitive ability. ## Typography: Atkinson Hyperlegible Gryt uses [Atkinson Hyperlegible Next](https://brailleinstitute.org/freefont) as its primary typeface and **Atkinson Hyperlegible Mono** for all monospaced text (code blocks, hotkey badges, debug panels, and technical displays). Atkinson Hyperlegible was created by the **Braille Institute of America** with one goal: maximum legibility. Traditional typefaces optimize for aesthetics; Atkinson Hyperlegible optimizes for character differentiation. Key design decisions include: - **Exaggerated letter forms** — Characters like `I`, `l`, `1` and `0`, `O`, `Q` are unambiguously distinct, reducing misreadings for users with low vision. - **Open apertures** — Letters like `c`, `e`, and `s` have wider openings so they remain distinguishable at small sizes or low resolutions. - **Asymmetric shapes** — Mirrored letters such as `b`/`d` and `p`/`q` have subtle asymmetries that make them easier to tell apart. - **Variable weight axis** — The font ships as a single variable file supporting weights 200–900, so we can use it everywhere from thin labels to bold headings without loading extra files. The mono variant applies these same legibility principles to fixed-width text, making it significantly easier to read code, IP addresses, keybinds, and latency numbers compared to traditional monospace fonts. ## Current accessibility features ### Keyboard navigation Core flows, meaning the chat input, the voice-control hotkeys and dialogs, are operable with the keyboard. However, some interactive elements (video cards, reply links, the image lightbox, and the focused-video overlay) are not yet keyboard-accessible, and list views (channels, servers, members) do not support arrow-key navigation. We are working toward full keyboard operability for every interactive element. ### Configurable hotkeys Users can rebind **push-to-talk**, **mute**, **deafen**, and **disconnect** to any key combination via _Settings → Hotkeys_. This lets users with limited mobility choose key placements that work for them. Camera and screen-share toggles are not yet rebindable. ### Screen reader support The client is built on `@gryt/ui`, which sits on Base UI primitives. Those provide a baseline of ARIA roles and keyboard interaction for dialogs, menus and form controls. However, comprehensive screen-reader support is still in progress: many icon-only buttons lack `aria-label` attributes, the layout does not yet use semantic HTML landmarks (`