Forum Discussion

KellyRipley's avatar
KellyRipley
Community Member
20 days ago

Accessibility Audit Results - Headers/Statements

I assume and from what I can see many others are encountering issues with RISE controlled elements appearing on Accessibility compliance audits and reports.  I have a number of items that appear to be outside of the authors control, and on the other hand I see Articulate reporting as recently as yesterday that they are fully compliant.

What concerns are others encountering, and what work arounds have folks identified to address concerns?

From my end, some of my most common flags are:

  1. Critical - Pulsing marker on interactive graphics can not be turned off, or set to stop after 5 pulses within RISE solution (ie:without use of custom CSS).
  2. High - Text is cut off when user increases text spacing. (ie Flip cards, and knowledge check results).  Solution again seems to only be in custom CSS.
  3. High - Knowledge check question headings are aria-hidden. When using JAWS, this causes the heading to not be announced.
  4. Medium - Non text Contrast do not meet minimums for Lesson completion status icons (circles), audio player bar. (Rise says is the is the authors responsibility but even on white background it fails.
  5. Medium - Checkbox lists are double labelled. "Inputs have aria-labelledby and label element"
  6. Medium - All buttons, and most labels force to ALL CAPS even when label is suctom set to sentence case. 

Has anyone had any luck overcoming any of these or getting Rise to actually address them? Or do you have others to add to the list?

2 Replies

  • Caitlin_B's avatar
    Caitlin_B
    Community Member

    These are all great issues to raise. I use Storyline more often and just helped someone with pulsing markers, and I didn't even think about how they are used in Rise and there isn't a way to stop them without custom CSS.

    I'm realizing now why I probably use Storyline far more.I just have so much more control of making sure everything is keyboard and screen reader accessible without having to code.

    Hoping to see some more accessibility improvements coming from Articulate. 🤞

  • I raise any issues I find as an individual case. It is the best way to get these addressed. These all seem worthy of being raised in my opinion.