Is the HTML Output Really 508 Compliant?
Jan 12, 2015
I recently asked the IT folks at my institution involved with 508 compliance to do some testing of the visibility of items in a Storyline presentation using a JAWS reader. I provided a link to both an HTML and HTML5 output of a presentation. The presentation featured slides with narration. This is the response I received:
"The visually impaired consumer cannot pause, rewind, fast forward or adjust the volume using a Mac with Voice Over or Windows with Jaws. This also precludes functionality for other Screen Readers like System Access or Window Eyes.
"Users can navigate to different list items and next or previous buttons, but they are not marked appropriately. These missing clues can create confusion for users."
As a result I have the following questions:
My understanding based on the Storyline documentation is that the Flash-based output is 508 compliant. However, that doesn't seem to be the case, according to the above statement. Can you explain?
Is there something that I can do in the presentation creation to resolve this issue? My development team always sets narrations to play automatically every time a slide is accessed, so users don't actually need a play button. Users can also access specific slides (for replay, etc.) through the menu instead of the next or previous buttons. However, I'd like to know if there is a way to make all of the buttons mentioned in the above statement accessible.
Is there any difference on this compliance issue with Storyline versus Storyline 2? I believe the files checked were created with Storyline 2, but I'm not certain on that. Is there something in the file name that indicates if Storyline or Storyline 2 was used?
I understand that only the Flash-based output is 508 compliant. However, we have been using the production options that allow for use with HTML5 and iOS. My understanding from looking at the code (and my understanding is VERY limited) is that the program will first seek to run using Flash, if available, then, if not, it will use HTML5 or the iOS version. Is that correct? Would adding the following statement near a link to a Storyline object in an online course be advisable? Statement-- Users with disabilities: For optimal access to this feature, view the presentation with a computer and browser that supports Flash.
8 Replies
Hi Kristin,
I'm not a 508 expert, but the majority of things are author controlled in terms of what you include in the course and how that'll work for your users with disabilities. You'll want to review the information here.
In regards to pause, play, rewind, etc. you may want to look at enabling the seekbar or volume control as described here.
Also, the player controls such as next buttons - what did they mean not marked appropriately?
Thanks for your prompt response, Ashley. I will look at the resources you sent. I am seeking clarification regarding what was meant that the previous and next buttons were "not marked appropriately."
Kristin Ballou
Curriculum Designer
Curriculum Development Department
Brigham Young University - Idaho
208-496-1898
Ashley,
Here is the response regarding what is meant that the player buttons are not appropriately labeled:
When you tab to those buttons they have no label (similar to Alt Text) so a blind user doesn't know what that button does.
JAWS users use keyboard shortcuts and use the tab key and shift tab to move around in the player. After you press tab, JAWS will say what the button/field is if it has a label. If it doesn't it won't say anything and therefore it is impossible to know where you are.
Pressing tab moves from play/stop to location slider in middle to prev to next, but I don't recall all of them being labeled.
Kristin Ballou
Curriculum Designer
Curriculum Development Department
Brigham Young University - Idaho
208-496-1898
HI Kristin,
Thanks for getting clarification on the issue. Have you changed the player text labels from their standard? You'll want to be sure that you've started JAWS prior to running the course, and I believe JAWS only provides support for the most recent update of Internet Explorer. Do you know what version of JAWS and IE you're using?
Thanks very much for this response. I will give that a try!
The player text labels were not altered from the standard. For example, the Previous button is shown as being labeled as PREV, yet the individual I had test with JAWS couldn't see a label on the button. Do you know what the problem may be?
Actually, disregard that question! It looks like the HTML file was fine; it was the HTML5 that was problematic. I'm already aware that there's not full compliance for HTML5. Thanks!
Great - thanks for the update Kristin!
This discussion is closed. You can start a new discussion or contact Articulate Support.