Authentication · Composite use case

Sign in without a memory test.

A complete form combines clear fields, password-manager support, recovery, usable errors, and calm submission feedback.

Builds on: authentication fields, show password, accessible authentication, and form errors.

The pattern

Let the browser and password manager fill the credentials. Do not block paste, demand transcription, or make recovery hard to find.

Interactive flow

Sign in

Submit the empty form to inspect error focus. Fill both fields to inspect non-disruptive progress and completion feedback.

Paste and password-manager autofill are supported.

Forgot your password?

Expected experience

A short, predictable sequence.

The show-password button follows its field, recovery remains available, and no CAPTCHA interrupts the route.

Keyboard order

  1. Email address
  2. Password
  3. Show password
  4. Sign in
  5. Forgot your password?

Feedback and recovery

  • Errors are summarized, linked, and attached to their fields.
  • Focus moves to the summary only when validation fails.
  • “Signing in” and completion are announced through one persistent status region.
  • Recovery should offer a password-manager-friendly email link or passkey route.