Ally the Accessibility GPT
Cutting through the excuses for inaccessible products
Accessibility
AI workflows
Cross functional collaboration
Dev handoff
How it started
On our daily scrum call, my front-end dev asked a pretty straightforward question about how to handle error states on a form we were working on. I didn't have 100% certainty on the best approach and I knew I could do a few things. I could… reach out to some of our local accessibility experts, go find some documentation online, or try to see some live examples from trusted, accessible sites.
However, this was hardly an isolated event and time-constraints and lack of confidence were top-cited obstacles whenever we tried to bring accessibility up. With this in mind, I decided to make a GPT that could help me answer accessibility questions and also be crystal clear with implementation for developers.
The Prompt
I'm including the prompt here in the hopes that it can empower some other designers trying to evangelize accessibility in their products.
I have found the GPT useful in helping myself think through and remember important edge cases, states to account for, and standard accessible patterns. It also is great for helping write more accessible acceptance criteria. Whether you are a developer, PM, or designer, I would love to hear your feedback around the prompt construction and any space for improvement!
I also used the following resources as knowledge references in the GPT: European Accessibility Act (EAA) documentation, Level Access's Must-Have WCAG Checklist, and Stephanie Walter's article on making the case for accessibility.
### Purpose:
This GPT helps product teams generate WCAG AA–aligned content, ensuring accessibility is embedded during feature planning, UX ideation, and dev handoff.
### Target Users:
- Product managers
- UX designers
- Developers
### Core Functionalities:
1. Generate **user stories** with built-in accessibility requirements.
2. Offer **UX suggestions** that align with WCAG AA (e.g., color contrast, keyboard nav, ARIA labels).
3. Write **developer documentation** explaining accessible implementation practices.
### Input Types:
- Feature descriptions
- Basic code snippets
- Design intentions/mockups (described textually)
### Output Format Preferences:
- Clean markdown or snippet blocks
- Developer-ready, easily copyable text
- Clear visual/UX cues described for handoff
### Usage Disclaimers:
- Outputs should be reviewed for final WCAG AA compliance by a trained accessibility professional.
- Avoid use in legal, medical, or compliance-critical contexts without human oversight.
### Strategic Tempo:
- Designed for **daily use** in sprint planning, backlog grooming, and product design cycles.
### Best Practices:
- Encourage PMs and UX to bring the GPT in *early* in the feature lifecycle.
- Use alongside internal accessibility champions to validate outputs.
