Using Accessibility Audit

Overview

The Accessibility Audit skill (/accessibility-audit) runs a WCAG 2.1 AA accessibility audit across your highest-traffic pages and produces a report. It uses your Noibu traffic data to identify the pages worth auditing, loads the ADA Site Compliance widget on each one to surface errors and warnings, captures screenshots of the flagged elements, and compiles everything into a prioritized report your developers can work from.

Findings are grouped by severity — critical, high, and medium — and each one is mapped to the WCAG criterion it fails, paired with a recommended fix and an effort estimate.

This skill is not included with Noibu's AI plugin. It is available from the Skill Store.

When to use it

Most merchants run an accessibility review on a fixed cadence, annually or twice a year, and this skill is built for that review. It is also useful:

• Before a site redesign goes live

• After a theme or app change that touched global styles

• When you need to scope accessibility remediation clearly enough to hand to a developer or an agency

• When accessibility compliance carries legal weight in your category

Requirements

• This skill must be downloaded from the Skill Store

• A browser extension for your AI tool, such as the Claude extension for Chrome. The audit runs the ADA Site Compliance widget directly on your live pages, so your AI tool needs browser access to open each page and read the results.

How to trigger it

Ask “run an accessibility audit on my site”, “check my site for WCAG compliance”, or “where are my accessibility issues?” You can also type /accessibility-audit.

To change the scope, specify a page count — for example, “audit my top 20 pages”. The default is your 10 most-visited pages over the last 30 days.

What you get

A report containing:

• An executive summary with pages audited, total violations, and the issues needing immediate action

• A scope and methodology table listing each page with its 30-day visit count, error count, and warning count

• Key findings ordered by severity, each with a screenshot showing the flagged elements, the WCAG criterion it fails, and a recommended fix

• A prioritized recommendation table with an effort estimate per finding

• Page-by-page findings, each with a clickable link that reopens the page with the audit widget already active

• A remediation plan split into three phases, and a WCAG 2.1 criteria reference appendix