Interface Core B · Official guidance Platform: Web

Focus Management

Focus management moves the keyboard's active point after the page changes. It also returns focus when a temporary surface closes.

See how it works
You might call it programmatic focusfocus placementfocus restoration

See how it works

Original worked exampleFocus Management
ACCESSIBLE UI RULEFocus Managementtrigger -> place focus -> finish or close -> restore to a sensible target
PROFILE DIALOGfocus: #display-name
OPENEREdit profile#edit-profile
OPEN DIALOG
1Display nameInitial focus#display-name
2Save changesComplete and closeEnter
Dialog closedfocus → #edit-profile
PASSFocus enters the dialog and returns to its opener.AVOIDDo not leave focus on a removed element or the page body.
trigger -> place focus -> finish or close -> restore to a sensible targetA11Y
Focus ManagementAccessible interface practice

Another example

A person opens Edit profile. Focus enters the dialog. After Save closes it, focus returns to Edit profile.

Main parts

  1. 01Triggering control
  2. 02Screen or DOM change
  3. 03Initial focus target
  4. 04Active element trace
  5. 05Close or completion event
  6. 06Return or fallback target

Use it when

Use it after opening or closing a dialog, deleting an item, or changing a route. Choose the next useful target first.

Do not use it when

Do not move focus for every small update. Unexpected jumps can make keyboard and screen-reader users lose their place.

Name used in code

trigger -> place focus -> finish or close -> restore to a sensible target

Before you ship

Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery.

Request you can copy

Outcome: Use Focus Management to solve this user need without losing the current context. User context: A person opens Edit profile. Focus enters the dialog. After Save closes it, focus returns to Edit profile. Recommended pattern: Focus Management. Why it fits: Use it after opening or closing a dialog, deleting an item, or changing a route. Choose the next useful target first. Do not use it when: Do not move focus for every small update. Unexpected jumps can make keyboard and screen-reader users lose their place. 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 Focus Management. Definition: Focus management moves the keyboard's active point after the page changes. It also returns focus when a temporary surface closes. Release checks: Give assistive tools the control’s name (accessible name), purpose (role), value, and state. Check keyboard use, visible focus, target size, disabled and busy states, feedback, and recovery. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

B
How official is this term?

Official guidance

The named platform, framework, project, or expert group has an official guide for this term.

It is official for that source. Other platforms or teams may use the term in another way.

Scope
Non-normative WAI-ARIA Authoring Practices guidance for keeping keyboard focus visible and predictable
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · W3C WAI · stable Discernible and Predictable Keyboard Focus Scope: Non-normative APG guidance for keeping keyboard focus visible and predictable Role here: Direct term reference Source covers: canonical name, definition, interaction, keyboard behavior, accessibility Background source W3C WAI-ARIA APG — Modal Dialog Pattern Role here: Helpful background, not a definition

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.