Chapter 7: Make the safest path the path of least resistance
The introduction explains why accessible security should shift work from users to systems rather than make identity checks another barrier.
After this chapter you will be able to
- System responsibility for accessible security. Explain how placing security complexity on users can create barriers, and how accessible security instead has the system absorb as much work as possible while supporting people when identity verification is required.
- Accessible proof-of-presence checks. Explain why a proof-of-presence check can be a legitimate security measure yet create accessibility barriers, particularly when it demands physical movement or cognitive effort without an accessible alternative.
- Limited security compliance budget. Explain why adding security tasks can lead people to cut corners or abandon a task, and what makes a security mechanism usable and accessible in context.
- Compounding access barriers. Describe how individually defensible security controls can combine into accessibility barriers, using Jess’s sign-in experience to explain the kinds of resistance and possible consequences.
- Security Friction and Safe Choices. Explain why security should support the user's primary task rather than become an obstacle, and how excessive friction can lead people to bypass safeguards.
- Context Dependent Security Choices. Explain why there is no universal least-resistant security method, using the hospital and weather-service examples to show how an appropriate choice depends on context.
- Whole-value credential pasting. Describe how password and verification-code fields should support copying and pasting, including when the displayed input format differs from the value supplied to the user.
- Browser and password-manager support. Explain how appropriate autocomplete values and password-manager support reduce authentication effort and can improve password security.
- Partial-password authentication barrier. Explain why asking for selected characters of a password creates a cognitive function test, why ordinary password managers do not resolve it, and the section's stated accessibility condition.
- Passkey authentication process. Trace where passkey keys are held and how a user authenticates without disclosing their biometric data to the website.
- Accessible passkey backup journey. Explain why passkeys alone do not ensure accessible sign-in and when alternative authentication or recovery methods are needed.
- Federated sign-in accessibility. Describe third-party sign-in and explain what an application must assess before relying on an identity provider.
- Identity Verification Versus Ability Tests. Explain why identity tasks should establish that a person has valid credentials and is who they claim to be, rather than test what they can do. Describe how checks intended to deter attackers or bots can create barriers when they demand particular abilities without alternatives.
- Recall support for credentials. Describe how to reduce recall and typing demands in password tasks without requiring people to avoid passwords.
- Transcription and its barriers. Explain what transcription means in authentication and why it can be difficult for users with different disabilities, especially when codes expire quickly.
- Lower-friction code entry. Describe ways to reduce the demands of code entry when transcription remains necessary, including whole-code paste, reasonable time limits, and fallback options.
- Alternatives and their tradeoffs. Describe alternatives to code transcription and explain why each needs its own accessibility and security assessment, support mechanisms, and other options.
- Identity versus puzzle solving. Explain why requiring someone to solve a puzzle is a poor way to verify them: the challenge tests their ability to complete a task rather than their identity.
- Proof-of-work abuse deterrence. Explain how proof-of-work operates in the background and why its computational cost discourages high-volume abuse.
- Fine Motor Barriers. Explain why puzzle challenges that require dragging or rotating can prevent some people from completing a task.
- Alternatives to Dragging. Describe what to provide when a task uses dragging and state the WCAG condition identified for tasks that rely entirely on it.
- Risk matched security checks. Describe how to defer high-effort verification until a user requests a higher-risk feature, while allowing low-effort access to low-risk features.
- Explicit Challenge Accessibility Barriers. Describe how visual, audio, recall, and arithmetic CAPTCHA tasks can test abilities rather than identity, including the authentication limits the section identifies for audio transcription and object recognition.
- Behavioral Classification Risks. Trace how an invisible CAPTCHA can use behavioral signals to decide whether to challenge someone, and explain why legitimate assistive technology use may be misclassified.
- Inclusive CAPTCHA Evaluation. Distinguish an accessible challenge interface from accurate recognition of assistive technology users, and describe how a team should evaluate a proposed CAPTCHA.
- Distinct identity factors. Explain why 2FA requires two different kinds of identity verification, how that reduces account risk, and why two steps or a CAPTCHA do not necessarily count.
- Cross-device code barriers. Describe how requiring a user to read a one-time code on one device and manually enter it on another can create an accessibility barrier, and how allowing transfer instead can help.
- Accessible second-factor choices. Explain why users should have accessible, secure choices for additional factors, including at least one method that does not require a cognitive function test, and describe examples and the cautions given here.
- Accessible and secure account recovery. Explain why an accessible account recovery path is necessary and why it must be as secure as authentication. Describe situations that can leave users needing recovery.
- Independent account recovery paths. Explain why account recovery must offer multiple ways back in that do not rely on the task, technology, or method that caused the lockout.
- Advance backup recovery setup. Explain why users should be able to configure backup recovery methods before losing access, and describe the kinds of methods the section suggests.
- Security question drawbacks. Explain why security questions are a poor account-recovery method from both accessibility and security perspectives.
- Security and user effort. Explain why a session timeout may be necessary but should not make users lose their work, and why apparent inactivity may reflect a task that is still in progress.
- Preserving and restoring form progress. Describe how to save progress through a long or multi-step form and let users continue after signing back in. Include how users learn that a save occurred and how to handle sensitive fields that cannot be restored.
What it builds on
- Ensure keyboard focus is visible (chapter 5) · Visible keyboard focus for interactive controls
- Forms done right (chapter 6) · Accessible handling of form inputs
- Input type and autocompl... (chapter 6) · Use of input types and autocomplete in forms
- Build keyboard-friendly websites (chapter 5) · The need to support keyboard interaction.
- Handle time-consuming tasks appropriately (chapter 6) · Giving people enough time for time-consuming tasks
- What does WCAG conformance mean? (chapter 1) · WCAG conformance levels
Section by section
Introduction
The introduction explains why accessible security should shift work from users to systems rather than make identity checks another barrier.
- System responsibility for accessible security: Explain how placing security complexity on users can create barriers, and how accessible security instead has the system absorb as much work as possible while supporting people when identity verification is required.
Why it matters: This principle helps distinguish a necessary identity check from an unnecessarily difficult one.
Key terms: security burden, identity verification, accessible security
7.1 Be mindful of identity and account tasks
This section explains why proof-of-presence checks can create accessibility barriers even when their security goal is legitimate.
- Accessible proof-of-presence checks: Explain why a proof-of-presence check can be a legitimate security measure yet create accessibility barriers, particularly when it demands physical movement or cognitive effort without an accessible alternative.
Why it matters: A security check should establish presence without unnecessarily excluding people who cannot complete its particular challenge.
Key terms: proof-of-presence (PoP), accessible methods, physical and cognitive barriers
7.2 Accessibility versus security – the tradeoff fallacy
This section explains why security measures can undermine both accessibility and security when their combined demands make ordinary tasks too difficult.
- Limited security compliance budget: Explain why adding security tasks can lead people to cut corners or abandon a task, and what makes a security mechanism usable and accessible in context.
Why it matters: Security requirements are less effective when people cannot reasonably complete them. - Compounding access barriers: Describe how individually defensible security controls can combine into accessibility barriers, using Jess’s sign-in experience to explain the kinds of resistance and possible consequences.
Why it matters: Judging each control alone can hide the difficulty and security risks created by the whole sign-in process.
Key terms: path of least resistance, budget for security compliance, friction, context of use, gatekeeping security processes, cognitive, temporal, interaction modality-related, one-time codes
7.3 Reduce resistance
This section argues that security should make the safe choice easy and that the least-resistant approach depends on the context of use.
- Security Friction and Safe Choices: Explain why security should support the user's primary task rather than become an obstacle, and how excessive friction can lead people to bypass safeguards.
Why it matters: A safeguard is less effective if people feel driven to work around it. - Context Dependent Security Choices: Explain why there is no universal least-resistant security method, using the hospital and weather-service examples to show how an appropriate choice depends on context.
Why it matters: Choosing security for the situation avoids imposing burdens that may not help users or protection.
Key terms: primary task, friction, path of least resistance, contexts of use, biometrics-based authentication
7.3.1 Offer mechanisms to support users
This section explains how password controls, copying and pasting, browser autofill, and password managers can reduce the effort of authentication without undermining security, and why partial-password checks create an accessibility barrier.
- Accessible password reveal control: Explain how an optional password reveal control helps users check for errors before submitting and what makes the control accessible.
Why it matters: Checking a password before submission can prevent errors and lockouts without requiring users to type it twice. - Whole-value credential pasting: Describe how password and verification-code fields should support copying and pasting, including when the displayed input format differs from the value supplied to the user.
Why it matters: Accepting a value as supplied spares users the memory and transcription work that can make authentication inaccessible. - Browser and password-manager support: Explain how appropriate autocomplete values and password-manager support reduce authentication effort and can improve password security.
Why it matters: Letting browsers and password managers help users can make strong, distinct passwords easier to use. - Partial-password authentication barrier: Explain why asking for selected characters of a password creates a cognitive function test, why ordinary password managers do not resolve it, and the section's stated accessibility condition.
Why it matters: A check intended to protect an account can instead make access depend on memory and manual character-by-character work.
Key terms: password reveal toggle, visible focus indicator, accessible name, copy and paste, one-time codes, transcription, single input fields, autocomplete, username, current-password
7.3.2 Offer alternative methods
The section explains alternative sign-in methods that can reduce cognitive demands, while showing why each method still needs an accessible end-to-end journey.
- Passwordless magic link sign-in: Describe how a magic link lets someone sign in without a password and why its expiry must allow enough time to use it.
Why it matters: A password-free option is only useful if people have a fair chance to complete it. - Passkey authentication process: Trace where passkey keys are held and how a user authenticates without disclosing their biometric data to the website.
Why it matters: This explains how passkeys can replace password recall without sending the user's biometric data to the site. - Accessible passkey backup journey: Explain why passkeys alone do not ensure accessible sign-in and when alternative authentication or recovery methods are needed.
Why it matters: A convenient sign-in method still needs a usable path when its device or required interaction is unavailable. - Federated sign-in accessibility: Describe third-party sign-in and explain what an application must assess before relying on an identity provider.
Why it matters: Outsourcing sign-in does not outsource responsibility for the barriers users encounter. - Enterprise single sign-on limits: Explain how enterprise single sign-on reduces repeated authentication and why it does not itself guarantee accessibility.
Why it matters: Fewer sign-ins help, but the shared sign-in method must still work for everyone.
Key terms: magic links, time-limited link, passkeys, relying party, authenticator, public key, private key, cryptographic challenge, accessible alternatives, biometrics
7.4 Verify identities, not cognitive and physical abilities
This section argues that identity tasks should verify a person’s credentials and claimed identity without making cognitive or physical abilities the test of legitimacy.
- Identity Verification Versus Ability Tests: Explain why identity tasks should establish that a person has valid credentials and is who they claim to be, rather than test what they can do. Describe how checks intended to deter attackers or bots can create barriers when they demand particular abilities without alternatives.
Why it matters: A security check can exclude a legitimate user if passing it depends on abilities the user does not have.
Key terms: identity tasks, valid credentials, proving legitimacy, cognitive, physical, perceptual, or technological capabiliti
7.4.1 Minimize recall
This section explains why password tasks should minimize memory demands and support people in using credentials securely.
- Password policy coping risks: Explain how demanding password rules can lead people to choose insecure ways of coping.
Why it matters: A rule intended to protect accounts may instead push people toward less secure habits. - Recall support for credentials: Describe how to reduce recall and typing demands in password tasks without requiring people to avoid passwords.
Why it matters: Supporting familiar credential tools can reduce mistakes and accidental lockouts without forcing people to memorize passwords.
Key terms: password policies, predictable variants, reusing passwords, browser autofill, copy-and-paste, password managers, cognitive function tests
7.4.2 Minimize transcription
The section explains why manually transferring authentication codes can create accessibility barriers and how to reduce transcription without overlooking security tradeoffs.
- Transcription and its barriers: Explain what transcription means in authentication and why it can be difficult for users with different disabilities, especially when codes expire quickly.
Why it matters: A security step can also become a barrier if it depends on abilities the user may not have. - Lower-friction code entry: Describe ways to reduce the demands of code entry when transcription remains necessary, including whole-code paste, reasonable time limits, and fallback options.
Why it matters: Small changes to code entry can prevent avoidable mistakes and lockouts. - Origin-bound SMS codes: Explain how supported browsers can assist with SMS one-time codes and why matching the code to a website matters.
Why it matters: Browser assistance can remove manual code entry, but it does not make SMS universally suitable. - Alternatives and their tradeoffs: Describe alternatives to code transcription and explain why each needs its own accessibility and security assessment, support mechanisms, and other options.
Why it matters: Removing typed codes helps only if the replacement does not create a different barrier or unacceptable risk.
Key terms: transcription, one-time code, copy and paste, fallback options, time constraints, autocomplete="one-time-code", origin-bound one-time codes, top-level host, magic link, QR or Cronto codes
7.4.3 Minimize problem-solving
This section explains why puzzle-based human verification can create barriers unrelated to the identity or humanity it is meant to establish.
- Identity versus puzzle solving: Explain why requiring someone to solve a puzzle is a poor way to verify them: the challenge tests their ability to complete a task rather than their identity.
Why it matters: A verification step can block a legitimate user for a reason unrelated to what it is supposed to check. - Cultural barriers in puzzles: Describe how image or knowledge puzzles can exclude people because the expected answer depends on cultural familiarity rather than whether they are human.
Why it matters: A challenge that seems obvious to its author may be impossible for a legitimate user elsewhere.
Key terms: problem-solving or puzzle-based challenges, verify a user’s identity, cultural familiarity, automated bot
7.4.4 Minimize reliance on behavioral patterns with proof-of-work (POW)
This section explains how proof-of-work makes high-volume abuse costly while cautioning that its computational demands can burden users on some devices.
- Proof-of-work abuse deterrence: Explain how proof-of-work operates in the background and why its computational cost discourages high-volume abuse.
Why it matters: The distinction is that proof-of-work raises the cost of abuse rather than simply stopping bots. - Device impacts of computational challenges: Describe why more demanding proof-of-work challenges require evaluation across devices.
Why it matters: A security check that runs in the background can still impose a real cost on users.
Key terms: proof-of-work (PoW), proof of completion, computational task, computational burden, resource-constrained hardware, proof-of-work challenges
7.4.5 Minimize movement
This section explains how movement-based identity challenges can exclude users and why dragging tasks need accessible alternatives.
- Fine Motor Barriers: Explain why puzzle challenges that require dragging or rotating can prevent some people from completing a task.
Why it matters: A challenge intended to verify a user can instead test their ability to make precise movements. - Alternatives to Dragging: Describe what to provide when a task uses dragging and state the WCAG condition identified for tasks that rely entirely on it.
Why it matters: An equivalent non-dragging option lets users complete the task without performing a gesture they cannot make.
Key terms: fine motor control, motor impairments, WCAG 2.2 Success Criterion 2.5.7 – Dragging Movements, single pointer, keyboard users, assistive technology users
7.4.6 Consider just-in-time over just-in-case security checks
The section argues for deferring demanding identity checks until users need higher-risk features, while making the resulting access limits clear.
- High effort verification barriers: Explain why requiring document scans during registration can exclude or discourage users even when the web application itself is accessible.
Why it matters: An accessible interface does not remove barriers created by a demanding security process. - Risk matched security checks: Describe how to defer high-effort verification until a user requests a higher-risk feature, while allowing low-effort access to low-risk features.
Why it matters: Matching verification effort to the risk of an action lets people use basic services without removing checks from higher-risk ones. - Clear access requirements: Explain what users should be told when verification is deferred until they need higher-risk features.
Why it matters: Users need to understand both their current access and the steps required for more sensitive tasks.
Key terms: high-effort security processes, scanning a document, low-risk features, low privileges, higher-risk tasks, high-effort verification process, higher-risk features, clear communication
7.5 CAPTCHA
This section explains how both visible CAPTCHA challenges and invisible bot detection can create accessibility barriers, and how product teams should evaluate whether and how to use them.
- CAPTCHA Purpose and Evolution: Explain that CAPTCHA is a family of tests intended to distinguish people from bots, and that its approaches have changed as automation has improved.
Why it matters: The accessibility problem is broader than any single CAPTCHA product or puzzle. - Explicit Challenge Accessibility Barriers: Describe how visual, audio, recall, and arithmetic CAPTCHA tasks can test abilities rather than identity, including the authentication limits the section identifies for audio transcription and object recognition.
Why it matters: A bot check can block a legitimate person when passing it depends on abilities unrelated to their identity. - Behavioral Classification Risks: Trace how an invisible CAPTCHA can use behavioral signals to decide whether to challenge someone, and explain why legitimate assistive technology use may be misclassified.
Why it matters: A challenge that is invisible to most users can still unfairly single out people using assistive technology. - Inclusive CAPTCHA Evaluation: Distinguish an accessible challenge interface from accurate recognition of assistive technology users, and describe how a team should evaluate a proposed CAPTCHA.
Why it matters: A usable fallback is not enough if the system disproportionately sends legitimate users to it.
Key terms: CAPTCHA, bots, risk signals, visual CAPTCHA, audio alternatives, Accessible Authentication (Minimum), Accessible Authentication (Enhanced), cognitive function test, invisible approaches, behavioral patterns
7.6 Two-factor authentication
This section explains what makes authentication genuinely two-factor and how to provide a secure second factor without creating accessibility barriers.
- Distinct identity factors: Explain why 2FA requires two different kinds of identity verification, how that reduces account risk, and why two steps or a CAPTCHA do not necessarily count.
Why it matters: It helps you tell genuine identity assurance from extra steps that merely burden users. - Cross-device code barriers: Describe how requiring a user to read a one-time code on one device and manually enter it on another can create an accessibility barrier, and how allowing transfer instead can help.
Why it matters: An otherwise secure login can exclude people when it makes memory and manual transcription unavoidable. - Accessible second-factor choices: Explain why users should have accessible, secure choices for additional factors, including at least one method that does not require a cognitive function test, and describe examples and the cautions given here.
Why it matters: Choice allows people to complete security tasks without having to trade away accessibility or appropriate protection. - Costs of inaccessible authentication: Explain the user and organizational consequences of inaccessible 2FA and why fixing it after launch can be costly.
Why it matters: Considering accessibility before launch can avoid lockouts and expensive changes across the product.
Key terms: two-factor authentication (2FA), multi-factor authentication (MFA), distinct factors, CAPTCHA, proof-of-work challenge, one-time code, primary device, secondary device, transcription, cognitive function test
7.7 Account recovery
Account recovery must help locked-out users regain access without weakening authentication security.
- Accessible and secure account recovery: Explain why an accessible account recovery path is necessary and why it must be as secure as authentication. Describe situations that can leave users needing recovery.
Why it matters: Recovery is another way into an account, so it must be usable by people who are locked out without becoming a weaker entry point.
Key terms: account recovery, authentication, 2FA
7.7.1 Help users recover from any incident that may lock them out
Account recovery must provide accessible ways back in that do not depend on whatever locked the user out.
- Independent account recovery paths: Explain why account recovery must offer multiple ways back in that do not rely on the task, technology, or method that caused the lockout.
Why it matters: A recovery option is only useful if someone who is locked out can actually use it. - Sign-in lockout review: Describe how to review default and alternative sign-in journeys to find steps that could lock users out and trigger recovery.
Why it matters: Reviewing all sign-in paths reveals obstacles that a recovery path must not repeat.
Key terms: account recovery, 2FA, CAPTCHA, accessible alternatives, sign-in journeys, default, alternative paths
7.7.2 Let users configure backup recovery methods before they need them
This section explains why users should be able to set up backup account-recovery methods before losing access, rather than relying on memory-based recovery.
- Advance backup recovery setup: Explain why users should be able to configure backup recovery methods before losing access, and describe the kinds of methods the section suggests.
Why it matters: A backup prepared in advance can make an urgent lockout easier to resolve. - Security question drawbacks: Explain why security questions are a poor account-recovery method from both accessibility and security perspectives.
Why it matters: A familiar-looking recovery question can both exclude a legitimate user and expose their account. - Password hint limitations: Distinguish a password hint from a genuine alternative recovery method.
Why it matters: A reminder is not a fallback for someone who cannot recall the password.
Key terms: backup recovery methods, recovery contact, recovery codes, backup passkey, redundancy in access methods, security questions, account-recovery method, knowledge-based authentication (KBA), password hints, alternative account recovery method
7.8 Handle session timeouts and session state gracefully
This section explains how to protect accounts with session timeouts without unnecessarily erasing users’ work or interrupting long tasks.
- Security and user effort: Explain why a session timeout may be necessary but should not make users lose their work, and why apparent inactivity may reflect a task that is still in progress.
Why it matters: A secure timeout need not turn a pause in activity into a lost task. - Preserving and restoring form progress: Describe how to save progress through a long or multi-step form and let users continue after signing back in. Include how users learn that a save occurred and how to handle sensitive fields that cannot be restored.
Why it matters: Preserving progress lets people recover from a timeout without repeating a lengthy form. - Timeout warnings and re-authentication: Explain the section’s WCAG Level AAA guidance for continuing after re-authentication and warning users about inactivity that could cause data loss.
Why it matters: Advance notice and a way to continue make necessary time limits less disruptive. - User-controlled unfinished work: Describe the options suggested for managing unfinished work in a long process.
Why it matters: People need control over whether unfinished work remains available for later.
Key terms: session timeouts, inactivity, persistent storage, volatile session state, autosaving, polite live regions, repopulate the form, WCAG 2.2, Level AAA, Re-authenticating
7.9 Summary
7.10 References
This section lists sources cited for the chapter’s discussion of identity, security, and CAPTCHA.
Concepts explained in this chapter
- cognitive function testA cognitive function test is a task that requires a user to remember or transcribe information, perform calculations, solve puzzles, or complete a similar mental task.
- CAPTCHAA family of challenge-response tests designed to distinguish human users from automated systems.
- account recoveryAccount recovery is a process for restoring access to an account when a person cannot use their usual sign-in method or credentials.
- autocomplete attributeAn HTML attribute that indicates whether and how a browser may automatically complete a form field using stored information.
- copy/pasteAn interaction technique for transferring selected text or data from one location to another without re-entering it.
- partial password authenticationPartial password authentication is an authentication method that asks users to provide selected characters from a password rather than the entire password.
- password reveal toggleA password reveal toggle is an interface control that switches a password field between masked and visible text.
- magic linkA magic link is a time-limited link sent to a user's email account that enables sign-in without a password.
- one-time codeA one-time code is a temporary code intended to be used once, commonly as part of an identity-verification process.
- passkeyA passkey is a passwordless authentication credential based on a public-private key pair and unlocked through an authenticator.
- accessible authenticationAccessible authentication is an authentication process designed so that people with disabilities can complete it without unnecessary barriers.
- two-factor authenticationTwo-factor authentication is an authentication method that requires evidence from two distinct factor categories to verify a user's identity.
- session timeoutA session timeout ends or interrupts a user's session after a period of inactivity or elapsed time.
- transcriptionThe process of rendering spoken language as written text.
- accessibility barrierAn accessibility barrier is a feature, condition, or design decision that prevents or impedes people from accessing or using technology.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.
