Supporting navigation with keyboards and assistive technology means ensuring that core functions work without a mouse, clearly showing keyboard focus, and enabling screen readers to identify page structure, control names, and states. Start with native HTML that provides the required semantics and behavior. Provide clear labels, logical heading levels, and a link to skip to the main content, then test with a keyboard and screen reader. Adding ARIA attributes alone does not mean accessibility support is complete.
Let users reach controls and complete actions
Keyboard navigation involves more than moving through items one by one. Some users with motor or visual disabilities rely on keyboards, so links, buttons, forms, and other core interactions should work without a mouse and clearly indicate the current position and available actions.
- Links should be focusable using the Tab key, and form fields should be usable without a mouse.
- Buttons and fields need clear labels so users know what to enter in a field and what will happen when they activate a button.
- For tabbed interfaces, NN/g recommends supporting keyboard navigation, using Enter or Space to select a tab, and providing a high-contrast focus indicator. These recommendations apply to tab components and should not be treated as universal keyboard rules for all components.
Give elements the right semantics before adding ARIA
Looking like a button does not mean assistive technology will recognize an element as one. For example, a div with only visual styling does not automatically have a button role in the accessibility tree. Prioritize native buttons, links, and selection controls, and give every control a clear accessible name, including icon-only buttons.
ARIA should supply necessary information that native HTML cannot express, rather than replace correct markup. W3C’s principle is to prefer native elements when they already provide the required semantics and behavior. Incorrect or empty ARIA attributes may convey misleading information, so verify the roles, names, and states actually exposed to assistive technology.
Shorten navigation paths with headings and a skip link
Screen readers announce headings and their levels, and users can use keyboard shortcuts to move between sections. Headings should therefore reflect the logical relationship between topics and subtopics—for example, using h2 for main sections and h3 for their subsections—rather than choosing levels solely by font size.
A “Skip to main content” link can also be added at the top of each page, allowing keyboard users to bypass repeated navigation menus instead of tabbing through every item whenever they open a page. Skip links bypass repeated blocks, while heading navigation helps users find content sections; the two complement each other.
Cross-check hands-on testing against the accessibility tree
Test with both a keyboard and a screen reader, and inspect important controls in the accessibility panel of the browser’s developer tools. For form submission, for example, verify that fields can be used without a mouse, the submit button has a clear name, and the accessibility tree shows the correct role. You can start with high-traffic pages and work through them to fix controls with missing names and unlabeled input fields.
Navigation with keyboards and assistive technology: perspectives from across the web
When do dynamic content and complex interactions need ARIA?
When native HTML cannot express necessary information, consider using ARIA to supplement component roles, states, or information about dynamic regions. For example, assistive technology may need to recognize content updated on a page. The principle cited from W3C still applies: prefer native elements when they already provide the required semantics and behavior. After adding attributes, verify that the information is correct; ARIA is not a guarantee that the required functionality has been implemented.
How can you check what information assistive technology can actually recognize?
You can select an element in the browser’s developer tools to inspect its computed role, name, and state. You can also use Playwright’s ARIA snapshot to inspect roles, accessible names, states, and nesting in the page’s accessibility tree. This can help uncover issues such as important actions lacking names, but it should still be combined with hands-on keyboard and screen reader testing rather than relying solely on the tree to determine whether an interaction is usable.
Besides keyboard controls, should you consider how much time users have?
Yes. Even when a feature works with a keyboard, users still need enough time to read the content and complete their tasks. The cited source lists both keyboard accessibility and sufficient time as considerations for operability. When reviewing navigation flows, check whether people who rely on keyboards or assistive technology have enough time. The source does not specify time limits or adjustment mechanisms, so it cannot be used to set a universal time allowance.
References
- AI Browsers Are Backward Because Agents Never Needed The Visual Layerwww.searchenginejournal.com · 2026-07-23T19:00:39+00:00 — Source used in the article above.
- The Accessibility Tree Is How AI Agents Read Your Site & It’s Breakingwww.searchenginejournal.com · 2026-06-24T15:00:13+00:00 — Discusses: When do dynamic content and complex interactions need ARIA?; How can you check what information assistive technology can actually recognize?
- 10 Best Practices to Follow for a Truly Accessible Websiteneilpatel.com · 2023-01-05T20:00:00+00:00 — Discusses: How can you check what information assistive technology can actually recognize?
- WAI-ARIA, 決定未來 SEO 的 25 項標準與通訊協定系列 IIIithelp.ithome.com.tw — Discusses: When do dynamic content and complex interactions need ARIA?
- Tabs, Used Rightwww.nngroup.com · 2024-08-02T17:00:00+0000 — Source used in the article above.
- 無障礙網頁設計:符合WCAG 2.1的實戰指南tenten.co · 2024-12-09T05:05:25.000Z — Discusses: Besides keyboard controls, should you consider how much time users have?
- What Are Heading Tags? & Why They're Important for SEOwww.semrush.com · 2025-06-13T07:35:00Z — Source used in the article above.
- Common UX Accessibility Mistakes Found on Websitesneilpatel.com · 2022-09-30T19:00:00+00:00 — Source used in the article above.
- Check Website Accessibility: Manual Checks and Tools to Use in 2025www.semrush.com · 2024-02-14T13:51:00Z — Source used in the article above.



