liveBook · Manning

Chapter 7: Make the safest path the path of least resistance

What you will learn in chapter 7 of Architecting Accessibility

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

What it builds on

Section by section

Introduction

The introduction explains why accessible security should shift work from users to systems rather than make identity checks another barrier.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

← Chapter 6: Help people complete tasks efficiently

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.