Skip to main content
Ihr Browser ist zu alt, um diese Website korrekt anzuzeigen. Bitte aktualisieren Sie auf die neueste Version von Chrome, Edge, Firefox oder Safari.
Back to WCAG Database
Level AWCAG 2.0

3.2.1 On Focus

When any user interface component receives focus, it does not initiate a change of context.

Last reviewed: September 9, 2026

Understanding 3.2.1

This criterion exists so that keyboard users and screen reader users, who typically move focus sequentially through a page (for example with Tab), are not disoriented by unexpected changes triggered simply by landing on a control. If merely focusing an element could submit a form, open a new window, or move focus elsewhere, users exploring a page would trigger actions they never intended. This especially affects people with visual or cognitive disabilities who may not immediately notice that the context has changed.

How to Meet It

Never trigger navigation, form submission, popups, or additional focus changes purely from a focus event (an onfocus handler or :focus state). Reserve those actions for explicit activation, such as onclick, a deliberate onchange after a selection, or pressing Enter/Space. Verify by tabbing through every interactive control on a page without pressing Enter or Space, and confirming that nothing changes context.

Code Examples

INCORRECT
<a href="#" onfocus="window.location='page2.html'">Continue</a>
<!-- Navigates away purely because the link received focus, disorienting keyboard users tabbing through the page -->
CORRECT
<a href="page2.html">Continue</a>
<!-- Navigation only happens on explicit activation (click, or Enter/Space while focused) -->

Frequently Asked Questions

Does showing a tooltip or expanding a hint when a field receives focus violate 3.2.1?

No. Displaying supplementary content in place, such as a tooltip or format hint, is not a "change of context" as WCAG defines it. A change of context means things like focus moving elsewhere, a new window opening, or a form submitting, not additional content appearing near the focused control.

Related Success Criteria

3.2.2 On Input3.2.3 Consistent Navigation3.2.4 Consistent Identification3.2.5 Change on Request

Quick Facts

  • Criterion3.2.1
  • LevelA
  • IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 3.2.1 issues in your codebase.

Try Scanner Free