3. Example of Challenging Interaction
Let's consider an example of content that has been designed to streamline the speed with which a user can find their way through a menu.
A classic example is a menu that is programmed to activate when focus is set to a menu choice.
This seems reasonable, right?
Because a mouse-user deliberately moves the mouse in conjunction with visually reviewing the content, they can accomplish the act of review and selecting an option before they actually activate the interaction with a click.
It is a quick and efficient design - for sighted people using a mouse. However, for keyboard users, the experience is quite different.
Because the menu is set to activate upon receiving focus, the screen reader user never gets to hear option 2.
Upon navigating to the menu, the first option will receive focus in order for the screen reader to read it aloud.
As soon as the user hears the first menu option, it is activated.
Break Down Review and Activation
The solution to this is to create a “trigger” event, effectively separating the action of reviewing and selecting, so that the content can be reviewed before being deliberately selected.
Some people might assert that the keyboard does not allow the same ease of use as a mouse, which might even be true for them. However, it is important to recognize that accessibility is an exercise in considering the needs of others - just in case you missed the memo. The truth is, keyboard access does allow the same functionality as a mouse for many people, even if it takes a little more awareness and effort to ensure your content is compatible.