Flows category icon
QA
Intermediate

Accessibility QA

Make your app usable by everyone: keyboard, contrast, labels, focus, and screen-reader basics.

5 steps15 verify checks60-90 minutesWorks with: emergent · chatgpt · claude · cursor
Start Guided Walkthrough

The Route

0/5 verified

Context Pack

Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.

Context Pack
PROJECT CONTEXT:
I want my app to meet accessibility basics so keyboard and assistive-tech users can actually use it.

GOAL:
Audit and fix the core accessibility layers: keyboard operability, contrast, semantics/labels, focus management, and forms.

REQUIREMENTS:
- Full keyboard operability of every interactive element
- WCAG AA contrast on text and UI elements
- Semantic structure and accessible names
- Managed focus for modals and dynamic content
- Accessible form labels and error announcement

CONSTRAINTS:
- Test by using the keyboard, not by scanning code
- Do not remove functionality to pass - fix it

DEFINITION OF DONE:
- Every action completable by keyboard alone
- Text and controls pass AA contrast
- Interactive elements have accessible names
- Modals trap and restore focus correctly
- Form errors are visible and programmatically associated

COMMON FAILURES TO AVOID:
- Click-divs unreachable by Tab
- Light-gray-on-white text failing contrast
- Icon buttons with no accessible name
- Modals letting focus escape behind them

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.

Flows category icon
QA
Generated

صياغة الفرق بين الأسئلة البحثية والمساهمات في ورقة أو مشروع بحثي

تدفق عملي لمساعدة المستخدم على التمييز بوضوح بين الأسئلة البحثية والمساهمات، ثم صياغتهما بشكل صحيح وقابل للاستخدام في مقترح أو ورقة بحثية.

01تحديد السياق الذي ستستخدم فيه المفهومين
02استخراج تعريفين منفصلين وغير ملتبسين
03بناء مقارنة مباشرة بين المفهومين

+6 more steps to Done

Best forbuilders who have shipped a basic app before

9 steps30-60 minutesIntermediate
Flows category icon
QA

API/Error Handling QA

Verify every API contract and failure path: status codes, error shapes, timeouts, and frontend recovery.

01Inventory the API contracts
02Test success and failure codes
03Normalize error responses

+2 more steps to Done

Best forproduction-grade builds with strict verification

5 steps60-90 minutesAdvanced
Flows category icon
QA

Auth Flow QA

Dedicated auth testing: signup, login, sessions, guards, reset, and the edge cases that expose fake auth.

01Test the signup surface
02Test the login surface
03Test the session lifecycle

+2 more steps to Done

Best forbuilders who have shipped a basic app before

5 steps45-75 minutesIntermediate

Made with Emergent