Basic Accessibility Issues
Jul 04, 2018
I've been using Storyline 2 for many years now but going round in circles with basic accessibility issues. To simplify matters I've built a VERY basic 1 slide course - see attached. Here's what's on the slide and behaviour when I test for accessibility using Windows Narrator (Windows key & U):
1. Simple text box with nothing added to the alternative text -> Windows narrator puts a yellow box around but doesn't read out the content
2. Simple text box with the same text added to the alternative text -> Windows narrator puts a yellow box around but doesn't read out the content
3. Green tick image with 'This is a green tick' text added to the alternative text -> Windows narrator puts a yellow box around but doesn't read out the alternative text
4. Green tick image with 'This is a green tick' text added to the alternative text AND a trigger added to jump to an external website -> Windows narrator puts a yellow AND blue box around AND DOES read out the alternative text
So, for me the only conclusion I can draw from this very simple test is adding a trigger to an object is the only way to make it accessible. I know this can't be the case!
Can someone please download the attached file, publish and see how you get on with accessibility testing? THANKS!
6 Replies
This post was removed by the author
Hi Brian,
Thanks for sharing that file here, it was helpful for testing. I took a look and published it with Storyline 2 update 13, and uploaded here to Tempshare.
I took a Peek recording of what I was seeing, and it was reading out the text and alt text when navigated to the items using Jaws +IE11 and the Flash output, which is our supported setup in Storyline 2 for screen readers.
With Storyline 3 and Storyline 360, we've added a few more options to our Accessibility support, so you may want to look at that information here and see if the upgrade would be something that could meet your needs.
Let me know if you need anything else!
Hi Ashley,
Thanks very much for all your effort looking into this for me. I've found a work colleague who has JAWS and am working with them now to test my work. What I've learned from this is not all screen readers are the same - what works in one may not work in another.
Thanks again,
Brian
Not a problem, Brian and we're here to help if you have any other questions. JAWS has a free trial version and that's what I use as well. Good to have around in case your colleague isn't able to help test!
Hi Ashley,
I've downloaded and installed the free version of JAWS - very useful thank you! I tested my course (not the one listed above) in JAWS by tabbing around the screen and it seemed to work fine.
However, I've just came off a call with my colleague and he informed me that most JAWS users use the function keys such as 'Insert & F5'. When this was used it seemed to ignore the text boxes in the course even though they are tagged for accessibility. Do you know if JAWS accessibility is just limited to tabbing around the screen or should it also support the 'Insert & F5' functionality also? Thanks.
Hi Brian,
I've not heard of using that key combination - did you colleague share that those keystrokes were used to navigate to items on the screen or for something else?
In the majority of posts I've seen in ELH, the learner can tab to items on the screen and if needing to select an item us the spacebar.
Hi Ashley,
They do seem to use these keystrokes but I've put instructions at the start of the course to use Tab to navigate around the course. Thanks for all your help with this.
This discussion is closed. You can start a new discussion or contact Articulate Support.