Accessibility.
This site is built to be usable with a keyboard, a screen reader, zoom or the motion turned off. Here is what that means, where it falls short, and how to tell us when something doesn't work.
fig. 00 · at a glance
- TargetAAWCAG 2.1 level AA, in both themes and every accent.
- KeyboardFullEverything works without a mouse, with a visible focus ring.
- MotionOptionalTurn on reduced motion in your system and the effects stop.
- Reply≤ 5 daysReport a barrier and we answer within five working days.
The short version
You should be able to read every page, request a hook and follow the journal with whatever setup you use. If you can't, that's a bug, and we want to hear about it.
Standard and status
Partially conformant with WCAG 2.1 AA.
The target is level AA of the Web Content Accessibility Guidelines 2.1, the level referenced by the European standard EN 301 549. The site has not had an independent audit, so it is described as partially conformant: most of it meets the target, and the known gaps are listed below.
What is in place
- Semantic HTML with landmarks and headings in order, and a “Skip to content” link.
- Every control reachable and usable with a keyboard, with a visible focus ring.
- Reduced motion respected: the intro, the animated terrain and the work-stage demos stop when your system asks for less motion.
- Text contrast checked in light and dark themes and with every accent colour.
- Pages readable at 200% zoom and at phone width without horizontal scrolling.
- Form fields with visible labels, required fields marked, and error messages linked to their fields.
- Images with text alternatives; purely decorative drawings hidden from screen readers.
Known limitations
Where it doesn't fully work yet.
- Interactive demos on the home page are drawings with pointer interactions. They are hidden from screen readers and their content is repeated in text next to them.
- Code samples in the journal scroll sideways on small screens instead of wrapping.
- Third-party pages such as Programmable's trading page, wallets, X and Telegram are outside our control.
How it is checked
Before a change ships it is checked with a keyboard-only pass, a screen reader (VoiceOver or NVDA), reduced motion turned on, and automated checks. Automated tools catch only part of the problems, so feedback from real use matters most.
Report a barrier
One email. An answer within five working days.
Write to hello@hookwright.xyz with the page, what you were trying to do and, if you like, the browser and assistive technology you use. We reply within five working days and, where possible, send the content you needed in another format in the meantime.