---
title: Password composition rules are shown before… · Rubric
description: 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…
url: https://rubric.design/ux/auth.password-requirements-visible
format: agent view of this page
updated: 2026-11-16
---

[UX guides](https://rubric.design/ux/) / Auth / Password composition rules are shown before submission, not after

# Password composition rules are shown before submission, not after

Usually high · How 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.

[Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents)

## Related guides

- [Labels are programmatically associated with their fields](https://rubric.design/ux/accessibility.form-label-association) · Usually critical · Associate every input's visible label with its control using a native \<label for>/id pair, or aria-labelledby when a native label element is not possible.
- [Video and audio content ships with captions and a transcript](https://rubric.design/ux/accessibility.video-captions-transcripts) · Usually critical · Provide synchronized closed captions for every prerecorded video that has a soundtrack, including speaker identification and non-speech sounds that carry…
- [Cancellation terms are stated before payment, not after](https://rubric.design/ux/auth.cancellation-policy-disclosed-before-payment) · Usually critical · State the cancellation policy — how to cancel, whether it can be done anytime, and what happens to access after cancelling — on the plan selection or payment…
- [Guest checkout available without account creation](https://rubric.design/ux/checkout.guest-option) · Usually critical · Offer guest checkout as an equally weighted option at the first step of checkout, presented alongside sign-in rather than beneath it, and let it reach payment…
- [Pages have a descriptive title and a logical heading hierarchy](https://rubric.design/ux/accessibility.heading-structure) · Usually high · Give every page a unique \<title> that identifies its specific content, with the page-specific part first (WCAG 2.2 SC 2.4.2).
