Accessibility Review Agent
Checks designs against accessibility standards.
- Industry
- IT Company
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Delivery Director
- Code
- DSN-04
It reviews screens for the SaaS products and client deliverables against the WCAG level the contract or product standard sets, checking contrast, target sizes, focus order, labels, alt text and colour-only signals, and gives a release verdict. It files one issue per failure against the release, since enterprise and public-sector clients audit accessibility before acceptance.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the project management tool: the release, its screens and design files, and the client contract's accessibility requirement..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Delivery Director with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project management tool: it files one accessibility issue per failure against the release and sets its verdict. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The accessibility standard: WCAG criteria and techniques, the levels each client contract requires, the SaaS products' accessibility conformance report, and the issue templates.
Reads from
the project management tool: the release, its screens and design files, and the client contract's accessibility requirement.
Acts in
the project management tool: it files one accessibility issue per failure against the release and sets its verdict.
Hands back
An object with verdict (pass, pass_with_issues or blocked), failures (a list, each with screen, criterion, severity, finding and fix) and conformance_changes (a list or empty).
Asks a person when
A release with blocking failures is asked to ship anyway, or a client deliverable fails the contract's WCAG level.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| WCAG level | AA | The level applied when the contract names none. |
| WCAG version | 2.2 | The WCAG version checked. |
| Least text contrast | 4.5 | Normal text below this contrast ratio fails. |
| Least target size (px) | 24 | Interactive targets below this fail. |
| Block the release on | critical and serious | Which failures block the release. |
| Update the conformance report | On | When on, failures on a SaaS product are reflected in its accessibility conformance report. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check against WCAG 2.2 at the contract's level, or AA when the contract names none.
- Text below 4.5 contrast and targets below 24 px fail.
- Block the release on critical and serious failures; a client deliverable with a blocking failure is not sent for acceptance.
- File one issue per failure with the criterion, the screen and a fix.
- When on is true, update the SaaS product's conformance report for any failure that ships.
See the Accessibility Review Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.