Accessibility
Everyone belongs. Intelligence for all.
This site is built and tested to WCAG 2.2 AA: an automated accessibility suite runs on every page, and keyboard operability and reduced motion are tested. That is the standard and the method — not a certificate. It is also where the work continues.
DifferentAbilities.SameOpportunities.
Tested on every page
The method, not a badge.
- Automated WCAG 2.2 AA checks
- Keyboard operability
- Reduced motion respected
- Colour contrast at AA
- Inclusive by designBuilt for every reader from the start
- Works with assistive technologyScreen readers and keyboard first
- English todayOther languages planned per deployment
- Follows your settingsText size, contrast, motion
- Tested, not badgedAn automated suite on every page
Our approach
Accessibility built into everything we make.
Four steps, repeated. The standard is WCAG 2.2 AA; the method is testing every page, not a one-time review.
1. Understand
Start from the needs of people who read with a screen reader, navigate by keyboard, need more contrast or need less motion — and from what stops them today.
2. Design
Build the page model so that structure, headings, labels and focus order are right once, in one component per kind, and every page inherits them.
3. Validate
Run an automated WCAG 2.2 AA suite on every page, and test keyboard operability and reduced-motion behaviour, before a change ships.
4. Improve
Treat every reported barrier as a defect to fix and a test to add, so the same barrier cannot come back.
How the site adapts
Built to work the way you read.
What this site does today. Where a feature waits on something that does not exist yet, it says so.
- Text sizeSizes are relative, so the site follows your browser's text setting rather than overriding it.
- ContrastColour contrast is held to the AA threshold and checked on every page by the automated suite.
- KeyboardEvery control can be reached and operated from the keyboard, with a visible focus indicator.
- Screen readersReal headings, labelled controls, described images and a logical reading order.
- CaptionsNo video exists on this site yet. When one does, it will carry captions and a transcript before it is published.
- Reduced motionIf your system asks for less motion, animation is reduced — and that setting is tested.
- Plain languageShort sentences, plain words, and defined terms wherever the site has to be exact.
- One languageThe site is in English only today. Other languages are planned deployment by deployment, not claimed now.
Inclusive for every reader
Supporting diverse needs.
What the design does for each need — stated as the build, not as an outcome.
- VisualScreen-reader structure, AA contrast, scalable text, and no meaning carried by colour alone.
- HearingNothing on the site depends on sound. Video, when it exists, will be captioned and transcribed.
- NeurodiversityConsistent layouts, one idea per section, plain words, and less motion on request.
- PhysicalFull keyboard operation, generous targets, and no action that needs a precise gesture or a time limit.
- LanguagePlain English and defined terms, with no jargon walls. Other languages are planned per deployment.
- Different ways of readingThe same content in more than one shape — a journey, a grid, a plain answer — never only a picture.
A platform for every ability
Learn without limits.
The discipline this site is built with carries into Zynaut Pathways: structure first, keyboard and screen reader as first-class routes, motion and contrast that follow your settings, and plain language for anything that matters. Pathways is in development, so its accessibility is a commitment being built to — not yet a tested result.
- WCAG 2.2 AA as the working standard
- Keyboard and screen reader as first-class routes
- Your text, contrast and motion settings respected
- Plain language throughout
- Barriers reported, fixed, and pinned by a test
Inclusion is not a feature. It is a mindset.
- Text sizeScales with your browser setting — never capped
- ContrastEvery text colour checked against its background
- Reduced motionHonoured from your system preference
- KeyboardEverything reachable, focus always visible
- Screen readersLandmarks, labels and a sound heading order
Tell us
How to report a barrier
If something on this site is hard to read, reach or operate, tell us through the contact form. Say which page, what you were trying to do, and the browser or assistive technology you were using, if you know it.
A person reads every report. A confirmed barrier is fixed and a test is added so it cannot return. You will be told what was done.
This site is built and tested to WCAG 2.2 AA. That describes the standard and the testing method. It is not a certification, and none is claimed.
Questions people ask
Accessibility, in plain answers
Which standard is the site built to?
The Web Content Accessibility Guidelines at level AA, in their current version, named exactly at the top of this page. An automated suite checks every page against it, and keyboard operability and reduced motion are tested as well.
Does the site hold an accessibility certification?
No, and none is claimed. What is true is the method: an automated accessibility suite runs on every page, keyboard operability and reduced motion are tested, and a reported barrier becomes a fix and a test. A certificate would be published with its scope if one existed.
Is the site available in other languages?
Not yet. The site is in English only. Other languages are planned deployment by deployment, because a deployment serves a particular place and its people, and none is claimed until it exists.
Does the site work with a screen reader?
It is built to: real headings, labelled controls, described images and a logical reading order, checked by the automated suite on every page. If your screen reader meets something that does not work, report it and it will be treated as a defect.
Will Zynaut Pathways itself be accessible?
It is being built to the same standard and by the same method as this site. Pathways is in development, so that is a commitment being built to rather than a tested result, and nothing about it is claimed until it can be shown.
Are there videos with captions?
There is no video on this site yet, so there is nothing to caption. When a video exists it will carry captions and a transcript before it is published, not after.
