A keyboard-only review checks whether people can reach and operate the page’s links, fields and interactive controls without a mouse. Start from the public page and follow real tasks. This is a practical check, not a complete accessibility certification; it can still reveal important problems that a screenshot cannot show.

Choose realistic tasks before testing

Identify the main destination, navigation, form and any tabs, accordion, slider or popup a visitor may use. Load the public page in a fresh session. Keep the mouse aside so the review does not accidentally skip a control that is difficult to reach from the keyboard.

Follow the focus order

Use Tab and the supported reverse-tab command to move through controls. Check that the visible focus indicator is easy to find and the sequence follows a sensible reading order. A control technically receiving focus is not enough if the person cannot see where they are.

Activate the relevant controls

Use the supported activation behavior for links, buttons and fields. Test tabs and accordions rather than assuming they behave identically to another component. Confirm that the content or destination changes as expected and that expanded information remains understandable in the page sequence.

Check overlays and return paths

Open any modal or popup and verify that its available closing route is reachable. Check the supported Escape behavior where provided. After closing, make sure the person can continue their task rather than getting lost at the top of the page or trapped behind an overlay.

Record concrete failures and retest

Write down the exact control, sequence and observed problem. Repeat the task at a narrow width, where hidden menus or changed layouts may introduce different controls. Fix the issue in the responsible component and test the original sequence again rather than checking only the control’s appearance.

Before you finish

  • Focus is visible throughout the task.
  • The order is understandable.
  • Controls perform their intended actions.
  • Overlays have usable closing and return paths.

Questions and answers

Does passing a keyboard check prove the whole page is accessible?

No. It is one useful part of a broader review that may include assistive technology, content, contrast and other requirements.

Should every interactive block use identical keyboard shortcuts?

No. Verify the behavior appropriate to the component and ensure its controls are reachable and understandable without relying on a mouse.

Sources and scope

This guide uses Blockenberg’s documented editor workflows and block definitions available on November 1, 2026. Labels and provider availability can change. Test the result with your theme and plugins.

AI-assisted draft, checked against product sources. Examples are illustrative; they are not customer results or performance guarantees.