Policy
Accessibility
The target is WCAG 2.2 Level AA. This page says what has been built to meet it, what is known not to, and what happens when you tell us about something that stops you reading a page.
What has been done
- It works without JavaScript. Every reference page is plain HTML and CSS. Scripts add convenience — a character counter, a filter — and their absence removes nothing you need to read.
- Structure carries meaning. Headings descend in order, tables use real header cells with scope, lists are lists, and landmarks mark the header, navigation, main content and footer. A screen reader can move by heading and reach any section.
- Keyboard first. Everything reachable by mouse is reachable by tab in a sensible order, focus is always visible, and a skip link is the first thing on every page.
- Contrast with room to spare. Body text sits well above the 4.5:1 minimum against the paper ground, and above 3:1 for large text and interface borders, in both the light and dark palettes.
- Text scales. Sizes are set in relative units, so browser zoom and an enlarged default font size reflow the page rather than clipping it. Nothing important is an image of text.
- Color is never the only signal. Status in the comparison tables is carried by words and rules, not by hue alone. The ground is a pale sage, but nothing is colored green to mean approved and nothing is red to mean failed — read the page in grayscale and it says exactly the same thing.
- Motion is restrained and optional. There is no autoplay, no parallax, no carousel, and transitions are suppressed for anyone whose system requests reduced motion.
- Both themes are honoured. The site follows your operating system’s light or dark setting, and the choice can be overridden per browser.
Where it falls short
Stating this plainly is more useful than a claim of full conformance:
- Wide comparison tables scroll sideways. On a narrow screen the standards matrix is wider than the viewport and sits in its own horizontal scroll area. It is keyboard scrollable and labelled, but it is not as comfortable as the rest of the site. Every figure in it also appears in prose on the relevant page.
- Some source documents are not accessible. Several regulations and standards are published as scanned or untagged PDFs by the bodies that issue them. We cannot fix those. Where one matters, the operative wording is quoted in HTML on the page so you do not have to open it.
- No formal audit has been carried out. The claims above rest on our own testing with keyboard navigation, browser zoom and automated checks, not on a third-party report. We will not describe the site as certified when it has not been.
Tell us what is broken
If something here stops you getting at the content, write to hello@ecoworldwide.com with the page and what happened. You will get an acknowledgement within two working days and an answer about a fix within ten. If a fix will take longer than that, we will say so and send you the content in a form you can use in the meantime — plain text, a tagged document, or read out in a call.
Reporting a barrier is not a complaint process you have to justify. One sentence is enough.
Questions about any of this go to hello@ecoworldwide.com, or through the contact form.