Complete the task using keyboard navigation
See this course’s project requirements
A personal non-sensitive task card and scoped navigation test using text size, zoom, keyboard and an available screen reader, with a truthful fallback comparison when a reader is unavailable.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Create a task-based access choice with available/unavailable tools and no sensitive personal data.
- Retain baseline/adjusted settings and observed information/control access, with restoration recorded.
- Complete and document the keyboard task or its exact observed barrier.
- Record an actual native setup/tutorial or a clearly labeled documentation-based fallback.
- Produce a task outcome comparison that separates actual observations, expected structure, and unavailable checks.
- Deliver a non-sensitive repeatable access plan with actual results, alternate route, and exact verification limits.
Review and revise
Use these criteria to check your work and choose what to improve.
- The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
- Normal, boundary and rejected cases are recorded with expected versus observed results.
- The changed case has a correct explanation and does not rely on hidden state.
- The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Want more background?
The idea in everyday life
The original assistive-practice.html task is to find Morning 10:00, enter fictional nickname Nova with 2 seats, and confirm locally. Open the local HTML file in an available browser. assistive-task-card.txt supplies the record template; no account or private data is used.
Keyboard navigation must expose a logical focus sequence and allow required actions. Visible focus and movement are observed behavior, not facts inferred from a native-control label.
Complete the task using keyboard navigation — original worked practice
Keyboard navigation must expose a logical focus sequence and allow required actions. Visible focus and movement are observed behavior, not facts inferred from a native-control label.
The original assistive-practice.html task is to find Morning 10:00, enter fictional nickname Nova with 2 seats, and confirm locally. Open the local HTML file in an available browser. assistive-task-card.txt supplies the record template; no account or private data is used.
1. Step 1
Use Tab and Shift+Tab to inspect the practice links, fields, and Confirm button; record the visible focus sequence.
You should see: The actual focus path is documented.
Keyboard navigation must expose a logical focus sequence and allow required actions. Visible focus and movement are observed behavior, not facts inferred from a native-control label.
2. Step 2
Activate the schedule link with Enter and find Morning 10:00. Return to the input fields.
You should see: The required information is located without a mouse.
Keyboard navigation must expose a logical focus sequence and allow required actions. Visible focus and movement are observed behavior, not facts inferred from a native-control label.
3. Step 3
Type Nova and 2; activate Confirm with an appropriate native-button key and read the status.
You should see: The local completion feedback appears.
Keyboard navigation must expose a logical focus sequence and allow required actions. Visible focus and movement are observed behavior, not facts inferred from a native-control label.
4. Step 4
Record any trap, skipped control, or unclear focus; retain the task result and key sequence.
You should see: A keyboard-only task record.
Keyboard navigation must expose a logical focus sequence and allow required actions. Visible focus and movement are observed behavior, not facts inferred from a native-control label.
What to finish
Complete and document the keyboard task or its exact observed barrier.
Watch for this
Inferring a keyboard pass from source structure without completing the actual key journey.
How can I tell I understand it?
Demonstrate the rule: Keyboard navigation must expose a logical focus sequence and allow required actions. Visible focus and movement are observed behavior, not facts inferred from a native-control label. Use the supplied variant to distinguish a changed result from a broken implementation.
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-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.