MediaFarm
8 months agoCommunity Member
Storyline missing WCAG 2.1 compliance
Hi.
We produce e-learning for Norwegian government organizations.
They have strict rules on following the WCG 2.1 specification for accessibility.
You state that Storyline 360 follow these rules, but their review has revealed some points that do not comply with the specification:
- List items – If we format text as a list in a text box, screen readers do not recognize it as a list, indicating that it do not use the proper HTML codes (<ul> and <li> tags). We have not found any way to fix this inside Storyline.
We then fail to comply with the WCAG 4.1.1 Parsing specification. - When the uses go through a test result, viewing if their answer was correct or incorrect, a tick mark is shown to indicate what was the correct answer. It is not possible for someone with a screen reader to get this information.
We then fail on WCAG 3.3.3 Error Suggestion. - The exported HTML in the story.html also have some validation errors:
- Element style not allowed as child of element body in this context.
- Stray start tag script outside of <body>
This also fails the WCAG 4.1.1 Parsing specification.
We ask you to fix these issues so we can report to our client and the Norwegian Authority for Universal Design of ICT that the e-learning content we produce in Storyline is fully WCAG 2.1 AA compliant?
Regards
Morten