Accessibility statement.

Last reviewed 4 July 2026.

Technika11y builds accessibility tooling. This site should be an example of the standard we hold others to, so we state our position plainly — including what we have not yet verified. Overclaiming conformance would betray the whole point.

target

We aim for WCAG 2.2 Level AA.

what this site does today

• Fully keyboard operable, with a visible focus indicator and a skip link.
• Semantic landmarks and a logical heading order.
• Respects prefers-reduced-motion, plus a visible control to pause motion.
• A high-contrast toggle, and support for forced-colors / high-contrast modes.
• Progressive disclosure via native <details> — works with mouse, keyboard, touch, and screen readers, never hover-only.
• No meaning carried by colour alone; status and labels are always text.

how we measure

This page is checked against our own Shadow-DOM Auditor as part of the build. Automated axe checks and manual assistive-technology testing are planned but not yet complete.

known limitations

• Not yet independently audited, nor tested across the full range of screen-reader and browser combinations.
• The hero uses a decorative animated grid; it is mitigated by reduced-motion support and the pause control, but is motion nonetheless.
• Any raster brand banner added later will ship with a text alternative — none is embedded on this page yet.

report a barrier

If something here is hard to use, tell us — that is a bug, and we want it. Open an issue on the technika11y GitHub organization, or email the maintainer listed there. We aim to acknowledge within 5 business days.