Assistive & Accessible AI · Capstone brief

ACC-07 · Motion and switch access

Evaluate an AI feature under keyboard-only / switch access constraints; file bugs as first-class deliverables.

The question

Evaluate an AI feature under keyboard-only / switch access constraints; file bugs as first-class deliverables.

Partners / materials

One AI-powered web or app feature. Keyboard-only and/or switch-emulation test script. Bug template (severity, expected, actual, severity). WAI / keyboard accessibility orientation (https://www.w3.org/WAI/). Consented partner preferred; otherwise self-test with switch emulation labeled as limited evidence.

Expected failure modes

Mouse-only testing. Filing vibes instead of bugs. Declaring WCAG conformance as a student without an audit method. Ignoring focus traps and time limits.

Done looks like

Test script; bug list (at least five substantive issues or a deep blocker with severity); severity rubric; one fix proposal the vendor or school IT could act on; limits of self-testing named.

Five C's

CT: access as requirement not polish. CR: reproducible bugs. CO: peer re-runs two bugs. CM: bug report packet. CZ: switch/keyboard users blocked by the feature.

Mentor role

ATC or accessibility-aware teacher reviews severity rubric. School-supervised.

Rubric calibration

R1: one feature, one access mode. R2: bugs reproducible. R3: mouse path as unfair baseline named. R4: blockers highlighted. R5: IT/vendor-ready. R6: no fake conformance stamp.

Two ways this goes wrong

(a) “Works with Tab” once. (b) A WCAG certificate drawn in Marker.

Credit lane fit

Lane A immediately. No verified credit claim.