Follow the task with a keyboard
Start at the top of a page and use Tab, Shift+Tab, Enter and Space. You should be able to tell which control has focus, activate it and recover from an error. Keep the browser’s focus indicator or provide a visible one that works on every surface it crosses. Focus Visible and Focus Not Obscured (Minimum) are separate WCAG 2.2 AA criteria. A sticky footer can entirely cover a focused control even when its ring would otherwise be visible.
:focus-visible {
outline: 2px solid currentColor;
outline-offset: 2px;
}This example uses the element’s current text colour. Verify that the outline stands out against its adjacent colours in the actual layout, including both themes. The browser uses input and element heuristics for the focus-visible selector. It can show a ring on a text field clicked with a mouse. The 3:1 requirement for an authored visual cue comes from Non-text Contrast where the cue is needed to identify the state. The separate Focus Appearance criterion adds size and contrast-change requirements at level AAA.
Check zoom and reflow separately
Resize Text checks that covered text can reach 200% without losing content or functionality. Try increasing the text size and completing a form. Fixed-height containers can clip larger text.
Reflow checks that vertically scrolling content works at the equivalent of 320 CSS pixels wide without losing content or requiring scrolling in two dimensions. For horizontally scrolling content the check uses a height of 256 CSS pixels. Some content needs a two-dimensional layout for its meaning or use, such as a map. Keep any necessary scrolling within the relevant content area when possible.
A useful desktop check starts with a 1,280 CSS pixel content viewport at 100% browser zoom, then moves to 400%. Verify the resulting content width and complete the same task. At narrow widths, make long text and form controls fit, and give an essential wide table its own scroll region.
Keep navigation and labels clear
CSS can move items visually without changing the underlying navigation sequence. Keep the order of controls meaningful at each breakpoint. Walk the sequence on the finished page rather than inferring it from a mockup.
Give fields persistent labels, programmatically associated with the inputs. A placeholder can provide an example and will disappear when the learner types. A correctly associated label on a checkbox lets the user click the words as well as the checkbox. Use that larger hit area and check the label still reads clearly when a field contains an error.
Describe what an image contributes
For an informative photograph, describe the detail the learner needs. For a standalone logo linked home, name the link’s destination. Decorative and redundant images can use empty alternative text. For a chart, provide a short description and a nearby text summary or table that conveys the important data. W3C’s image decision tree gives examples.
Test a whole journey
Start with a school sign-up form. Complete it by keyboard at 400% browser zoom. Check that you can read each label, find the active control, receive an error message and recover. Repeat with VoiceOver, TalkBack or NVDA on a device you have. An automated check can identify some defects. Use manual testing to check whether the reading order and feedback make sense.
Check your understanding
At 400% zoom, Tab reaches the Continue button, but a sticky footer completely covers it. What should the team fix?
Pick the one you would defend. Your answer stays private.
Your place and first choices stay on this browser. Classroom credit is recorded separately.
Stuck on something?Ask Meher, your AI tutor