Discrepancy in tagging between the Deque University website and the repo

[jdudley1123]

Product

axe-core

Product Version

4.10.2

Latest Version

• I have tested the issue with the latest version of the product

Issue Description

Expectation

I expect the Deque University documentation linked in the console error messages to match the behaviour defined in the repo.

Actual

There seems to be a discrepancy in some of the tagging between the Deque University website and the repo. For example, the rule button-name is tagged against WCAG 2.1 (A) and WCAG 2.2 (A) on the Deque University website but in the repo it is only tagged against WCAG 2.0 (A).

This makes it confusing to work out what tags to use with according_to.

How to Reproduce

Links above, screenshots below.

Deque website:

Repo:

[straker]

Thanks for the issue. The repo uses the WCAG tag of when the success criterion was first added to WCAG, whereas the help pages on Deque University lists each WCAG version the success criterion applies to. The help pages do this since different versions of WCAG can remove success criterion, making some rules no longer valid if running against that version.

In terms of using according_to, you should always use what the repo docs have listed for tags.

[jdudley1123]

Thanks for the clarification. I think this is worth highlighting somewhere in the docs. It's very confusing when the failure messages link to a webpage that says something that's different from the behaviour of the actual tool.

Personally I would expect running according_to :wcag22aa to run against all the criterion of that spec rather than just things that have been added since the past version. My understanding is that if I want that I need to do:

expect(page).to be_axe_clean.according_to :wcag2a, :wcag2aa, :wcag21a, :wcag21aa, :wcag22a, :wcag22aa

Other than that confusion, this is a fab tool and has helped me catch loads of accessibility issues. Thank you for your work on it.