Skip to main content

Selah Legal

Accessibility Statement

Last updated March 30, 2026.

Our commitment

Selah is built to be usable by everyone. We follow WCAG 2.2 Level AA guidelines as our target standard and continuously work to improve the accessibility of the reading, study, and journaling experience.

What we do

  • Keyboard navigation: All interactive elements are reachable and operable by keyboard. A skip link is provided on every page to jump directly to main content.
  • Semantic HTML: We use proper heading hierarchy, landmark regions (nav, main, footer), and semantic elements throughout the app.
  • Focus indicators: Visible focus outlines appear on all interactive elements when using keyboard navigation.
  • Focus visibility and fixed-header support: Pages use scroll offsets and focus treatment intended to prevent anchored content or keyboard focus from being hidden beneath the fixed navigation bar.
  • Screen readers: ARIA labels, live regions for dynamic content (toast notifications, chat messages), and descriptive alt text for images.
  • Color contrast: Text and interactive elements meet WCAG AA contrast ratios in both dark and light themes.
  • Reduced motion: Animations respect the prefers-reduced-motion media query. Users who prefer reduced motion will see minimal or no animation.
  • Touch targets: Interactive elements have a minimum tap target size of 44x44 pixels on touch devices.
  • Responsive design: The app works across screen sizes from mobile to desktop without loss of content or functionality.
  • Form accessibility: All form inputs have associated labels. Error messages are linked to their inputs and announced to screen readers.

Known limitations

  • The AI study chat interface may not announce all dynamic updates to screen readers in real-time. We are improving ARIA live region coverage for streamed responses.
  • Some third-party Bible text may not include optimal semantic markup for reading order in all translations.
  • Verse wallpaper images are decorative and generated dynamically; alt text describes the verse reference but not the visual design.

Testing

We test Selah using a combination of automated accessibility scanning (axe-core), manual keyboard testing, and periodic screen reader testing with VoiceOver and NVDA.

Accessibility is an ongoing engineering process, not a one-time audit. We prioritize fixing issues that block users from completing core tasks.

Report an issue

If you encounter an accessibility barrier, please email hello@selahscripture.com with:

  • The page or feature where the issue occurred
  • Your device, browser, and assistive technology (if applicable)
  • A description of what you expected and what happened

We aim to acknowledge accessibility reports within 5 business days and resolve blocking issues as quickly as possible.

Related