Which standard does it check?

WCAG 2.1 AA, including contrast of at least 4.5:1 for normal text and 3:1 for large text and UI parts, keyboard access, a logical focus order, a visible focus indicator, touch targets of at least 44 by 44 pixels, clear labels and error messages, and name, role, and value for every control.

What does the audit look like?

A summary count of critical, major, and minor issues, then findings grouped by the four WCAG principles with the criterion, severity, and a recommendation for each. It ends with a contrast table, a keyboard navigation table, a screen reader table, and a ranked list of priority fixes.

How is this different from the AI Design Critique?

The design critique reviews usability, visual hierarchy, and consistency with a short accessibility section. This tool is only about accessibility and goes through WCAG 2.1 AA criterion by criterion.

Does this make my site compliant?

No. It is a review to guide your fixes, not a certification or a legal opinion. Automated checks catch only part of the issues, so test with a keyboard and with screen readers such as VoiceOver or NVDA as well.

It does not fix your code, run a screen reader on your live site, or check WCAG 2.2 or AAA criteria. Contrast ratios are only as exact as the colors you give it, so share hex codes when you can.

AI Accessibility Checker

Share a screenshot or a description of a page, screen, or flow and get a WCAG 2.1 AA audit in the chat, with each issue tied to a criterion and a fix.

Run

Tap a field to fill it in

Nothing sends until you start, and you can change anything afterwards.

What you get

Text in the chatCopy it wherever you need it. Keep chatting to adjust the tone, length, or wording.

How it works

Share the page, screen, or flow as a screenshot or a description, and include the text and background colors when you know them.
askROI's Run an accessibility review tool checks it against WCAG 2.1 AA: findings grouped as perceivable, operable, understandable, and robust, each with its criterion, a severity, and a fix, plus contrast, keyboard navigation, and screen reader tables.
Read the audit in the chat, fix the critical items first, and keep chatting to check the next version or go deeper on one criterion.

What people use it for

Before a launchcatch contrast, labeling, and keyboard problems in a design before it ships.
Brand palettescheck which color pairs pass the 4.5:1 and 3:1 contrast ratios.
Forms and modalsthe usual trouble spots: missing labels, vague errors, focus traps, and small targets.
Prioritizing fixesturn a long list of accessibility problems into a ranked set of fixes for the team.

Questions

Which standard does it check?: WCAG 2.1 AA, including contrast of at least 4.5:1 for normal text and 3:1 for large text and UI parts, keyboard access, a logical focus order, a visible focus indicator, touch targets of at least 44 by 44 pixels, clear labels and error messages, and name, role, and value for every control.
What does the audit look like?: A summary count of critical, major, and minor issues, then findings grouped by the four WCAG principles with the criterion, severity, and a recommendation for each. It ends with a contrast table, a keyboard navigation table, a screen reader table, and a ranked list of priority fixes.
How is this different from the AI Design Critique?: The design critique reviews usability, visual hierarchy, and consistency with a short accessibility section. This tool is only about accessibility and goes through WCAG 2.1 AA criterion by criterion.
Does this make my site compliant?: No. It is a review to guide your fixes, not a certification or a legal opinion. Automated checks catch only part of the issues, so test with a keyboard and with screen readers such as VoiceOver or NVDA as well.
What does it not do?: It does not fix your code, run a screen reader on your live site, or check WCAG 2.2 or AAA criteria. Contrast ratios are only as exact as the colors you give it, so share hex codes when you can.