Registration keyboard and error-recovery tests
Record keys, expected and actual results on real registration paths, then hand over error and value-retention retests.
Defects can be traced to the same-path retest in a fixed version.
- File formats
- English XLSX · CSV (UTF-8)
- Version
- 2.0
- Editorial review
- 31 Oct 2026
- Use this for
- Record keys, expected and actual results on real registration paths, then hand over error and value-retention retests.
When to use it
Record keys, expected and actual results on real registration paths, then hand over error and value-retention retests.
This form does not certify accessibility conformance. Do not use real applicant data for tests; agree how test submissions will be handled and deleted.
Start with the guide: Event registration form keyboard access and error correction: a practical guideFill in the template step by step
When to use it
Open a record when preparing the work. Link later checks and changes using the same item ID.
What to have ready
- Separate test URL/version and approved test data
- Keyboard paths, value rules and actual browser/reader environment
Record screen/environment, selections and keys so the issue can be reproduced.
Separate expected behaviour from actual focus, errors and retained data.
Retest the same path in the fix and record screen-reader checks separately.
Worked example
Fictional example, not an actual event or supplier record
Eight columns · scroll horizontally to view the complete worked example.
| Test ID, URL and version | OS, browser and embed | Path, selections and keys | Expected result and value rule | Actual focus, error and retained values | Screen reader and evidence | Fix and same-path retest | Publication decision and deadline |
|---|---|---|---|---|---|---|---|
| KF01 / test form REG-v2 | Windows/browser versions ENV01 / iframe | Select session→date→submit / KEY01 | Missing-field text and focus link; valid data retained | Focus lost after error link / BUG01 | Screen reader not tested / REC01 | Fix request DEV01 | Hold publication; developer Kim to reply8 Nov12:00 |
| KF01-R1 / REG-v3 | Same ENV01 / iframe | Repeat KEY01 path | Same RULE01 | Focus correct; name/session retained | Screen reader test still pending / REC02 | Kim fix checked8 Nov13:00 | SR01 pending; QA Lee by15:00 |
| KF02 / REG-v3 | ENV02 / approved screen-reader combination | Read field names and errors / SR01 | Names and guidance correspond to actual fields | Keyboard test KF01-R1 referenced | SR01 results/limits REC03 | Changed path retested by QA Lee | Registration Park records release decision16:00 |
Blank template preview
This preview shows a few rows. The downloaded file contains 24 prepared rows.
Eight columns · scroll horizontally to view the complete blank worksheet.
| Test ID, URL and version | OS, browser and embed | Path, selections and keys | Expected result and value rule | Actual focus, error and retained values | Screen reader and evidence | Fix and same-path retest | Publication decision and deadline |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
Sources used to develop this template
EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.
- W3C WAI — WCAG 2.2 Understanding 2.1.1 Keyboard; reviewed 27 October 2026
Adapted to link the guide’s checks with evidence, owners and follow-up records. The fields are editorial proposals, not an authority’s official submission form.
- W3C WAI — WCAG 2.2 Understanding 2.4.7 Focus Visible; reviewed 27 October 2026
Adapted to link the guide’s checks with evidence, owners and follow-up records. The fields are editorial proposals, not an authority’s official submission form.