Every interaction, including drag-and-drop, hotspots, and custom buttons, can be done with a keyboard, and its name and state are described.
Why it matters
Many learners can’t use a mouse, including screen reader users and people with motor disabilities.
If a drag-and-drop activity has no keyboard path, they simply can’t finish the course.
What passing looks like
- Each interaction has a keyboard way to do it, noted in the storyboard.
- Custom controls have names that say what they do.
- States are announced: selected, expanded, correct, incorrect.
- Drag-and-drop has an alternative, such as choosing from a list.
Example
Drag each document to the correct folder. (no other interaction notes)
The problem: There’s no keyboard or screen reader way to complete it.
Drag each document to the correct folder, or select a document and choose its folder from a list. Each folder announces how many documents it holds.
What Pedagrade can’t tell
This check reads the interaction notes in your storyboard. Keyboard support has to be tested in the built course; five minutes with the Tab key catches most problems.
This check is covered by Pedagrade’s published accuracy tests. See the accuracy report.
Learn more
- W3C, Understanding Success Criterion 2.1.1: Keyboard
- W3C, Understanding Success Criterion 4.1.2: Name, Role, Value
- Pedagrade guide: WCAG checklist for e-learning
Check your own course against this.
Paste a lesson, quiz, or whole course. Each finding shows where it is, why it matters, and the fix written out. Your first review is free.
Start your free review