Accessibility risk and test planner

Select the interaction types your course uses. You will get the accessibility checks most likely to matter, the WCAG criteria involved, and what to test by hand.

What does your course use?

Select any that apply. You can select more than one, or none at all.

Showing the checks that apply to any course. Select interaction types above to add more.

Relevant WCAG criteria (26)

WCAG 1.1.1WCAG 1.3.1WCAG 1.3.2WCAG 1.3.3WCAG 1.4.10WCAG 1.4.11WCAG 1.4.13WCAG 1.4.3WCAG 1.4.4WCAG 2.1.1WCAG 2.1.2WCAG 2.3.1WCAG 2.4.1WCAG 2.4.11WCAG 2.4.2WCAG 2.4.3WCAG 2.4.4WCAG 2.4.7WCAG 2.5.3WCAG 2.5.5WCAG 3.1.1WCAG 3.2.3WCAG 3.2.4WCAG 4.1.1WCAG 4.1.2WCAG 4.1.3

Keyboard Navigation

8 to check

How to test: Unplug your mouse. Tab through the entire course using only Tab, Shift+Tab, Enter, and arrow keys, and confirm you can reach and operate everything you could reach with a mouse.

  • Keyboard inaccessible elements
    WCAG 2.1.1How to fix
  • Missing focus indicator
    WCAG 2.4.7
  • Invisible focus outline
    WCAG 2.4.11
  • Focus trapped in dialog
    WCAG 2.1.2
  • Positive tabindex values breaking natural order
    WCAG 2.4.3How to fix
  • Scrollable regions not keyboard accessible
    WCAG 2.1.1How to fix
  • Skip navigation link missing
    WCAG 2.4.1
  • Touch target too small (under 44x44px)
    WCAG 2.5.5

Colour and Visual

10 to check

How to test: Check text and important graphics against the WCAG 2.1 contrast ratios, and zoom the published course to 200% to confirm nothing clips or requires horizontal scrolling.

  • Text contrast ratio below 4.5:1
    WCAG 1.4.3How to fix
  • Large text contrast below 3:1
    WCAG 1.4.3How to fix
  • Button and icon contrast below 3:1
    WCAG 1.4.11
  • Instructions using colour alone
    WCAG 1.3.3
  • Instructions using position alone
    WCAG 1.3.3
  • Instructions using shape or size alone
    WCAG 1.3.3
  • Fixed pixel font sizes that break resize
    WCAG 1.4.4
  • Containers clipping text at 200% zoom
    WCAG 1.4.4
  • Fixed width containers breaking reflow
    WCAG 1.4.10
  • CSS animations flashing more than 3 times per second
    WCAG 2.3.1

Images and Alt Text

5 to check

How to test: Go through every image, icon, and graphic on every slide and confirm each one either has alt text that conveys its meaning, or is genuinely marked decorative.

  • Missing alt text on images
    WCAG 1.1.1How to fix
  • Meaningless alt text (filename used as alt)
    WCAG 1.1.1How to fix
  • SVG icons without accessible name
    WCAG 1.1.1How to fix
  • Canvas elements containing text a screen reader cannot read
    WCAG 1.1.1How to fix
  • Low accessible text density on graphical slides
    WCAG 1.1.1How to fix

Structure and Headings

9 to check

How to test: Check the heading order slide by slide with a screen reader's headings list, and confirm the reading order announced by the screen reader matches the order things appear visually.

  • Wrong heading order (H3 before H2)
    WCAG 1.3.1How to fix
  • Missing headings on slides
    WCAG 1.3.1How to fix
  • Duplicate slide titles across the course
    WCAG 2.4.2
  • Missing page landmarks (main, navigation)
    WCAG 4.1.2How to fix
  • DOM reading order does not match visual order
    WCAG 1.3.2How to fix
  • Page language not set
    WCAG 3.1.1
  • Duplicate IDs on the same page
    WCAG 4.1.1
  • Inconsistent navigation button labels across slides
    WCAG 3.2.3
  • Navigation button position changes between slides
    WCAG 3.2.4

ARIA and Interactive Elements

6 to check

How to test: For every form field, quiz question, and custom interactive element, confirm a screen reader announces a real name, a role, and any error or status message the moment it changes.

  • Broken ARIA ID references
    WCAG 4.1.2How to fix
  • Invalid ARIA roles
    WCAG 4.1.2How to fix
  • Unnamed custom interactive elements
    WCAG 4.1.2How to fix
  • Accessible name does not match visible label
    WCAG 2.5.3
  • Tooltip that cannot be dismissed
    WCAG 1.4.13
  • Empty ARIA live regions
    WCAG 4.1.3

Links

2 to check

How to test: Read every link's text on its own, out of context, and confirm it still makes sense.

  • Vague link text ("click here", "read more")
    WCAG 2.4.4How to fix
  • Link purpose unclear without context
    WCAG 2.4.4How to fix

Screen Reader Experience

9 to check

How to test: Turn on NVDA or VoiceOver and go through the whole course by ear alone. Anything that announces as blank, out of order, or not at all is a real finding.

  • Unlabelled interactive element announced as blank
    WCAG 4.1.2How to fix
  • Button read without accessible name
    WCAG 4.1.2How to fix
  • Announcement order does not match visual order
    WCAG 1.3.2How to fix
  • Decorative image announced aloud
    WCAG 1.1.1How to fix
  • Live region not announcing dynamic updates
    WCAG 4.1.3
  • Link purpose unclear from screen reader announcement
    WCAG 2.4.4How to fix
  • Image described by filename only
    WCAG 1.1.1How to fix
  • Heading level skipped in reading order
    WCAG 1.3.1How to fix
  • Screen reader reads hidden or off-screen content aloud
    WCAG 1.3.1How to fix

Storyline and Rise Specific

3 to check

How to test: Play through every branch, every layer, and every Rise block interaction yourself, not just the default path, since these are the checks a quick click-through of the main path will not catch.

  • Slide navigation buttons with inconsistent labels
    WCAG 3.2.3
  • Slide navigation buttons in inconsistent positions
    WCAG 3.2.4
  • Template slides with repeated contrast issues
    WCAG 1.4.3How to fix

A11yCheck already checks all of this automatically, along with everything else on the full check list.

Scan your course free