How accessible is your website?Start free check
WCAG 3.3.8Level AAUnderstandable

Accessible Authentication: Logins Without Memory Tests

Also called: Accessible login, Accessible Authentication (Minimum), Cognitive function test

Definition

Accessible Authentication (Minimum) is WCAG success criterion 3.3.8. No step of a login may require a cognitive function test – remembering a password, transcribing a code, solving a puzzle – unless an alternative, a helping mechanism or an allowed exception is available.

Accessible authentication means people can log in without passing a memory or puzzle test. If a login asks someone to remember a password, retype a code or solve a math CAPTCHA, the site must also offer a way through that does not rely on those skills – for example by letting a password manager fill the fields or allowing paste.

What it means

WCAG 3.3.8 Accessible Authentication (Minimum) is a Level AA criterion, new in WCAG 2.2. A cognitive function test is not required for any step in an authentication process unless that step provides one of four exceptions.

W3C defines a cognitive function test as a task that requires the user to remember, manipulate or transcribe information. Entering your own name, email address or phone number does not count – that information is personal and the same on every site.

Exception What it allows
Alternative Another login method without a cognitive test, such as an email link, a passkey or third-party sign-in
Mechanism Help to complete the test, such as a password manager or copy and paste
Object recognition A test that only asks people to recognize objects, such as "select all cars"
Personal content Picking an image the user uploaded to the site earlier

The criterion covers logging in to an existing account, including every step of a multi-step login and account recovery. Creating an account is not in scope. It helps people with cognitive limitations around memory, reading (such as dyslexia), numbers (such as dyscalculia) or perception and processing.

Examples

Example
<form action="/login" method="post">
  <label for="email">Email address</label>
  <input id="email" name="email" type="email" autocomplete="username">

  <label for="password">Password</label>
  <input id="password" name="password" type="password" autocomplete="current-password">

  <label for="code">Verification code</label>
  <input id="code" name="code" inputmode="numeric" autocomplete="one-time-code">

  <button type="submit">Log in</button>
</form>

Visible form labels and the right autocomplete values let browsers and password managers fill the fields. Paste works because no script blocks it. The one-time code is a single field, so a pasted code lands in one go.

Do

Allow paste and autofill in every login field, offer a magic link, passkey or hardware key as another route, accept a pasted code in one field, and keep account recovery free of memory tests.

Don't

Block paste with JavaScript, ask for "the 3rd and 5th character" of a password, split a code into six boxes that reject paste, or rely on a math CAPTCHA without another way in.

How to check accessible authentication

    Questions

    Are passwords still allowed under WCAG 2.2?

    Yes. A password is a memory test, but it passes when a mechanism helps – the field allows a password manager to fill it and accepts paste. Then nobody has to remember or type it by hand.

    Do CAPTCHAs fail accessible authentication?

    Not all of them. A test that only asks people to recognize objects is allowed at Level AA. Math problems, text puzzles or rotating 3D models need another login method that avoids them.

    Is two-factor authentication accessible?

    It can be. A code sent by SMS or email passes if people can paste it or the browser fills it in. Hardware keys, approval prompts in an app and device unlock with fingerprint or face are not cognitive tests at all.

    Does 3.3.8 apply to signing up?

    No. W3C limits the criterion to logging in to an existing account, including multi-step logins and account recovery. Creating a username or account is not in scope.

    • Redundant Entry: Don't Ask for the Same Data Twice

      Redundant Entry is WCAG success criterion 3.3.7. Information a user already entered or was given in the same process must be auto-populated or available to select when it is needed again – unless re-entry is essential, needed for security or the information is no longer valid.

      Read definition: Redundant Entry: Don't Ask for the Same Data Twice
    • Form Labels: Clear Labels and Instructions

      Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.

      Read definition: Form Labels: Clear Labels and Instructions
    • Timing Adjustable: Fair Time Limits and Timeouts

      Timing Adjustable is WCAG success criterion 2.2.1. For each time limit set by the content, users can turn it off, adjust it to at least ten times the default or extend it after a warning – unless the limit is part of a real-time event, essential, or longer than 20 hours.

      Read definition: Timing Adjustable: Fair Time Limits and Timeouts
    • CAPTCHA: Accessible Bot Checks Under WCAG 1.1.1

      A CAPTCHA is a test meant to confirm that a person, not a computer, is using a website. WCAG 1.1.1 requires a text alternative that describes its purpose and at least one alternative form using a different sense.

      Read definition: CAPTCHA: Accessible Bot Checks Under WCAG 1.1.1

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done