-
Notifications
You must be signed in to change notification settings - Fork 21
2.4.3
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
When there are interactive elements (links, form elements or other interactive objects).
Tab through the page.
If the focus is not visible use Show tab focus bookmarklet or Show keyboard focus bookmarklet or caret browsing (in Firefox via "Always use the cursor keys to navigate within page" under 'Preferences > Browsing').
Check:
- the order makes sense - it should follow the visual order but does not need to have exactly the same order as long as the focus order doesn't change meaning or functionality
You can still check if the order of invisible elements makes sense, but it might not be practical.
Make sure Javascript is turned on.
Check:
- inserted content comes directly after the triggering element - for example, if selecting a radio button that reveals additional fields, those fields should appear immediately after the radio button
- if clicking on a link or a button reveals new content, focus moves immediately or after the next tab to the right place
- either to the new content
- or to the top of the page if appropriate, for example if most of the page changed in a Single Page Application
- if closing a modal window, what's focused next comes after the initial trigger
Note: If you can tab further behind a modal window, that's bad accessibility but not a WCAG fail (unless you cannot close the window again with keyboard only).
Use an external keyboard.