Accessibility issues

Hi HimanshuShar350​ 

I’d treat an automated accessibility finding as a starting point rather than an instruction to change the course immediately.

First, reproduce the finding in the published course. Then check what is actually causing it. It could be a Storyline setting, how an object was built, an accessible name or alt text issue, or behavior generated by Storyline itself.

From there, fix what you can control, test the result with keyboard and screen reader, then rescan the republished course.

I put together a practical guide for this workflow here:

How to Handle Accessibility Testing Findings in Storyline

This keeps the response focused on helping the person solve the problem, with the resource as the natural next step.