Part of the accessibility requirements is to read out alt text for different button states using a screenreader.
I have set different alt text for different button states as such - button active, button disabled, button visited. But what I have noticed is that the alt text for the disabled and visited button are not read out accordingly - they are just reading 'button active'.
This is a basic requirement for people with disability as without visibility on the colour of button (for example being greyed out), the button states needs to be read out by a screenreader.
Is there anyone out here facing the same issue? Are there any ways around it?
I don't think there are different alt-text for different states of object, there is only one alt-text for each object.
Back to your question, I would only want to know(hear) what I need to know if I am blind. That means I would not like to know there is a disabled button(it is meanless to me and may even confuse me why would there be a button I can't do with it on my way). So rather than tell them what's on the slide, you might consider more about what they need to know and how to make them go through the content they need/want smoothly.
Joanne, just giving an example - I have 6 buttons on a page. All buttons are disabled except the first. Once first is completed, second gets activated. Once second is completed, third gets activated and so on. Screenreader users need to know which buttons are activated/disabled - either through listening the button states or turning off the alt text for disabled buttons completely (and reactivate alt text when button is activated). But neither of them seems workable.
Matt, thanks for sending me the link. I saw that post just now. But the post was over 2 years ago and I was really hoping that the issue would have been fixed by now as Storyline is claiming that it is accessible.
In your example, I would write screen reader users an alt-text to explain how to go through(complete) the slide. They don't really need to go through the buttons that disabled on the screen but to know the processing rule and the first button.(Well, if they need to know what buttons there are, you can introduce them in the alt-text of the rule explaination.) As to the visual slide, I would use hidden state buttons for the rest of five and put five disabled buttons without alt-text for those who can view. So users can see one actived BTN + 5 disabled BTNs. After the first one is completed, change the second BTN 's state to normal so the screen reader will read the button.
Hi Joanne, I wanted to let you know that you can have different alt text for different states. You can change the alt text in the "edit state" tab by right-clicking the object and selecting Accessibility.
5 Replies
Hi James,
I don't think there are different alt-text for different states of object, there is only one alt-text for each object.
Back to your question, I would only want to know(hear) what I need to know if I am blind. That means I would not like to know there is a disabled button(it is meanless to me and may even confuse me why would there be a button I can't do with it on my way). So rather than tell them what's on the slide, you might consider more about what they need to know and how to make them go through the content they need/want smoothly.
Thanks for your replies.
Joanne, just giving an example - I have 6 buttons on a page. All buttons are disabled except the first. Once first is completed, second gets activated. Once second is completed, third gets activated and so on. Screenreader users need to know which buttons are activated/disabled - either through listening the button states or turning off the alt text for disabled buttons completely (and reactivate alt text when button is activated). But neither of them seems workable.
Matt, thanks for sending me the link. I saw that post just now. But the post was over 2 years ago and I was really hoping that the issue would have been fixed by now as Storyline is claiming that it is accessible.
Hi James,
In your example, I would write screen reader users an alt-text to explain how to go through(complete) the slide. They don't really need to go through the buttons that disabled on the screen but to know the processing rule and the first button.(Well, if they need to know what buttons there are, you can introduce them in the alt-text of the rule explaination.)
As to the visual slide, I would use hidden state buttons for the rest of five and put five disabled buttons without alt-text for those who can view. So users can see one actived BTN + 5 disabled BTNs. After the first one is completed, change the second BTN 's state to normal so the screen reader will read the button.
Thanks Joanne! Your suggestion re using buttons with hidden states works. :)
Hi Joanne, I wanted to let you know that you can have different alt text for different states. You can change the alt text in the "edit state" tab by right-clicking the object and selecting Accessibility.
This discussion is closed. You can start a new discussion or contact Articulate Support.