What works, what does not, and how to tell us we are wrong.
Required of a consumer service sold in the EU, and worth writing honestly rather than as a badge.
1What we hold ourselves to
The target is WCAG 2.2 level AA, which is the level the European standard EN 301 549 points at and therefore the level the European Accessibility Act expects of a consumer service sold in the EU. The Act has been enforceable since June 2025.
We say target rather than certified on purpose. Below is what is done, what is not, and how to tell us we are wrong.
2What works today
Tested by keyboard and with a screen reader on every page of this service:
- Everything is reachable by keyboard. Tab moves in the order things appear, Enter and Space activate, Escape closes. No trap, no mouse-only control.
- Focus is always visible — a two-pixel ring in the brand colour, on every control including form fields, which is where it is usually dropped.
- Touch targets are at least 44 by 44 pixels on touch devices, which is WCAG 2.2's new criterion and the one most sites fail.
- Every page has one h1 and headings that descend without skipping.
- Form fields have real labels, and errors say what to fix in words rather than turning a border red.
- Nothing is announced by colour alone. A sold-out size is struck through as well as greyed, a failed field is named as well as outlined.
- Motion respects
prefers-reduced-motion, and there is no animation that moves on its own for longer than five seconds. - Text reflows to 320 pixels without a horizontal scrollbar, and survives being zoomed to 200%.
- Contrast meets 4.5:1 for body text and 3:1 for interface edges. There is a
higher-contrast palette for
prefers-contrast: more.
3What is not done
An accessibility statement that claims everything works is a statement nobody checked. Ours:
- The preview tiles are decorative gradients with no textual equivalent, because there is nothing to describe. A real frame in a live service would carry a description written by the person who ordered it — that field does not exist yet.
- Long documents like this one have no in-page search of their own; you are relying on the browser's.
- The interface is in English only. Thai is planned, and a service sold in Thailand being English-only is a real barrier, not a nice-to-have.
None of these has a date attached, and pretending otherwise would be worse than saying so.
4How it was tested
By keyboard alone, start to finish, on every page. With the browser zoomed to 200% and at a 320-pixel width. With a screen reader on the flows that matter — registration, the brief, the account area. With automated checks for contrast, labels, heading order and target size on every build.
Automated checks catch perhaps a third of what is wrong. The rest is somebody using the thing without a mouse, which is why the list above is short and specific rather than a badge.
5Telling us it is broken
If something here blocks you, write and say what you were trying to do and what got in the way. That report is worth more than another audit, and it gets an answer from a person within two working days.
If the answer does not satisfy you, every EU member state has an enforcement body for this, and you are entitled to go to it without our permission.
