Accessibility fix guide
Accessibility Violations Detected (axe-core)
Automated accessibility testing with axe-core found critical violations that prevent some users from accessing your content.
Issue ID: A11Y-AXE-BASIC-001
Severity: major
Impact: High
Effort: M
Use this article when
- You need deeper remediation guidance than the issue card can show.
- You want CMS-specific steps before handing the fix to a developer.
- You want a repeatable re-check path after shipping the change.
What this issue is
Automated accessibility testing with axe-core found critical violations that prevent some users from accessing your content.
Why it matters
Automated accessibility testing with axe-core found critical violations that prevent some users from accessing your content. This affects usability, compliance risk, and how many visitors can successfully consume the page.
How we detect it
- FreeSiteAudit flags this issue when the rule for A11Y-AXE-BASIC-001 fails and the page evidence points to Dom body.
- You can usually confirm this by checking the page source or the relevant page settings inside your CMS.
Evidence examples
Check the affected page source, rendered output, or relevant CMS setting to confirm the missing or incorrect element.
How to fix it
- 1Run axe DevTools in Chrome to identify specific violations
- 2Fix critical and serious violations first (WCAG 2.1 A and AA)
- 3Address form labels, ARIA roles, color contrast, and keyboard navigation
How to re-check it
- Run axe-core audit and confirm zero critical or serious violations
Related tools
This issue is best verified with the full FreeSiteAudit crawl rather than a single-point mini tool.