Keyboard navigation is an everyday way of using the web for many people. It also offers a useful perspective on the structure of a page.
Use the Tab key to move through interactive elements and look for a visible focus indicator. The order should make sense, and a dialog should offer a clear way to close it.
A page that works through more than one input method is more adaptable. Accessibility is part of the experience rather than an extra feature added at the end.
- Follow the page’s tab order.
- Look for a visible focus indicator.
- Open and close an interactive panel.
Imagine a practical setting.
A visitor closing a dialog needs a sensible place to continue. Returning focus to the control that opened it preserves the surrounding task.
Before the next experiment.
A page has relationships as well as appearances. Make sure its structure still communicates those relationships when the layout changes or decoration disappears.
Follow a related question
Connect the permission to an app feature.
Permissions should have a purposeRecord the actual steps of a task.
A workflow worth simplifyingKeep learning
Related background to continue exploring this subject.
W3C: web accessibility W3C: understanding accessibility criteria

