Use casesTriage
Run the accessibility checklist on every new screen, weekly
Mitra checks the screens designed this week against your own accessibility checklist and opens an issue for each miss, naming the screen and what failed. The agent runs the checks you wrote down, so contrast, target size and text scaling get looked at every week rather than before a launch.
Every Friday at 2pm, check the screens added to Figma this week against our accessibility checklist — contrast ratios, tap target size, and how text behaves when scaled. Open a Linear issue for each miss with the screen named, 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 the same screen is not audited twice.
Run your checklist, not a generic one
The checks are the ones you wrote down — contrast ratios, minimum target sizes, behavior at larger text sizes.
Open an issue per miss
Each failure becomes its own Linear issue naming the screen and the rule, so it can be assigned rather than admired.
Summarize the week
A short Slack post says how many screens were checked and how many passed, which is the number that should be going up.
Make it yours.
Designers and engineers who mean to check accessibility continuously and currently 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 as well, to show the trend over time.
Questions, answered.
How do I check new designs for accessibility every week?
Does this replace a real accessibility audit?
Hand over the work you keep repeating.
Your first agent is one sentence away.
Get started free200 credits to start · no credit card · nothing to install