Make keyboard navigation faster and more inclusive
Keyboard navigation lets people reach and operate every interactive element without a mouse or trackpad. On an information website, links, menus, search controls, forms and media controls must remain understandable when users move with Tab, Shift+Tab, Enter, Space and arrow keys.
Australian visitors use varied devices: some browse on a laptop at home, while others check a service during a train or tram journey or on a phone with a limited connection. Clear focus order, visible focus indicators and predictable controls improve access for everyone, particularly people with motor, vision or cognitive disabilities.
Build a logical, predictable page structure
Start with semantic HTML. Use an anchor for navigation, a button for an action and a form control for data entry. CSS may change their appearance, but not their purpose. Arrange elements in the DOM in the order readers are likely to need them, because focus normally follows source order.
Use one page title, a sensible H1 and a hierarchy of H2 and H3 headings. Mark major regions with header, nav, main and footer elements. Place a “Skip to main content” link at the start of the header so keyboard users can bypass repeated navigation.
Never use headings merely to resize text. Heading levels form an outline for people navigating by headings, so each should describe its section and give automated tools a clearer view of the content.
Make focus visible and easy to follow
Every interactive element needs a clear focus state. Keep the native outline where possible, or use :focus-visible to create a high-contrast ring that avoids distracting mouse users. Never remove the outline without an equally visible replacement; colour alone should not be the only cue.
WCAG 2.2 AA includes a 24 by 24 CSS pixel minimum target size, with exceptions such as inline text links. Australian government teams can use the Digital Service Standard and WCAG guidance as benchmarks, while the Disability Discrimination Act 1992 and related state and territory laws make accessibility relevant to many services.
Test focus styling in light and dark themes, at high zoom and with reduced motion. The indicator should appear immediately and remain obvious, even if the next keypress is delayed.
Support familiar keyboard behaviour
Users carry expectations from operating systems and everyday software. Preserve them instead of inventing a different interaction model for every component.
- Links activate with Enter and move to a destination.
- Buttons activate with Enter or Space without navigating.
- Tab moves forward; Shift+Tab moves backward.
- Arrow keys move within menus, radio groups and tabs.
- Escape closes a dialog, menu or temporary layer when allowed.
Prefer native activation. If a custom element must respond to keys, use the appropriate ARIA role, update its state and follow the expected pattern. Avoid broad keydown handlers that fire while someone is typing. Escape should restore focus sensibly after closing a temporary layer.
Compare pointer and keyboard paths
A familiar control can serve pointer and keyboard users through one implementation. Compare major actions before creating separate code paths.
| Action | Pointer path | Keyboard path | Key check |
|---|---|---|---|
| Move between controls | Click or tap | Tab or Shift+Tab | Order matches the reading flow |
| Open a link | Select it | Enter on the focused link | Destination is clear |
| Run an action | Click a button | Enter or Space | No accidental submission |
| Choose an option | Click a radio button | Arrow keys within the group | Selection is announced |
| Dismiss a dialog | Use the close control | Escape or activate the control | Focus returns to the opener |
Avoid positive tabindex values because they create a focus order separate from the visual and reading order. At narrow widths, a focused control appearing left of its neighbour often reveals an order problem.
Australian sites serve residents of Sydney, Melbourne, Brisbane, Perth and regional towns across different devices and connection speeds. Shared patterns should remain clear when a page loads slowly, the viewport changes or a visitor resumes a task after an interruption.
Handle widgets, dialogs, and dynamic content
Composite controls need clear relationships between their parts. Prefer a native select, details element or radio group when suitable. For custom tabs, accordions and menus, manage focus, expose selected and expanded states, and support arrow keys. ARIA describes a pattern but cannot repair broken focus logic.
Move focus into a dialog when it opens, keep Tab within it while modal, and return focus to the opener. Give the close button an accessible name. If the dialog contains substantial content, use a heading so screen-reader users can identify it.
For updates without a page reload, use a restrained live region when the change matters. Do not announce decorative changes or repeatedly move focus. After a failed submission, move focus to an error summary or first invalid field, explain the problem and preserve submitted values for correction.
Test real journeys and prevent regressions
Start each review by unplugging the mouse. Travel from the page top to the footer, complete the main form, open and close overlays, and use browser navigation. Record where focus disappears, jumps unexpectedly or becomes invisible.
- Confirm that every visible control can be reached.
- Check that focus order matches the visual reading order.
- Verify that Enter, Space, arrows and Escape behave as expected.
- Use browser zoom and a narrow viewport without losing controls.
- Check the page with a screen reader and at least one keyboard.
Test with NVDA, VoiceOver or JAWS, then correct missing labels, unclear button names and inconsistent announcements. Automated checks cannot judge whether the focus sequence makes sense, so include keyboard-only users in usability sessions where possible. Australian English screen readers also benefit from plain labels and consistent terminology.
Performance belongs in the same audit because slow responses make keyboard interactions feel broken. For image-heavy pages, faster image loading can reduce waiting, while declared dimensions prevent layout shifts that move the focused control. Treat keyboard behaviour as a release criterion beside content accuracy, accessibility checks and performance monitoring, then repeat the journey after major interface changes.