Some problems arose during an accesibility audit
Feb 06, 2023
We chose Rise 360 because we were under the impression that content create by Rise 360 would be WCAG 2.0 compliant AND accessible to screen readers. We recently had an audit done and here are the critical results (using JAWS). I am not sure how to address these other than removing the various components below. Any suggestions?
| The carousels are not accessible to screen reader users. The entirety of the carousel is exposed to screen reader users, beyond what is visually available. Attempting to navigate the carousel with a screen readers moves the focus to the top of the page, resulting in users having to listen to the entire page/carousel over again. Additionally the carousels are labeled "Process group" with aria-label="Process" role="group". This is not informative for users. |
| The sorting activity is not screen reader accessible. Users cannot move the cards if a screen reader is being used. If a user attempts the activity, focus is moved to the top of the page. Additionally, as the activity is currently set up the only way a user knows that their choice is incorrect is by seeing the card shake. Screen reader users need a way to receive this feedback when the activity is accessible to them. |
| The matching activity is not screen reader accessible. Users cannot move the cards if a screen reader is being used. The right column is not available to screen reader users. |
1 Reply
Hello, Gilberto! Thanks so much for sharing those details with us.
This article lists blocks that currently aren't in conformance with WCAG guidelines. At this time, we don't recommend using carousels, sorting activities, and matching activities when creating accessible content, for the reasons you listed.
In case you do use them, we've provided partial workarounds here.