Accessibility
Our commitment to making Dia Logos usable by everyone.
Our standard
We aim to meet WCAG 2.1 Level AA across all pages and interactive flows. We test with:
- Automated axe-core scan (CI, every pull request)
- Keyboard-only navigation through all top-10 flows
- NVDA (Windows) screen-reader pass on top-10 screens
- VoiceOver (macOS / iOS) screen-reader pass on top-10 screens
- 200% browser zoom test on all pages
prefers-reduced-motionmedia query honored for all animations
Accessibility features
- Skip to main content — press Tab as the first action on any page to reveal the skip link.
- Keyboard navigation — every interactive element is reachable and operable by keyboard. Modal dialogs (e.g. scripture passage drawer) trap focus and dismiss on Esc.
- Visible focus indicators — all interactive elements show a visible focus ring meeting the WCAG 2.2 Focus Appearance criterion.
- ARIA landmarks — pages use
main,nav,aside, andheaderlandmarks so screen-reader users can navigate by region. - Live regions — form errors, status messages, and async state changes are announced via
aria-liveregions (role="alert"for errors,role="status"for informational updates). - Decorative images — all icon SVGs carry
aria-hidden="true". Meaningful images have descriptive alt text. - Colour contrast — text and interactive elements meet the 4.5:1 contrast ratio for normal text and 3:1 for large text, in both light and dark mode.
- Current page indication — active navigation items carry
aria-current="page"so screen readers announce which section you are in. - Dark mode — full dark-mode support; contrast targets maintained in both themes.
Tested keyboard flows
The following flows are verified keyboard-only complete in every release:
- Sign in / register
- Dashboard — today view
- Journal: create entry, set visibility
- Group: weekly flow, weekly reflection
- Insight inbox: review and resolve
- Story prompts: respond to prompt
- Prayer hub: submit and view threads
- Testimonies: draft, edit, share
- Account settings: change password, manage data
- Data export and account deletion
Full keyboard navigation steps are documented in docs/playbooks/a11y-keyboard-flows.md in the project repository.
Known limitations
- Third-party embeds (scripture passages via API.Bible) inherit the accessibility of that provider. We fall back to the local World English Bible corpus wherever possible.
- PWA offline mode (planned) will include accessible offline state indicators when implemented.
Feedback and contact
If you encounter an accessibility barrier, please let us know. We take all reports seriously and aim to respond within 5 business days.
Email: accessibility@dialogos.app
When reporting a barrier, it helps to include: the page URL, the assistive technology you were using (browser, screen reader, version), and a description of what you expected versus what happened.