Business website owners serving customers in Europe should review their accessibility practices against EN 301 549 v4.1.1, which aligns the standard with WCAG 2.2. The update adds clearer expectations for keyboard focus, touch controls, dragging actions, and display preferences.
Businesses in the United States, the United Kingdom, Australia, and Canada can also benefit from the review. Better accessibility helps more people use forms, menus, shopping tools, account areas, and other important website features.
What EN 301 549 v4.1.1 changes
EN 301 549 is an accessibility standard for information and communication technology. Its fourth version, v4.1.1, was formally delivered to the European Commission and updates the web guidance from WCAG 2.1 to WCAG 2.2.
The change includes six new WCAG 2.2 Level AA success criteria. Several directly affect common website design choices, especially navigation, touch controls, and interactive components.
Focus should not disappear
The Focus Not Obscured criterion addresses keyboard users who move through a page with a visible focus indicator. Sticky headers, cookie notices, chat controls, pop-ups, and other overlays should not completely hide the item receiving focus.
A visitor should be able to see which link, button, field, or control is active. Website teams should test keyboard movement while fixed elements remain visible at the top, bottom, or sides of the screen.
Dragging needs another control
The Dragging Movements criterion covers features that require a path-based drag gesture. Examples can include sliders, sortable lists, calendars, maps, and upload areas that depend on dragging.
These features should also support a simpler single-pointer action. A click, tap, button, or keyboard method can give visitors another way to complete the same task.
Touch targets need enough space
The Target Size criterion sets a minimum target size of 24 by 24 CSS pixels, or requires enough spacing when a control is smaller. This applies to many links, buttons, icons, and other touch controls.
Small controls placed close together can cause mistakes on phones and tablets. Designers should inspect menus, close buttons, pagination links, form controls, and icon-only actions at normal mobile screen sizes.
Other areas worth reviewing
The update also addresses accessibility beyond the most visible interface controls. It removes the obsolete Parsing criterion and adds clearer connections between technical requirements and European accessibility obligations.
It also expands attention to user preferences, including browser zoom, system font scaling, dark mode, and high-contrast settings. A website should remain usable when visitors change these settings.
Check zoom and text size
Test important pages at increased browser zoom and with larger system text. Content should remain readable without overlapping, disappearing, or forcing visitors to scroll in two directions.
Pay particular attention to navigation bars, pricing sections, comparison tables, forms, and checkout or inquiry steps. These areas often contain fixed widths or tightly packed controls.
Respect color and contrast preferences
Review how the site behaves when a visitor uses dark mode or high-contrast settings. Decorative colors can change, but text, borders, icons, and controls must still communicate their purpose.
Do not rely on color alone to show errors, required fields, selected items, or status changes. Add clear text, labels, shapes, or other visible information.
A practical website review
A complete accessibility review does not need to begin with every page. Start with the pages that support business goals and contain the most interaction.
- List the homepage, main service pages, contact forms, account areas, purchase steps, booking tools, and customer support pages.
- Use only a keyboard to move through each page and confirm that focus remains visible.
- Check fixed headers, banners, dialogs, and notices to ensure they do not cover the active control.
- Test every dragging feature and confirm that a simpler alternative performs the same action.
- Inspect touch controls on a phone-sized screen and look for targets that are too small or too close together.
- Increase browser zoom and system text size, then check for clipping, overlap, and horizontal scrolling.
- Test dark mode and high-contrast settings where supported by the operating system or browser.
- Record each issue with the page address, affected control, user impact, and recommended correction.
Do not treat accessibility as a one-time project
Website changes can introduce new barriers. A redesigned header can cover keyboard focus, a new form can weaken error messages, and a mobile update can place controls too close together.
Include accessibility checks in design reviews, content updates, quality assurance, and release testing. Keep a short issue log so the team can confirm which problems were fixed and which need further work.
Automated scanning can help find missing labels, contrast problems, and some structural issues. It cannot fully test keyboard operation, understandable instructions, focus behavior, or whether a task remains practical for real users.
What the update means for legal planning
Publication of EN 301 549 v4.1.1 does not by itself answer every legal question. The legally recognized baseline for presumption of conformity remains connected to the version formally cited in the Official Journal of the European Union.
Businesses should therefore separate two tasks. First, confirm which rules apply to the organization, service, and target customers. Second, improve the website using current accessibility practices rather than waiting for a formal deadline.
For businesses serving customers across several countries, a consistent accessibility standard can simplify design and testing. It can also reduce the risk that a basic website interaction works for one group of visitors but fails for another.
What to do next
Ask the person responsible for the website to review the highest-value pages against WCAG 2.2 Level AA practices. Begin with keyboard focus, dragging alternatives, touch target spacing, zoom, text size, and display preferences.
Then test the complete path a customer follows, from the first page through the final form, request, account action, or purchase step. Accessibility is strongest when visitors can complete the entire task, not merely open the page.
Sources
- Beyond compliance to readiness: What EN 301 549 v4.1.1 means for your accessibility strategy
- seroundtable.com
- gov.uk
- roirevolution.com
- nist.gov
- fortunelords.com
Want a second pair of eyes on this for your own site? Contact us or schedule a call.
Tags
Frequently Asked Questions
What changed in EN 301 549 v4.1.1?
The update aligns the standard with WCAG 2.2 and adds accessibility expectations for focus visibility, dragging alternatives, touch target size, and user display preferences.
Does the update immediately change the legal baseline?
Not necessarily. The legally recognized presumption of conformity remains tied to the version formally cited in the Official Journal of the European Union.
Should businesses outside Europe review their websites?
Yes. Reviewing WCAG 2.2 practices can improve keyboard access, touch usability, readability, and access for customers using different devices or settings.
Enjoyed this article?
Share it with your network
