WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Articulate Storyline SCORM export WCAG 2.4.3 failure

for

From: Ryan E. Benson
Date: May 7, 2024 6:16PM

I agree with what Steve said. That has been my experience as well.

--
Ryan E. Benson

On Mon, May 6, 2024, 1:41 PM Steve Green < <EMAIL REMOVED> >
wrote:

> It's a couple of years since I worked on Articulate Storyline, but there
> were indeed issues with the focus order of the menu. The developer
> specialised in Storyline, so we took his word when he said he couldn't even
> see the menu code, let alone fix it. There were other issues (particularly
> reflow, as I recall) but he said he could only fix the e-learning module,
> not the player it's enclosed in.
>
> BTW, this is nothing to do with SCORM, which is just a JavaScript wrapper
> that passes information between an e-learning module and its host LMS, but
> doesn't have a user interface.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Mike Warner
> Sent: Monday, May 6, 2024 5:57 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [WebAIM] Articulate Storyline SCORM export WCAG 2.4.3 failure
>
> Hi,
>
> I've been evaluating SCORM content created with Articulate Storyline and
> have found that the SCORM content fails hard for 2.4.3 Focus Order. The
> auto-generated menu is visually on the left and appears to be the first
> tabbable item, but it's really the last or almost the last tabbable item on
> the page due to its position in the DOM. Divs with IDs of sidebar, topbar,
> and app-top come toward the end of the DOM, which is the exact opposite of
> what it should be. Has anyone else experienced this and have a fix? I'm
> no Articulate expert so I could be missing a setting.
>
> Thanks,
> Mike
>
> Mike Warner
> Director of IT Services
> MindEdge Learning
> > > at http://webaim.org/discussion/archives
> > > > > >