Use casesTriage
Run the accessibility checklist on every new screen, weekly
Mitra checks this week's new screens against your own accessibility checklist. The agent opens a Linear issue for each miss, naming the screen and the rule that failed. Contrast, target size and text scaling get looked at every week, not before a launch.
Every Friday at 2pm, check this week's new Figma screens against our accessibility checklist. Open a Linear issue for each miss and post a summary to #design.
200 credits to start · no credit card
What the agent actually does.
Collect this week's screens
The agent finds the frames added or changed since the last run, so nothing is audited twice.
Run your own checklist
The checks are the ones you wrote down: contrast ratios, target sizes, behavior at larger text.
Open an issue per miss
Each failure becomes its own Linear issue naming the screen and the rule, so it can be assigned.
Summarize the week
A short Slack post says how many screens were checked and how many passed.
Make it yours.
For designers and engineers who mean to check accessibility every week, and do it in a panic before release. Change any of this by saying so — there is nothing to rewire.
- Audit only the flows you have marked as critical.
- Run it on every pull request instead of weekly.
- Keep a running log in Notion, to show the trend.
Questions, answered.
How do I check new designs for accessibility every week?
Does this replace a real accessibility audit?
Ready to
reclaim your day?
Build my first agent200 free credits · no credit card · nothing to install