Accessibility

Veyragram aims to meet WCAG 2.2 level AA. This page describes what is in place and what hasn’t been tested yet.

Keyboard#

• Skip to content is the first thing you reach with Tab on every page.
• Every control works with the keyboard. Menus open with Enter or Space and move with the arrow keys; dialogs keep focus inside and return it when they close; Escape closes them.
• In a conversation, Enter sends and Shift+Enter starts a new line. If you prefer Enter for new lines, turn off Settings → Appearance → Enter sends messages; then Ctrl+Enter (⌘+Enter on a Mac) sends.
• In these docs, / or Ctrl+K (⌘+K) opens search.

Screen readers#

• The message list is announced as a log. New messages are read politely and never move your focus.
• Each message is labelled with its sender, time and text, or with “cannot decrypt on this device” or “message deleted”.
• Delivery states (sending, delivered, read, not sent), typing and connection changes are announced as text.
• While the app opens, its status line changes only when the real loading stage changes, so the animation isn’t read out.

Motion#

If your system asks for reduced motion, Veyragram shows a still loading mark with the same status text, switches between Day and Night instantly, and turns off sliding panels, shimmer and smooth scrolling.

Seeing and touching#

• Text and controls meet AA contrast in Day and Night and in every colour theme.
• Meaning is never shown by colour alone: errors, unread conversations and room requirements are also written out.
• Buttons are at least 44 × 44 pixels, except the small menu button beside each message.

Not yet tested#

Veyragram hasn’t yet had a full keyboard-only review, testing with screen readers (NVDA, VoiceOver, TalkBack), or testing on real phones. If something is hard to use, please tell the operator through Support.