Yellow Highlight Box for Accessibility
May 12, 2018
I am working in Storyline 360. I am having an issue with the yellow highlight box for accessibility. I have a button on the base layer of a slide that is triggered to show a layer. The yellow box appears on the base layer correctly to identify the button but it also appears on the layer it is triggered to show even though the button is not visible. The yellow box for the button should only show on the base layer. How do I resolve this? It will not pass 508 compliance as is. Thanks!
6 Replies
Thank you, I figured it out. I needed to check "prevent users from clicking on the base layer" in the layer properties.
Glad you were able to get this figured out Sherri.
I appreciate you chiming in with an update and for sharing with the community as well :)
Leslie, would making the change to the layer property I described above throw the focus to the skip Navigation link when a screen reader is in use? After I made that change, we experienced this issue in a 508 review. I need to know as soon as possible if the two are connected.
Hi Sherri,
Did you add in a Skip Navigation link, or you're using the option outlined here?
Also what screen reader were you using? Or were you just attempting with the tab/yellow accessibility box? I uploaded a quick sample here and was able to continuously tab through the items on the slide and the navigation items.
Hi Ashley,
I did not add in a Skip Navigation link. We were using JAWS to complete 508 testing. The problem was not with continuously tabbing through items on the slide and the navigation items. The problem was that the yellow indicator box for accessibility around the buttons on the base layer was showing on the other slide layers even though the button was not. When I checked prevent users from clicking on the base layer in the layer properties it corrected this issue but created another issue of the screen reader's focus being placed on skip navigation as the learner is tabbing through the layer. I submitted a case to Articulate Support yesterday and they responded that they logged it as a possible software bug and are going to look it into it and get back to me with an update.
Thanks so much for the update and letting us know that you reached out and worked with our team. I see where Miker got this reported for you :)
This discussion is closed. You can start a new discussion or contact Articulate Support.