Check a task with the keyboard
See this course’s project requirements
Deliver the repaired workshop notice and the review evidence assembled across all six lessons.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Provide clear event facts, action instructions and meaningful link labels.
- Show a semantic heading outline and logical reading order.
- Record image alternatives and a justified contrast decision.
- Provide timed captions and a descriptive transcript for the sample clip.
- Attach a keyboard trace, issue statuses and a scoped handoff.
Review and revise
Use these criteria to check your work and choose what to improve.
- Clarity: essential facts and actions are understandable without visual guessing.
- Structure: hierarchy and reading order match content relationships.
- Equivalence: visuals and media have meaningful text support.
- Evidence: tests and remaining limits are documented honestly.
Want more background?
The idea in everyday life
Keyboard access matters for people using many different input methods, including assistive technologies that emulate a keyboard. A link that looks clickable may still be unreachable or unusable. You will inspect the workshop’s sample path using an existing local document, or evaluate the supplied focus trace on paper without opening any real registration service.
Test whether a task can be completed, not only whether a control can be reached.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Define the test task: open workshop details, reach the sample form, choose a session, save the practice selection and return to the notice. Exclude any real submission or personal-information entry from the exercise.
- 2
If using a digital sample, press Tab and Shift+Tab to move between controls. Look for a visible marker showing keyboard focus—the control ready for keyboard input. Open links with Enter and use each control’s standard keys.
- 3
Record each step as reachable, operable and understandable. A focused item that cannot perform its action still creates a barrier; focus visibility is also a separate observation.
- 4
For the paper alternative, inspect this trace: details link receives visible focus and opens; session choice receives focus and changes; Save is skipped; Back receives focus. Record the missing save action as a blocker.
- 5
Repeat the path after a proposed repair in the simulated trace: Save receives visible focus and activates with its expected keyboard control. Label simulation versus actual testing, and keep unresolved behavior visible.
See how it works.
Fictional keyboard record: Tab 1 reaches "Workshop details" and Enter opens it. Tab 2 reaches the session selector, whose arrow keys change the selected option. Tab 3 jumps straight to "Back to notice," leaving no keyboard route to the Save action. The report names the task impact: a keyboard user cannot finish the practice selection. A proposed repair uses an ordinary button with visible focus. In the revised trace, Save receives focus and activates before Back. This trace is evidence about the supplied scenario; it does not certify an untested website or document.
Did you cover these?
- Trace identifies every action needed for the task.
- Missing Save is marked as a task blocker.
- Actual versus simulated evidence is explicit.
What to finish
A keyboard task trace and one barrier report with a retest result or plan.
Watch for this
Checking Tab movement alone without attempting the task’s actions.
How can I tell I understand it?
Distinguish reaching, seeing and operating a control.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Opened the standards organization’s public educational modules for content authors. Used to verify appropriate subject coverage; this is an original course, not a reproduced W3C syllabus.
Access: Free public reading; no account or certificate is required for this Life Starter course.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Source & access notes · checked 2026-09-10
Read keyboard-interface requirements and exceptions; used a completed task rather than a mouse-only interaction as the test goal.
Access: Free public reading; no account or certificate is required for this Life Starter course.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.