Forum Discussion
Button States Read as "Unlabeled" by Screen Reader
Hello! I am experiencing an alt text 508 issue. I created a chapter selection screen where each chapter is represented by a sticky note with the name of the chapter, and an icon indicating it is ready to start or revisit. Each sticky note has 3 states: normal/default, a state change that occurs when the previous button was selected (i.e., after chapter 1 is selected, chapter 2 changes to say "start"), and a state change that occurs when it is selected (showing a replay button). I have used custom states and triggers to accomplish this and everything is working well.
The issue is that these buttons' custom states are being read by a screen reader as "unlabeled one button" or "unlabeled two button," etc. I have gone to each state and added alt text (e.g., Chapter 1 - selected), but it's not being read correctly by the screen reader. This is posing a 508 accessibility concern. Does anyone know why these buttons' states' alt text isn't being read by the screen reader?
2 Replies
Hello AlexisRoman,
I'm happy to check this for you!
It looks like you have this tagged as a Rise 360 issue, but the mention of states leads me to believe that this might be Storyline 360-related. Can you confirm if your course was authored in Rise 360 or Storyline 360?
We'll need to test your project to understand what's happening. If it was created in Storyline 360, would you be willing to share a copy of your project file here or in private by opening a support case for testing? We'll delete it when we're done! Please include your Storyline 360 version and the name and version of the screen reader you used for testing so we can test the behavior as accurately as possible. If it's a Rise 360 course, you can open a case directly so a support engineer can share instructions with you on how to share a copy of your course with us.
- AlexisRomanCommunity Member
Hello JoseTansengco, thanks for responding - I appreciate your offer to test this Storyline 360 (not Rise 360) issue! Unfortunately due to the nature of the work I'm unable to share a copy of the project file here or in testing. I will reach back out for assistance if that changes.
Related Content
- 5 months ago
- 2 months ago
- 2 years ago