Accessibility
Accessibility
What has been done, what is aimed for, and how to tell us when something does not work.
Last updated: 23 August 2026
This document is a starting template. It has not been reviewed by a lawyer and does not constitute legal advice. It must be reviewed and adapted before Onyx Development relies on it.
The target
This site aims to meet WCAG 2.2 Level AA. That is a target and an ongoing commitment rather than a certification — no absolute claim of conformance is made.
What has been built in
Semantic HTML with a correct heading structure, a skip link to the main content, and landmarks throughout.
Full keyboard operation: every interactive control is reachable and usable by keyboard, focus is always visible, and dialogs trap focus while open and return it to whatever opened them.
Text contrast is checked against the AA thresholds, and colour is never the only way information is conveyed.
Form controls have real labels, errors are announced, and no field relies on placeholder text as its label.
Motion
This site uses movement deliberately. If your system is set to reduce motion, that preference is respected: parallax and scroll-linked movement stop, the pointer-lit effects and custom cursor are disabled, and reveals become simple fades.
No content is ever hidden behind an animation that cannot run — everything remains readable with motion off.
Known limitations
Some sections use scroll position to advance a visual sequence. These are always accompanied by the same information as text, and they show their completed state when reduced motion is enabled.
Telling us about a problem
If any part of this site is difficult or impossible to use, please get in touch through the contact page and say what you were trying to do. Accessibility problems are treated as defects, not feature requests.