Accessibility test case manager

Step 1 of 3

ActionInventory additional content that appears on pointer hover or keyboard focus and is controlled by the page rather than the browser.

Step 2 of 3

ActionReveal each item, attempt to dismiss it without moving pointer or focus, and move the pointer from the trigger onto the additional content.

Step 3 of 3

ActionLeave the content visible without dismissing it, then move focus or hover away and repeat at increased zoom.

Step 1 of 3

ActionPut the pointer aside, reload the page and use Tab, Shift+Tab and the expected component keys to reach every interactive function.

Step 2 of 3

ActionOperate every link, button, form control, menu, dialog, disclosure, media control, drag alternative and custom widget using its expected keyboard interaction.

Step 3 of 3

ActionRepeat for content added after loading and for opened, error, empty, loading and success states.

Step 1 of 3

ActionTab and Shift+Tab through the complete page, entering every embedded player, menu, dialog, editor and custom widget.

Step 2 of 3

ActionWhere ordinary Tab or arrow keys do not leave a component, follow any displayed keyboard instruction and test Escape or the documented exit command.

Step 3 of 3

ActionRepeat after validation errors, dynamic updates and nested overlays.

Step 1 of 3

ActionIdentify every available mechanism for bypassing blocks repeated across pages, such as a skip link, page regions, headings or another supported navigation method.

Step 2 of 3

ActionUse each bypass mechanism with the input method it supports.

Step 3 of 3

ActionCompare the available bypass mechanism on another page containing the same repeated block.

Step 1 of 3

ActionList interactive elements in the order a user needs to encounter them to preserve meaning and complete the task.

Step 2 of 3

ActionUse Tab and Shift+Tab through the page and operate controls that add, remove, reorder or reveal focusable content.

Step 3 of 3

ActionOpen menus and dialogs, trigger errors and complete navigation or submission actions while tracking focus.

Step 1 of 3

ActionUse Tab, Shift+Tab, arrow keys and other expected component keys to move focus through every operable element.

Step 2 of 3

ActionCheck focus against all backgrounds and in hover, selected, error, disabled-adjacent and responsive states.

Step 3 of 3

ActionMove focus into and out of custom widgets, menus, dialogs and content revealed dynamically.

Step 1 of 3

ActionTab forward through the page while sticky headers, cookie notices, chat controls, drawers and other author-created overlays are present.

Step 2 of 3

ActionRepeat with Shift+Tab and after opening menus, dialogs, validation messages and responsive navigation.

Step 3 of 3

ActionScroll each partially covered target into view using only ordinary keyboard navigation and activate it.

Step 1 of 3

ActionIdentify shortcuts that activate using one letter, number, punctuation mark or symbol without a modifier key.

Step 2 of 3

ActionWith focus in each relevant page context, press the inventoried shortcut and common printable characters.

Step 3 of 3

ActionFor each active shortcut, locate and test a method to turn it off, remap it to include a modifier, or restrict it to when the relevant component has focus.

Step 1 of 3

ActionInventory links in default and updated states and record each visible label, accessible name and destination or action.

Step 2 of 3

ActionDetermine each link's purpose from its link text alone or together with its programmatically associated sentence, paragraph, list item, table cell or heading context.

Step 3 of 3

ActionReview links out of visual context in a screen-reader links list and compare links with the same wording.

Step 1 of 3

ActionSelect representative pages that are not steps in, or results of, a process and record the primary way each page is reached.

Step 2 of 3

ActionFor each applicable page, find additional locating methods such as site search, sitemap, table of contents, related links or navigation from a landing page.

Step 3 of 3

ActionUse each method with keyboard and verify that it reaches the intended page rather than only mentioning it.

Step 1 of 3

ActionSelect at least two pages that repeat global, section, footer, breadcrumb or sidebar navigation.

Step 2 of 3

ActionCompare the relative order of each repeated navigation region and the items within it across the selected pages.

Step 3 of 3

ActionRepeat in the responsive version and after any user preference that intentionally changes navigation.

Step 1 of 3

ActionInventory components that perform the same function on different pages, including icon controls, links, form controls and repeated status indicators.

Step 2 of 3

ActionCompare the visible label, icon meaning, accessible name and announced role of each pair.

Step 3 of 3

ActionOperate each component with keyboard and assistive technology to confirm that apparently consistent identification leads to the same function.

Step 1 of 3

ActionInventory human contact details, human contact mechanisms, self-help options and fully automated contact mechanisms available in the tested page set.

Step 2 of 3

ActionCompare the relative order and location in the content of each repeated help mechanism across pages.

Step 3 of 3

ActionRepeat in responsive layouts and after opening navigation, footer or support panels that contain help.

Step 1 of 3

ActionInventory functions that use multipoint or path-based gestures, including pinch, two-finger movement, swipe paths, drawing and free-form tracing.

Step 2 of 3

ActionComplete the same function using a single pointer without following a path, such as tapping a button, choosing a value or using separate zoom controls.

Step 3 of 3

ActionIf no alternative exists, verify whether the path or multipoint input is essential to the function rather than merely the chosen design.

Step 1 of 3

ActionOn each single-pointer control, press down inside the target, move outside it and release without completing a click.

Step 2 of 3

ActionPress down outside a target, move onto it and release, then test drag, selection and drawing functions at their completion point.

Step 3 of 3

ActionFor any action that completes on pointer down, immediately try to reverse or undo it and assess any claimed essential down-event exception.

Step 1 of 3

ActionInventory functions triggered by device motion or user motion detected by the device, such as shake, tilt, pan or camera-detected gesture.

Step 2 of 3

ActionPerform the same function through an ordinary user-interface control without moving the device or user.

Step 3 of 3

ActionFind and activate the method that prevents accidental motion activation, then repeat the motion.

Step 1 of 3

ActionInventory operations that require dragging, including sliders, maps, reorder lists, splitters, drawing controls and drag-and-drop uploads.

Step 2 of 3

ActionComplete the same result with a single pointer without dragging, using controls such as buttons, menus, direct value entry or select-then-place.

Step 3 of 3

ActionIf an alternative is absent, test keyboard operation and assess the claimed essential exception separately.

Step 1 of 3

ActionInventory pointer targets in each responsive layout and meaningful state, including icon controls, inline links, map markers and controls revealed on hover.

Step 2 of 3

ActionMeasure the rendered target width and height in CSS pixels without relying on the visible icon size alone.

Step 3 of 3

ActionFor each undersized target, centre a 24 CSS-pixel-diameter circle on its bounding box and compare it with every other target and with the same circle around every other undersized target.