Is there a way to create unique alt tags for different object states. I need a way for a screen reader to say that a button is selected, visited, etc.. in order to comply with the below requirement:
"User interface controls are announced with role (e.g. checkbox, tab), name (e.g. text prompt or information that tells a user what type this is), and state (e.g.selected, disabled, checked) and available options."
I don't have a screen reader to test with, but it looks like alt text works with objects' states, based on this document. Is this something you've already tested with no luck, or are you in the planning stage?
Thanks Peter. I haven't done any testing, just trying to figure out how this is all going to work.
From messing around in Storyline It looks like the alt text applied to an object does not apply to its states. I can enter "button 1" as an alt tag, but if I go into any state (even the normal state) the alt text field is blank again. I wonder, for the selected state would I enter "button 1 selected" or just "selected".
That document makes it sound like Storyline reports the name of the state automatically (e.g. selected, hover, etc.) rather than the alt tag associated with it.
Anyone know a good way to test this without dropping a fortune on a screen reader?
I've asked for our QA guys to give this a test and let me know the results. Can't promise a quick turnaround, but I'll be sure to pass on whatever I hear. Thanks for the topic.
Hi Michael! This thread is a bit dated and Peter has a different position at Articulate, but I think that this thread will assist you with your question.
The two threads are relating to different issues. I thought this was pretty clear, but I'll clarify the difference here:
This thread relates to the inability to apply different Alt text to different states (reported in Nov 2012).
The other thread relates to the inability to add or update Alt text to an object (in its Normal state) after states have been added to the object (bug reported Nov 2016).
Now, can you please confirm if this bug is still unresolved after 4 years, and when it might be due for someone to attend to?
The first issue mentioned in this discussion as you saw is a bit older, and I know you've also been discussing the issue in your other forum discussion as a part of a Support case with my colleague Justin. He did link the open issue here with the recent issue you also discussed with him based on their similarities and to provide more information to our QA team as we push for great accessibility support.
When we have updates to share about a particular bug or feature, our team will update the forum discussions as appropriate and communicate via direct email to those users such as yourself who have been communicating as a part of a support case.
Hi there, Bobby. We still have the issue of alt text on buttons and other objects with states under review.
Let me share how alt text is working in the latest version of Storyline 360 so folks can create solutions for their courses:
JAWS will read the alt text of your button’s Normal state and any custom states when you enter the alt text in the Size and Position window while editing those states.
The alt text of built-in states will not be read.
For these objects, use the alt text field in the Size and Position window while editing states rather than the Tab Order window.
Appreciate the feedback, Crystal. This is very helpful and actually solves what I was having issues with. I'm looking forward to being more involved with E-Learning Heroes!
15 Replies
Hi Justin,
I don't have a screen reader to test with, but it looks like alt text works with objects' states, based on this document. Is this something you've already tested with no luck, or are you in the planning stage?
Thanks Peter. I haven't done any testing, just trying to figure out how this is all going to work.
From messing around in Storyline It looks like the alt text applied to an object does not apply to its states. I can enter "button 1" as an alt tag, but if I go into any state (even the normal state) the alt text field is blank again. I wonder, for the selected state would I enter "button 1 selected" or just "selected".
That document makes it sound like Storyline reports the name of the state automatically (e.g. selected, hover, etc.) rather than the alt tag associated with it.
Anyone know a good way to test this without dropping a fortune on a screen reader?
Let me see if I can do some digging around and get you a straight answer, Justin. I'll check back in...
Hey Justin,
I've asked for our QA guys to give this a test and let me know the results. Can't promise a quick turnaround, but I'll be sure to pass on whatever I hear. Thanks for the topic.
Hi Peter, what was the outcome of the test? Will object states be automatically reported to screen readers?
Hi Michael! This thread is a bit dated and Peter has a different position at Articulate, but I think that this thread will assist you with your question.
Ok, thank you Leslie.
No problem Michael :)
Leslie, I can't see any resolution in the thread you linked to...?
Does this mean that this bug has still not been resolved, 4 years after it was reported?
Hi Kuriko!
Looks like you have identified and shared with users here.
Hi Leslie,
The two threads are relating to different issues. I thought this was pretty clear, but I'll clarify the difference here:
Now, can you please confirm if this bug is still unresolved after 4 years, and when it might be due for someone to attend to?
Hi Kuriko,
The first issue mentioned in this discussion as you saw is a bit older, and I know you've also been discussing the issue in your other forum discussion as a part of a Support case with my colleague Justin. He did link the open issue here with the recent issue you also discussed with him based on their similarities and to provide more information to our QA team as we push for great accessibility support.
When we have updates to share about a particular bug or feature, our team will update the forum discussions as appropriate and communicate via direct email to those users such as yourself who have been communicating as a part of a support case.
Has there been any movement/improvements to screenreaders reading the specific state to a button?
Hi there, Bobby. We still have the issue of alt text on buttons and other objects with states under review.
Let me share how alt text is working in the latest version of Storyline 360 so folks can create solutions for their courses:
For these objects, use the alt text field in the Size and Position window while editing states rather than the Tab Order window.
Appreciate the feedback, Crystal. This is very helpful and actually solves what I was having issues with. I'm looking forward to being more involved with E-Learning Heroes!
This discussion is closed. You can start a new discussion or contact Articulate Support.