Evanreads

Accessibility Statement

Last reviewed: August 17, 2026

Evanreads is a reading tool built for students who find sustained reading difficult — particularly students with ADHD, dyslexia and related learning differences. Accessibility is the reason the product exists rather than a requirement bolted on afterwards, and we would rather tell you precisely where we stand than claim more than we can evidence.

Conformance status

Evanreads substantially conforms to WCAG 2.1 Level AA. We also report against Revised Section 508 (36 CFR 1194 Appendix A) and EN 301 549, both of which incorporate WCAG 2.1 AA.

"Substantially conforms" means every applicable Level A and Level AA success criterion is met except the items listed under Known limitations below. None of them prevents a student from completing a reading task, and none leaves content without an alternative — the homepage film, the one item on this list where that was true, now has captions and a written transcript.

Accessibility features

These are ordinary preferences inside the main interface. There is no separate "accessibility mode", no reduced-functionality alternate version and no third-party accessibility overlay — a student using these features is using the same product as everyone else.

• Line-by-line and paragraph reading modes. Text is presented one line or section at a time so the eye does not run ahead of comprehension.
• OpenDyslexic typeface. A weighted-bottom typeface, offered as a preference rather than an evidence-backed claim: in the eye-tracking study we cite, it was no faster than standard fonts.
• Text-to-speech. Any passage can be read aloud, with pause and stop controls. Nothing plays automatically.
• Bionic reading. Bolds the leading portion of each word as a fixation anchor. Offered as a preference, not as an evidence-backed claim — controlled studies are mixed.
• Adjustable type size, line height and contrast. Including a dark mode and high-contrast reading tokens.
• Full keyboard operation. The reader and every dialog can be driven entirely from the keyboard.

Known limitations

We publish these rather than waiting to be asked. Each is scheduled for the next evaluation cycle.

• Audio description for the homepage film. The 55-second brand film on our homepage now has captions and a full written transcript, which you can open next to the video without playing it. What it does not have is audio description — a spoken narration of what appears on screen. Its soundtrack plays continuously with no pauses to speak into, so adding one would mean producing a second version of the film. The transcript carries everything the film says, and nothing in the reading application depends on it.
• Non-text contrast. Primary controls and focus indicators meet the 3:1 requirement. A systematic sweep of every icon, border and interface state against 3:1 has not yet been completed; no failures were identified on primary controls.
• Moving content on the homepage. The animated preview in our homepage header loops continuously and has no pause button. It stops automatically if your system is set to reduce motion, and it is not used anywhere in the reader.
• Mixed languages when Spanish is selected. Choosing Spanish translates the interface, but pages we have not translated yet stay in English without being marked as English. A Spanish screen-reader voice will read those passages with Spanish pronunciation.
• Screen-reader verification. Conformance was verified using the browser accessibility tree — the interface assistive technology consumes — together with keyboard-only operation and programmatic focus and ARIA inspection. A full manual pass with VoiceOver and NVDA is planned as additional assurance.

How we evaluated this

Evanreads is a rolling web release, so this statement reflects the application as evaluated on August 17, 2026. Assessment was performed by manual evaluation of the running application using the browser accessibility tree, keyboard-only operation, programmatic focus and ARIA inspection, hand-computed colour-contrast ratios, and source-code review of surfaces that sit behind authentication.

This is a self-evaluation. No third-party accessibility auditor has assessed the product, and we say so plainly because a first-party report and an independent audit are not the same evidence.

VPAT / ACR

Our completed Voluntary Product Accessibility Template (VPAT® 2.5 Rev WCAG) covers WCAG 2.1 AA, Revised Section 508 and EN 301 549 criterion by criterion. It is published in full — no form and no request needed.

Download the VPAT (PDF) — VPAT® 2.5 Rev WCAG · issued August 17, 2026

If your procurement needs an ACR countersigned for a specific solicitation, or you have questions about anything in the report, email hello@evanreads.ai.

Reporting an accessibility problem

If any part of Evanreads is difficult or impossible for you to use, tell us — this is the fastest route to getting it fixed, and reports from people using assistive technology are the most useful thing we receive.

Email hello@evanreads.ai with "Accessibility" in the subject line. It helps if you can include the page or feature, what you were trying to do, and any assistive technology, browser or operating system involved — but please report it even if you cannot supply those.

We aim to acknowledge accessibility reports within 5 business days and to tell you what we intend to do and roughly when. If a fix will take time, we will try to describe a workaround in the meantime.

Contact

Accessibility questions, VPAT requests and procurement enquiries: hello@evanreads.ai