WCAG 2.2 and new success criteria

Success Criterion 2.4.11 Focus Not Obscured (Minimum) says that the element in focus must never be entirely hidden behind another element.

For users who rely on a keyboard or similar assistive technology for navigating the digital environment, it is important that they always see which element they are on. If there is a cookie message at the bottom of the screen, a sticky header at the top, or a chat window popping open in the corner, the focus element may sometimes be hidden underneath.

Moreover, in order to move onto the cookie message or chat window and close it, keyboard user usually has to move to the end of the page, since floating elements are usually last in the code. Going a little off-topic, I would suggest placing the cookie message and chat window in the beginning of the code.

Not all people can use a mouse to drag things from one place to another.

Success Criterion 2.5.7 Dragging Movements says that there must be an alternative for dragging (moving, reordering, grouping, etc.) elements which can be done simply by clicking. This applies for touch screens as well as dragging with a mouse.

For example, it must be possible to move the map in different directions not only by dragging your finger, but also by using arrow buttons; it must be possible to move tasks from one column to another through a context menu in addition to dragging them, etc.

Clickable elements must be large enough or far enough from each other to be clicked comfortably.

Success Criterion 2.5.8 Target Size (Minimum) says that the size of a clickable area must be at least 24 x 24 pixels. If there is enough free space between the clickable areas, the clickable area may also be smaller.

For example, if clickable icons on are 16 x 16 pixels in size, there must be at least 8 px of free space between them.

Help is easier to find if it is always in the same place. Success Criterion 3.2.6 Consistent Help says that if there is a help mechanism on the website (for example, FAQ, message form, phone number), it must be located in the same place on each page.

If there is no help function on any of the pages, then the requirement is not applicable.

Success Criterion 3.3.7 Redundant Entry says that information that has already been entered by the user must not be requested again during the same session. None of us want to type in the same thing multiple times, especially if entering information is painstaking.

If the user has already entered information (e.g. their e-mail or personal identification code) on the page, the relevant fields must be filled in automatically or the previously entered data must be offered as recommendations.

If re-entry is important, for example, for security reasons ("Repeat password"), it is of course allowed.

For a user who has difficulty reading, calculating or memorizing, it can be difficult to remember their personal identification code or password, perform calculations and solve tests.

Success Criterion 3.3.8 Accessible Authentication (Minimum) says that the authentication mechanism (including the "Forgot password?" function) must not require a cognitive test (e.g. remembering a username or password by heart, calculation, etc.).

This means, for example, that when filling in the username and password fields, you need to allow copying and pasting text or using a password manager.

CAPTCHAs that require object recognition are still allowed.