Accessibility

Published 3 October 2026. Last reviewed 22 October 2026.

1. What this covers

turiyahq.com and holynt.com, including every page in the product site's build. It does not cover the third-party services we link to, or the interfaces of the tools named on the vulnerability disclosure page.

2. The standard, and our status

We work to WCAG 2.2 Level AA. Our status is partially conformant: some parts of the sites meet the standard and some have not been assessed. Section 4 says which, and section 3 says how little has been measured.

3. How this was assessed

By one automated script, run locally before each deploy. scripts/check-contrast.mjs drives a real browser over every page in the build, in both the dark and light themes, and asks the browser what each text element actually resolves to. It asserts a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. On the last run it covered 84 pages across two themes and reported no failures.

It also fails the build when a design token is declared twice in one block, because a duplicate silently overrides the value above it.

An automated pass is not an audit. No external audit has been carried out, and no assistive technology has been tested.

4. What that assessment does not cover

Stated plainly, because a claim of conformance would otherwise read into the gap:

• Screen readers. Not tested with NVDA, JAWS or VoiceOver. Heading order, landmark structure and reading order across the terminal-styled sections are unverified.
• Keyboard traversal. A focus style is defined and a skip link is present. Whether every interactive element is reachable and in a sensible order has not been audited.
• Zoom and reflow. Tested at the browser's default size. Behaviour at 200% zoom, and at 320px width, is unverified.
• Content added later. The check runs against the build, so anything published after a run carries only the checks that run covered.
• The PDF and image outputs. Receipt pages and generated images have not been assessed as documents.

Motion is the one item here that is handled: the animated components fall back to a static frame when the browser reports a preference for reduced motion.

5. If something blocks you

Write to [email protected] and say what you were trying to do and what happened. If you need a fact or a document here in another form, ask, and we will produce it.

We aim to reply within 7 days. Where a barrier cannot be fixed quickly, we will tell you what we can offer instead rather than leave the message unanswered.

6. Review

This statement is reviewed when the site changes materially, and at least every quarter. Its date is at the top. When a limitation in section 4 is closed by a new check, the line is removed rather than reworded.