Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. Understand focus and order
  2. Dialogs need an entrance and a return path
  3. Who checks it

Keyboard access and semantics: navigate without a mouse

Understand focus, navigation order, and semantics, and why menus, forms, and dialogs need keyboard and assistive-technology support.

Not every customer uses a mouse. Some use a keyboard; others listen through a screen reader. The page needs to communicate their position, available actions, and what happens next.

Semantics means describing content roles through web structure: headings, navigation, buttons, and fields. Similar-looking content can have different roles in code. A screenshot alone cannot verify those structures.

Understand focus and order

Focus is the location currently receiving keyboard input, usually shown by a visible outline or another indicator. Tab moves between many controls; Shift+Tab moves back. Different controls have their own appropriate keyboard behaviors.

Check Why it matters
Visible focus Customers know which control they are using
Sensible order They do not jump unpredictably around the page
Clear names They can distinguish booking a consultation from downloading information
Opening and closing They can leave menus and dialogs after entering

A text link should be a real link, a submission should use an appropriate button, and a field needs an associated label. These choices let browsers and assistive technology provide suitable behavior, beyond making text look clickable.

Dialogs need an entrance and a return path

When a dialog opens, focus moves to a suitable position inside. Closing usually returns it to the opener. A modal dialog keeps background content inactive while open. Provide appropriate closing keys and a visible close button so customers do not become trapped.

For example, someone opening an enlarged price illustration with a keyboard should return near their reading position after closing it. They should not need to search again from the top. See overlays and enlarged images .

Who checks it

You can try finding a service, opening a menu, and completing an inquiry without a mouse. Record where you become stuck. The team also checks web structure, accessible names, and behavior. A quick keyboard trial is not a complete accessibility assessment.

Heading structure and reading order also need to agree with the typography . For implementation guidance, see the W3C page structure tutorial .

Keyboard behavior and page structure are part of the implementation to agree in our website design and development service . Bring the customer tasks that matter most, and we will explain how they will be checked.