Accessibility issues

One of our clients is performing accessibility QC on a Storyline SCORM package using an automated accessibility testing tool. While the client has not explicitly mentioned the tool name, based on the type of issues reported, it appears that a tool such as axe DevTools may have been used.

As per my understanding, tools like axe are primarily designed for evaluating custom HTML websites where developers have direct control over HTML structure and ARIA attributes. However, this course has been developed using Articulate Storyline, which automatically generates the HTML and ARIA markup through its player framework.

Given these authoring tool constraints, we are unsure how to address certain reported issues that require direct HTML or ARIA-level changes. Has anyone encountered a similar situation, and could you please share how such accessibility findings are typically handled or communicated when working with Storyline-generated content?

Also, attaching the list of issues that we received.