Back to Bible Progress

Accessibility Statement

Last Updated: January 17, 2026

Our Commitment

Bible Progress is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

We believe Scripture should be accessible to all people, and we strive to make our Bible reading tracker usable by as many people as possible, regardless of ability.

Accessibility Standards

Bible Progress aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards. These guidelines explain how to make web content more accessible for people with disabilities.

While we strive for full compliance, we recognize that some areas may still need improvement and welcome your feedback.

Accessibility Features

Screen Reader Support

Bible Progress includes comprehensive ARIA (Accessible Rich Internet Applications) labels throughout the application:

  • 35+ ARIA labels describing interactive elements
  • Tab navigation with proper ARIA roles and states
  • Profile management controls with descriptive labels
  • Chapter checkboxes with book and chapter context
  • Progress indicators and statistics labeled for screen readers
  • Modal dialogs with proper ARIA attributes
  • Action buttons with clear purposes

Keyboard Navigation

All functionality is accessible via keyboard:

  • Tab key to navigate between interactive elements
  • Enter/Space to activate buttons and checkboxes
  • Arrow keys for reading plan selection
  • Escape key to close modals and menus
  • Focus indicators visible on all interactive elements

Visual Design

  • High contrast text and UI elements for readability
  • Color-coded categories with text labels (not color-only identification)
  • Large touch targets for buttons and checkboxes (minimum 44x44 pixels)
  • Readable fonts using system fonts and web-safe fallbacks
  • Responsive design that works on all screen sizes
  • Dark mode option for reduced eye strain (Settings page)

Semantic HTML

  • Proper heading hierarchy (H1, H2, H3) for content structure
  • Semantic HTML5 elements (header, nav, main, section, article)
  • Descriptive link text (no "click here" links)
  • Form labels properly associated with inputs
  • Alternative text for all meaningful images and icons

Data Control

  • Local-first data storage (no account required)
  • Full data export capability (JSON backup)
  • Works completely offline (Progressive Web App)
  • Optional cloud sync (user-controlled)

Browser and Assistive Technology Support

Bible Progress has been tested with:

Browsers

  • Chrome (latest version)
  • Firefox (latest version)
  • Safari (latest version)
  • Edge (latest version)
  • Mobile browsers (iOS Safari, Chrome Android)

Assistive Technologies

  • NVDA screen reader (Windows)
  • JAWS screen reader (Windows)
  • VoiceOver (macOS, iOS)
  • TalkBack (Android)
  • Browser zoom up to 200%

Known Limitations

While we strive for full accessibility, we acknowledge the following limitations:

  • Some visual animations may not respect prefers-reduced-motion preferences (planned improvement)
  • Heatmap visualization may be challenging to interpret with screen readers (alternative text descriptions provided)
  • Third-party services (Blue Letter Bible links) are outside our control for accessibility
  • Easter egg features may not all be keyboard-accessible (these are optional fun extras)

Ongoing Improvements

We are actively working on:

  • Regular accessibility audits using automated tools and manual testing
  • Implementing user feedback from people with disabilities
  • Expanding ARIA support for dynamic content updates
  • Adding skip navigation links for long content
  • Improving focus management in modal dialogs
  • Enhancing color contrast ratios to meet AAA standards where possible

Feedback and Contact

We welcome your feedback on the accessibility of Bible Progress. Please let us know if you encounter accessibility barriers:

Email: accessibility@bibleprogress.com

Issue Tracker: Report on GitHub (if repository is public)

Response Time: We aim to respond within 5 business days

When reporting an issue, please include:

  • The specific page or feature affected
  • Your assistive technology (if applicable)
  • Browser and operating system version
  • Description of the issue and impact

Assessment and Compliance

This accessibility statement was created on January 17, 2026. The application has been:

  • Self-evaluated for WCAG 2.1 Level AA compliance
  • Tested with automated accessibility tools (aXe, WAVE, Lighthouse)
  • Manually tested with keyboard navigation
  • Tested with multiple screen readers
  • Reviewed for color contrast compliance

Our Commitment to You

Accessibility is not a one-time effort but an ongoing commitment. We believe that everyone should be able to engage with Scripture, and we are dedicated to making Bible Progress as accessible as possible.

Thank you for using Bible Progress. May your Bible reading journey be blessed!

Bible Progress © 2026 | Privacy | Terms