---
title: Overview
date: 2026-06-13T16:23:00+01:00
author: John Henry Donovan
canonical_url: "https://johnhenry.ie/plugins/accessibility-audit/docs/getting-started/overview"
section: Plugins
---
esc

↑↓ to navigate↵ to selectesc to close

Menu On this page 

- [Return to top](#)

Documentation

Documentation

# Overview

**Accessibility Audit** brings WCAG 2.2 accessibility scanning straight into the Craft control panel. It pairs a PHP-based HTML scanner with an optional axe-core overlay to give you broad, accurate coverage, and it works across every element type in Craft, not just entries.

## What it does

- Scans every published page with a public URL: entries, categories, and Craft Commerce products out of the box, and any custom element type you [opt in](https://johnhenry.ie/plugins/accessibility-audit/docs/getting-started/configuration).
- Checks HTML structure against **25+ WCAG 2.2 rules**, covering images, links, forms, headings, colour usage, tables, media, and document structure.
- Runs the **axe-core** accessibility engine on live page renders, catching issues you can only see once the page is rendered: things like low contrast, invisible focus states, and undersized touch targets.
- Surfaces **8** [potential issues](https://johnhenry.ie/plugins/accessibility-audit/docs/guide/potential-issues) that can't be confirmed as failures automatically, and routes them to a separate section for a human to look over.
- Tracks every issue over time and shows site-wide scores on its own [dashboard](https://johnhenry.ie/plugins/accessibility-audit/docs/guide/dashboard).
- Scores how readable your writing is against WCAG 3.1.5, and throws in [colour tools](https://johnhenry.ie/plugins/accessibility-audit/docs/guide/colour-tools) for checking contrast and simulating colour blindness.

## How scanning works

Two engines feed one score. A PHP scanner checks the HTML of every page, and axe-core covers what only a rendered page can show: contrast, focus visibility, target size. Anything both catch is counted once. Checks that need human judgement are asked as questions in [Potential Issues](https://johnhenry.ie/plugins/accessibility-audit/docs/guide/potential-issues) rather than reported as failures.

The full picture, what gets scanned, how the two engines share a score, and the complete WCAG rule coverage, lives on [Scanning Pages](https://johnhenry.ie/plugins/accessibility-audit/docs/advanced-operations/scanning-pages).

## Scoring

Each scan gets a score from 0–100, worked out from the definite issues found by the PHP and axe-core scanners. The score starts at 100 and every occurrence takes points off according to its **severity**:

SeverityPoints per occurrenceError10Warning4Notice1

So ten notices cost the same as one error. The total is floored at 0. Potential issues (the human-review checks) don't affect the score until you confirm them.

On this page