dequelabs / dequelabs/axe-core

What is the correct percentage of issues that axe actually finds it when running?

Open
#4,415 1 comment 0 reactions 0 assignees View on GitHub
extension question
Dominant language
JavaScript
Stars
7.5k
Forks
933
Avg merge
2d 23h
Merged PRs (30d)
17

Description

### Product

axe Extension

### Question

Hello! Could you please clarify the correct percentage that axe-core usually gets when running?

I ask this because sometimes we need to prepare presentations and slides with this information. Yesterday, I was looking at the [Deque DevTools website](https://www.deque.com/axe/devtools/), and it says it gets 80% of accessibility issues. Still, if you come here in the axe-core repository, you have this quote:

> With axe-core, you can find on average 57% of WCAG issues automatically. Additionally, axe-core will return elements as "incomplete" where axe-core could not be certain, and manual review is needed.

The website statement for DevTools:

image

Axe is amazing, but in my position, I have to report to some other leadership asking what's the impact of using tools for A11Y, and it would be amazing to have some clarification on this subject.

Thank you for all your work!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.