Trust
Accessibility
A company built on the idea that everyone should see their own shade accurately has no business shipping an interface some people cannot use.
Our commitment
We aim to meet Level AA of the Web Content Accessibility Guidelines 2.2 across exacthue.com, the ExactHue console and the embeddable shade-finder widget. We treat accessibility defects as ordinary defects: they go in the same backlog, with the same severity scale.
What is in place today
- Works without JavaScript. Every page of this website is static HTML. All content, navigation and forms function with scripting disabled — which also benefits assistive technology, low-bandwidth connections and older devices.
- Semantic structure. Landmarks, a single logical heading order per page, real lists, real tables with header cells, and native form controls with associated labels.
- Keyboard operable. Every interactive element is reachable and usable by keyboard, in a logical order, with a visible focus indicator that meets contrast requirements. A skip link is the first focusable element on every page.
- Contrast. Body text meets or exceeds 4.5:1 against its background; large text and interface components meet 3:1. The palette was checked at design time rather than after the fact.
- Reduced motion. The animated gradients and rotating graphics on the homepage are decorative and are disabled entirely when your system requests reduced motion.
- Text resizing and reflow. Layouts use relative units and reflow to a single column down to 320 px, and remain usable at 200% zoom without horizontal scrolling of the page body.
- Meaningful alternatives. Decorative graphics are hidden from assistive technology; informative graphics such as the Fitzpatrick tone strips carry text descriptions.
- Colour is never the only signal. Status, selection and emphasis are always conveyed by text or shape in addition to colour.
The shade-finder widget
The widget is where accessibility is hardest, because capturing an image is an inherently visual task. What we do about it:
- Every control is keyboard operable and properly labelled.
- Capture-quality feedback is announced through a live region, not signalled by colour alone — “too dark” and “mixed lighting” are words, not a red border.
- Results are rendered as text first: shade name, code, ΔE and confidence, with the visual preview as an enhancement rather than the sole output.
- Where JavaScript or a camera is unavailable, the widget degrades to a server-rendered shade grid so the product page remains complete and usable.
- Upload is offered as an alternative to live capture, for anyone who cannot frame a live shot comfortably.
Known limitations
Listing these is more useful than claiming full conformance.
| Limitation | Impact | Plan |
|---|---|---|
| Live capture requires a camera and JavaScript | Some users cannot complete a match on-device | Upload alternative is available now; a fully server-side path is on the roadmap |
| Shade preview is inherently visual | Blind and low-vision users cannot judge the rendered preview | Text-first results with ΔE and undertone are provided; we are researching richer verbal shade descriptions |
| No formal third-party audit yet | Conformance claims are based on internal testing only | Independent audit planned; we will publish the report |
| Console data tables | Complex tables can be laborious with a screen reader | Improved table semantics and export alternatives in progress |
How we test
A contrast and structure audit runs against every build of this site, and a failure blocks the build rather than filing a ticket for later. Automated tools only ever catch a fraction of real barriers, though, so we also go through by keyboard alone, at 200% and 400% zoom, and with reduced-motion and forced-colours turned on. We are a small team and we would rather tell you what our tooling actually covers than imply a testing lab we do not have.
Report a barrier
If something on this site or in our product is difficult or impossible for you to use, please tell us. You do not need to know why it is broken or use any particular terminology — describing what you were trying to do is enough.
- Email support@exacthue.com with “Accessibility” in the subject line.
- Tell us the page, what you were trying to do, and what happened.
- If you can, mention your browser and any assistive technology — helpful, but not required.
We acknowledge accessibility reports within two business days and will tell you our plan and timeline for a fix. If you need information from this site in an alternative format, ask and we will provide it.
Formal statement
This statement applies to exacthue.com and was last reviewed on 12 August 2026. It was prepared by ExactHue Pte. Ltd. on the basis of internal evaluation against WCAG 2.2 Level AA. We describe the site as partially conformant: it meets the majority of Level AA success criteria, with the exceptions listed under known limitations above.
ExactHue Pte. Ltd. · 352 Yishun Ring Road, Singapore 760352