Add accessibility in one prompt

Coding with an AI? Copy one of these prompts and paste it into your assistant. It installs the Conformly accessibility guardrail, fixes your RGAA/WCAG code, or wires up the API — without leaving your editor.

Copy a prompt, paste it into your AI assistant (Cursor, Claude Code, Windsurf, GitHub Copilot), and replace the values between angle brackets < >.

Install the CLI (CI guardrail)

Add a free accessibility guardrail to your project: one npm command, no API key. The build fails if the RGAA score drops below your threshold.

Add an accessibility guardrail to my project using the Conformly CLI (public npm package "conformly", free, no API key).

1. Add an "a11y" npm script to package.json: "npx conformly scan <MY_SITE_URL> --threshold 90" (replace <MY_SITE_URL> with your staging or production URL).
2. Create a GitHub Actions workflow at .github/workflows/accessibility.yml that, on every push, installs Node 18+ and runs "npx conformly scan <MY_SITE_URL> --threshold 90" — the job fails if the RGAA score drops below 90.
3. Explain in two lines how to read the result (RGAA score out of 100 + number of issues).

The CLI needs no authentication: it calls Conformly's free scan API.

Fix accessibility (RGAA/WCAG)

Have your AI audit and fix your code against RGAA 4.1 and WCAG 2.1 AA, without touching the design.

Act as an accessibility expert in RGAA 4.1 / WCAG 2.1 level AA. Audit this project's code and fix the most common accessibility issues, without changing the design:

- Images: meaningful alt text (empty alt if the image is decorative).
- Forms: every field tied to a <label>, errors announced (aria-describedby, aria-invalid).
- Contrast: text ≥ 4.5:1 (≥ 3:1 for large text) — flag the ones to fix.
- Keyboard: visible focus, logical tab order, no keyboard trap, skip link to content.
- Structure: a single <h1>, consistent heading hierarchy, landmarks (header/nav/main/footer), lang attribute on <html>.
- Interactive components: correct ARIA roles and states, touch targets of at least 24px.

Work file by file, explain each fix, and list separately anything that needs a human decision. Then I'll verify with a Conformly scan: npx conformly scan <MY_SITE_URL> --threshold 90

Show the score badge

Display a live conformance badge on your site, linking to the public report of your scan.

Add a Conformly accessibility score badge to my site.

- Conformly serves a live SVG badge at https://conformly.online/api/free-badge/<SCAN_ID> (the ID is returned after a free scan on conformly.online). For a monitored site, the badge is https://conformly.online/api/badge/<SITE_ID>.
- Insert an image in the footer showing this badge, clickable, linking to the matching public report.
- Make the image accessible: alt text describing the score (e.g. "RGAA accessibility score: 92/100"), and let the badge update itself.

Ask me for the ID if you can't find it; I get it after a scan or in my Conformly dashboard.

Wire up the REST API

Trigger scans from your application via the authenticated REST API (cfy_ key generated in the dashboard).

Integrate the Conformly REST API into my application to trigger accessibility scans programmatically.

- Authentication: "Authorization: Bearer cfy_..." header (site-scoped key generated in the Conformly dashboard). Keep it in an environment variable, never hard-coded.
- Trigger a scan: POST https://conformly.online/api/v1/scans with JSON body {"threshold": 90} → 202 response { id, status, statusUrl }.
- Poll the scan: GET https://conformly.online/api/v1/scans/<ID> until status = "done" → { status, score, threshold, pass, scanId, violationsUrl }.
- Respect the quota: 60 requests per minute per key, X-RateLimit-* headers, 429 + Retry-After beyond that.

Write a small reusable module in my project's language: trigger, polling with backoff, error and 429 handling.

No score yet?

Test a page for free, no account — then paste the fix prompt.

Free scan CI/CD guide