Accessibility is the baseline now
Since June 2025, accessibility has been the law for shops, banks and apps across Europe. A year in, the gap between compliant and good is where the work is. Four rules from WCAG 2.2 that change how interfaces feel, with demos.
On this page
In my projects, accessibility is the area with the most surprises. Most teams do care, they just test it with a plugin and a green score. Then a real person with a tremor misses a 20-pixel icon, a keyboard user loses the focus under a sticky footer, and the checkout asks for the same address twice.
Since 28 June 2025 the European Accessibility Act applies to e-commerce, banking, transport, e-books and more. The first year taught most teams the same lesson: compliance is a floor, not a result. And the newest criteria in WCAG 2.2 are design decisions you can see on the screen. These are the four I check first.
Twenty-four pixels
The newest rule is also the simplest: every pointer target is at least 24 by 24 CSS pixels, or has enough space around it that neighbours do not overlap. That is the legal minimum. Comfortable is bigger: Apple asks for 44 points on iPhone and iPad. In practice, it is the icons that fail: a 16-pixel close cross, a tiny checkbox, three actions crammed into one table row.
The fix costs nothing. Padding counts toward the target, so an icon can stay small while its hit area grows. And the people who benefit are not only those with motor impairments. Everyone on a train, everyone holding a coffee, everyone over fifty.
44 px targets, 8 px apart
20 px targets, touching
The focus stays visible
Keyboard users navigate by focus. If you cannot see where it is, you are lost. WCAG 2.2 adds two rules: the focused element may not be hidden behind sticky headers, cookie banners or chat bubbles, and the indicator itself has to be visible. Removing the outline because it looks ugly is still the most common accessibility bug I find, and it has been for ten years.
Design the focus ring like any other state: two pixels, a small offset, a colour that contrasts with the element and the background. Then press Tab through the page once and watch whether anything covers it.
Visible ring, scrolls clear of the footer
No ring, focus ends up under the footer
Never ask twice
Information a person has already given in a process must be filled in automatically or be selectable, not typed again. The billing address after the shipping address, the email after the account step, the name in step four. It sounds trivial. In the checkouts I see, it is the single most common source of typos, and typos become failed orders.
Pre-fill, offer “same as above”, remember the state when someone goes back a step. The browser helps too: with the right autocomplete attributes, address and card fields fill with one tap.
Same as shipping, one tick
Please re-enter your address for billing.
Typed again, with new typos
A login is not a test
The last new rule says that signing in may not require a cognitive test: no password that has to be remembered without help, no code retyped from an image, no “select all traffic lights”. A password manager, pasting, a code sent by email or a passkey all count as help. In practice this is the rule that moves products fastest towards passkeys.
And passkeys are no longer a niche. In the latest industry index, passkey sign-ins succeed 93 percent of the time against 78 percent for passwords with a second factor, and they are about three times faster. Accessibility and conversion point in the same direction, as they usually do.
Passkey or a code by email
Password rules, no paste, a puzzle
What the first year showed
Twelve months into the Accessibility Act, three things stand out from my projects. Most sites pass the automated check and fail the keyboard. Most accessibility overlays add problems instead of removing them. And the sites that score best did not run a project. They changed their defaults: a component library with focus states, target sizes and labels built in, so nobody has to remember.
That is why accessibility is not a separate phase in my projects. It is part of every decision, next to usability, performance and content. These points are simply normal before anything ships:
- Targets at least 24 pixels, better 44, with space between them.
- Focus visible on everything, never hidden under sticky elements.
- Nothing asked twice within one flow.
- Sign-in works with a passkey or a code, never with a puzzle.
- Tested with the keyboard and a screen reader, not only with a plugin.
An accessible interface is simply the normal one, done carefully.
Sources
- W3C: What’s New in WCAG 2.2
- European Commission: European Accessibility Act
- Apple Human Interface Guidelines: Accessibility
- FIDO Alliance: Passkey Index 2026 (October 2026)