Accessibility statement
We target WCAG 2.1 Level AA, which is the standard EN 301 549 references and therefore the one the European Accessibility Act is measured against. This page says what we do, what we have verified, and what we know is still imperfect.
- Target
- WCAG 2.1 Level AA
- Standard
- EN 301 549
- Measured by
- European Accessibility Act
- Independent audit
- Not yet held
Keyboard, everywhere
Every interactive element is reachable and operable by keyboard alone, with a visible focus ring. The enquiry form, the navigation drawer and the whole checkout path are completable without a mouse.
Motion is honored, not degraded
If your system asks for reduced motion, animation stops rather than slowing down. Nothing on this site conveys meaning through movement alone, so nothing is lost by turning it off.
Readable without JavaScript
Every page renders its full content from the server. No section is hidden behind an animation that a script failure would leave invisible. If our JavaScript fails, you get a plain, complete page.
Contrast measured, not assumed
Text contrast is checked against the actually rendered colors, including where a panel sits on a gradient, rather than against the token values in isolation.
One accessible path, not two
There is no separate simplified version of this site. Everyone uses the same pages, the same forms and the same confirmations.
Errors that announce themselves
Form errors are announced to screen readers, tied to their field, and focus moves to a summary so you are never left guessing what went wrong.
Measured on the rendered page, not reviewed in the code
Accessibility problems are mostly invisible in source. Ours are caught by rendering each page and querying the DOM.
- Horizontal overflow checked at twelve viewport widths from 280px upward, because a page that scrolls sideways is unusable at magnification.
- Every form control checked for an associated label, and every aria-describedby checked for a target that exists.
- Heading order checked for skipped levels, since screen reader users navigate by heading.
- Contrast sampled from composited backgrounds on the live page.
- Reduced-motion emulated and the page re-checked with animation off.
- Every page fetched with JavaScript disabled and asserted to still carry its full text.
What is not yet done
We would rather list these than claim a conformance level we have not independently verified.
- This site has not been audited by an independent accessibility specialist. Our checks are our own, automated and manual.
- We have not tested with every assistive technology. Coverage so far is keyboard, and screen reader behavior inferred from the accessibility tree rather than confirmed in JAWS, NVDA and VoiceOver.
- No formal VPAT or EN 301 549 conformance report exists yet. If your procurement requires one, tell us and we will say honestly where we are rather than produce one to order.
- Scroll-linked animation is used on some pages. It is disabled under reduced-motion, but we have not user-tested it with people who have vestibular conditions.
Tell us when we get it wrong
If any part of this site is difficult or impossible for you to use, email us and describe what happened, what you were trying to do, and what you use to browse. We will reply within one business day and tell you plainly whether and when we can fix it.
If you are in the EU and are not satisfied with our response, you may escalate to the market surveillance authority in your member state. The European Accessibility Act has applied to service transactions with EU consumers since 28 June 2025, regardless of where the provider is established.
Accessibility, answered directly.
Every answer here is the same string this page puts in its structured data, so a person and an answer engine read the identical text. Open one to read it.
What accessibility standard does MetaMinds target?
WCAG 2.1 Level AA. That is the level EN 301 549 references, which makes it the standard the European Accessibility Act is measured against, and it is the level named rather than a vaguer commitment to being accessible. It is a target that the site is built and tested to, and it is stated separately from the question of whether conformance has been independently verified, because those are two different claims.
What accessibility evidence can MetaMinds provide for procurement?
The checks this site runs on itself, which are automated and manual and run on every deploy: WCAG 2.2 AA contrast measured against the rendered tokens, keyboard-only traversal of every route, a JavaScript-off pass, a reduced-motion pass, and a 24 by 24 target-size sweep. Where your procurement needs a formal VPAT or an EN 301 549 report, ask and you will get a straight answer the same day about scope and timing.
How is accessibility actually verified on this site?
By rendering each page and querying the DOM, not by reviewing source, because most accessibility problems are invisible in code. Horizontal overflow is checked at twelve viewport widths from 280px upward. Every form control is checked for an associated label and every aria-describedby for a target that exists. Heading order is checked for skipped levels. Contrast is sampled from composited backgrounds on the live page rather than from token values in isolation. Reduced motion is emulated and the page re-checked with animation off. And every page is fetched with JavaScript disabled and asserted to still carry its full text.
Which assistive technologies has this site been tested with?
Keyboard operation is tested directly: every interactive element is reachable and operable by keyboard alone with a visible focus ring, including the enquiry form and the navigation drawer. Screen reader behaviour is inferred from the accessibility tree rather than confirmed in JAWS, NVDA or VoiceOver, and that gap is stated rather than left for a reader to discover. Scroll-linked animation is disabled under reduced motion but has not been user-tested with people who have vestibular conditions.
Is there a separate accessible version of the site?
No, deliberately. There is one set of pages, one set of forms and one set of confirmations, and everyone uses them. A separate simplified version would not satisfy the European Accessibility Act in any case, and in practice a second version is the one that stops being maintained.
Does the European Accessibility Act apply to MetaMinds?
The European Accessibility Act has applied to service transactions with EU consumers since 28 June 2025, regardless of where the provider is established. MetaMinds currently fits the microenterprise exemption, which does not stop a buyer asking for a conformance report and evaporates with growth. A reader in the EU who is not satisfied with MetaMinds' response to an accessibility problem may escalate to the market surveillance authority in their own member state.