Accessibility
This statement covers the Tincograph website and web app. It is written from what is measured, not from what is intended, and it names the gaps.
What is measured
- Every page of this website scores 100 for accessibility in Lighthouse, on mobile and desktop, and that score is a gate in our build: a change that drops it below 95 fails before it can be merged.
- Colour contrast is computed, not eyeballed. Every colour that carries text is asserted in a unit test to clear WCAG AA (4.5:1) against the surface it sits on, in both the dark and light themes. One colour in our palette is marked decorative-only and a test stops it being used for body text.
- Headings are in order. A real heading-order failure on the product pages — an h1 followed by an h3 — was found by that gate and fixed.
- Keyboard focus is always visible. The focus ring is defined once in our design system rather than left to each component, so a custom style cannot quietly strip it.
- Motion respects your settings. With "reduce motion" on, animation durations collapse to nothing across the whole interface at once.
- Form errors are announced, not only coloured: each is a live region tied to its field, so a screen reader hears what went wrong.
What is not done
- No testing with real assistive technology. Automated audits catch a useful fraction of problems and miss whole categories — a label that is technically present but meaningless, a reading order that is valid but confusing. Nobody has sat down with a screen reader and used Tincograph end to end.
- No audit by an accessibility specialist, and no formal WCAG 2.2 AA conformance claim. We believe the website is close; "believe" is the accurate word.
- The apps are less well covered than this website. The web app shares the same design system and the same contrast guarantees, but it has not had the same per-page audit.
If something does not work for you
Write to support@tincograph.com or use thecontact form. Tell us what you were trying to do and what got in the way — that is more useful than a standard name. Accessibility problems are treated as bugs, not requests, and they go to the front of the queue.
If you would rather not use a form at all, email works for everything: account questions, data export requests, deletion requests, all of it.