Search the Guide
Knowing which fields are required to submit a form makes filling that form much easier to do, and less likely to return an error message that confuses the user.
New in WCAG 2.2
Not all site visitors use a computer mouse to navigate a webpage. Some people get around a webpage by using only keyboard controls. Some assistive technologies also act as keyboard emulators, which means they rely on keyboard controls working in order to function. This includes switch devices, eye-tracking software, and voice recognition.
Content that autoplays can distract site visitors with attention-related disabilities or vestibular disorders, which may prevent the visitor from being able to use the rest of the page. People that use screen readers may also experience autoplay while trying to listen to their screen reader audio—this makes it difficult to navigate a page, if not impossible.
Not all users can visually tell a new window or tab is opened, like someone using a magnifier or a screen reader. Or, the user may want to stay in the same browser tab or window so they can easily navigate through their browser history.
Enforcing the behavior within a link can frustrate users who don't realize the link opened elsewhere, or users on mobile devices where it can take more steps to find either the new or previous window. The user should be able to decide where a page opens using their preferences.
If a user can’t visually perceive a page, they may not realize that statuses, updates, or confirmations were loaded on a page. This is disorienting, and can make users wonder if the button or control they pressed worked.
People using magnification to enlarge webpage text may also miss status status message altogether due to the message being out of frame. If the message can be coded semantically, then the message can still be understood and conveyed by assistive technology.