Forum Discussion
Screen reader and alt txt
I agree with you GiovanniFinotto . And that's not what I was describing.
I take a different approach. Considering that visually impaired learners will never “see” the images, whether synchronized or not, and considering that learners using screen readers “to give themselves time” to see (the images), hear (the audio), and understand (the interaction between images and audio), I will only describe the FIRST image-context in the alt text, which will also describe the following image(s) and how/why they appear.
Or, using another technique I use in my last project I mentioned , I provide a transcript of the audio, interspersed with descriptions of the images that appear in sync with the audio, in the “Comment” panel (or whatever name you want to give it), which opens on the left side of the screen (instead of the default Menu panel). Is that clear enough?
In short, give the learner a general but meaningful overview of the whole, not every detail. I don't have THE solution, this is just my suggestion. Thierry
Hello GiovanniFinotto
So, as far as I know, SL does not detect whether a screen reader is being used, or even whether keyboard navigation (using the Tab keys) is being used. But the Articulate staff will be better placed to answer that question.
BUT, according to one of the essential principles for making a module fully accessible, the learner must be able to control the controls of an audible media (audio/video) in all cases: it is not only visually impaired people who use a screen reader! Therefore, your media should not start automatically at the beginning of the timeline, but rather through an action by the learner. You can set this in Video Tools/Options/Play video: on trigger. The button that triggers media playback will have clear and precise alt text explaining its function and what happens when clicked. And it will be placed (in my opinion) in second position in the focus order. First the description of the image/context, then the media playback button.
*** Of course, this can be very annoying for learners who do not use a screen reader (having to click each time to play media that would be more engaging if it started automatically). In my most recent project, I asked learners on the first screen if they use a screen reader. If so, a T/F variable is set to TRUE and each media item on each screen is stopped at the beginning of the timeline because the variable is TRUE. The learner must click the “Play” button. If the variable remains FALSE, the media items play automatically. Would this solve your problem? Let us know. Perhaps someone else has a better solution.
Hi ThierryEmmanuel,
thank you very much, the answer is truly complete and interesting. I really like the second tip, which is really useful.
My doubt remains about the use of images synchronized with the video which, to be "described", would lead the user to block the video many times and make the lesson much longer than expected.
I greatly reduce the use of alternative text for this reason too.
I agree with you GiovanniFinotto . And that's not what I was describing.
I take a different approach. Considering that visually impaired learners will never “see” the images, whether synchronized or not, and considering that learners using screen readers “to give themselves time” to see (the images), hear (the audio), and understand (the interaction between images and audio), I will only describe the FIRST image-context in the alt text, which will also describe the following image(s) and how/why they appear.
Or, using another technique I use in my last project I mentioned , I provide a transcript of the audio, interspersed with descriptions of the images that appear in sync with the audio, in the “Comment” panel (or whatever name you want to give it), which opens on the left side of the screen (instead of the default Menu panel). Is that clear enough?
In short, give the learner a general but meaningful overview of the whole, not every detail. I don't have THE solution, this is just my suggestion. ThierryI understand what you mean well, in fact I also provide subtitles synchronized with the video and complete transcriptions. I also really like the idea of using the "comment panel". Thank you, it is always useful to discuss and learn about other people's methodologies. Thanks. I am left with the first perplexity about how to bind the focus of the screen reader to the slide and not to the entire web context, but there is probably a setting in the screen reader that I don't know. Thanks again.
Hi GiovanniFinotto,
Great question, and thanks to ThierryEMMANUEL for sharing such thoughtful suggestions.
The suggestion of letting learners control playback with a Play button is right on the mark. Storyline doesn’t detect when a screen reader is active, so it can’t automatically pause a video. Setting the video to Play video: From trigger helps avoid overlapping audio and keeps the experience accessible.
Your idea for automatic detection is a good one. I’ll share it with our team as a feature request to help improve accessibility in future updates.
You can also connect with us privately in a support case if you want us to review your setup together.
