Select your language
Select other languages

Automatic translation

Loading translator…

Magoomake your components work correctlyBack to homepage

Input "password"

Allows entering a password and switching between hidden and visible content.

For working examples and design patterns for this component, see the references tab (opens the references on this page).

COMPONENT GUIDE

Explore behaviors before defining the interface.

Quick guide for designers

Always consider the context of the application, even when the guidance follows a standard pattern. Interaction design documents intent. Behavior must be verified in the implementation.

When to use

Use to enter a password, allowing pasting and password managers.

What to design

Show a persistent label, instructions, focus, errors, and hidden or visible content. The button indicates the next action: Show password or Hide password.

How it behaves

Showing or hiding preserves the value and focus on the button without submitting the form. Do not include the password in messages or announcements.

What to document in Figma

Record rules, messages, whether the purpose is sign-in or password creation, and the button name in each state.

How to review

Check whether the purpose and states are clear on small and large screens and with zoom. Verify documented behavior in the implementation, including keyboard and screen reader use where applicable.

Full guidance

Interaction Design

Questions to ask when designing Input "password" components.

Assess each guideline according to the component's context of use.

Designing for "no interaction"

Designing for mouse use

Designing for gesture use

Designing for keyboard use

Designing for screen reader use

Designing the visibility button

Interaction Methods

The password starts hidden and the button displays "Show password".

Mouse interaction

Keyboard interaction

Gesture interaction

Keyboard (or gesture) interaction + screen reader

Show and hide the password

Gherkin

BDD (Behavior-Driven Development) methodology focusing on three pillars: User Stories, Acceptance Criteria, and Gherkin Syntax (Given, When, Then).

Scenario: Given that I am on a page containing Input "password"

Keyboard navigation

Screen reader on desktop

Screen reader on mobile devices

Input validation

Show and hide the password by keyboard

Password visibility with a desktop screen reader

Password visibility with a mobile screen reader

Points to consider

Text button and optional icons

Implementation notes and behavior decisions

  • The accessible name follows the text of the next action. In this changing-label pattern, use an action button without aria-pressed. The screen reader should not receive extra announcements containing the password.

References

Additional references for components of type Input "password".

Important:
Most references are on the course platform alongside the lessons cited in this material.

Disclaimer:
The links listed here are a curated collection of references where you can find implemented components, rather than recommendations. There is no unified implementation format and no guarantee that these links follow every design pattern. Direct questions to the teams responsible for the linked materials. Before copying a model, remember that all materials are constantly updated and that patterns, particularly proprietary ones, may change.

Field documentation

Design System

Original content by Marcelo Sales, initially used in the AccessBoost course (external link - opens in a new window). These interactions represent standard industry patterns, but may be customized in specific cases, provided there are sufficient instructions for people to understand the behavioral change.