SquishPixel Blog · Accessibility · Front-end · SEO

WCAG 2.2 enters the new EN 301 549 standard, but it is not yet legally in force

According to DEV Community, where a developer who works on public administration sites wrote about it, ETSI published EN 301 549 v4.1.1 on 2 September 2026. This is the European accessibility standard that both public sector rules and the European Accessibility Act point to. Its main change is a move from WCAG 2.1 to WCAG 2.2, the web accessibility guidelines.

The author stresses that publication is not the same as being in force. The new version gives a presumption of conformity only once the European Commission cites it in the Official Journal of the EU. As of 19 November 2026 that had not happened, and estimates range from late November to mid-December. Until then, the binding reference in Italy stays WCAG 2.1 level AA, through EN 301 549 v3.2.1. After the citation, the Italian agency AgID will need to update its guidelines and checklists.

WCAG 2.2 adds six criteria. The author lists them with common failures: focus hidden under sticky headers or cookie banners (2.4.11), upload that works only by drag and drop (2.5.7), tap targets smaller than 24 × 24 px (2.5.8), help links in inconsistent places (3.2.6), asking for the same data twice in one process (3.3.7), and logins that block pasting into password fields or split one-time codes across boxes (3.3.8). Criterion 4.1.1 Parsing is removed, though duplicate IDs still cause problems.

The author also highlights a new requirement on user preferences, clause 9.7, which now applies to the web. Pages should not override settings users have chosen in their system or browser, such as text size, zoom, high contrast and dark mode. This is not part of WCAG, and the author says the axe scanner does not check it. Common errors include fixed pixel font sizes, zoom blocked in the viewport tag, icons drawn as background images that vanish in Windows high contrast, and custom focus styles that disappear in forced colours mode.

Why it matters

Automated scans cover only part of the picture. The author tested their own town's site, which was built well and had only one scanner finding. Narrowing the window to 320 px, equal to 400% zoom, revealed horizontal scrolling caused by fixed-width columns. A clean report, in the author's words, is not the same as an accessible site, and the new standard widens that gap.

If you build for public bodies, banks, e-commerce or transport, the changes are worth planning for before they become mandatory. The author says most of the new criteria are cheap to fix now and costlier to retrofit later. The preference checks also need no special tools.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.