I am producing eLearning for a university and am concerned with meeting requirements of those with visual impairments and colour blindness.
I know that many visually impaired web surfers have custom CSS files which display webpages by inverting blacks and white for example - I was wondering whether such solutions would work with storyline output?
Is there anyone out there with experience of this?
If anyone wants to offer corrections to what I'm saying please chime in. I'm also at a university, and am struggling with these issues.
I've been able to use custom CSS to make changes to the Storyline player, but not to the actual slides. My best guess is that slides are images, which explains why screen readers can't do anything with them. So extensions like GreaseMonkey or StyleBot are useful for the sidebar menus and the rest of the player, but not for the actual content on the slide.
The color-changing extensions, like the ones that make the screen grayscale or high-contrast, seem to work.
It's also helpful to remember Storyline can output Flash and HTML5. The "story.html" file serves up the Flash file first, and uses HTML5 as a fallback. This is important to know because the Flash output won't change based on custom CSS. There are some discussions about how to bypass the Flash output. I think it's as easy as deleting or renaming a file, but I can't remember offhand. This whole issue bugs me, as I want HTML5 to be default, and Flash to be the fallback.
Not that it makes a huge amount of difference, since both the Flash and HTML5 versions are equally inaccessible. And don't get me started on closed captioning.
I've been using Storyline for three years, but we're seriously thinking about jumping ship for Lectora. The new MIT lawsuit has everyone running for cover.
2 Replies
Hi Ant! Hopefully someone in the community with experience with this will chime in to assist you here.
If anyone wants to offer corrections to what I'm saying please chime in. I'm also at a university, and am struggling with these issues.
I've been able to use custom CSS to make changes to the Storyline player, but not to the actual slides. My best guess is that slides are images, which explains why screen readers can't do anything with them. So extensions like GreaseMonkey or StyleBot are useful for the sidebar menus and the rest of the player, but not for the actual content on the slide.
The color-changing extensions, like the ones that make the screen grayscale or high-contrast, seem to work.
It's also helpful to remember Storyline can output Flash and HTML5. The "story.html" file serves up the Flash file first, and uses HTML5 as a fallback. This is important to know because the Flash output won't change based on custom CSS. There are some discussions about how to bypass the Flash output. I think it's as easy as deleting or renaming a file, but I can't remember offhand. This whole issue bugs me, as I want HTML5 to be default, and Flash to be the fallback.
Not that it makes a huge amount of difference, since both the Flash and HTML5 versions are equally inaccessible. And don't get me started on closed captioning.
I've been using Storyline for three years, but we're seriously thinking about jumping ship for Lectora. The new MIT lawsuit has everyone running for cover.
This discussion is closed. You can start a new discussion or contact Articulate Support.