Accessibility - Broken ARIA Reference

Sep 23, 2020


I am developping a course that need to meet WCAG 2.0 AA standards. I am using the WAVE Evaluation Tool to verify everything works and I'm getting a few errors on Broken ARIA references. These errors seems to come from the fact that some of my menu item have the ARIA-LABELLEDBY attribute set to blank. It seems to be only on the first element of each modules that has a heading. (see attachments). Any help?

2 Replies
Lauren Connelly

Hi Frédéric!

I'm happy to help! You'll see on our feature roadmap that we are currently working on semantic formatting. This feature will make sure text publishes with the proper semantic formatting for headings, links, etc. so screen reader users can explore content easily.

Stay up-to-date by booking the Storyline 360 release notes!

Leslie McKerchie

Hello again, Frédéric!

We just released another update for Articulate 360 and included a few new items you'll see in the release notes.

The items you'll be interested in is:

  • New: Let learners with accessibility needs change the visual appearance of text in a published course to make it more readable. Learn more about accessible text.
  • New: Text publishes with the proper semantic formatting for headings, links, lists, and other elements so screen reader users can explore content easily.
  • New: Use text styles to make content easy to navigate with a screen reader. Accessible text styles allow learners with visual disabilities to identify headings, hyperlinks, blockquotes, and paragraphs on each slide so they understand its layout and context. Learners can also use screen reader shortcuts to jump directly to headings and links.

Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.