Fix pack and AI prompts
What the fix pack contains, which platforms get their own instructions, and how to use the AI prompts.
The fix pack
Every issue group in a paid report comes with:
- A plain explanation of the problem and who it affects.
- Step-by-step instructions.
- Code before and after, built from the actual HTML on your page. Where a value needs a person, such as a description of an image, the after-code contains a
TODOto replace. - For colour contrast, a suggested colour that passes, computed from your actual foreground and background.
- Instructions for your platform.
Platforms with their own instructions: WordPress, Elementor, Shopify, Webflow, Wix, Squarespace, Framer, Next.js and Lovable (also used for Bolt and v0). Other sites get general HTML advice. The platform is detected automatically.
AI prompts
Each group has three prompt flavours, and the Prompts tab has a whole-site prompt for the biggest problems, ordered by impact:
| Flavour | For |
|---|---|
| ChatGPT, Claude or other assistant | Explaining and writing the fix in a chat. |
| Cursor, Claude Code or Copilot | AI code editors. Includes selectors and HTML and asks the tool to find the source in your codebase. |
| Lovable, Bolt or v0 | AI site builders. Conversational, no file paths assumed. |
In the site's settings, under AI prompt preferences, you can set your framework (React, Vue, Svelte or plain), styling (Tailwind or CSS) and the language for new text. They are used in the next scan's prompts.
Alt text suggestions with your own AI key
On Pro and Agency you can save your own OpenAI or Anthropic key under Settings → API and integrations. AccessibilityBrief can then suggest alt text by sending the image crops of an issue group to that provider, only when you ask. Review every suggestion before using it.
The fix pack is written from templates, not generated by AI, so the same issue always gets the same advice.
Still stuck? Write to us and we will help. Contact support