Forum Discussion
Best accessibility practices to use when developing a custom player in SL360
Hello everyone,
I'm starting to deep dive into the Accessible courses design and while I get most of the principles, I have a few challenges that maybe you will help with ;)
1) I tend to design (at least partially) my own course player, where I have master slide with some additional layers on it. For example, a "navigation instructions", so people can always access the instructions or an indicator that you have finished all the content on the slide and can proceed. Question: Is there a way to not include all of the items on those master_layers focus order? Or create the focus order ONCE, and then place that "grouped" focus order in our focus tab? And will the screen readers skip that part if the layer is not visible? Do you have some best practices to share in doing such things?
2) Accessible text switch - should I enable that option in the beginning and hide it completely? Will that have any impact on my regular course? I think the less options to "switch" is the better and the accessibility cog is getting on my nerves, as it doesn't explain things ;)
3) Zoom to fit - any best practices regarding this one, are there any cons to leaving that completely out?
4) As I mentioned, I have my own next button and I disable jump to the next slide when user swipe - is that ok when discussing accessible course? I always believed that this is purely for 'tablet' courses.
Thanks!
Mateusz
1 Reply
I noticed you hadn’t gotten a reply from your colleagues in the community yet, so I wanted to jump in. I’m not a designer, but I wanted to share some initial thoughts that might help as you work through your player setup and perhaps bring other items to mind.
- Focus order and master layers
- Q: Is there a way to not include all of the items on those master layers in the focus order? Yes. When you open the focus order panel, you can remove any items that don’t need to be read out (like decorative elements).
- Q: Can I create the focus order once and reuse it? Not exactly. Focus order is set per slide with its layers. The best approach is to follow a consistent pattern across all slides. Documenting your approach helps keep things predictable for learners.
- Q: Will screen readers skip items if the layer isn’t visible? Yes. If a layer or object is hidden, screen readers won’t announce it.
- Accessible text switch
- Q: Should I enable it by default and then hide it? Will it affect my course? You should enable accessible text by default, and I’d recommend keeping it visible because the control is for more than one thing. It won’t affect learners who don’t use it. If you’re worried people won’t know what it is, you can add a quick note in your course intro.
- Zoom to fit
- Q: Any best practices? Are there downsides to leaving it out? It’s best to leave zoom options available. Learners with low vision may need to adjust how content fits on the screen. There aren’t really downsides to keeping it; it gives people more control.
- Custom next button and swipe navigation
- Q: Is it okay to use my own Next button and turn off swipe?
Yes. Just make sure your Next button is accessible (clear meaning, in the focus order, works with keyboard and mouse, etc.). Turning off swipe is fine if it fits your design, as long as learners still have a clear and consistent way to proceed.
The built-in player already handles many accessibility features, such as play/pause, volume control, captions, transcripts, skip navigation, and progress indicators. If you go fully custom, you’ll want to add those features back in so learners don’t miss out.
You’re definitely on the right track. The fact that you’re asking these questions already puts you ahead in creating accessible learning experiences. I’m also looking forward to hearing what others in the community might add to this conversation.
