Validated
Builder workbench
Keyboard traversal, slot activation, removal, focus visibility, and live-status messaging were rechecked on the public builder flow.
Accessibility
Accessibility validation is tracked publicly instead of hidden behind release notes.
This page summarizes the current WCAG-oriented validation work on QC+AI Studio: keyboard checks, browser automation, live fixes, and the assistive-technology follow-ups that still require a dedicated lab environment.
Validated
Account lifecycle
Create, login, logout, and delete-account forms were rechecked for labels, visible focus, and clear submission messaging.
Validated
Lesson playback and study controls
Lesson navigation, flashcard/quiz links, media framing, and public study actions were reviewed for structural semantics and keyboard reachability.
Live
Automated accessibility tooling
A browser-based Lighthouse accessibility audit now runs against the public route set through npm test:a11y.
Fixes already in the live public deployment
Circuit slots keep focus, announce their placement status, and support Enter, Space, Delete, and Backspace interactions.
Each support field is labeled, validation text is explicit, and submission results are announced in a live region.
Status and accessibility pages follow the site-wide skip-link, heading, landmark, and panel patterns.
Tracked follow-up work
- A full NVDA/VoiceOver assistive-technology lab pass remains an explicit operational follow-up because it requires dedicated screen-reader environments outside the deployment pipeline.
- Simulation-heavy interactions should continue to be rechecked when new drag, chart, or canvas behaviors are added.
If you encounter an accessibility problem on a public route, use the support page so the issue lands in the first-party review queue instead of disappearing into generic feedback.