Accessibility Statement

Where we stand

We build this site to WCAG 2.2 level AA. We are not fully there yet, and this page says where the gaps are rather than claiming otherwise. A statement that asserts full conformance while known defects are open is worth nothing to the person who hits one.

What we test, and how

These are checked programmatically on every page before it ships, not assessed by eye:

• Contrast. Every text element is measured against its actual rendered background, including elements over gradients and mid-animation. The AA thresholds are 4.5:1 for body text and 3:1 for large text.
• Keyboard. Everything interactive can be reached and operated from a keyboard, and the focus indicator is visible against every background it appears on.
• Without JavaScript. Every page renders its content with scripting disabled. The assessments cannot score themselves without it, and say so plainly rather than showing a blank page.
• Reduced motion. Where a browser requests reduced motion, animation is switched off rather than merely shortened, and nothing depends on movement to be understood.
• Reflow. No horizontal scrolling from 320 px to 1920 px.
• Structure. One h1 per page, headings in order, landmarks present, and form controls with real labels.
• Not colour alone. Anything indicated by colour is also indicated by text, a shape or a label.

Known problems

Being specific is more useful than being reassuring. As of the date above:

• The main navigation opens on hover on some pages. A menu that only opens on hover is not operable by keyboard and is awkward on touch. It is being rebuilt to open on click and close on Escape.
• Some pages lack a skip link and a main landmark. Pages carried over from the previous site make a screen-reader user traverse the navigation on every page. The rebuilt pages have both.
• Older pages have not been retested. Anything not yet rebuilt may fall short of the criteria above.

If something does not work

Tell us and we will fix it. Email contact@dataproducts.io with “Accessibility” in the subject line, and if you can, include the page address, what you were trying to do, and what happened.

We aim to acknowledge within two working days. If something on the site is blocking you from reaching us, ask a colleague to send it on your behalf — we will not treat that as a problem.

If you need something on this site in another format, ask and we will provide it.

Technical notes

The site relies on HTML, CSS and JavaScript. Content is readable without JavaScript, though some interactive features — the assessments in particular — need it to function.

It is tested in current versions of Chrome, Firefox, Safari and Edge, with the assistive technologies those platforms provide.