Test a real task

Digital accessibility testing worksheet

Work through 16 practical checks. Record what you tried, what happened and what needs to change, then keep a report your team can reproduce.

These are manual observations, not an automated scan or a WCAG conformance score. No website is fetched or tested when you enter its address.

Set up your review

Keep the test specific

  1. Choose a page and task, such as finding a course or completing a form.
  2. Use a test account and non-sensitive sample data. Record the browser and assistive technology you actually use.
  3. Try each relevant check. Record steps and evidence; use “Not checked” when you cannot test something.
  4. Retest fixes and include people with disabilities in broader evaluation.

Interpret your observations

“No issue found” describes this test in this environment. “Not applicable” needs a reason, such as no video in the reviewed task. An untested check is not evidence that a page is accessible.

Use the linked WCAG 2.2 guidance for requirements, exceptions and deeper evaluation. This worksheet does not cover every criterion, page, process or assistive-technology combination.

Review details and manual observations

Review details

All fields are optional. Include enough detail to repeat the test. Entries stay in this page unless you choose Save or Download.

Your review progress

0 of 16 checks recorded. 16 not checked.

Progress tracks recorded observations, including “Not applicable”. It is not a compliance percentage.

Keyboard and pointer

01. Complete a task without a mouse

Try this: Choose a realistic task. Use Tab and Shift+Tab to move, Enter to follow links, and Space or Enter for buttons. Try menus, dialogs and any custom widgets using their documented keys. Move away from each component again.

Look for: The task can be completed with a keyboard. Focus does not become trapped; any nonstandard way to leave a component is explained.

WCAG 2.2: 2.1.1 Keyboard (A) · 2.1.2 No Keyboard Trap (A)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

02. Follow focus through the page

Try this: Tab forward and backward through a task, including opened menus or dialogs. Check where focus goes after opening and closing them. Repeat near sticky headers, banners and the bottom of the viewport.

Look for: The order preserves meaning and operation, with a visible focus indicator. Author-created content does not entirely hide the focused control. For user-opened content, check whether the control can be revealed without advancing focus; assess user-movable content in its initial position.

