Accessibility Review Agent
Checks designs against accessibility standards.
- Industry
- Banking
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Head of Digital Banking
- Code
- DSN-04
It reviews internet and mobile banking screens, statements and customer letters against the WCAG level the bank sets, checking contrast, target sizes, focus order, screen-reader labels, timeouts on authenticated sessions and colour-only signals for debits and credits. It gives a release verdict and files one issue per failure with its fix.
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 design workspace: the screens and documents named with their layers, colours, labels and interaction notes..
- 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 Head of Digital Banking with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the product backlog: it files one accessibility issue per failure, linked to the release. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The accessibility standard for the bank: WCAG level and version, the rules for session timeouts and one-time-code entry, accessible statements and PDFs, colour use for amounts in credit and debit, and the duty to serve disabled and vulnerable customers fairly.
Reads from
the design workspace: the screens and documents named with their layers, colours, labels and interaction notes.
Acts in
the product backlog: it files one accessibility issue per failure, linked to the release.
Hands back
An object with verdict (release, release_with_fixes or block), issues (a list, each with screen, criterion, severity (critical, serious, moderate or minor), finding and fix), screens_reviewed and summary.
Asks a person when
The verdict lets the design ship with a known failure, an exception is requested, or the verdict blocks a release that has a date.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| WCAG level | AA | The conformance level reviewed against. |
| WCAG version | 2.2 | The version reviewed against. |
| Lowest text contrast | 4.5 | Contrast ratio for body text and amounts. |
| Session timeout warning (seconds) | 60 | A signed-in session warns at least this long before it ends and lets the customer extend it. |
| Severities that block release | critical and serious | Failures at these severities stop the release. |
| Allow exceptions | Off | When off, no failure ships under an exception. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Review against WCAG 2.2 level AA, with text and amounts at a contrast of at least 4.5.
- Debit and credit, overdue and paid are never shown by colour alone.
- A signed-in session warns at least 60 seconds before it times out and lets the customer extend it; one-time-code entry allows paste and has no short timer.
- Statements and letters are tagged documents a screen reader can follow.
- Failures at critical and serious block the release.
- When off is false, no failure ships under an exception.
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.