Legal
Accessibility statement
This site is built to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA: every colour pairing meets the required contrast ratio, every page renders as real text rather than an image, and every control works from a keyboard alone. If something does not work with your assistive technology, tell us and we will fix it.
Last reviewed 6 September 2026
What we build to
The two brand blues on this site are not chosen by eye. Each one was measured against white and set to a fixed use: one for large text, graphics, and borders only, and a deeper one for every piece of body-size text, so nothing you need to read falls below the contrast a low-vision reader needs.
Every page renders its content server-side, as real text, not as an image or behind client-side JavaScript that has to finish loading first. A screen reader gets the same words on first load as a sighted visitor does. Every page carries exactly one heading marked as the page title, an automated check fails the build otherwise, so a screen reader's heading navigation always lands somewhere meaningful.
The mobile menu is built on the browser's own disclosure element rather than a custom dropdown we wrote ourselves, so keyboard and screen reader behaviour comes with it rather than being reconstructed by hand. Every interactive element shows a visible focus outline when you reach it by keyboard.
What we test
Before any page ships, we run it through Lighthouse and require an accessibility score of 100. That is a real gate, not a target: a page that scores below it does not go live.
What we have not yet done
We have not commissioned an independent accessibility audit, and we have not manually tested every page on this site with a screen reader such as JAWS, NVDA, or VoiceOver. An automated score is a strong signal, not a guarantee, and it can miss things a real assistive technology user would hit immediately. If you find one of those things, you are the fastest way we have of finding out.
How to report a barrier
Email hello@zway.ai with the page you were on, the assistive technology and browser you were using, and what happened. We will reply, and we will fix the specific thing you reported rather than filing it away for a general review that never happens.
The standard we aim for
We build against the WCAG 2.1 quick reference at Level AA. Where a specific page falls short of that standard, it is a bug, and the report above is how to reach us about it.