Accessibility
Accessibility statement
Wexlo sells verifiable accessibility information. That is why this page should honestly state what is not yet right on this site itself.
What we focus on.
This website is designed and built with WCAG 2.1 level AA as the normative minimum, with relevant improvements from WCAG 2.2 where practical, such as consistent focus appearance and minimum target sizes. We test with automated scans, keyboard, screen readers, 200% text zoom and 320px reflow, in light and dark theme.
We only make a claim of full conformity after appropriate automated and manual assessment. That is the same standard we hold our clients to.
Scope.
This statement covers the website https://wexlo.eu, including the Dutch-language section at /nl, the French-language section at /fr, the German-language section at /de, the free scanner, the checkout on our own site and the customer portal. It does not cover the websites of third parties we link to, or the customer websites our scan reports describe.
The checkout is covered up to and including the order form on this site. When you select “Continue to payment”, you are taken to the hosted payment page of our payment provider Mollie, on their own domain. That page is not ours and we cannot change it, so it falls outside this statement. What we measured on that page is listed below under Known limitations.
The invoice you receive after an order is a PDF document and not a page on this site. It is produced in our accounting system, a service from an external supplier, so we cannot change the file. It falls outside this statement for the same reason the payment page does. What we measured in it is listed below under Known limitations.
Conformance status.
This website is partially conformant with WCAG 2.1 level AA. “Partially conformant” means that some parts of the content may not yet fully conform. Automated checks can only cover part of the WCAG 2.1 AA success criteria. Our own scanner tests 31 of the 55 WCAG 2.2 AA success criteria automatically, in full or in part, and only 2 of them fully. Most criteria require human evaluation, and a full manual audit of this site has not yet been completed, so issues outside the reach of automated testing may exist. We say the same about our customers’ scans, and we hold ourselves to it too.
Every page is scanned before every release with axe-core against WCAG 2.1 A and AA, on desktop and mobile viewports, with zero known violations as our release baseline, complemented by manual checks on keyboard navigation and colour contrast. What we have not measured yet is listed below under Known limitations.
Known limitations.
Manual assessment of this site
- What you may notice
- The full manual assessment of this site has not been completed. What is missing: the criteria that need human judgement have not yet been walked across the whole site, including a screen reader pass, 200% zoom and the reduced-motion preference. Cause: we built the automated layer first and planned that round after it. Consequence: outside the reach of automated testing there may be barriers we have not seen, and about our own site we cannot claim otherwise.
- What you can do now
- Alternative: if you run into something, tell us at the address below; we respond within 5 business days and will find a way to get you what you came for.
- What we are improving
- Measure: complete the manual assessment and record the outcome here, by 31 October 2026 at the latest.
Mollie payment page
- What you may notice
- Part of the checkout runs on the hosted payment page of our payment provider Mollie, on their own domain. We cannot change that page. In our own measurement of 7 September 2026 it did not meet WCAG 2.1 level AA on three points: four images without alternative text (1.1.1), an interactive element nested inside the Apple Pay button (4.1.2), and no visible keyboard focus on the four payment method buttons (2.4.7). In our previous measurement of 6 August 2026 there were five, with eleven images without alternative text; the language selector has since been given an accessible name and the page allows zooming again.
- What you can do now
- If this leaves you stuck at payment, tell us at the address below.
- What we are improving
- We reported this to Mollie, and we re-measure the page periodically with a script of our own.
- Next review
- We will review this entry by 6 November 2026 at the latest.
Invoice (PDF)
- What you may notice
- The invoice you receive after an order is produced in our accounting system, a service from an external supplier. We cannot change that file: we only receive a temporary download link to the PDF that system generates. In our own measurement of 27 August 2026 that PDF was not tagged. Against EN 301 549 chapter 10 that means: no programmatically determinable structure, so no headings and no table relationships in the invoice lines (10.1.3.1); no language declaration, so a screen reader can fall back on the wrong pronunciation (10.3.1.1); no text alternative for the logo (10.1.1.1); and a document title fixed to “Invoice”, including on invoices in other languages (10.2.4.2). The text itself can be read out, but because the file is not tagged, no reading order is recorded in it. In our measurement the underlying order does not follow the visual layout: the footer with our registration numbers comes first, and the recipient address only fourth, after the sender address. What a reader actually hears therefore depends on how their PDF viewer reconstructs the page.
- What you can do now
- If you need the invoice details in another form, tell us at the address below and we will send them as accessible text.
- What we are improving
- We reported this to the supplier on 14 August 2026. On 26 August 2026 they told us that the digital accessibility of their documents has their attention, that no specific change is on their plan yet, and that they expect to improve this but not in the short term. This limitation stands for as long as that is the case.
- Next review
- We will review this entry by 14 October 2026 at the latest.
Scan reports for customers
Scan reports we deliver to customers describe third-party websites we do not control; the accessibility of those websites is the subject of the report, not covered by this statement.
Feedback and contact.
Found a barrier on this site? Tell us. That is exactly the kind of finding we exist for: hello@wexlo.eu. Describe the page and the problem, and which browser or assistive technology you are using, if you know it. We aim to respond within 5 business days and to fix confirmed barriers in the next release.
Enforcement.
If you are not satisfied with our response, you can turn to the Dutch market surveillance authority for the European Accessibility Act. For digital services like ours that is the Autoriteit Consument & Markt (ACM, acm.nl); the Rijksdienst voor Ondernemend Nederland (RVO) provides general EAA guidance for businesses. If you are in another EU country, you can also contact the authority in your own country.
Version of this statement.
This statement was first drawn up on 5 July 2026 and last revised on 9 September 2026. The coverage figure above comes from the criterion map of our own scanner.