Skip to content
Skills Library
Design & UX · Review & audit

input-accessibility-qa

/input-accessibility-qa

Use to audit keyboard/gamepad/multitouch input traces, stuck buttons, rebinding conflicts and accessibility; not implement controls.

Licence
MIT
Last repository change
30.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
18
Scripts
4
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 4 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: src/audit_input.py, src/recorder.mjs, tests/recorder.test.mjs, tests/test_audit.py

What it does and when to use it

Use to audit keyboard/gamepad/multitouch input traces, stuck buttons, rebinding conflicts and accessibility; not implement controls.

Original author description

Use to audit keyboard/gamepad/multitouch input traces, stuck buttons, rebinding conflicts and accessibility; not implement controls.

How it works

  1. Workflow
  2. Trace event schema
  3. Limitations and references
Original SKILL.md headings · 37 lines, 475 words
SKILL.md preview
---
name: input-accessibility-qa
description: Use to audit keyboard/gamepad/multitouch input traces, stuck buttons, rebinding conflicts and accessibility; not implement controls.
---
# Input Accessibility & QA (v1.0.0)

Independent instrumentation/auditing skill. Observe the existing input system. Do not overwrite core input, save, UI or physics subsystems. The runnable CLI checks JSON, JSONL and CSV event traces, and the JS recorder produces JSONL.

## Workflow

1. Read the project's action map and current contexts; identify critical escape and confirmation actions, gamepad index ownership, touch zones, lifecycle events, user profiles.
2. Instrument **physical** down/up and pointer events plus **logical** action consumption. Use anonymized device labels, not serial numbers or persistent raw hardware identifiers. Do not log keystrokes typed into chat/text fields.
3. Capture normalized events with strictly nondecreasing millisecond time; `InputTraceRecorder` is reference instrumentation only (`src/recorder.mjs`).
4. Run `python3 src/audit_input.py trace.jsonl --report report.json`. Exit status `0` = no errors, `1` = invariant failures, `2` = invalid input/read errors. Warnings are deliberately separate from errors.
5. Test keyboard pointer and gamepad simulated sequences, then real mobile device/multiple fingers, unplug/hot-plug and remap when hardware is available. Check hold-vs-toggle, deadzone sensitivity and axis inversion settings plus ability to recover from a bad bind.
6. Verify browser/focus behavior: `blur`, `visibilitychange`, composition, editable inputs, `pointercancel`, lost pointer capture, gamepad disconnect and index reuse.
7. For UI-based accessibility verify WCAG input modalities, no mandatory complex touch chords, alternate controls for time-sensitive repetitive actions. Review actual prompts and accessible labels; a trace alone cannot certify accessibility.
8. Execute `python3 -m unittest discover -s tests -v`, `node --test tests/*.test.mjs`, `tsc --noEmit -p tsconfig.json`.

## Trace event schema

Common: `{time:number,type:string,device?:string,control?:string}`. Use monotonic ms and event-specific fields:

- `down` / `up`: `device`, `control`. Duplicate down and orphan up are errors.
- `pointerdown` / `pointerup` / `pointercancel`: `pointerId`, optional `zone`. Unknown pointer or reused live pointer is an error.
- `axis`: normalized `x,y`; radius must be <= 1 after calibration. Raw unsanitized joystick values should be logged separately to avoid false positives.
- `blur` / `hidden` / `releaseAll`: clears held and active pointers (emits a warning if held was cleared). A missing physical up **before** blur is expected; do not classify it as a failure.
- `consume`: `inputId` must be unique per action consumption.
- `binding`: optional `conflict:true` for violations detected by host action map.
- `context`, `device`, `press`, `release`, `sample`: accepted telemetry.

An unfinished short trace produces **warnings**, not automatic failures, because a trace can stop while a control is deliberately held. Stuck input exceeding configured timeout is an error. No system should trust `event.type` fields supplied by untrusted remote clients without validation.

## Limitations and references

CLI observes one trace. It cannot infer held-state latency against screen photons, network timing, physical button accessibility or whether a user can comfortably perform a gesture. Use real-device playtests with disabled/reduced mobility options.

Source docs: Xbox XAG 107 https://learn.microsoft.com/en-us/xbox/accessibility/xbox-accessibility-guidelines/107 ; WCAG 2.2 input modalities https://www.w3.org/WAI/WCAG22/Understanding/input-modalities ; MDN Pointer Events https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events ; MDN Gamepad API https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API/Using_the_Gamepad_API

Files: `src/audit_input.py`, `src/recorder.mjs`, `src/recorder.d.mts`, `tests/`, `examples/`, `references/test-matrix.md`.
Files in this package (18)
  • CHANGELOG.md 1 KB
  • LICENSE 1 KB
  • PROVENANCE.md 1 KB
  • SKILL.md 4 KB
  • TESTING.md 1 KB
  • VERSION 1 KB
  • tsconfig.json 1 KB
  • attribution/upstream/LICENSE 11 KB
  • attribution/upstream/NOTICE 1 KB
  • examples/run-qa.md 1 KB
  • examples/trace.jsonl 1 KB
  • references/test-matrix.md 1 KB
  • src/audit_input.py 5 KB
  • src/recorder.d.mts 1 KB
  • src/recorder.mjs 1 KB
  • tests/recorder.test.mjs 1 KB
  • tests/test_audit.py 3 KB
  • typecheck/example.mts 1 KB

Versions

The database has no other skills named input-accessibility-qa.

Database snapshot: 13.11.2026 · package version 116ca3614c45 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100input-systems
    Architect game input — action mapping (abstracting keys into named actions), rebinding with conflict detection and persistence, multi-device support (keyboard, gamepad, touch), analog deadzones, and feel features like input buffering and coyote time, plus accessibility.…
  • 90accessibility-review
    Audit a UI for real accessibility, keyboard-first, with concrete failures and fixes rather than checkbox compliance. Use when reviewing or building any user interface.
  • 84audit-accessibility
    Audit UI components and pages for accessibility (a11y) issues. Use when user says "check accessibility", "audit a11y compliance", "find WCAG violations", "is this component accessible", "run an accessibility audit", or "check screen reader support".
  • 100input-systems
    Architect game input — action mapping (abstracting keys into named actions), rebinding with conflict detection and persistence, multi-device support (keyboard, gamepad, touch), analog deadzones, and feel features like input buffering and coyote time, plus accessibility.…
  • 100input-system
    Handle player input in Godot across keyboard, mouse, gamepad, and touch devices. Use this skill when configuring input actions, processing keyboard/mouse/gamepad events, implementing touch controls, setting up virtual joysticks, managing mouse modes, or building remappable input systems.
  • 100godot-input-handling
    Expert patterns for input handling covering InputMap actions, InputEvent processing, controller support, rebinding, deadzones, and input buffering. Use when setting up player controls, implementing input systems, or adding gamepad/accessibility features. Keywords InputMap,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.