# WCAG 2.1 AA+ accessibility rules in SonarQube

**URL:** <https://community.sonarsource.com/t/wcag-2-1-aa-accessibility-rules-in-sonarqube/177930>\
**Category:** Sonar Updates\
**Tags:** html, a11y, wcag, accessibility\
**Created:** [February 17, 2026, 10:03pm UTC](https://community.sonarsource.com/t/wcag-2-1-aa-accessibility-rules-in-sonarqube/177930 "2026-02-17T22:03:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gab](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/gab/32/72206_2.png) [@gab](https://community.sonarsource.com/u/gab)\
**Post date:** [February 17, 2026, 10:03pm UTC](https://community.sonarsource.com/t/wcag-2-1-aa-accessibility-rules-in-sonarqube/177930/1 "2026-02-17T22:03:48Z")

</div>

Hello Community,

We’ve added new accessibility rules for Web Content Accessibility Guidelines (WCAG) criteria:

- WCAG 2.1 A: 60% coverage (18 of 30 requirements)
- WCAG 2.1 AA: 52% coverage (26 of 50 requirements)
- WCAG 2.1 AAA: 38% coverage (30 of 78 requirements)

Coverage in this case means SonarQube has rules for these criteria.

This brings our total number of [accessibility rules](https://next.sonarqube.com/sonarqube/coding_rules?tags=accessibility) to 114 for HTML, CSS, and JSX (JS/TS).

This better coverage makes it easier for teams to spot and fix accessibility problems much earlier. This helps companies meet compliance standards with less friction, lower costs and most importantly, build better software for everyone.

You can start using these new rules in SonarQube Cloud, SonarQube Server 2026.1 LTA, and SonarQube for IDE.

---

<div class="post-metadata">

**Author:** ![Pablo\_Martinez](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/pablo_martinez/32/75257_2.png) [@Pablo\_Martinez](https://community.sonarsource.com/u/Pablo_Martinez)\
**Post date:** [February 26, 2026, 12:06pm UTC](https://community.sonarsource.com/t/wcag-2-1-aa-accessibility-rules-in-sonarqube/177930/2 "2026-02-26T12:06:56Z")

</div>

Is there any plan/roadmap to have all of them covered at some point?  
Thanks!

---

<div class="post-metadata">

**Author:** ![ChristopheS](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/christophes/32/47998_2.png) [@ChristopheS](https://community.sonarsource.com/u/ChristopheS)\
**Post date:** [February 26, 2026, 5:34pm UTC](https://community.sonarsource.com/t/wcag-2-1-aa-accessibility-rules-in-sonarqube/177930/4 "2026-02-26T17:34:18Z")

</div>

> [@Pablo\_Martinez](#):
>
> Is there any plan/roadmap to have all of them covered at some point?

It is not possible to check all of WCAG automatically. The claim of 38% coverage of the 78 success criteria in WCAG 2.1 is already questionable.

---

<div class="post-metadata">

**Author:** ![Pablo\_Martinez](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/pablo_martinez/32/75257_2.png) [@Pablo\_Martinez](https://community.sonarsource.com/u/Pablo_Martinez)\
**Post date:** [February 27, 2026, 8:53am UTC](https://community.sonarsource.com/t/wcag-2-1-aa-accessibility-rules-in-sonarqube/177930/5 "2026-02-27T08:53:13Z")

</div>

Thanks for your answer Christophe  
Sorry for not being clear: I was meaning all the coverable points, I know some of them require rendering to be checked so it’s impossible doing here

---

<div class="post-metadata">

**Author:** ![gab](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/gab/32/72206_2.png) [@gab](https://community.sonarsource.com/u/gab)\
**Post date:** [February 27, 2026, 3:04pm UTC](https://community.sonarsource.com/t/wcag-2-1-aa-accessibility-rules-in-sonarqube/177930/6 "2026-02-27T15:04:10Z")

</div>

To clarify, coverage here means that SonarQube has rules for the given accessibility criteria.

Indeed not all criteria can be checked statically or sometimes _fully_ checked statically. We are aware of the limitations and appreciate the nuance. I added a note above, thanks for the feedback!