Developers

Success Criterion 3.3.9 Redundant Entry (Level A)

 

For steps in a process such as registering or completing a form, information that the user has already entered must be made available to them. In a nutshell, this success criterion helps users by not making them enter information more than once unless it’s absolutely necessary.

Developers

3.3.8 Accessible Authentication – No Exception (Level AAA)

 

If your website authentication requires a cognitive function test, make sure it has an alternative that doesn’t have such a test. What you need to know The AA success criterion 3.3.7 allows authentication by using object or content recognition (for example, check every box with a traffic light), but 3.3.8 level AAA doesn’t.  Common identifiers […]

Developers

3.3.7 Accessible Authentication (Level AA)

 

A cognitive function test to log in can only be required under limited circumstances. What you need to know According to W3C, a cognitive function test is a task that “requires the user to remember, manipulate, or transcribe information.” This could take the form of a username and password, doing calculations, or solving a puzzle.  […]

Designers, Developers

3.2.6 Consistent Help (Level A)

 

If you have a help option, make sure it’s consistently available and in the same relative place on each page. This will make it easy to find as users navigate your website. What you need to know Access to help mechanisms may be provided directly on the page or may be provided by a link […]

Developers

2.5.8 Target Size – Minimum (Level AA)

 

All interactive targets should take up at least 24×24 CSS pixels of space. This can include white space around the target. What you need to know Ensuring that targets are big enough and that there’s sufficient space between them makes it less likely that a user will accidentally activate the wrong control.  Meeting this success […]