Forum Discussion
Ordered/Unordered List not using semantic mark-up in the Notes section
When adding content to the Notes panel in Storyline 360, we can apply semantic mark-up using the heading definitions and text formatting tools available to text within text fields for slide content.
What I have found is that the headings are correctly marked up as headings, but bullet lists (ordered and unordered) are not correctly marked up.
This means the screen reader does not get the correct information. For example, the list is not announced, which means the number of items in the list are not announced and the list type is not announced. This also means that nested lists (indented) are also not identified. Each list, regardless of layout is just read as a sequence of bullet items (if unordered) or a sequence of numbers (if ordered).
Here's a video demonstrating the issue: https://app.screencast.com/WGiiTXZfjjYaa
It would be great to get this up to scratch with the rest of the product as I understand many people use the Notes section for audio/video transcripts.
4 Replies
Hi SamHill!
Thank you for sharing the feedback!
We understand how important it is for screen reader users to receive accurate information about listed items from a Storyline course. By default, Storyline publishes courses with semantic formatting for headings, links, lists, and other elements so screen reader users can understand and explore the content easily. If you're experiencing issues with bullet lists not being correctly marked up, it's helpful to check if the text is using Modern Text formatting.
However, if the project text has already been upgraded, and screen reader dictation is still inaccurate, do you mind sharing a copy of the .story file you've been working with? Feel free to upload that here in the discussion, or privately through a support case. Also, can you clarify which screen readers were used in your testing?
Looking forward to hearing from you!
I believe Sam is saying the notes is not using semantic markup and the video confirms that
Thank you, SamHill. I am seeing the same behavior with a quick test, and I'll get this reported to the right team.
Thanks LeslieMcKerchie I appreciate this. It is affecting our WCAG/508 conformance as our modules are failing testing on these items. I haven't tested blockquotes, just the heading levels. I'll do a quick test now on blockquotes.
Update: I can confirm blockquotes use the correct semantic HTML.
