Accessibility statement

This statement covers e.zi2.app and every imprint storefront, reader and console served from it. It was written on 9 October 2026 and is reviewed with every release.

What we aim for

The target is WCAG 2.2 at level AA. Every page is built to be read by screen readers, driven by keyboard alone, and resized to 200 percent without loss. The reader applies the same standard to every book it opens.

What is in place

• The Access panel at the bottom corner of every page, also reachable with Alt+Shift+A. It carries six profiles (seizure safe, vision impaired, ADHD friendly, color blind, dyslexia friendly, cognitive), content adjustments (scaling, font size, text and line spacing, alignment, readable and dyslexia-friendly fonts, a text magnifier, reading mode, highlighted titles and links, hidden images, stopped animations, muted sounds), color adjustments (background, heading and text colors, brightness, black and white, saturation, contrast, dark and light high-contrast), navigation aids (reading mask, reading guide, big cursor, focus highlight, keyboard help), a page structure list and a sitemap. Choices persist on your device.
• Skip link to main content on every page, landmarks for header, navigation, main and footer, headings in order, labels on every control, visible focus, and no content that flashes.
• The reader: themes including high contrast, three typefaces, adjustable measure and alignment, line focus, guided reading, read aloud, auto-scroll, bookmarks, search and a full keyboard map.
• Every image carries alternative text; decorative images are hidden from assistive technology.
• Forms announce their errors and keep what you typed.

Known limits

• Third-party pages we hand off to, such as Stripe Checkout, follow their own accessibility statements.
• Publisher-supplied PDFs vary in tagging; the sealed and EPUB editions carry the full structure.

Tell us

If any part of the site stops you, write to [email protected] with the page address and what happened. We answer within two working days and we fix the page, or we provide the content or transaction another way in the meantime.

How we test

Each release is checked with keyboard-only navigation, VoiceOver and NVDA, browser zoom to 200 percent, and automated contrast checks across light and dark themes.