auditing-web-accessibility

Provide the target URL and the Skill launches a browser, runs a full axe-core audit on each page, and groups violations by critical, serious, moderate, and minor impact. It finishes by generating an HTML report and summarizing the top fixes by leverage.

Axe-core detects missing image alt text, unlabeled form inputs, buttons without accessible names, invalid ARIA attributes, missing landmarks, computed color-contrast failures, and heading-order problems. Each violation includes its rule id, description, helpUrl, and affected nodes.

Yes, capture an authenticated session once with the authenticated-sessions skill, then launch the audit with a storage_state_path so every page is audited in the logged-in state. Authenticated surfaces like dashboards often carry different findings than public pages.

No, automated tools cover only a subset of WCAG criteria and cannot fully test keyboard traps, focus order, or screen-reader announcement quality. Treat the audit as a fast first pass and pair it with manual VoiceOver or NVDA testing for compliance claims.

If axe-core fails to load, the tool silently falls back to about eight supplementary checks and the response looks identical. A suspiciously clean result on a complex, ARIA-rich page is worth re-running before concluding the page is accessible.

Use the Lighthouse audit skill, which returns Lighthouse's official Accessibility score for dashboards and tracking targets. This skill returns the itemized axe violations behind such a score, and the two outputs are not convertible.