Rethinking Storyline's Accessibility Checker Guidance on Accessible Video Controls and Autoplay

Hi AustonStamm​ 

I think the bigger point here is that passing the Accessibility Checker does not necessarily mean the accessibility review is finished.

For something like video controls, I’d test the published course with the keyboard and check whether the controls behave as expected. If a screen reader is part of your testing requirements, I’d test that as well.

I’d also check whether Storyline’s player controls and any custom video controls are both exposed to the learner. Two separate control sets can create a confusing experience even when the individual controls are accessible.

A useful workflow is:

Scan → verify → fix what you can → manually test → rescan.

I put together a practical guide for working through accessibility findings in Storyline:

How to Handle Accessibility Testing Findings in Storyline