Keyboard test recorder

What does the keyboard test recorder produce?

Record and reconcile actual ordered manual keyboard steps, observed focus, activation and exit behavior.

Use the exact local files and task-specific inputs listed below. Preparation and review stay in this browser. Inspect all findings before preparing the finalized pack.

What do you need before you start?

• Define your exact task, source population and method.
• Keep the unchanged original files and the selected source versions.
• Review missing, invalid and unresolved facts before preparation.

What information do you enter?

Select the actual local sources and freeze the task-specific inputs below. Keep source files and complete findings private.

• Reference. Stable reference for this exact supplied population.
• Working pack version. Customer-controlled version.
• Organization. Actual organization owning this work.
• Approved jurisdiction scope. Select and support the actual jurisdiction and instrument for each exact scope.
• Responsible reviewer. Accountable human reviewer.
• Review timestamp. Exact timestamp with seconds and confirmed offset.
• Approved task scope. Included and excluded scopes, populations, assumptions and intended use.
• Scope approval reference. Actual accountable approval reference.
• Approved method version. Actual your method and calendar assumptions.
• Method source reference. Exact original file supporting the selected method.
• Approved method source locator. Exact JSON pointer or reviewed locator.
• Method approver. Responsible human approver.
• Method approval timestamp. Approved instant no later than review.
• Scope population. Selected or declared complete supplied population.
• Declared scope count. Required for a declared complete population.
• Manual keyboard scenario results scope inputs. Readable named rows, exact relationships, original sources and responsible decisions.
• Keyboard Scenarios. Readable named rows, exact relationships, original sources and responsible decisions.
• Keyboard Steps. Readable named rows, exact relationships, original sources and responsible decisions.
• Keyboard Issues. Readable named rows, exact relationships, original sources and responsible decisions.
• Evidence. Readable named rows, exact relationships, original sources and responsible decisions.
• Actions. Readable named rows, exact relationships, original sources and responsible decisions.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the keyboard test recorder work?

1. 1
   Define the approved scope

   Reference. Stable reference for this exact supplied population.

2. 2
   Enter task-specific evidence

   Validate actual page/version/browser/OS, ordered unique step sequences and declared coverage. Compare the supplied expected and observed target/action, visible focus, operation and exit outcomes. Detect contradictory pass claims, skipped or repeated steps, traps and unresolved retests. Keep initial failures and subsequent exact retests separate.

3. 3
   Inspect complete findings

   Review all named calculations, original source bindings and unresolved findings.

4. 4
   Keep recoverable work

   Exact original bytes and unfinished strings save locally. Restore validates exact tool, revision, row shape, source hashes and history before replacement. Earlier work and purchases remain separate.

5. 5
   Prepare the finalized pack

   Prepare 7 plus selected attachments complete files, then download them free. Review the fictional sample below.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• Web Content Accessibility Guidelines 2.2Supports named source-bound preparation and precise reviewed criteria. Current applicability and actual outcomes require accountable review. WCAG 2.2, December 12, 2024 Recommendation. Sections 2.1, 2.4, 4.1 and conformance requirements on full pages, complete processes, accessibility-supported technologies and noninterference. Selected criteria and actual evaluations stay explicit.World Wide Web Consortium. Reviewed 2026-10-09.

Common questions

What still needs review?

This browser preparation retains original customer evidence and selected source-approved criteria. Actual manual tests, authorization, delivery, signatures, employment status and legal applicability remain responsible human decisions. PDF checks cover only supported structural indicators, not semantic accessibility or conformance. No external scan, filing, remote AI or provider is called. Exact sources stay in this browser. Original files are not saved to the cloud.

At most 500 rows/200000 characters per table, 20 files/10 MB each/25 MB total, 900 KB input and 8 MB output metadata. PDF has at most 100 pages and 20000 structure nodes.

No statement or preparation table proves accessibility, employment eligibility, worker classification or current filing/legal duties. Your operative source versions and actual evidence remain required.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all marketing and consumer protection tools.

• Screen-reader test evidence managerPreserve coverage, devices, versions and findings. Try a free example, then review your inputs and the result. No account or payment required.
• Accessibility remediation trackerLink issues, fixes and retesting. Try the free example, then enter your own inputs and review the result before exporting.
• Accessibility statement assemblerDraft from actual scope, results and limitations. Try a free example, then review your inputs and the result. No account or payment required.
• VPAT or accessibility conformance report preparationOrganize evidence without inventing conformance. Try a free example, then review your inputs and the result. No account or payment required.
• PDF accessibility preflightCheck supported structural and metadata conditions. Try a free example, then review your inputs and the result. No account or payment required.