E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: Mike Warner
Date: Mon, May 06 2024 10:56AM
Subject: Articulate Storyline SCORM export WCAG 2.4.3 failure
No previous message | Next message →

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

From: Steve Green
Date: Mon, May 06 2024 11:40AM
Subject: Re: Articulate Storyline SCORM export WCAG 2.4.3 failure
← Previous message | Next message →

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 ADDRESS REMOVED = > On Behalf Of Mike Warner
Sent: Monday, May 6, 2024 5:57 PM
To: WebAIM Discussion List < = EMAIL ADDRESS 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

From: Ryan E. Benson
Date: Tue, May 07 2024 6:16PM
Subject: Re: Articulate Storyline SCORM export WCAG 2.4.3 failure
← Previous message | Next message →

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 ADDRESS 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 ADDRESS REMOVED = > On Behalf Of
> Mike Warner
> Sent: Monday, May 6, 2024 5:57 PM
> To: WebAIM Discussion List < = EMAIL ADDRESS 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
> > > > > >

From: Lyndal Box
Date: Tue, May 07 2024 6:21PM
Subject: Re: Articulate Storyline SCORM export WCAG 2.4.3 failure
← Previous message | Next message →

Hi Mike,

The auto-generated menu in Articulate Storyline is part of the "Player" frame and can be switched off during the design process before SCORM output is generated. After SCORM is generated, it is too late.

Without the auto-generated menu you can create a compliant focus order and user-friendly experience by introducing your own navigation. This requires a little more skill but can still be achieved without coding experience.

Cheers,
Lyndal

Lyndal Box
Learning Consultant
LB Learning Solutions Pty Ltd



-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Mike Warner
Sent: Monday, May 6, 2024 5:57 PM
To: WebAIM Discussion List < = EMAIL ADDRESS 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

From: Mike Warner
Date: Wed, May 08 2024 3:38PM
Subject: Re: Articulate Storyline SCORM export WCAG 2.4.3 failure
← Previous message | No next message

Thanks all. I unminified slides.min.js and found where to add code to move
the menu etc. in the DOM. It'll take a little more work to fix the CSS
classes that are no longer inherited, but it's doable.

I wonder whether anyone has filed a bug report with Articulate. I've heard
some say that accessibility issues of a critical or significant impact
should be considered as bugs.

Mike