Accessibility QA
Make your app usable by everyone: keyboard, contrast, labels, focus, and screen-reader basics.
The Route
0/5 verifiedKeyboard-only audit
Unplug the mouse: can you use the whole app?
Fix keyboard operability
Everything clickable must be tabbable, activatable, and visibly focused.
Contrast and visual pass
Text people cannot read is text that does not exist.
Names, semantics, and structure
Assistive tech needs names and structure to navigate.
Focus management and forms
The dynamic layer: modals, updates, and error handling must guide focus.
Context Pack
Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.
Paste this into your AI builder first. It teaches the AI what you want before you give it the build prompt.
Related routes
More QA flows that share ground with this one.
صياغة الفرق بين الأسئلة البحثية والمساهمات في ورقة أو مشروع بحثي
تدفق عملي لمساعدة المستخدم على التمييز بوضوح بين الأسئلة البحثية والمساهمات، ثم صياغتهما بشكل صحيح وقابل للاستخدام في مقترح أو ورقة بحثية.
+6 more steps to Done
Best forbuilders who have shipped a basic app before
API/Error Handling QA
Verify every API contract and failure path: status codes, error shapes, timeouts, and frontend recovery.
+2 more steps to Done
Best forproduction-grade builds with strict verification
Auth Flow QA
Dedicated auth testing: signup, login, sessions, guards, reset, and the edge cases that expose fake auth.
+2 more steps to Done
Best forbuilders who have shipped a basic app before