axe-core
Check rendered pages for detectable accessibility issues during template reviews.
Community support
Upvotes come from SearchEngineAnswer members. GitHub stars and reader reviews are counted separately.
Claim this tool if you maintain it.
- Best for
- Site audits
- Setup required
- Node.js and npm to install the package. Run the engine against a rendered document in a browser or browser test harness.
- Costs to check
- No engine license fee. Budget for browser test infrastructure and manual accessibility review.
- License in catalog
- MPL-2.0
GitHub repository
- GitHub stars
- 7,788
- Forks
- 985
- Last push
- 2026-11-05
- Primary language
- HTML
GitHub snapshot from . Stars count GitHub bookmarks. Reader ratings appear separately below.
How to install axe-core
-
Install axe-core with npm in a local browser test project or fixture directory.
npm install axe-core - Load the installed axe.min.js file into your local HTML fixture with a script tag, then open the fixture in a browser.
First tutorial for axe-core
-
Add a visible icon-only button with no accessible name to the fixture. In the browser console, run axe and inspect the violations array.
axe.run().then(result => console.log(result.violations)); - Give the button a descriptive accessible name and run the same scan again. Confirm that the button is no longer flagged for that issue.
Where axe-core fits
Use it to catch detectable accessibility regressions on article templates, such as missing accessible names for icon buttons.
- When to choose another tool
- Use keyboard and assistive technology checks for interaction quality, reading order, and issues that automated rules cannot judge.
- First evaluation
- Create a local HTML fixture with a visible icon-only button that lacks an accessible name. Run the engine and check whether it reports the button.
- How to interpret the result
- A clean result covers the tested rules and page state only. It does not establish accessibility compliance or a search ranking benefit.
Reviews and discussion
Reader reviews
Be the first to share your experience with this tool.
Discussion
Ask a question or share a setup tip.
Flag an outdated detail
Include the field that needs updating and a source link. Copy your draft, then use the corrections policy to contact the editorial team.
Write a review or join the discussion