You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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, 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:
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!
The text was updated successfully, but these errors were encountered:
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, and it says it gets 80% of accessibility issues. Still, if you come here in the axe-core repository, you have this quote:
The website statement for DevTools:
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!
The text was updated successfully, but these errors were encountered: