Agent skill

Accessibility check: catch what people cannot read before it ships

Audits a page, a design or a colour palette against WCAG 2.2 Level AA, with a fix for each finding.

The accessibility check is a skill in Ai1, the AI agent platform by MyZone AI. The Designer, the Landing Page Builder and the Portal Compliance Agent run it before work ships: it audits a web address, a page file or a set of colour pairs against WCAG 2.2 Level AA and returns a report with each finding and how to fix it.

Book a call See an example check
  • Part of Ai1
  • WCAG 2.2 Level AA

  • Text everyone can read

    Colour pairs that fail contrast are caught before they reach a page or a pack.

  • Fixed before launch

    Problems are found in the design, not after customers complain.

  • A fix for each finding

    Each issue comes with what to change.

At a glance

The accessibility check in short

The accessibility check at a glance
ChecksA web address, a page file or a set of colour pairs
StandardWCAG 2.2 Level AA
You getA report with each finding and its fix
WhenBefore a design, page or app ships
Run byThe Designer, the Landing Page Builder and the Portal Compliance Agent
DecidesYou, at the design and page approvals

Why check accessibility before you ship

A colour that looks right on screen can fail the contrast test, so small print and buttons become hard to read for many customers. Finding it after launch means rework on a live page. The check runs before you see the final design, so what reaches you has already been tested.

How this differs from the Designer as a whole: the agent builds your brand book and designs; this skill is the accessibility test every final design must pass.

How it works

From a design to a pass or a fix list

Four steps, before anything reaches your review.

How the Designer works: you ask through the Comms Hub and Ai1 runs the steps: brief it, brand first, wireframe review, design and check and final sign-off. It works with Figma. You approve at: wireframe review, final sign-off. It returns a finished designs.
Tap the diagram to enlarge it

Step 1: The work is ready

A design, landing page or app reaches the end of its build.

Step 2: It runs the audit

The page or colour pairs are checked against the standard.

Step 3: It reports the fixes

Anything that fails comes back with what to change, and is fixed before review.

You approve

Step 4: You approve the result

You review the checked work. It goes live only after your approval.

Example accessibility check

Example: a new tea brand's colours and a plumbers page

Example with a fictional business. Names and figures are invented to show the kind of output you get.

What it was asked: Give me a calm, grown-up starter look for my new tea brand (colours, fonts, logo direction, a tin and a home page sketch, and the rules) that my designer can use from day one.

What the checks found, a fictional tea brand and a fictional landing page
Brand coloursFour of seven colours are safe for small text. Green on the rose tin failed contrast at 4.25 to 1, so small print uses dark ink.
Landing page buttonFixed. A low-contrast button failed the first build of a plumbers page and was fixed before review.
Seven colour swatches for a fictional tea brand, from oat paper to deep green and amber, with hex codes and a table showing which text and background pairings pass or fail the readability test.
Colour paletteSeven colours with hex codes and which text and background pairs pass the readability test.
A table of five checks shows two issues on the first build, a buzzword and a low-contrast button, both fixed and now passing, followed by the approval path: your design review, a separate review of the live staging page, then live only when you say push it to live.
Checks and approvalsTwo issues on the first build, both fixed and passing, before your approvals.

Built-in guardrails

It checks, you approve

How the accessibility check fits around your approvals.

  • Nothing reaches your review until the checks have run.
  • It reports findings and fixes. Approved work is published by your web team, never by the check.
  • Brand colours are never changed by the check. Problem pairings are flagged with a safer use.

Better together

Works well with

The agents that run this check, and a skill they work with.

Common questions

Frequently asked questions about the accessibility check

What standard does it check against?

WCAG 2.2 Level AA, the level most accessibility rules and policies ask for.

What can it check?

A live web address, a page file before it is published, or just a set of colour pairs, such as a new brand palette.

Who fixes what it finds?

The agent that built the work fixes it before your review, and the report says what changed. Live changes are published only after your approval.

Check your pages before they ship

Send us a page or your brand colours and we will show you the check.

Book a call See plans & pricing
  • Your own private serverEvery Ai1 plan runs on a private server that belongs to your business alone.
  • Your data stays yoursStored on your server, not used to train AI models, and you can export everything you build at any time.
  • Choose your AI modelBring your own AI provider account and pay it directly, with no markup from us.
  • No lock-inMonthly plans run month to month with no long-term commitment, and everything you build can be exported.