Accessibility statement
How accessible myevra.com is, how we built and tested it, what we know is not right yet, and how to tell us about a problem.
Draft, to be reviewed by a solicitor before launch. Text in square brackets is a placeholder for details Evra has not confirmed yet.
Last updated:
The short version
- We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
- We built the site with accessibility in mind from the start, and checked it with automated tools and keyboard-only testing on 14 October 2026.
- It has not yet had a full audit by an accessibility specialist, or been tested by disabled people, so we do not yet claim that it fully meets the standard.
- If something does not work for you, please tell us. We will help you another way while we fix it.
About this statement
This statement covers the Evra website, myevra.com, run by [PLACEHOLDER: legal name of the business], trading as Evra.
We want everyone to be able to browse, compare and buy everyday essentials on Evra, however they use the web. That includes people who use a keyboard instead of a mouse, a screen reader, voice control, screen magnification or their device's display settings.
It does not cover brands' own websites, which our "Buy from brand" buttons take you to. Those websites are run by the brands.
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA. These guidelines are published by the World Wide Web Consortium (W3C) and are the most widely used standard for accessible websites.
We have not yet had the site fully audited against WCAG 2.2, so we do not claim that it fully meets it. What we have checked, and what we know is not right yet, is set out below.
How we built it
The site was designed and built with these in mind:
- Clear structure. Pages use proper headings, landmarks, lists, tables and buttons, so screen readers and other tools can describe them and help you move around.
- Keyboard access. Links, buttons, menus, drawers, filters and forms can be used with a keyboard alone, and whatever has focus shows a visible focus indicator. "Skip to main content" is the first link on every page. Menus and drawers close with the Escape key and take you back to where you were.
- Colour contrast. Every combination of text colour and background colour we use has been checked against the WCAG 2.2 AA contrast levels, in both the light and dark themes.
- Light and dark themes. The site follows your device's light or dark setting. You can change it with the dark mode switch in the header, or in the menu on phones.
- Reduced motion. If your device is set to reduce motion, menus and pop-up windows fade in instead of sliding, and page transitions are switched off. Motion on the site is short and calm in any case.
- Zoom and text size. You can zoom in up to 400% without scrolling sideways, and text follows your browser's text size setting.
- Not by colour alone. We never rely on colour alone to tell you something. Form errors, for example, are explained in words with an icon, and the Checked badge has a word and a tick.
- Forms. Every field has a label, and in forms with more than one field, each field says whether it is required or optional. If something needs correcting, we tell you in words next to the field, and screen readers announce when a form has been sent.
- Images. Photos on product pages have text descriptions. Where a photo only repeats the words next to it, as on product cards, or is decorative, it is hidden from screen readers, and so are icons.
- Without JavaScript. If JavaScript does not load, you can still read the shop, category and product pages, and send our contact, partner enquiry and email sign-up forms. Search results, filters and sorting, quick view, the basket and saved items need JavaScript.
Your device can help too. AbilityNet has advice on making your device easier to use if you have a disability.
Known limitations
We know about these limitations:
- Audit results. [PLACEHOLDER: results of the pre-launch accessibility audit. For each issue: what it is, who it affects, a workaround, and when we expect to fix it.]
- Not yet tested with assistive technology. We have not yet tested the site with screen readers (such as VoiceOver, NVDA, JAWS or TalkBack), voice control or screen magnifiers, or with disabled people. There may be problems we do not know about yet.
- Sample content. While we prepare to launch, the brands and products on the site are fictional samples. Their photos and descriptions only show how listings will look, and some photos are placeholders that say "Photo to follow".
- Checkout and accounts. Our checkout and customer accounts are not built yet, so they have not been tested. We will test them before they open, and update this statement.
- Brands' websites. "Buy from brand" buttons take you to websites we do not control. If you have trouble buying on a brand's website, please contact the brand, and tell us as well.
How we tested this website
We last tested the site on 14 October 2026, while it was being redesigned and before launch. We:
- checked every page with axe-core, an automated accessibility testing tool, in both the light and dark themes, at phone and desktop widths (320, 390 and 1440 pixels wide). It reported no failures;
- checked that no page needs scrolling sideways at those widths;
- checked every text and background colour pair against the WCAG 2.2 AA contrast ratios, in both themes;
- used the site with a keyboard only for the main tasks: choosing cookie settings, opening the shop menu and the menu on phones, searching, filtering and sorting products, saving a product, adding it to the basket, switching the theme and sending the contact form.
Automated tools can only find some kinds of problem, so these checks are a starting point, not proof that the site is accessible. [PLACEHOLDER: re-run these checks on the finished site just before launch, and update the date].
Still to do: [PLACEHOLDER: a full audit against WCAG 2.2 AA by an accessibility specialist, with who will do it and when], and testing with disabled people, including people who use screen readers, voice control and screen magnification.
Report a problem or ask for help
If you find a problem on our website, or you cannot use part of it, please tell us:
- use our contact form and choose "An accessibility problem";
- or email [PLACEHOLDER: contact email].
It helps us if you tell us the address of the page, what you were trying to do and what happened. If you can, tell us which device and browser you use, and any assistive technology, such as a screen reader.
If you need information from the site in another format, such as plain text by email, please ask. [PLACEHOLDER: the other formats Evra can provide, if any]. We will do our best to help, for example by answering your question or giving you product information by email.
What happens next
- We reply. We aim to reply within [PLACEHOLDER: number of working days] working days.
- We help you another way if you cannot do something on the site while we look into it.
- We tell you what we will do about the problem and, if we can fix it, roughly when. [PLACEHOLDER: target time to fix reported problems].
If you are not happy with our response, you can make a complaint.
Your rights
In England, Scotland and Wales, the Equality Act 2010 says that businesses providing services, including online shops, must not discriminate against disabled people, and must make reasonable adjustments. That includes thinking ahead about what disabled customers may need, not only responding when a problem is reported. In Northern Ireland, the Disability Discrimination Act 1995 applies.
The accessibility regulations for public sector websites do not apply to Evra, so this statement is voluntary. We have followed the same approach because we think it is the right thing to do.
If you are not happy with how we deal with a problem you report, please use our complaints process. If you are still not satisfied, you can get free advice from the Equality Advisory and Support Service (EASS) in England, Scotland and Wales, or the Equality Commission for Northern Ireland.
Preparation of this statement
This statement was prepared on 14 October 2026, and last reviewed on 14 October 2026. It is based on the testing described above.
We will review it [PLACEHOLDER: when, for example after the pre-launch audit and then at least once a year], and whenever we make a significant change to the website, such as opening our checkout.