JSX-A11y Plugin Compatibility with WCAG 2.2

[jashan777]

Hello! I’m opening this issue to inquire about the compatibility of the current plugin rules with WCAG 2.2. Are there any plans to update the plugin to align with the WCAG 2.2 guidelines?

[ljharb]

It just came out last October.

Any changes that are nonbreaking can be easily added. What new guidelines did you have in mind? I'm not seeing anything on https://dequeuniversity.com/resources/wcag-2.2/#:~:text=New%20Success%20Criterion-,Summary%20of%20Changes,was%20released%20in%20October%202023. that would or could be handled by linting.

[jashan777]

thanks for such a speedy reply, I was looking at the rules documentation and the rules follow Wcag 2.1 Accessibility guidelines and there are some points I noticed (related to Wcag, in context to rules documentation)

1. The jsx-a11y/scope rule: 4.1.1 Accessibility guidelines Parsing is obsolete and removed from WCAG 2.2.
2. No other rule change.
   with the above points, is there a possibility that the plugin rules documentation can be updated to point to WCAG 2.2?

[ljharb]

That doesn't mean the scope rule isn't useful - that WCAG no longer requires violating it to be a parsing error doesn't mean it's correct to violate it.

[jashan777]

I’m completely with you on this—I was just bringing up the point with respect to WCAG 2.2 standards and not to question the value of the rule itself.

[ljharb]

So, it sounds like there's nothing we need to do to be compliant with WCAG 2.2.