Accessibility statement

Read Master is a reading tool, so it has to work for people who read in different ways: with a keyboard, with a screen reader, with large text, with high contrast, or with a font made for dyslexia. We design for the Web Content Accessibility Guidelines (WCAG) version 2.2, the international standard for accessible websites.

WCAG has three levels: A (minimum), AA (the usual legal benchmark) and AAA (the strictest). These are our targets. A target is what we build and test towards. It is not a claim that every page already meets it.

We do not yet claim full conformance with WCAG 2.2 at any level. We will make that claim only after the manual tests listed under “What we have not tested yet” are done and their findings are fixed. Until then, please read this page as an honest progress report.

• Automated checks on every change. A standard tool (axe-core) scans our main public pages and the reader's menus for accessibility faults, in each colour theme. A fault found there blocks the change.
• A wider automated scan every night. The same tool scans more pages, including signed-in ones, in English and Arabic and at phone and desktop sizes. This scan reports faults to us. It does not block a release by itself.
• Shared components. The buttons, menus, dialogs and other building blocks are made with React Aria, a toolkit designed for keyboard and screen-reader use. Each one is scanned by the automated tool on every change.
• Contrast on the book page. The text colours of the book page are checked in every theme for a contrast of at least 7 to 1.

Automated tools find only part of what can go wrong. That is why the next section matters.

• Screen readers. We have not yet done a manual test with NVDA, JAWS or VoiceOver. Date of the last manual screen-reader test: none yet. This is planned before our public launch, and this page will be updated with the date and the results.
• Some browsers and devices. Our automated accessibility checks run in Chrome's engine only. We have not yet done a full manual test in Safari on a Mac, on an iPhone or iPad, or in Firefox.
• Some pages. Not every page is in the automated scan yet. This page and our other legal pages are among those still to be added.

• Single-key shortcuts. The reader, flashcard review and quizzes use single keys as shortcuts (for example, number keys to pick an answer). If these get in your way, for instance with speech input, turn them off: in the reader, open “Reading preferences”, find “Keyboard”, and switch off “Single-key shortcuts”. The setting applies to your whole account.
• Books you import. We show your book as it is in the file. If a PDF is a scan with no text layer, or a book's images have no descriptions, we cannot add what is missing.
• Text read aloud and one-word-at-a-time reading. These features have not had a manual screen-reader test.

• Light, dark, sepia and High Contrast colour themes, for both the app and the book page.
• Text size from 12 to 40 pixels and line spacing from 1.2 to 2.0.
• Two fonts made for easier reading: Atkinson Hyperlegible and OpenDyslexic.
• Built for keyboard use, with a skip link on every page and a visible focus outline.
• Less animation when your device asks for reduced motion.
• Arabic with a right-to-left layout.

If something on Read Master is hard or impossible for you to use, write to [email protected]. It helps if you tell us the page, what you were trying to do, and the browser and assistive technology you use. We aim to reply within 5 working days. We treat accessibility faults as top-priority bugs.

This statement was written on 12 October 2026 from our own automated test results. It was not prepared by an outside auditor. We will update it when the manual tests are done, and whenever something on this page stops being true.