Skip to content
Stribog

§00/Accessibility

Accessible by engineering, not by afterthought.

We target WCAG 2.2 AA and treat accessibility defects as bugs. Here is our conformance posture, how we test, and how to tell us when we fall short.

Conformance target

This site aims to conform to WCAG 2.2 Level AA. Accessibility is treated as an engineering requirement, not a retrofit — the same audit-grade posture we bring to client systems.

§01/Measures in place

  • Semantic HTML landmarks and a logical, sequential heading order on every page.
  • Full keyboard operability, with a clearly visible focus indicator on every interactive element.
  • Colour contrast meeting AA in both light and dark themes.
  • Meaningful images carry descriptive alt text; purely decorative graphics and icons are hidden from assistive technology.
  • prefers-reduced-motion is honoured — entrance and ambient animations collapse to no motion.
  • The interface follows your operating-system light/dark preference by default, and the theme control is fully labelled.
  • Layouts are responsive and remain usable when zoomed to 200%; nothing depends on colour alone.
  • No auto-playing media and no flashing content.

§02/How we test

We combine automated and manual checks. Automated audits (Lighthouse) currently report a perfect Accessibility score on every route. Because automated tooling catches only a portion of real-world barriers, we also exercise the site by keyboard and with assistive technology, and we review contrast in both themes. We treat any accessibility defect as a bug, not a backlog nicety.

§03/Known limitations

We aim for full AA conformance and believe the site meets it, but no site is ever finished. If you encounter something that does not work with your assistive technology, that is a defect we want to know about — the assessment below invites exactly that.

§04/Report a barrier

If any part of this site is difficult or impossible to use, please tell us at [email protected]. Describe the page, what you were trying to do, and your browser and assistive technology if you can. We prioritise accessibility reports and will respond.

See also the colophon for how the site is built and the privacy statement for what it collects.

Last reviewed: June 2026.