Accessibility Statement
Version 1.0 · 4 October 2026 · reviewed on every release
We sell accessibility auditing. The first place anyone should check is our own front door. So we scan this site with the same tool we sell, and we publish the result — including anything that does not pass.
1 · Standard we hold ourselves to
This site aims at WCAG 2.2 Level AA, the standard adopted by EN 301 549 and relied on by the European Accessibility Act (Directive (EU) 2019/882).
Conformance status: we believe this site fully conforms to WCAG 2.2 Level AA. "Fully conforms" means we have found no failure against the success criteria we can test. It does not mean no barrier exists — see section 4.
2 · What we measured, and what came out
Every page below was scanned with TOLMENA's own engine: the automated rule set plus four stress tests — text enlarged to 200%, text spacing increased, viewport narrowed to 320 px, and every string lengthened by about a third to simulate translation.
| Page | Rule failures | Overflow | Horizontal scroll |
|---|---|---|---|
| Home | 0 | 0 | 0 px |
| Privacy Notice | 0 | 0 | 0 px |
| Terms of Use | 0 | 0 | 0 px |
| Imprint | 0 | 0 | 0 px |
Two failures we found on ourselves, and fixed
These are published because hiding them would make every other number on this page worthless.
- An
aria-labelon adivwith no role. Screen readers were not required to announce it, so a group of payment marks had no accessible name. Fixed by giving the group a role. - Path labels at 7.5 px with 3.81:1 contrast. Below the 4.5:1 minimum, and below the 12 px floor this site claims for itself. Raised to 11 px and 5.58:1.
3 · What we did to get here
- Every interactive control is reachable and operable by keyboard, with a visible focus ring.
- A skip link is the first thing in the tab order on every page.
- Touch targets are at least 44 px; no control relies on a 23 px hit area.
- Text is sized in
rem, so the browser's own text-size setting works. - Layout reflows to 320 px without a horizontal scrollbar; wide tables become cards.
- Scan progress is announced through a live region, not colour alone.
- Motion respects
prefers-reduced-motion; the animated globe can also be stopped with a visible button. - Page language is set correctly for each of the 35 languages, and changes with the switcher.
- Fonts are served from our own domain — no third-party request is made on your behalf.
4 · What we know we cannot promise
Automated testing reaches a minority of the success criteria. We also check by hand, but no audit is complete. If you hit a barrier, that is a defect on our side, not a failure on yours.
- We have not completed a formal audit by an external body.
- We have not tested with every combination of assistive technology, browser and operating system. Our own testing uses keyboard navigation, browser zoom to 400%, forced text spacing, and VoiceOver.
- Reports we generate are HTML documents built from your site's data; their content reflects what we found on your pages and we cannot guarantee that material we quote from your site is itself accessible.
5 · Tell us when we get it wrong
Write to info@tolmena.com. Please tell us the page, what you were trying to do, what happened, and what you were using — browser, operating system, and any assistive technology.
We answer within 5 working days and tell you either the fix and when it lands, or why we cannot fix it and what we will do instead. If our answer does not satisfy you, you may contact the enforcement body in your country; the Imprint names who operates this service and from where.
6 · How this statement was prepared
Self-assessment, carried out by the operator on 4 October 2026, using TOLMENA's own scanning engine (rule set v1.4) together with manual keyboard and screen-reader testing. It is reviewed on every release of this site.