WCAG 2.2: 2.4.3 Focus Order (A) · 2.4.7 Focus Visible (AA) · 2.4.11 Focus Not Obscured (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

03. Skip repeated navigation

Try this: Start at the top of two pages with the same navigation. Look for a keyboard-operated skip link or another effective bypass mechanism. Activate it and continue navigating the main content.

Look for: A mechanism lets users bypass repeated blocks. If a skip link is used, it takes keyboard navigation to the intended content rather than only scrolling the page.

WCAG 2.2: 2.4.1 Bypass Blocks (A)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

04. Inspect small pointer targets

Try this: Inspect small icon buttons, pagination and controls at normal zoom. Measure the clickable area in CSS pixels, including padding. For undersized targets, inspect surrounding space and the exceptions in the linked criterion.

Look for: Targets meet 24 by 24 CSS pixels, or satisfy a permitted spacing or other exception. Do not automatically fail an inline text link; record the applicable exception and evidence.

WCAG 2.2: 2.5.8 Target Size (Minimum) (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

Structure and meaning

05. Identify the page from its title

Try this: Read the browser-tab title, then open another page in the same service. If using a screen reader, listen to its announcement when the new document opens.

Look for: Each title identifies the page topic or purpose. Similar pages have enough context to distinguish them.

WCAG 2.2: 2.4.2 Page Titled (A)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

06. Compare visual and semantic structure

Try this: Use a screen reader heading list or the browser accessibility tree to inspect headings. Read a sample list and data table. Compare announced relationships with the visible grouping and table headers.

Look for: Structure and relationships shown visually are available programmatically or in text. Headings identify their sections; lists and table headers retain their meaning.

WCAG 2.2: 1.3.1 Info and Relationships (A) · 2.4.6 Headings and Labels (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

07. Check image purpose in context

Try this: Read each informative image with its surrounding text. Inspect its accessible alternative; for image links or buttons, test the action name. Check how decorative images are exposed. For a chart, locate an equivalent description or data.

Look for: Alternatives convey the information or function needed in this context. Decoration can be ignored by assistive technology. Complex information is available beyond a short image label.

WCAG 2.2: 1.1.1 Non-text Content (A)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

Try this: Review links in their sentence, paragraph, list item or associated table context. Try repeated “read more” links and icon-only links. Compare the accessible name with the destination or action.

Look for: The link purpose is clear from its text alone or its programmatically associated context. Ambiguous links are not dependent only on nearby visual positioning.

WCAG 2.2: 2.4.4 Link Purpose (In Context) (A)

Forms and feedback

09. Understand each field before entry

Try this: Review the form while empty, then while populated. Focus each field with a screen reader or inspect its accessible name. Check grouped choices, required indicators and any expected format instructions.

Look for: Labels or instructions explain the expected input and remain available when needed. Programmatic names and groups match the visible meaning; placeholders are not the only label.

WCAG 2.2: 3.3.2 Labels or Instructions (A) · 1.3.1 Info and Relationships (A) · 4.1.2 Name, Role, Value (A)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

10. Recover from an input error

Try this: In an authorized test environment, leave a required field blank or enter an invalid format, then submit. Locate the error using both keyboard and screen reader. Correct it and try again.

Look for: Detected errors identify the affected input and explain the problem in text. A correction suggestion is provided when known, unless it would compromise security or purpose.

WCAG 2.2: 3.3.1 Error Identification (A) · 3.3.3 Error Suggestion (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

11. Hear updates without moving focus

Try this: With a screen reader running, trigger an update such as a search-result count or an item added to a cart in a test flow. Keep focus on the initiating control and note what is announced.

Look for: Relevant status messages are exposed to assistive technology without receiving focus. Their meaning includes enough context; routine updates do not unnecessarily interrupt ongoing speech.

WCAG 2.2: 4.1.3 Status Messages (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

12. Try assisted sign-in

Try this: Use a test account to check sign-in, password reset and verification steps. Try a password manager and pasting a password or code. Inspect any memory, puzzle or transcription task and the available alternative or assistance.

Look for: A cognitive-function test is not the only route unless a criterion exception applies. Document the mechanism or alternative that removes the memory or transcription burden, and test it.

WCAG 2.2: 3.3.8 Accessible Authentication (Minimum) (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

Zoom, color and media

13. Use the page at a narrow width

Try this: At a 1280 CSS-pixel-wide desktop viewport, zoom to 400%, or test a viewport 320 CSS pixels wide. Complete the same task. Inspect clipped labels, dialogs and controls; note any content requiring two-dimensional layout.

Look for: For vertically scrolling content, information and functions remain available without scrolling in two dimensions at 320 CSS pixels. Content such as a data table may need two-dimensional layout; inspect the rest of the page separately.

WCAG 2.2: 1.4.10 Reflow (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

14. Measure text contrast in every state

Try this: Use a contrast tool to sample text and its actual background in default, focus, hover and error states, including each supported theme. Record both colors, ratio, text size and weight. Inspect gradients at their weakest area.

Look for: Ordinary text reaches 4.5:1; large text reaches 3:1. Large means at least 18 pt, or 14 pt bold. Check the criterion exceptions, including inactive controls and incidental text, before recording a finding.

WCAG 2.2: 1.4.3 Contrast (Minimum) (AA)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

15. Review prerecorded video captions

Try this: Play a prerecorded video with sound, then review it with sound muted and captions enabled. Compare the captions with speech, speaker changes and sounds needed to understand the content. Test player controls by keyboard.

Look for: Captions communicate the meaningful audio and align with the video. Automatic captions need review for names, terminology and timing. The criterion includes an exception for clearly labeled media alternatives to text.

WCAG 2.2: 1.2.2 Captions (Prerecorded) (A) · 2.1.1 Keyboard (A)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

16. Pause moving and updating content

Try this: Look for carousels, tickers, animations and auto-updating regions that start without a request. Check their duration and whether they appear alongside other content. Try pause, stop, hide or update-frequency controls where applicable.

Look for: Automatically moving, blinking or scrolling content lasting more than five seconds alongside other content has a pause, stop or hide mechanism unless essential. Auto-updating content has a mechanism to control it unless essential.

WCAG 2.2: 2.2.2 Pause, Stop, Hide (A)

Record the element, exact steps, observed behavior and proposed action, or explain why this check does not apply.

Digital accessibility review report

Turn observations into better experiences

Practice focus and status behavior in the interaction lab, improve alternatives with the alt-text lab, and measure colors with the contrast checker.

For a broader evaluation, use the WCAG 2.2 Quick Reference and W3C WAI evaluation guidance. References checked September 2026.