Help us improve Storyline 360 & Accessibility

Please for the love of all thats good and holy.... overhaul the hideous Focus Order controls. I shudder every time I know I will have to use them, they are so antiquated and quarrelsome!

And as Sam already says, adding the ability to change this via code/triggers would be huge.

Thanks!

One thing I know that videos in Storyline are in violation for is the lack of audio descriptions.

Storyline's closed captioning editor is one of the best I've ever seen. One thing that would infinitely helpful would be the ability to select a range of captions and move them all. Say for instance, you edit the audio in the video to add or remove a phrase, and now you must move several minutes of captions a few seconds one way or the other - quite painful as it stands now.

Really exciting to see this accessibility work keep pushing!

Looking forward to the outcomes from this survey. I think SL has come a long way in recent years, but still quite a long way behind what is possible hand coding. I'd love to be able to get to the stage of testing SL content, and not having to give allowances as the content is built in SL360. I'd like to be as tough on SL360 content as I am on hand coded content.

I think some major enhancements could be providing the ability group elements into containers that could then have aria attributes added such as aria-live.

Being able to programmatically change the screen reader focus would be a big leap for developers and provide the ability to provide a good end user experience when reading the content with a screen reader.

Well, we have just got SL360, having been users of SL3 for some years now (and Studio before that).

Shame the survey is now closed.  We're users of SL for the Player shell but import published Adobe Captivate simulations into slides.

I was just using some free time on a Friday afternoon to look into Text-to-Speech and Closed Captions and wondered if they were both available in regards to the hint boxes in SL simulations.

I think we have never moved off Captivate because of the method of screen capturing in SL.  As I recall, all the captures are in SL Story window, and I think they also stay within the player and can't pop-out fullscreen.

If text-to-speech does work with the hint boxes, closed captions therefore could replace hints but only if you had control of freeform movement of closed captions around each slide when necessary and the sims could pop out to be full screen, that would be a winner for us.

BTW, if you type https://research.articulate.com into a browser it sends you to Typeform: People-Friendly Forms and Surveys.  thought it worth you knowing :) as I was wondering if you could see other research surveys :D

Dear Articulate Staff,

You guys make one of the best products, if not "THE BEST'' product in the market. That said, I am writing this concern as I am visually impaired, and it appears to people who tested the product for accessibility are not impaired with any impairments.

I state the above, as you will see in the attached screen, the scale numbering seen if you were to open the Edit Audio dialog box is gray on white, extremely poor choice if the audience is visually impaired. Gray on white background does not provide color contrast discrimination as black would as seen in the stage/slide timeline. 

If you guys could please make the update in not-too-distant future, I (and I am sure anyone else with visual impairment) would be much obliged. Thank you and looking forward to the update.

Kind regards.

Happy (sometimes not so happy) User

From the development side the focus order can be difficult to deal with, especially when you have slides with multiple layers. If we could have some kind of option where we could organize the layers would be greatly appreciated. 
Ideally, there would be some kind of built-in accessibility checker/reminder about alt-text for images etc. 

In doing accessibility testing I found that the text entry boxes do not have enough contrast for people who use screen magnification aids. This could be fixed by having a border around the text entry. 

I was just thinking some more about this. If you really want to up your accessibility credibility Articulate should either deprecate some of the built-in features that aren't accessible, like matching and sequencing (anything that requires a mouse) or include a warning that the activity isn't accessible.