The standard we build to
This site targets WCAG 2.2 level AA. That is the level most public sector procurement and most large corporate accessibility policies reference, and it is the level we think a compliance product ought to meet without being asked.
The commitments below are not aspirations. They are checks that run against every page before it ships, and the section after them is honest about what has not been done.
What is verified on every page, every release
Text contrast
Every text and surface pairing used on the site has been measured. The lowest step permitted for body text is 5.1:1 on dark surfaces and 5.3:1 on light. Two tones that failed were removed from the palette rather than used carefully.
Keyboard operation
A skip link is first in the tab order. Navigation menus open on focus as well as hover, so they are reachable without a pointer. Every interactive control shows a 2px focus ring at a 3px offset.
Without JavaScript
Core content and navigation work with JavaScript unavailable. Motion pre-states are applied only once JavaScript has confirmed it can animate, so nothing is ever left invisible.
Reduced motion
With the operating system preference set, smooth scrolling and scroll-triggered animation are disabled entirely and final states render immediately — rather than animations simply running faster, which is the common and inadequate implementation.
Heading structure
One h1 per page and no skipped levels. Headings inside product illustrations are not headings, because those illustrations are images rather than document structure.
Images and illustrations
Every product illustration carries a written description of what it depicts, not a filename.
Forms
Every field has a visible label. Errors are tied to their input programmatically and described in words rather than by colour alone.
Small screens
Every page is checked at 360px with no horizontal overflow.
Known limitations
Stated rather than discovered. We would rather you knew before you hit them.
No formal third-party audit yet
The checks above are run by us. An independent audit has not been commissioned, and until it has we are not going to describe the site as certified or fully conformant.
Data tables scroll horizontally on small screens
The feature matrix and factor tables are wider than a phone. They scroll within their own container rather than reflowing, which is usable but not ideal.
Screen reader testing is not exhaustive
We test with keyboard navigation and automated checks. We have not carried out a full assistive technology test across every screen reader and browser combination.
The mega menu is a long tab sequence
Reaching the main content by keyboard means passing the navigation, which is why the skip link is first in the tab order. It works, but it is not the most elegant possible solution.
Reporting a barrier
If something on this site does not work for you, write to accessibility@emvert.com and tell us what you were trying to do, what happened, and what you were using. We will acknowledge within two working days and tell you what we can fix and when.
If the answer is that we cannot fix it quickly, we will say so and offer an alternative way to get what you needed — including a person who will simply do it for you.