Reviewing a course registration before launch
Combine automated and manual testing techniques to assess one registration experience and make an evidence-based launch recommendation.
- Difficulty:
- beginner
- Estimated time:
- 105 minutes
Scenario
A community organization is preparing to launch online registration for a new course. You have been asked to perform a focused pre-release accessibility review of the registration experience and advise whether it is ready to launch.
Your role: Accessibility tester supporting a pre-release review
What you will practise
- Define and document a reproducible review scope and test environment.
- Sequence automated and manual checks across relevant interface states.
- Record findings and passing checks with useful evidence.
- Consolidate overlapping observations without inflating issue counts.
- Prioritize impact and make a concise, evidence-based launch recommendation.
Methods used
Testing with automated tools
Run a reproducible accessibility scan, verify every result in context, and identify what still requires manual testing.
Testing keyboard accessibility
Check whether every interactive element can be reached, identified, and operated with a keyboard in a logical sequence.
Testing visual accessibility
Review contrast, color-dependent information, text readability, and visible interaction states systematically.
Testing text spacing and user overrides
Apply the complete text-spacing condition and check whether content and functionality remain available.
Testing zoom and reflow
Check whether content and functionality remain available when text is enlarged and the page reflows into a narrow CSS viewport.
Testing forms and validation
Check whether people can understand, complete, correct, and successfully submit a form.
Optional preparation
Complete your independent review before consulting the Exercise solution.
Learning path
Your first accessibility review
Build a practical beginner review through paired methods and Exercises for automated, keyboard, visual, user-preference, motion, mobile-touch, media, zoom, forms, and time-limit testing.
Level: beginner
Estimated time: 530 minutes
Exercise
Testing a community-course registration form
Complete, invalidate, correct, and submit a realistic registration form while examining its form relationships and messages.
Estimated time: 25 minutes
You can complete this Testing journey in one focused session or split it across two sessions. Preserve your notes between stages so the final recommendation reflects the same documented review scope.
Testing journey workspace
Open the Testing journey workspace for course registration in a separate page and use that same interface throughout the Testing journey. It contains intentionally designed accessibility problems, but the Testing journey does not tell you how many findings to expect. A useful review also records passing checks.
Build useful evidence
For each observation, record the interface state, Testing method, steps, actual result, expected result, and user impact. For text spacing, include the override mechanism, viewport, and confirmation that all four values were applied. Keep observed evidence separate from assumptions. If several Testing methods expose the same underlying problem, report one finding with all relevant evidence instead of inflating the issue count.
Record meaningful passing checks as well. They help reviewers understand the tested scope and help developers avoid regressions while correcting other behavior.
Make the launch recommendation
Prioritize findings by their effect on completing registration, not by an automated tool’s severity label alone. Identify problems that block or seriously obstruct the task, changes that should follow soon after launch, and any review areas that remain incomplete.
End with a concise recommendation: ready to launch, ready only if specified blockers are corrected, or not ready to launch. Connect the recommendation to your evidence and state any conditions or follow-up testing clearly.
Review stages
Define the review scope
Record the route, browser, viewport, zoom baseline, theme, assistive technology, test data, and included interface states. State what is outside the review.
Establish an automated baseline
Scan the initial form and the invalid-submission state. Verify each result against the rendered interface and record the configuration and state needed to reproduce it.
Test core manual access
Review keyboard operation, focus order, visible focus, visual instructions, required indicators, control boundaries, error presentation, and interactive states. Record passing behavior as well as findings.
Test responsive conditions
Apply and verify the complete text-spacing condition, then review browser zoom, text resizing, and reflow at the Testing methods' defined conditions. Confirm whether content and controls remain available without assuming the interface must contain a defect.
Test the complete form journey
Inspect labels, instructions, and groups; submit invalid data; locate and understand errors; correct values; submit successfully; and use a screen reader to verify relationships and announcements.
Consolidate and recommend
Merge duplicate evidence, distinguish findings from passing checks, prioritize user impact, identify launch blockers and follow-up work, and make a concise launch recommendation.
Deliverables
- Scope and test-environment note.
- Test record organized by Testing method.
- Findings table with evidence, user impact, and remediation direction.
- Passing checks worth preserving during remediation.
- Short launch recommendation identifying blockers and follow-up work.