WCAG 2.2 success criterion 3.2.1, On Focus, is a Level A requirement: focusing an element does not change context.
Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).
How BearScan checks it
Focusing an element does not change context
Checked automatically: clicks through the page. Severity: medium. A keyboard user tabbing through a page cannot avoid focusing each control. If focus alone submits a form or opens a new page, they lose their place.
An approximation: A browser presses Tab through the page, doing nothing else, and watches for the page navigating or opening a window. Either one is caused by focus alone. A focus handler that opens an in-page dialog, submits nothing visible or moves focus elsewhere is not detected, and a stop is not checked until Tab lands on it.
How to fix it. Only change context on an explicit action such as click, Enter or a submit button, never on focus.
All WCAG 2.2 criteria · Next: 3.2.2 On Input
Questions
Is WCAG 3.2.1 required by the ADA?
The ADA doesn't name a technical standard for businesses, but the Justice Department's 2022 guidance points businesses to WCAG, and its 2024 rule for state and local governments adopted WCAG 2.1 Level AA, which includes 3.2.1.
Can an automated tool check WCAG 3.2.1?
Mostly. BearScan checks it automatically (clicks through the page). A clean result still isn't proof every page passes, only the pages scanned.
How do I fix a WCAG 3.2.1 failure?
Only change context on an explicit action such as click, Enter or a submit button, never on focus.