# Is Discourse AA compliant?

**URL:** https://meta.discourse.org/t/is-discourse-aa-compliant/131317
**Category:** Support
**Created:** [October 17, 2019, 10:51pm UTC](https://meta.discourse.org/t/is-discourse-aa-compliant/131317 "2019-10-17T22:51:38Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Nina\_11](https://avatars.discourse-cdn.com/v4/letter/n/3ab097/32.png) [@Nina\_11](https://meta.discourse.org/u/Nina_11)
#### Post date: [October 17, 2019, 10:51pm UTC](https://meta.discourse.org/t/is-discourse-aa-compliant/131317/1 "2019-10-17T22:51:38Z")

</div>

Hi - I see there’s a lot of work that Discourse has put in for accessibility. Does anyone know if Discourse is AA compliant?

---

<div class="post-metadata">

### Author: ![Heather\_Dudley](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/heather_dudley/32/151925_2.png) [@Heather\_Dudley](https://meta.discourse.org/u/Heather_Dudley)
#### Post date: [October 17, 2019, 11:01pm UTC](https://meta.discourse.org/t/is-discourse-aa-compliant/131317/2 "2019-10-17T23:01:25Z")

</div>

I’ve had a few complaints about accessibility on my forum. On mine, sometimes our vision-impaired users complain their VoiceOver and screen reader technology doesn’t cooperate well.

Some examples:

> [@](#):
>
> Another issue I’ve noted: The VoiceOver screen reader (and probably other screen readers) don’t follow changes in focus due to the keyboard shortcuts. For example, hitting the = key opens the hamburger menu, but VoiceOver focus doesn’t jump to that menu.

Another:

> [@](#):
>
> While this seems like an issue for any user, it’s especially painful for the vision impaired with VoiceOver screen reader enabled, as we frequently use Command+Up/Down Arrow to not just move to the top/bottom of a page but also bring focus to the first/last readable HTML element. It’s especially useful for quickly jumping to the top banner from any point on any web page.

We’ve also had some complaints from our neurodivergent users about infinite scrolling.

---

<div class="post-metadata">

### Author: ![Nina\_11](https://avatars.discourse-cdn.com/v4/letter/n/3ab097/32.png) [@Nina\_11](https://meta.discourse.org/u/Nina_11)
#### Post date: [October 17, 2019, 11:02pm UTC](https://meta.discourse.org/t/is-discourse-aa-compliant/131317/3 "2019-10-17T23:02:17Z")

</div>

Ah thanks! So I do mean AA compliant but not Alcoholics Anonymous compliant!

I’m talking about AA compliant that is a part of the WCAG 2.0 guidelines: [WCAG 2 Overview | Web Accessibility Initiative (WAI) | W3C](https://www.w3.org/WAI/standards-guidelines/wcag)

---

<div class="post-metadata">

### Author: ![awesomerobot](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/awesomerobot/32/142900_2.png) [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [October 18, 2019, 12:54am UTC](https://meta.discourse.org/t/is-discourse-aa-compliant/131317/4 "2019-10-18T00:54:14Z")

</div>

I’d say we’re pretty close, but we’re not completely compliant at this time. It’s definitely possible that we’ll be compliant within the next year.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [November 17, 2019, 1:01am UTC](https://meta.discourse.org/t/is-discourse-aa-compliant/131317/5 "2019-11-17T01:01:43Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
