liveBook · Manning

Accessible authentication

As explained in Architecting Accessibility

Accessible authentication is an authentication process designed so that people with disabilities can complete it without unnecessary barriers.

Authentication should confirm who someone is, not test whether they can perform a particular physical or cognitive task. A person whose phone is lost, unavailable, or out of battery still needs a way to sign in or recover their account. section 7.3.2 section 7.9

Design alternatives into the whole authentication journey:

  • Offer another way to authenticate or recover access when a method depends on a specific device, biometric capability, or interaction such as scanning a QR code. section 7.3.2
  • Avoid making sign-in depend on remembering or transcribing information, solving puzzles or arithmetic challenges, or completing CAPTCHA tasks. section 7.3.2 section 7.9
  • Let users configure backup recovery methods before they need them, and provide a way back in if they are locked out. section 7.9

A passkey is not the whole journey

A passkey may be unavailable when its device is lost or its battery is dead. Provide an alternative for sign-in and recovery, and check that enrollment and authenticator replacement are accessible too. section 7.3.2

How Architecting Accessibility covers it

How deep it goes
Explains alternatives across sign-in and recovery, without specifying a technical implementation.
Examples
Uses unavailable passkey devices, biometric or QR-code barriers, cognitive challenges, and backup recovery methods.
What you can do after
Evaluate authentication paths for barriers tied to devices, sensory abilities, physical abilities, or cognitive tasks.
How it connects
Connects authentication to passkeys, federated identity, multifactor authentication, CAPTCHA, and account recovery.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.