Accessibility statement

Accessibility is the reason Zacess exists, so it is part of every decision rather than a check at the end. This statement covers this website and sets out the standard every part of Zacess is held to.

Our standard

  • WCAG 2.2 level AA is the minimum everywhere, with AAA contrast (7:1 or higher) in the reading view.
  • Everything works from the keyboard, with a visible focus indicator. Zacess is designed for switch access and voice control too.
  • Every control has a label and every image has alt text or a description.
  • Colour is never the only way information is shown.
  • Motion follows your reduced motion setting.
  • Light and dark modes follow your system. You can also choose one yourself.
  • An accessibility problem is treated as a bug, not a feature request.

How Zacess is built for it

  • The interface is real HTML rather than a painted canvas, so screen readers and braille displays can work with it.
  • Every contrast theme in the reading view meets AAA contrast. A test checks each one on every change.
  • Exported HTML is checked against WCAG 2.2 AA by automated tests on every change. EPUB exports are checked with EPUBCheck.
  • Text that may have been misread is marked with a dotted underline as well as a highlight and is announced to screen readers as unclear.
  • Reading profiles never change silently. Any suggested change is shown for you to accept or refuse.
  • Zacess will be able to show what is inaccessible about a document, such as missing headings, missing image descriptions or a confusing reading order. It will also preview a document as a screen reader would.

This website

This site uses real headings and landmarks, a skip link, text at 7:1 contrast or higher and the Atkinson Hyperlegible typeface, designed by the Braille Institute for low-vision readers. It works without JavaScript. Our own small scripts drive the colour mode control, which offers System, Light and Dark as labelled buttons that say which one is selected, the menu button on small screens and some gentle motion that switches off when you ask for reduced motion. Cloudflare Web Analytics adds its own script to count visits, as the privacy page explains.

Links open in the same tab, link text says where it goes and the layout works at 400% zoom and on narrow phone screens without scrolling sideways.

Assistive technology we will test with

We plan to test every part of Zacess with:

  • VoiceOver on macOS and iOS
  • TalkBack on Android
  • NVDA and JAWS on Windows
  • Orca on Linux
  • braille displays and embossers, for the braille-ready files

This testing has not been done yet. The browser version is an early release. Results will be published here as each part of Zacess is tested.

Testing with disabled people

Automated checks are not enough. Before each phase ships, it will be tested by people with different access needs, including people with low vision, blind people using a screen reader and people with dyslexia, ADHD or hearing loss. Their feedback decides what changes before release. If you would like to take part, email contact@zacess.com.

Known limitations

Zacess is pre-release, so the browser version and the apps have not been tested with users yet. Some limits in the core are already known:

  • A table whose cells wrap onto several lines or whose columns do not line up is read as paragraphs.
  • Joined handwriting and dark blackboards cannot be read yet. A page that could not be read is marked rather than passed off as notes.
  • Braille-ready files have not yet been read on a physical braille display or embossed.
  • Slide capture has been tested with a simulated camera, not yet with a real phone and projector.

We will list every known issue here, with what we are doing about it, before each release. A full conformance report, listing the assistive technologies supported, test results and the issues being worked on, will be published with the first release.

Tell us about a problem

If anything here is hard to use, please tell us at contact@zacess.com or in Zacess Discussions on GitHub. Say what you were trying to do and what happened. You never need to share a diagnosis or any personal detail.

Last reviewed on 13 October 2026.