I have a slide with 2 different button sets. Each button set have 2 radio buttons. The 2 button sets works independently as excepted.
The problem: I use NVDA as a screen reader and it reads mychoice 1 radio button not checked 1 / 4 and it should read mychoice 1 radio button not checked 1 / 2.
Is there a solution to have the expected behaviour?
I also tested this with JAWS (as Phil mentioned that's the screen reader supported for Storyline content) and I also heard the same notation about 1 out of 4 when there were two different button sets. I also tried placing the button sets on different layers and experienced the same thing.
It appears this only happens with Radio buttons. As radio buttons are designed to indicate one choice, perhaps you could use Checkboxes instead?
Yes, it's actually a bug that JAWS is reading "# of # buttons" and that is with our team for investigation. It should only read out the radio button text as well as if it's selected or not.
5 Replies
I think the only supported screen reader is Jaws at the moment
Hi Ludovic,
I also tested this with JAWS (as Phil mentioned that's the screen reader supported for Storyline content) and I also heard the same notation about 1 out of 4 when there were two different button sets. I also tried placing the button sets on different layers and experienced the same thing.
It appears this only happens with Radio buttons. As radio buttons are designed to indicate one choice, perhaps you could use Checkboxes instead?
Ashley, If is happening in jaws isn't this a bug. Replacing radio buttons with checkboxes really goes against common web conventions.
Hi Phil,
Yes, it's actually a bug that JAWS is reading "# of # buttons" and that is with our team for investigation. It should only read out the radio button text as well as if it's selected or not.
Good news, folks! We fixed the issue you reported where JAWS would read "# of #" when tabbing to radio buttons on a quiz slide.
Install the latest Storyline 360 update to take advantage of all the recent features and fixes.
If the problem happens again, please record a Peek 360 screencast for me, and I'll be happy to help!
This discussion is closed. You can start a new discussion or contact Articulate Support.