Level
AA
Since
WCAG 2.2
/ WCAG criterion

3.3.8 Accessible Authentication (Minimum)

Signing in must not depend on remembering, transcribing or solving something, unless there is another way, help such as a password manager or paste, or the test is to recognise objects or the user's own content.

/ What it requires

A cognitive function test is a task that requires the user to remember, manipulate or transcribe information: recalling a password, typing characters from a distorted image, copying a code by hand, solving a puzzle or doing a sum. For people with memory, reading or processing impairments such a test can lock them out of their own account. This criterion forbids requiring one for any step of an authentication process unless that step offers an alternative method without such a test, or a mechanism that helps the user complete it. The common identifiers name, email address and phone number are not considered cognitive function tests.

W3C names the usual mechanisms: support for password managers filling the fields, and copy and paste, so that nobody has to retype anything. A password field therefore passes when it can be filled automatically or pasted into. At level AA two kinds of test are also allowed: recognising objects, such as picking the pictures of a car, and identifying non-text content the user gave the site, such as their own photo. A verification code that has to be typed by hand fails; the user must at least be able to paste it. The AAA criterion 3.3.9 removes the object and personal content exceptions.

This criterion is new in WCAG 2.2 and is not part of WCAG 2.0 or 2.1.

/ How pages fail it

  • The password field cancels the paste event with a script, so a password copied from a password manager cannot be entered.
  • The sign-in form uses a custom on-screen keypad that password managers cannot fill, and offers no other way to sign in.
  • A six-digit code from a text message has to go into six separate inputs, and pasting the code fills only the first one.
  • A CAPTCHA asks the user to type distorted characters, and its audio version also has to be transcribed.
  • A bank asks for the first, third and fifth digit of a passnumber, which a password manager cannot fill and a person cannot paste.

/ How to check it yourself

  1. List every step of signing in, of signing up where it authenticates, of resetting a password and of confirming a second factor.
  2. At each step that asks for something remembered or transcribed, let a password manager fill the field. Then copy a value and paste it with Ctrl+V and with the context menu.
  3. In the developer tools, look for listeners on the paste event of credential and code fields, and check that the fields carry autocomplete="username", "current-password" or "one-time-code" where they apply.
  4. For a one-time code split across inputs, paste the whole code into the first one and check that every part fills.
  5. For any CAPTCHA or puzzle, check for an alternative that needs no recall, transcription or calculation, or confirm that the test is to recognise objects or the user's own content.

/ How to fix it

  • Remove every handler that cancels paste on credential and code fields.
  • Use standard input elements inside a form element, with autocomplete="username" and autocomplete="current-password", so that browsers and password managers can fill them.
  • Accept a one-time code in one input with autocomplete="one-time-code" and inputmode="numeric", or, if the design splits it, spread a pasted string across all the parts.
  • Offer a method that needs no test at all: a sign-in link sent by email, WebAuthn, or sign-in with a third-party provider.
  • Replace a transcription CAPTCHA with a check that involves no cognitive function test, or one based on recognising objects, and make sure any audio option does not require typing what is heard.

/ What our scanner checks

No automated check in our scan covers this. The site scan visits pages as an anonymous visitor and never signs in, and none of our rules try a password manager, paste a value or look for scripts that cancel paste. Whether each step of signing in demands a memory or transcription test is checked by a person with a test account in a manual audit.

/ Who fails it, in our own measurements

The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Does a password login fail WCAG 2.2 3.3.8?

Not if the password can be filled in by a password manager or pasted. W3C names both as mechanisms that meet the criterion. A login fails when it blocks paste or autofill and offers no other method, because the user is then left to remember and type the password unaided.

Is CAPTCHA allowed under Accessible Authentication (Minimum)?

A CAPTCHA that asks the user to type distorted characters is a cognitive function test and needs an alternative that is not one. An audio version counts only if the user does not have to transcribe it. A test of recognising objects, such as picking the images that show a bicycle, is excepted at level AA but not at AAA.

Are SMS verification codes allowed under 3.3.8?

Yes, if they can be pasted. W3C says a service that requires manual transcription of a verification code is not compliant, and that the user must at least be able to paste the code. A code field that accepts paste, ideally with autocomplete="one-time-code", meets this level AA criterion, which is new in WCAG 2.2.