WCAG 2.2 vs 2.1: what changes in the new version
WCAG 2.2 vs 2.1: 9 new criteria (focus, target size, forms, login) and Parsing removed. Check what to change on your site and how to verify it.
WCAG 2.2 mainly changes how the interface is operated: focus visibility, the size of clickable elements, dragging, forms and login. It is an update to the WCAG 2.1 guidelines. If the site was properly prepared for the previous version, you are starting from a good place.
How WCAG 2.2 differs from 2.1 (in short)
WCAG 2.2 adds 9 new success criteria and removes criterion 4.1.1 Parsing. W3C describes the full list of changes in “What’s New in WCAG 2.2”. The foundation stays the same: levels A, AA and AAA do not change, and for most businesses and online stores the practical target is still level AA.
Put simply: if you know WCAG 2.1, you are not starting from zero. If you are only getting into the subject, start with my guide to web accessibility (WCAG). WCAG 2.2 builds on the previous version and spells out a few things that strongly affect everyday use of websites: keyboard focus, small buttons, dragging elements, login, forms and repeated data entry.
In practice the WCAG 2.1 vs 2.2 comparison comes down to one question: can your site be used comfortably when someone is not using it “perfectly”? Without a precise mouse, on a small screen, with a weaker memory or without being sure where the keyboard cursor currently is.
For the owner of a business or an online store this is good news. These changes are specific and can be checked on real parts of the site: in the basket, the checkout, the contact form, the login, the discount popup, the sticky header and the mobile menu. That is where problems show up most often.
New success criteria in WCAG 2.2
The new version adds 2 criteria at level A, 4 at level AA and 3 at level AAA. On a typical company website or store, most of the work usually concerns level AA: focus, dragging, the size of clickable elements and login.
Level A gains Consistent Help and Redundant Entry. The first concerns a consistent place for help, if such help appears in a process across several pages. The second limits situations in which the user has to enter the same data a second time within one process.
Level AA gains Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum) and Accessible Authentication (Minimum). It sounds technical, but the meaning is simple: the user should see where they are on the page, hit buttons without surgical precision, complete an action without dragging and log in without unnecessary puzzles.
Level AAA adds Focus Not Obscured (Enhanced), Focus Appearance and Accessible Authentication (Enhanced). That is a higher threshold. For most businesses the priority will be AA, but the AAA criteria are worth knowing too, because they show a good direction for design.
Visible focus: Focus Not Obscured and Focus Appearance
Focus is the highlight on the element where a user moving through the page with a keyboard currently is. If you press Tab and move through links, form fields and buttons, the page should clearly show where you are.
The new version watches this more closely. The Focus Not Obscured (Minimum) criterion requires that the focused element is not entirely hidden by content the site itself has added. The simplest example: a sticky header. The user tabs to a link, but the link hides under the menu bar. Formally something happens, in practice the person loses their bearings.
Popups, cookie banners, promotion bars, chats and side widgets cause a similar problem. They may be needed in themselves. The trouble starts when they cover a button, link or form field that has just received focus.
Focus Appearance at level AAA goes further and concerns the quality of the focus indicator itself. The outline should be visible, have adequate contrast and not disappear against the button. A thin, light grey frame on a white background is usually not enough. The user should not have to guess where they are.
The simplest test? Open the site, put the mouse aside and go through the main paths with the Tab key. Check the menu, the contact form, the search, the basket and the checkout. If at some point you do not know where you are, you have a specific lead for a fix.
Touch and mouse operation: Dragging Movements and Target Size
The 2.2 guidelines take a close look at operating a page with a pointer: a mouse, a finger on the screen or a stylus. Two new criteria are especially practical here: Dragging Movements and Target Size (Minimum).
Dragging Movements says that if an action requires dragging, it should have an alternative that can be done with a simpler movement. An example? Sorting items by drag and drop. For some people, dragging an item to a specific place is difficult or impossible. A good alternative is “up” and “down” buttons, choosing from a list or a plain click.
In an online store this can concern price sliders, photo galleries, product configurators or modules for setting an order. If the user has to hold, move and release in exactly one place, check whether the same result can be achieved more simply.
Target Size (Minimum) concerns the size of clickable elements. The guidelines set a minimum of 24 × 24 CSS pixels, with exceptions. Not every link in a text has to suddenly become a big button. But if you have small icons next to each other, miniature close buttons, carousel arrows or checkboxes set tightly in the checkout, the risk grows.
A small target is a real cost, and it shows most on a phone. The user wants to confirm the order and hits “remove”. They want to expand a product variant and click the neighbouring option. A detail like that can ruin a sale faster than an ugly header.
Easier forms: Consistent Help and Redundant Entry
Forms are one of the places where accessibility meets business very quickly. If a form is tiring, some people will simply abandon it. Quietly, without any message.
Consistent Help is about the consistency of help. If a help mechanism appears in a process, it should be placed in the same relative position on the following pages. It can be a contact link, a chat, a phone number, a help section or a support button. The user should not have to look for it again at every step.
In a store this makes sense in the checkout, for one. If help with delivery sits next to the address form, do not then hide it somewhere completely different at the payment step. If someone gets stuck, they should find a way out quickly.
Redundant Entry concerns entering the same data again within one process. If the user has already given their name, email, address or phone number, do not force them to type it a second time when the site can fill that data in or let them select it.
The simplest example is the delivery address and the billing address. If they are the same, a checkbox is enough. When booking an appointment, do not ask for the email again at the last step when the user gave it at the start. Every repetition raises the risk of an error and of frustration.
There are situations where entering data again makes sense, for example for security reasons. The new guidelines do not take away common sense. They only require that a form is not turned into an obstacle course for no reason.
Login without barriers: Accessible Authentication
Accessible Authentication concerns logging in and confirming identity. A site should not require cognitive tests from the user unless it gives them an accessible alternative or a support mechanism.
The problems tend to be retyping distorted characters from an image, memorising complicated codes, puzzles, blocking the pasting of a password or one-time code, and making life hard for password managers.
For an online store this is a very practical subject. The user wants to check an order, download an invoice, return to an abandoned basket or change their account details. If logging in is too demanding, some people will take a shortcut: a weak password, giving up the account or abandoning the purchase.
Good solutions are fairly simple. Allow passwords and codes to be pasted. Do not block autofill. Take care of sensible error messages. If you use CAPTCHA, choose a solution that has an accessible alternative. With codes sent by text message or email, give time and the option to send the code again.
The standard does not expect login to be trivial at the cost of security. The point is that security measures should not cut off people who use assistive technologies, have difficulty with memory or are simply on a phone in awkward conditions.
What was removed from WCAG 2.2: criterion 4.1.1 Parsing
Criterion 4.1.1 Parsing was removed from WCAG 2.2 because modern browsers and assistive technologies handle parsing differently from the time when the earlier guidelines were written. In an audit against the new version it is not reported as a separate criterion, but errors in the code can still cause real problems.
Parsing concerned, among other things, the correctness of HTML markup: closed tags, nesting, unique identifiers and duplicated attributes. Such errors used to break the way assistive technologies read a page more often. Today browsers handle many of these situations, and some of the problems are caught by other criteria.
This is not an invitation to messy code. If a button has the wrong attribute, a form has no correct label, or two elements have the same identifier and a script goes haywire, the user can still be in trouble. A problem like that can fall under other criteria, for example Name, Role, Value or Info and Relationships.
So in an audit the version of the standard has to be stated clearly. If you are checking conformance with version 2.2, 4.1.1 Parsing drops off the checklist as a separate item. If a contract, terms and conditions or a tender requirement refers to WCAG 2.1, the auditor can still include this criterion, because they are working to the older version.
Does WCAG 2.2 mean changes on your site
Most often WCAG 2.2 means targeted fixes in specific components. Rebuilding the whole site is rare. First check the places where the user types, clicks, selects, drags or confirms something.
On a company website these will usually be contact forms, booking forms, the menu, popups, chat, the cookie banner and elements stuck to the screen. In a store there are also the product page, variants, the basket, the checkout, payment, login and the customer panel.
If you have WooCommerce, pay attention to the small elements that are easy to miss: the small plus and minus buttons next to the product quantity, the icon for removing an item from the basket, the coupon link, the checkbox for accepting the terms and the error messages after a failed payment. These are the places where accessibility affects sales directly.
E-commerce, sites with user accounts and pages with longer forms will feel the new requirements especially quickly. There, every extra effort hurts more. If a customer has to enter data twice, cannot see the focus or cannot log in from a password manager, the problem blocks a specific action.
A good order of work? First the paths that matter to the business: a purchase, sending an enquiry, booking a slot, creating an account and downloading a resource. Only then the less used subpages and smaller views.
How to check conformance with WCAG 2.2
Start with an automated scan, then go through the most important paths with a keyboard and check the new criteria by hand. Write down where the problem is, a description, the impact on the user and the proposed fix.
An automated scan is a good start, because it quickly shows some of the errors: contrast, missing labels, problems with element names, heading structure or attributes. It will not catch everything, though. A tool cannot sensibly judge whether help is in a predictable place, whether the alternative to dragging really works, or whether the user sees the focus in a difficult layout.
The second step is a keyboard test. Go to the home page and tab to the most important places. Open the menu. Close the popup. Fill in the form. Add a product to the basket. Go through the checkout. Try to log in. At each step ask simply: do I know where I am, can I complete the action, is anything covering the active element?
The third step is a manual review of the new criteria. Check whether clickable elements have a sensible size and spacing. See whether dragging has an alternative. Go through the forms looking for repeated data entry. Check that the help mechanisms do not wander around the screen without logic. Test login with a password manager, with a pasted password and with a one-time code.
In your notes, do not write just “does not conform to WCAG”. That is not enough. A better note looks like this: “Checkout, delivery step: the focus on the postcode field hides under the sticky header. A keyboard user loses their bearings. Fix: add a scroll offset or change the sticky header’s behaviour on focus”. A description like that can be handed to a designer or developer without guessing.
An audit by a specialist makes sense when a site has many forms, a user account, payments, integrations with external systems, or is subject to formal accessibility requirements. It also makes sense after a larger redesign. An automated report is quick, but only manual tests show whether a user will really get through the process from start to finish.
The new version does not flip the table. It puts in order things that should work on good sites anyway: visible focus, comfortable clicks, sensible forms and login without unnecessary obstacles. For the user that means less frustration. For the business: fewer abandoned actions and fewer situations where the site gets in the way where it should help.
FAQ: WCAG 2.2 vs 2.1
Does WCAG 2.2 replace WCAG 2.1?
Formally WCAG 2.2 is the newer W3C recommendation, but a site that conforms to 2.2 also meets 2.1 (apart from the removed Parsing). In contracts and legal requirements, the version that is named is the one that counts. Check which one your document refers to.
How many new criteria does WCAG 2.2 have?
Nine: two at level A (Consistent Help, Redundant Entry), four at AA (Focus Not Obscured, Dragging Movements, Target Size, Accessible Authentication, all in the Minimum variant) and three at AAA.
Do I have to rebuild my site for WCAG 2.2?
Most often not. The changes usually mean targeted fixes in specific components: the sticky header, popups, the basket, the checkout and login. A rebuild only makes sense when the problems sit in the whole template.
Does criterion 4.1.1 Parsing still apply?
In an audit against WCAG 2.2, no, it has been removed. If a requirement refers to WCAG 2.1, the auditor can still include it. Correct code pays off anyway: the same errors can fall under other criteria.
Which conformance level should be the target?
For most businesses and online stores, level AA. That is the one that appears in project, tender and legal requirements. Treat AAA as a good direction for the future; it is usually not mandatory.