Accessibility Review Agent
Checks designs against accessibility standards.
- Industry
- Insure AI
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Head of Distribution
- Code
- DSN-04
It checks designs of quote, claims and servicing journeys and policy documents against accessibility standards, and decides whether a release can go ahead or must be fixed first. It weighs that people making claims are often under stress, older or have a disability, so a blocker on FNOL or cancellation is never waived.
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 agent and broker portal: the release's screens and their component versions..
- 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 Distribution with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the agent and broker portal: it records the accessibility decision on the release and creates fix items. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The accessibility standard, the insurer's accessibility statement, the journeys that must stay accessible (FNOL, cancellation, complaints, payments), and document accessibility rules.
Reads from
the agent and broker portal: the release's screens and their component versions.
Acts in
the agent and broker portal: it records the accessibility decision on the release and creates fix items.
Hands back
An object with decision (release, release_with_fixes or block), issues (a list, each with criterion, screen, severity and fix), exceptions (a list) and fix_dates (a list).
Asks a person when
An exception is asked for, a serious issue ships with a fix date, or a protected journey has any blocker.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| WCAG level | AA | The level enforced. |
| WCAG version | 2.2 | The version enforced. |
| Lowest text contrast | 4.5 | Contrast ratio for body text. |
| Smallest touch target (px) | 24 | Smallest tap target. |
| Journeys that can never ship with a blocker | fnol, cancellation, complaints, payments, claim_tracking | Comma-separated. |
| Days to fix a serious issue | 30 | Serious issues on other journeys get this long. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check against WCAG 2.2 level AA, text contrast 4.5 and targets of 24 px.
- A blocker on fnol, cancellation, complaints, payments, claim_tracking stops the release; no exception is possible.
- Serious issues elsewhere may ship with a fix date within 30 days, approved by the Head of Distribution.
- Policy documents and letters must be available in accessible formats, such as large print and screen-reader friendly PDFs.
- Timeouts in quote and claim journeys must warn and let the user extend.
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.