Select your language
Select other languages

Automatic translation

Loading translator…

Magoomake your components work correctlyBack to homepage

Input "search"

Allows entering terms to search 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 terms and find content.

What to design

Show the label, field, results, filters, and clearing controls. Include initial, loading, no matches, and failure states with retry.

How it behaves

Define whether search runs on submission or while typing. Clearing empties the field without submitting and allows continued editing.

What to document in Figma

Record search scope, submission or dynamic updates, filters, pagination, and clearing. Define how to preserve the query and communicate results without moving focus unexpectedly.

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 "search" 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

Editorial extension — interaction patterns and decisions

Magoo editorial adaptation: extends the previous guidance with design, documentation, and review decisions. References support the adaptation; these scenarios do not represent executed tests or certification.

From the field to the search experience

Define the search scope: the whole site, a section, or a set of records. Keep the submitted term visible and distinguish text being edited from the query whose results are displayed.

Choose between explicit submission and updates while typing. With explicit submission, Enter and the Search button run the same search. For dynamic updates, document the delay before querying and prevent an older response from replacing results for a newer query.

Search suggestions and results are different sets. If autocomplete is present, document when suggestions appear and whether committing one only fills the field or also runs the search. Adopt a combobox pattern appropriate to the interaction.

Results, filters, and recovery

Design initial, loading, results, no matches, and query failure states. A failure must not look like a search with no results. Offer retry while preserving the term and filters.

Show result count, submitted term, and applied filters. With no results, allow editing the term or removing filters. Define whether filters update immediately or require Apply, and their effect on pagination.

Distinguish Clear search, Remove filter, and Clear all filters. Document whether clearing the field also updates results. When returning from a result, preserve the query, filters, and page when that continuity is part of the flow.

Design and implementation review

In the design, check that each result provides enough title and context to choose a destination, including on small screens. In the implementation, verify keyboard search, filters, clearing, and failure recovery while keeping focus predictable. For same-page updates, communicate a summary after the response without announcing every keystroke or rereading the full list.

Interaction Methods

Scope: the basic methods below describe the search field. Results, filters, and failure recovery are covered in the editorial extension of the Interaction design tab.

The field uses type="search" and has a label explaining what will be searched.

Mouse interaction

Keyboard interaction

Gesture interaction

Keyboard (or gesture) interaction + screen reader

Submit and clear search

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 "search"

Keyboard navigation

Screen reader on desktop

Screen reader on mobile devices

Input validation

Search activation

Additional scenarios — editorial extension

Dynamic search: out-of-order responses

Filters with no matches

Query failure and retry

Points to consider

References

Additional references for components of type Input "search".

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

Editorial extension references

USWDS — Search (external link, opens in a new tab)

W3C APG — Combobox (external link, opens in a new tab)

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.