Tab navigation and layers

Jun 22, 2020

Emma Spencer
By Emma Spencer

We are building a course and testing throughout to ensure we are meeting all accessibility standards.

As such we are working hard to make sure we create correct tab order for people who need to use keyboard navigation to use the course.

A lot of our information comes from buttons with popups. Unfortunately the buttons on the base layer continue to be active for keyboard navigation even when the layer is active. 

I don't want to hide the base layer and I have selected the option to Prevent the user from clicking on the base layer. Unfortunately the keyboard navigation still tabs through these items.

Am I missing something or is there another element I need to incorporate to ensure this is working correctly?

Thanks.

1 Reply
Sam Hill
almost 4 years ago06/22/20 at 3:50 am (UTC)

Hi Emma, preventing the user from clicking on the base should do the trick. It sounds like you are having a buggy experience there. You can also hide individual elements from the base layer just be toggling visibility when you have the layer selected. Maybe that will help in your instance?

I always ensure I have all of the elements in the logical tab order (including layers) unless the layer does have the property to prevent access to the base selected.

This discussion is closed. You can start a new discussion or contact Articulate Support.