spec 1 linked patterns checked
WAI WCAG Understanding: Focus Visible
Explains that keyboard-operable interfaces need a mode where the keyboard focus indicator is visible so users can identify the focused element.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Focus traversal | Choose focus traversal when the design problem is the user's sequential path through focusable elements and dynamic state changes. | The sequential focus path follows DOM and reading order unless a well-tested component-specific model declares a different internal focus contract. | Supports visible focus indicators for keyboard-operable controls. |
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: W3C WAI. Last checked: .