Group
  • Testing

    Run an accessibility pass before launch

    Adds automated axe checks to the test suite and walks the core flows with a keyboard to fix the worst violations.

    • Improve quality
    • Plan & validate
    • Intermediate
    • General

Free Prompt

Give my app a baseline accessibility pass before launch. 1. Automated scan: add axe-core (via axe-playwright, cypress-axe, or the integration for my test runner) to my test suite and run it against my key pages: landing, signup, login, the main app screens, and checkout. Fail the build on critical violations. 2. Keyboard walkthrough: manually walk the core flows (signup, login, main create/edit action, checkout) using only the keyboard. Fix what breaks: elements that cannot be reached by Tab, actions that only work on click, focus that disappears into hidden elements, and modals that do not trap and return focus. 3. Quick wins audit: check the high-frequency violations across all pages: every form input has an associated label, every image has meaningful alt text or an empty alt for decorative images, color contrast on body text and buttons meets 4.5:1, and page language is set on the html element. 4. Focus visibility: make sure focus indicators are visible; if a CSS reset killed outline, restore a styled one instead of leaving keyboard users blind. 5. Error accessibility: form errors must be announced to screen readers (aria-live or associating the error with the input via aria-describedby), not just red text. Do not attempt a full WCAG certification pass; this is the baseline that catches the violations real users hit first. Do not change the visual design except where contrast fails. Give me: the axe integration code, the list of violations found and fixed per page, and the results of the keyboard walkthrough per flow.

What This Does / How This Helps

Adds automated accessibility scanning to your tests and runs a keyboard-only pass over the flows that make you money. Accessibility problems are conversion problems wearing a disguise. A checkout that cannot be completed by keyboard loses sales. An unlabeled form loses signups. And automated tools catch about a third of issues instantly, the easy third you have no excuse to ship. The prompt sets the realistic baseline: axe in CI on your key pages, a keyboard walkthrough of the money flows, and the quick-win fixes (labels, alt text, contrast, focus) that cover most of what users actually hit.

Want to skip doing this by hand?

Fortivibe audits your app for all of the areas these prompts cover (and more).

See What We Check

Related Prompts