Forum Discussion
Focus Order in Storyline
My organization is using most of the accessibility functionality available within Storyline. We are struggling with focus order. Simple slide containing text with or without image is straightforward. Slides with buttons to display layers not so much. My understanding is that the player's prev/next buttons don't play nice together with focus order. Can certainly create custom navigation buttons on master slide if necessary.
Problem is that we don't have any screen readers in house and can only use keyboard navigation.
I've done extensive research on this topic and can find a lot of information on setting up focus order, but haven't found anything on how to test.
I'd really like to see a webinar dedicated to focus order from set up to testing coming soon.
Andrea
1 Reply
Great questions, AndreaBojko. A couple of quick points. In Storyline, the player’s built-in navigation buttons are always last in the tab order for slide objects. You shouldn't see conflict with player navigation and on-slide interactive objects.
In screen readers like NVDA (free and available here), there are two modes to be aware of:
- Focus Mode: Tabs through interactive elements in your set focus order; skips static text/images.
- Browse Mode: Reads all elements in the slide’s reading order, which may differ from focus order.
I have a quick start class on using NVDA to test Storyline projects: Beginner’s Guide to NVDA and Storyline for Accessibility Testing | Articulate - Community
One thing that might help is to post a sample interaction you want to test. I'd be happy to review the file and provide specific feedback for testing and correcting (if necessary) the focus order for your objects.
