Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 38 ยท Testing Tools and Audits

Manual Testing: Keyboard, Zoom and Inspection

A practical 15-minute manual accessibility test: keyboard-only walkthrough, focus visibility, zoom and reflow, grayscale, reduced motion and the accessibility tree.

Manual testing is where you find what automation cannot: confusing order, invisible focus, broken widgets, and text that makes no sense out of context. You do not need special skills to start. A mouse-free walk through your page, plus a few quick browser settings, catches a large share of the serious barriers in about fifteen minutes.

The 15-minute routine

  1. Keyboard walkthrough (5 minutes).
  2. Zoom and reflow (2 minutes).
  3. Visual checks: grayscale, contrast, motion (3 minutes).
  4. Structure check in DevTools: headings, landmarks, names (3 minutes).
  5. Forms and dynamic parts (2 minutes).

Do this on each key template, not just the home page.

1. Keyboard walkthrough

Put the mouse aside. Use these keys:

Key Expected behavior
Tab / Shift+Tab Move to next / previous interactive element
Enter Activates links and buttons
Space Activates buttons, toggles checkboxes, scrolls page
Arrow keys Move within radios, tabs, menus, selects
Escape Closes dialogs, menus, popovers

Ask these questions as you tab through:

  • Can I reach everything that I can click? (Custom divs with click handlers often cannot be reached.)
  • Is the focus always visible? (2.4.7 Focus Visible; WCAG 2.2 2.4.11 says it must not be hidden behind sticky headers.)
  • Does the focus order match the visual and logical order?
  • Is there a skip link that jumps past repeated navigation?
  • Can I leave every widget? (No keyboard traps, 2.1.2.)
  • After a dialog closes or content updates, is focus somewhere sensible?
  • Do links and buttons do what they should? Buttons act, links navigate.

Record each failure with the element, the key pressed and what happened.

Spot the keyboard problems

Press Tab: only the green button is reachable. The red div is a classic "works with the mouse only" bug.

2. Zoom and reflow

  • Zoom to 200% and to 400% (Ctrl and plus). Content must stay readable with no overlap and, at 400%, no horizontal page scroll.
  • Check that sticky headers do not swallow half the screen.
  • Increase the browser's default font size and reload.

See text resize and reflow for the criteria.

3. Visual checks

  • Grayscale (OS setting or DevTools): is any information carried only by color?
  • Contrast: use the DevTools color picker or a contrast checker for text and UI borders.
  • Reduced motion: DevTools > Rendering > "Emulate CSS prefers-reduced-motion". Does animation calm down?
  • High contrast / forced colors: Windows contrast themes (emulate in Rendering). Icons and borders that rely on backgrounds can vanish; use real borders and currentColor.
  • Dark mode if you offer it.

4. Structure check in DevTools

Open the Accessibility panel (Chrome: Elements > Accessibility). Inspect:

  • The name and role of controls: does the icon button say "Close" rather than nothing?
  • The heading outline: one h1, no skipped levels, headings describe sections.
  • Landmarks: header, nav, main, footer, with labels when there are two navs.
  • The page title and lang attribute.

A quick console snippet lists headings:

JavaScript
[...document.querySelectorAll('h1,h2,h3,h4,h5,h6')]
  .map(h => h.tagName + ': ' + h.textContent.trim())
  .join('\n');

You can also use the built-in "Show accessibility tree" in Firefox or the Accessibility Insights extension for a visual overview.

List headings and landmarks of a snippet

The scan flags the jump from h2 to h4, a common outline error.

5. Forms and dynamic parts

  • Submit an empty form. Are errors described in text and reachable?
  • Open every menu, dialog and accordion with the keyboard.
  • Trigger loading and success messages: is anything announced? (See live regions.)
  • Check that links make sense out of context ("Read more" repeated ten times does not).
  • Resize the window to phone width and test touch targets.

Write findings so they get fixed

A useful bug report has:

  1. Where: URL and element.
  2. What: the failure, in plain words.
  3. Who it affects and which WCAG criterion (for example, 2.1.1 Keyboard).
  4. Steps to reproduce and the expected result.
  5. Suggested fix if you know one, and a severity.
flowchart TD
  A["Tab through the page"] --> B["Zoom 200 and 400 percent"]
  B --> C["Grayscale, contrast, reduced motion"]
  C --> D["Inspect headings, landmarks, names"]
  D --> E["Forms and widgets"]
  E --> F["Write up findings with criteria and steps"]

Repeat for each key template.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which key activates a native button but is also used to scroll the page when nothing is focused?

    Space activates buttons and toggles checkboxes; on a non-interactive page it scrolls.
  2. 2. A clickable div cannot be reached with Tab. What is the best fix?

    A real button gets focus, keyboard activation and the right role for free.
  3. 3. At what viewport width (CSS px) should content reflow without sideways scrolling?

    400 percent zoom corresponds to a 320 CSS pixel wide viewport.
  4. 4. Why test in grayscale?

    If something disappears when color is removed, it relied on color only.

Summary

  • A 15-minute manual routine catches many barriers: keyboard, zoom, visual modes, structure and forms.
  • Keyboard testing checks reachability, visible focus, order, no traps and sensible focus after changes.
  • Use DevTools to inspect names, roles, headings and landmarks.
  • Report findings with location, criterion, steps and suggested fix.

Next: Testing with Screen Readers