Skip to content

UX guides / Auth / Password composition rules are shown before submission, not after

Password composition rules are shown before submission, not after

Usually highHow serious this usually is when it goes wrong. Not a score.

The guideline

If the password field enforces composition rules, state them next to the field before the first submit attempt — as static hint text or a live checklist that updates as the user types — rather than only as a rejection message after submission. Prefer a minimum-length requirement over a complex composition mandate: NIST SP 800-63B recommends verifiers stop imposing arbitrary composition rules and instead check new passwords against a list of commonly used or breached values. Where a composition rule is kept for other reasons, disclosing it up front is the minimum bar.

Common failures

  • The registration form does not display password requirements—such as minimum character count, required special characters, or mixed case rules—near the password input field, forcing users to guess acceptable formats and discover errors only after submission.

Where it applies

Pages

  • Auth
  • Onboarding

Disciplines

  • Conversion
  • Accessibility

Devices

  • Desktop web
  • Mobile web

Why it matters, how to fix it, and the research behind it

Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.