Accessibility

The accessibility scan checks a page against the WCAG criteria. The run usually takes only a few seconds. Two procedures are used: HTML_CodeSniffer against the WCAG level set by your administration (Level AA by default) and axe-core against its own rule set.

1. Starting the audit

Choose the type “Accessibility” and the page to check or an external URL. A focus keyword is not evaluated here and can stay empty.

2. Structure of the result

You get an audit score from 0 to 100 and the findings, split into errors, warnings and notices. Each finding names the criterion affected and carries a classification of how it can be fixed. The mix is typical: missing alternative texts are usually fixable straight away, whereas contrast or focus problems belong in the template and therefore with development or your agency.

3. Fixing findings and passing them on

Missing alternative texts can be generated straight from the result, see Fix with AI (fix wizard). For everything that depends on the template, the best route is “Export as CSV” and passing the list on.

A scan is no substitute for an audit

Automated tests find only part of the barriers. Criteria such as comprehensible language, sensible order or meaningful link texts cannot be assessed reliably by machine. A green score therefore does not mean the page is accessible.