KWCAG 2.2 checkpoints that automation cannot judge, with instructions for testing them yourself. Identical to the 'manual checks' section of A11y Check reports.
WCAG reference: 1.1.1
Automated checks verify alt text exists; a human must judge whether it conveys the image's meaning. Verify with a screen reader and check decorative images use empty alt.
WCAG reference: 1.2.1, 1.2.2, 1.2.3
Play each video/audio and confirm captions, transcript, or sign language are provided and synchronized.
WCAG reference: 1.4.1
View the page in grayscale and check whether any information is conveyed by color alone.
WCAG reference: 1.3.3
Check for instructions that rely only on shape, size, location, orientation, color, or sound.
WCAG reference: 1.4.3
Automated checks cover most cases; manually verify text over images/gradients and hover/focus states meet 4.5:1 (3:1 for large text).
WCAG reference: 1.4.2
Check no audio plays automatically for more than 3 seconds, or a stop/mute control is provided first.
Verify adjacent content blocks are visually distinguishable by borders, spacing, or background differences.
WCAG reference: 2.1.1, 2.1.2
Operate every feature using only the keyboard; ensure no keyboard traps.
WCAG reference: 2.4.3, 2.4.7, 2.4.11
Verify logical focus order, visible focus indicator, and that focused elements are not obscured.
WCAG reference: 2.5.5, 2.5.8
Verify interactive targets are at least 24×24 CSS px or adequately spaced.
WCAG reference: 2.1.4
If single-character shortcuts exist, verify they can be turned off, remapped, or are active only on focus.
WCAG reference: 2.2.1
If time limits exist (session timeout, etc.), verify users are warned and can extend or disable them.
WCAG reference: 2.2.2
Verify auto-moving content (carousels, tickers) provides pause/stop/previous/next controls.
WCAG reference: 2.3.1
Check nothing flashes more than 3 times per second.
WCAG reference: 2.4.1
Press Tab at page top and confirm a working skip link moves focus to main content.
WCAG reference: 2.4.2
Verify page titles are descriptive and unique, frames are titled, and content sections have headings.
WCAG reference: 2.4.4
Check link text (with context) identifies the destination — avoid bare 'click here' / 'more'.
Applies to web-based e-publications: verify fixed page locators exist. Often N/A for ordinary web pages.
WCAG reference: 2.5.1
Verify multipoint or path-based gestures have single-pointer alternatives.
WCAG reference: 2.5.2
Verify actions trigger on pointer-up and can be aborted by moving off the target.
WCAG reference: 2.5.3
Verify the visible text of controls is contained in their accessible name.
WCAG reference: 2.5.4
Verify motion-triggered functions have UI alternatives and motion sensing can be disabled.
WCAG reference: 3.2.1, 3.2.2
Verify focus or input alone never triggers unexpected context changes; new windows are announced in advance.
WCAG reference: 3.2.6
Verify help mechanisms appear in the same relative location across pages.
WCAG reference: 1.3.1, 1.3.2
Disable CSS or use a screen reader to verify the content order is logical.
WCAG reference: 1.3.1
Verify captions and header cells exist (automated) and header associations read correctly in a screen reader.
WCAG reference: 3.3.2, 1.3.1
Automated checks verify labels exist; confirm they describe the purpose and placeholders aren't used as labels.
WCAG reference: 3.3.1, 3.3.3
Submit invalid forms and verify errors are identified in text with correction suggestions.
WCAG reference: 3.3.8
Verify authentication doesn't rely solely on cognitive tests; paste and autofill must not be blocked.
WCAG reference: 3.3.7
In multi-step processes, verify previously entered information is auto-populated or selectable.
WCAG reference: 4.1.2, 4.1.3
Automated checks catch ARIA misuse; verify custom widgets announce role/state and follow APG keyboard patterns.