Accessibility

Accessibility Statement

We are committed to making Light of Scripture accessible and usable for everyone. This statement explains our approach, current support, and how to report accessibility barriers.

Last updated: March 8, 2026

Jump to section

Commitment Standards Supported Features Known Limitations Feedback Improvement

1. Accessibility Commitment

Light of Scripture is committed to making Bible study tools accessible to as many people as possible, including users with visual, auditory, motor, cognitive, and neurological disabilities.

Accessibility is treated as a core quality requirement, not an optional enhancement.
We design for inclusive reading, navigation, and interaction across desktop and mobile experiences.
We aim to reduce barriers so users can focus on learning and spiritual growth.

2. Standards and Approach

We work toward recognized accessibility practices and continually improve implementation across our interfaces.

Our accessibility work is guided by modern web accessibility principles and semantic-first UI development.
We prioritize keyboard support, readable structure, contrast awareness, and clear interaction patterns.
Accessibility checks are part of ongoing design, engineering, and QA workflows.

3. Supported Accessibility Features

Many platform components are designed to improve usability with assistive technology and alternative navigation methods.

Keyboard-friendly controls are used for core navigation and primary study interactions.
Headings, labels, and structural layout are designed to support screen reader comprehension.
Form fields include explicit labels and validation messaging for clearer input flows.
Responsive layouts are optimized for zooming and smaller screens where practical.
Color and contrast choices are selected to improve readability across major content areas.

4. Assistive Technology Compatibility

We strive for compatibility with common assistive technologies and modern browsers.

Users may access the platform with screen readers, keyboard-only navigation, and browser zoom tools.
Support quality may vary by specific browser, operating system, and assistive technology combinations.
If a specific setup causes usability barriers, report it so we can investigate and improve compatibility.

5. Known Limitations

Despite ongoing improvements, some areas may still present accessibility challenges.

Certain complex interactive tools or embedded content may require additional refinements.
Legacy pages may not yet have full parity with newer accessibility improvements.
Third-party integrations can occasionally introduce behavior outside our direct control.

6. Accessibility Feedback and Support

If you encounter an accessibility issue, we want to hear about it and provide support.

Contact us with the page URL, device/browser details, and a short description of the issue.
If possible, include steps to reproduce the barrier and any assistive technology you are using.
Feedback is reviewed by the team and prioritized into ongoing product updates.

7. Continuous Improvement

Accessibility work is continuous. We regularly review product areas and iterate based on testing and user feedback.

Engineering and design updates are planned to reduce known barriers over time.
We track recurring usability issues to improve long-term consistency across the platform.
As new features launch, accessibility is evaluated alongside functionality and performance.

Need Accessibility Support?