Sign-In Form
A form that collects account details for sign-in. It must support recovery, password managers, clear errors, and secure sending.
A real example
A returning customer signs in with email and password. They can show the password, paste it from a password manager, or recover access without losing their place.
Main parts
- 01Persistent label
- 02Input control
- 03Hint or format
- 04Validation message
Use it when
Use a focused page with correct autocomplete values and clear links for account recovery and sign-up.
Do not use it when
Do not block paste, reveal whether an account exists, or clear valid entries after a fixable error. Do not hide password rules.
Name used in code
form + autocomplete=username/current-password + POST over HTTPS Before you ship
Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages.
Outcome: Use Sign-In Form to solve this user need without losing the current context. User context: A returning customer signs in with email and password. They can show the password, paste it from a password manager, or recover access without losing their place. Recommended pattern: Sign-In Form. Why it fits: Use a focused page with correct autocomplete values and clear links for account recovery and sign-up. Do not use it when: Do not block paste, reveal whether an account exists, or clear valid entries after a fixable error. Do not hide password rules. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Sign-In Form. Definition: A form that collects account details for sign-in. It must support recovery, password managers, clear errors, and secure sending. Release checks: Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.