Forum Discussion
Accessiblity tag Landmark failing accessibility audit
Hi,
A Storyline module has been audited by our external accessibility auding company and it has failed on the basis that Landmaek tags have been applied to Next and Previous buttons and Exit Full ...
Hello Darren,
Thank you for sharing the results that you've experienced.
We reorganized the Storyline 360 player controls into logical groups, added ARIA landmarks, and restructured player features to follow a consistent order and hierarchy. As a result, it’s easier for learners with assistive technologies to understand the structure of a course, stay in context, and move around quickly.
I'm curious about why your audit shows a navigation landmark role as a failing element. Can I ask if you've tried using online accessibility evaluation tools to confirm if you'll get the same results as the audit?
It's best practice for all of your page content to have landmarks for screen reader users. Is your audit company using automated testing tools or is this a manual audit? I've tested in three automated tools and I'm unable to recreate this error in the player.
