Back to BlogWebsite Accessibility

Your Customer Has the Right Password. Can They Actually Sign In?

A practical guide to accessible authentication under WCAG 2.2: password managers, paste, verification codes, CAPTCHA and account recovery.

7 sections · 4 min read · 823 words

Written by Edward Sm

Digital Accessibility Specialist, ADA Access Group LLC

4 min read

Hands typing on a laptop with a smartphone on the desk.

A customer is ready to check an order, book a visit, or manage an account. They enter a password, receive a verification code—and find that the site will not let them paste it. For someone who relies on a password manager or finds transcription difficult, login can become the point where the journey stops.

Accessible authentication means making identity verification usable without needlessly excluding people. Security remains essential: product, security, and accessibility teams can work together on secure paths through sign-in, verification, and recovery.

What WCAG 2.2 says about authentication

WCAG 2.2 Success Criterion 3.3.8, Accessible Authentication (Minimum), is Level AA. It addresses cognitive function tests in authentication, such as tasks requiring someone to remember, manipulate, or transcribe information. When such a test is required, at least one listed condition must be met: an alternative, an assisting mechanism, object recognition, or identification of personal non-text content provided by the user.

W3C gives password-manager support and copy and paste as examples of mechanisms that assist users. The criterion focuses on authentication of existing users; W3C notes similar practices can still help during account creation. Other criteria may apply to labels, keyboard access, focus, instructions, and errors.

Let password managers and paste work

Blocking paste or password managers can force customers to memorize or transcribe credentials. Use clearly labeled username and password inputs, appropriate input-purpose markup, and test browser autofill alongside password managers. Do not block paste without evaluating how the user will complete the step through another accessible path.

If security requirements seem to conflict with a proposed change, involve the security and accessibility teams together. Evaluate the whole implementation, including alternatives; one technical setting alone does not establish WCAG conformance.

Test verification codes beyond the happy path

Person holding a smartphone while using a laptop.
Photo: Polina Tankilevitch / Pexels.

A one-time passcode may arrive by text, email, or authenticator. A common failure occurs when six separate visual fields accept only one pasted character instead of the whole code. Test paste, autofill, keyboard navigation, focus order, screen reader announcements, expiration, and retry.

W3C explains that transcribing a code is a cognitive function test, so an accessible mechanism or alternative is needed. Its guidance notes that whether a code transfers seamlessly between separate devices is outside the scope of the criterion. In practical usability testing, still consider people who cannot easily use a second device or channel.

Offer workable choices without weakening security

Depending on the service and security model, choices may include email sign-in links, security keys, or device-based authentication using WebAuthn. W3C lists examples of these approaches. Test enrollment, sign-in, fallback, and recovery with the actual providers and devices your customers use.

A biometric option should not be the only usable route: a customer may lack a compatible device, have difficulty using the biometric, or prefer another method. Providing an option does not guarantee it works for every user; verify it.

Check CAPTCHA and account recovery

Laptop and smartphone with charger on a desk.
Photo: Sami Abdullah / Pexels.

A puzzle, calculation, or transcription challenge can block a user before sign-in. WCAG 3.3.8 has limited exceptions for object recognition and identifying personal non-text content. W3C notes that these exceptions do not fully support all users with cognitive disabilities. A mathematical or logic puzzle is not covered by them, so an appropriate alternative or assistance mechanism is needed. CAPTCHA may also raise visual, auditory, motor, and screen reader issues; see W3C’s CAPTCHA accessibility guidance.

Customers also need a route back after a lost phone, expired code, or changed email. Check recovery for clear labels and instructions, keyboard access, errors, and an accessible way to get help. Evaluate authentication steps within recovery too. Our guide to accessible form problems covers related barriers.

A practical test for product teams

  1. Map sign-in, multi-factor verification, recovery, and fallback paths.
  2. Use only the keyboard and check visible focus and operable controls.
  3. Try autofill and paste in password and verification-code fields.
  4. Test errors, expiration, resend, and lost-device recovery.
  5. Use representative screen reader/browser and mobile combinations, and involve users with disabilities where possible.
  6. Record versions, reproduction steps, actual results, responsibility, fixes, and retesting.

These checks are a starting point, not a complete WCAG or security audit. Our screen reader testing guide explains testing combinations.

Turn findings into a plan

Identify the journeys that require an account, including vendor-provided identity components. Agree on ownership with the provider, prioritize barriers that block access, and retest fixes. Automated tools can identify certain issues but cannot prove that someone can finish every sign-in or recovery flow.

WCAG is a technical standard; legal obligations depend on the organization, jurisdiction, and facts. Read the DOJ’s web accessibility guidance and consult qualified counsel about legal questions.

Can customers sign in and recover accounts independently? Contact ADA Access Group to discuss a scoped assessment and retesting of important customer journeys. Learn what an audit should include.

This article is general information, not legal advice. No single change or audit guarantees compliance or a particular legal result.

Featured photo: Kaboompics / Pexels.

Article Tags

accessible authenticationWCAG 2.2login accessibilityMFAscreen reader testing

Need a website accessibility audit?

This article explains the topic. The audit is a manual WCAG 2.2 AA review by default (WCAG 2.1 AA when a contract or regulation requires it) with a prioritized report — not another automated scan.