Forum Discussion
508 Compliant Dials and Sliders
Are dials and sliders 508 compliant?
24 Replies
Yes, you can tab to them and then use the arrow keys to navigate them.
That does not make them 508 compliant. Run it through ANDI. If there are no alt tags, and the screen reader cannot identify the elements, it is not 508 compliant. I am having this issue and trying to figure out how to add alt tags to the GUI post production. @Tom, if you have any information on this, I would greatly appreciate it!
Can you share what you're doing with the slider? Also what version of Storyline are you using?
You can add alt text to objects on the screen. However, I suppose it also depends on what the slider is doing to the objects. If you can share a slide that we can look at, that would help.
Yes, adding alt-text is not an issue on screen. The issue is the wrapper... Ie... you add a logo and can't add the alt text for that logo. When you tab through the elements, many of the wrapper/gui elements do not have tags built in. I would recommend hiding elements you don't want the user to tab to in the wrapper/gui. I would also like to be able to add an alt-tag to our Logo.
Susan
Hi Susan!
I appreciate the feedback! Both of your requests have already been shared with our Engineering team, so it sounds like we're on the same wavelength!
We don't have a timeline to share when alt text will be available for Player elements and logos, but we'll keep you updated in this discussion! You can stay up to date with what we are currently working on by looking at our feature roadmap.
This is great. I am so glad this has sparked so much discussion and movement on the part of Articulate. Thank you to everyone.
Thank you, Lauren! I am excited that you forwarded this to the product engineers. I do have a question, will there be updates to Storyline 3? I noticed the product roadmap only includes 360.
Best regards,
Susan
I also wanted to share about removing Player features in Player Properties and Slide Properties. You can uncheck the boxes beside each Player tab if you don't want it to appear on the Player for the entire course or a specific slide!
Lastly, the Player tabs should be read off by a screen reader when moving through the slide content. I've tested this using JAWS and NVDA, and I am hearing the Player tabs read off. Let me know if this isn't working the same on your end.
We are continuing to update Storyline 3, but we aren't sharing that roadmap publicly. Another thought came to mind about the Player tabs; if you head over to Text Labels in the Player Properties, you can change the Player Tabs' name. For example, the Menu Tab, Resources Tab, etc.
We just released a Storyline 3 update today. You can see what's included in the update here.
So in the end are we saying that Dials and Sliders are 508 Compliant?
Hi Martha, and welcome to E-Learning Heroes. 😊
Yes, you can use dials and sliders to create accessible content.
Are you running into an issue that we can help you with?
Hi Leslie
Thank you for your prompt response. I am struggling with moving the slider using the tab key. I can only move it using the left and right arrows on the key board.
Hello Martha!
To move the slide, you'll want to tab to the thumb and move the slide using the right and left arrow keys.
That is correct. You'll need to avoid drag and drop and hotspot question types to build an accessible course.
