A library that meets you where you are.
ReadInward should be usable by everyone who wants to read more deliberately. This statement explains where we stand, what we measure against, and how to reach us when something fails you.
Standards we target
We design and build ReadInward toward conformance with WCAG 2.2 Level AA, which incorporates the Section 508 Refresh requirements and the European EN 301 549 baseline used to satisfy the EU European Accessibility Act (EAA). For audiobooks and e-reading services delivered to EU consumers, the EAA has been in force since 28 June 2025, and we treat its requirements as launch gates.
What we currently meet
- Keyboard operability across all primary navigation, the reader, the audio player, and account flows.
- Visible focus rings on every interactive control, with a 2-pixel offset and a high-contrast gold outline.
- Skip-to-content link present on every page.
- Color contrast that meets or exceeds the AA 4.5:1 threshold for body text and the 3:1 threshold for large text and UI components.
- Reflow at 320 CSS pixels for content and 200% zoom for text without loss of information.
- Forms with programmatic labels, error identification, and instructions where needed.
- Captions and transcripts for synchronized audio (Read While Listening) where the source provides them.
- Respect for the operating-system prefers-color-scheme setting on first visit.
Known limitations we are working on
- Manual screen-reader QA across NVDA, JAWS, and VoiceOver is in progress; please report mismatches you find.
- Reduced-motion handling is being audited end-to-end; if you observe motion that ignores prefers-reduced-motion, let us know.
- An explicit high-contrast theme beyond Light, Dark, and Sepia is on the roadmap.
Reach us
If you encounter a barrier — a control that cannot be reached with a keyboard, a screen reader that cannot announce content, a color pairing that is unreadable, or anything else — write to accessibility@readinward.com with the page URL, the device and assistive technology you used, and a short description of what failed. We aim to acknowledge within five business days.
Compliance status
ReadInward is on a path to full WCAG 2.2 AA conformance. We perform automated checks (axe-core) on every build and conduct periodic manual audits. Most recent statement review: 2026-05-04.