Forum Discussion
Screenreaders and Storyline questions
I'm trying to make questions in Storyline which are Screenreader-proof. For example the flow of the screenreader through the page is logical. It should be as easy as possible to answer and submit the question. Even more important it is easy to answer and submit the question again and again...
My experiences so far are that there is some inbuild behaviour in Storyline questions which influences the way the screenreader goes through the question slide. Especially whith more than 1 attempt. The screenreader jumps to the end of the slide or the beginning or out of the content area.
I also noticed that the way you select an answer can be different. Somtimes the checked state goes automatically with the screeenreader form choice to choice. So if it reads answer A: choice A is selected. When you move to B: choice B is selected, etc. And another time the behaviour is completely different.
I'm sure the Articulate development team spent a lot of thinking and time into developing the setup of the questions and the way questions are handled by screenreaders.
Is there any documentation about Storyline questions and accesibility in particular screenreaders?
What are the best practices in developing accessible questions?
I'm looking for detailed inside information which helps me to understand the Storyline questions and helps me to develop really accesible Storyline questions.
Hi DouweHarder,
Thanks for reaching out, and good call on opening questions about accessibility.
We've prepared this document, which contains tips and tricks for designing accessible courses in Storyline 360.
We help this points you in the right direction when it comes to your accessibility journey!
Hello DouweHarder
It sounds like you may be asking about the difference between radio button questions and checkbox questions.
We have an article on multiple choice questions:
Storyline 360: How to Navigate Multiple Choice Questions with a Screen Reader or Keyboard
I'm happy to elaborate further on this standard.
- Radio buttons for questions like True/False, Multiple Choice, and Pick One include a button set that allows one selection within the group. So, screen reader users will arrow through these answer choices. (Note: Empty radio buttons occur on page load but will auto-select as you move through the buttons, or the space bar will select.) Check out the W3C recommendation for radio groups here.
- Checkboxes for questions like Multiple Response and Pick Many allow for multiple selections, so screen readers announce each checkbox individually with its state, making it focusable and tabbed individually. Check out the W3C recommendation for checkboxes here.
Please let us know if you have any further questions.
Hi LeslieMcKerchie, thank you. That is valuable background information.
