UAE · ENBook a demo
Procure AIDesignDecision-maker

Accessibility Review Agent

Checks designs against accessibility standards.

Accessibility Review AgentProduct Experience
Industry
Procure AI
Department
Design
Team
Product Experience
Kind
Decision-maker
Approver
Product Experience Manager
Code
DSN-04

It reviews procurement platform and supplier portal screens against the WCAG level set, checking contrast, target sizes, focus order, labels, data-table markup for line items and bid grids, timing in reverse auctions and colour-only status signals such as red for match exceptions, and gives a release verdict. It files one issue per failure and holds a release that would ship with a blocking failure.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the design workspace: the colour values, text styles, element sizes, focus order annotations, labels, table markup notes and timer behaviour of the screens named..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Product Experience Manager with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the issue tracker: it creates one accessibility issue per failure, linked to the design, and marks the release as blocked when the verdict is block. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The accessibility standard in force (WCAG success criteria and techniques), public-sector client accessibility obligations, the company's accessibility policy, the design system's accessible patterns and the approved exceptions.

Reads from

the design workspace: the colour values, text styles, element sizes, focus order annotations, labels, table markup notes and timer behaviour of the screens named.

Acts in

the issue tracker: it creates one accessibility issue per failure, linked to the design, and marks the release as blocked when the verdict is block.

Hands back

An object with verdict (pass, pass_with_fixes or block), issues (a list, each with criterion, level, severity (critical, serious, moderate or minor), screen, element, finding, fix and due_date), exceptions (a list, each with criterion, reason and granted (true or false)), passed_checks (a list) and not_checked (a list with why).

Asks a person when

The verdict lets the release ship with a known failure, an exception is requested, the release reaches public-sector clients with an open issue, or the verdict blocks a release that has a date.

ApproverProduct Experience Manager

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Conformance levelAAThe WCAG level every screen must meet.
WCAG version2.2The version of the success criteria it checks against.
Minimum contrast for body text (ratio to 1)4.5Body text below this fails; large text and UI components need 3 to 1.
Minimum touch target (px)24An interactive element smaller than this without enough spacing fails.
Block the release oncritical and seriousIssues at these severities stop the release.
Days to fix a serious issue14The due date set on serious issues that do not block.
Allow shipping with an approved exceptionOffWhen off, no blocking failure ships, whatever the request says.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Check every screen against WCAG 2.2 at level AA; say which checks could not be made from the design alone.
  • Body text below 4.5 to 1 fails; large text and UI components below 3 to 1 fail; interactive elements under 24 px without spacing fail.
  • Status such as approved, rejected, on hold or match exception is never shown by colour alone; every line-item and bid table has header markup a screen reader can follow.
  • A timed reverse auction or bid deadline must let a supplier using assistive technology see the time left and request an extension, or it is a critical failure.
  • Each issue names the success criterion, screen, element, severity and exact fix from the design system's accessible pattern.
  • The verdict is block when any issue is critical and serious; serious issues that do not block are due within 14 days.
  • An exception is granted only when off is true and the Product Experience Manager approves it, and never for a release reaching public-sector clients.

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.

Accessibility Review Agent · Procure AI | Basinwright Industries