Move from WCAG 2.1 AA to WCAG 2.2 AA



In the past it was agreed that XWiki would strive to fulfill the WCAG 2.1 level AA standard.
This standard has been updated and the current recommendation is WCAG 2.2.


I propose to update our goal to say we aim at fulfilling the WCAG 2.2 level AA instead of the WCAG 2.1 level AA.


There’s not much changed in WCAG 2.2 compared to 2.1 (even less when we consider only level AA). Updating this would not add any work because the WCAG 2.2 updated rules were already used as an advisory to prepare for a seamless migration (e.g., CSS recommendation: pointer targets are large enough ).
Note that WCAG 2.1 AA still exists, it still makes sense to say we fulfill it. However updating to the 2.2 version also shows that we care about and keep in touch with the progress of web accessibility :slight_smile:


Here’s my +1.

Thank you for reading this proposal, I’m looking forward to your feedback! :slight_smile:
Lucas C.

+1, thank you!


Two points:

  1. make sure to update our docs on when this is agreed
  2. is our usage of axecore already set for WCAG 2.2 for our tests? I think I know the answer :wink:


:+1: I noticed we didn’t even write the exact goal down on, even if our strategy gave a very large hint about the goal. I’ll add a sentence at the start here, and also something in

Yup, see xwiki-platform/xwiki-platform-core/xwiki-platform-test/xwiki-platform-test-ui/src/main/java/org/xwiki/test/ui/ at f2e3326ecae5ed37b4fcb6194077d1efb37c3ad6 · xwiki/xwiki-platform · GitHub there wasn’t even a comment about it not being in our scope yet, so no need to update anything here ^^’

Lucas C.

It would be best to have the specific info in a single place and link the other places to this place (less maintenance).

Note that we have it in but I’m not sure if it’s the right place for it.

Note: Strangely we mention WCAG 2.2 AA on (we should probably also link to our single place where we mention our goal).

Ah yes, I remember my comment that it’s not nice that they don’t have a ruleset for a given version of WCAG. This forces us to monitor their rules and how they evolve across axe-core releases to make sure we’re not missing new ones or still using old ones that are deprecated.

1 Like


+1 thanks

+1 thanks

Positive proposal result. I’m closing this subject and proceeding with the changes to documentation discussed :slight_smile:

Thank you for your participation!
Lucas C.