Success criterion 3.3.9
Accessible Authentication (Enhanced)
Authentication processes offer methods that do not require cognitive function tests or provide support to assist users in completing these tests, ensuring that access is straightforward and does not exclude users with cognitive disabilities.
- Level AAA
- Principle 3: Understandable
- Guideline 3.3: Input Assistance
- New in WCAG 2.2
In a user’s words
“Security shouldn't be a puzzle. Let's make access straightforward for everyone.”
What each role can do
- Product manager
- Prioritize the development of enhanced authentication methods that cater to a wide range of cognitive abilities.
- Designer
- Create a seamless authentication experience that supports users with cognitive impairments, using clear instructions and alternative access methods.
- Developer
- Develop and implement support mechanisms within authentication processes, such as object recognition or the use of personal content, to assist users.
- Tester
- Conduct comprehensive testing to validate that the authentication process is accessible, focusing on users with cognitive impairments and ensuring the process is easy and secure.
Once it is fixed
“Your inclusive approach to security has opened doors for me that were once closed. Thank you for empowering me with easy access!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 3.3.9 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.