Accessibility
What we test for, on every commit.
This site has an automated accessibility suite that runs before every deploy, and a deploy that fails it does not ship. This page says exactly what that suite checks. It is not a conformance claim: nobody has audited the site against a WCAG level, and we do not say they have.
Checked automatically
- One heading per page at the top level, and no heading level skipped.
- A skip link as the first tab stop, and a focus ring that is visible on the dark surface.
- Every form control labelled; every meaningful image described.
- The fixed controls at the bottom of the page — the button and the chat launcher — never overlap each other, and the page keeps room beneath its last line so nothing ends under them.
- Dialogs that take focus, hold it, close on Escape and return focus where it was.
- The whole page readable, and the builder usable, with JavaScript off.
- Under reduced motion, nothing is hidden and nothing animates.
- Colour contrast measured on both surfaces: the ember on the dark floor and the darker ember on the light paper both pass AA for text.
Not checked automatically
How the pages read with a screen reader, whether the motion is comfortable for you, and anything an automated check cannot judge. We test those by hand, less often than we would like.
If something is in your way
Email contact@dknappdesign.tech and say what you were trying to do and what happened. A person reads it, and it gets fixed or you get a straight answer about why not.