It sounds like you might have a specific use case in mind! Do you have a sample file that you can show us, and we can provide more details from there?
As my teammate, Katie explained, to meet accessibility guidelines which also include keyboard navigation compliance, you'll want to skip out on using the Mouse Hovers Over trigger.
I've recorded a short demo explaining how screen readers interact with a slide that has both a When Mouse Hovers Over trigger and a When User Clicks trigger. Here's the link!
I see that you were able to work with Cleo on our support team and a feature request has been filed.
As Katie and Lauren mentioned, we have the following information in our How to Design an Accessible Course article with regards to mobility and vision impairments:
While hover states (i.e., rollover effects that require a mouse) are great for conveying interactivity, don’t rely on them to display important information. If you do use hover states to display text or images, consider providing a keyboard-accessible alternative.
For example, it’s fine to change the color of a button when a mouse hovers over it to indicate that it’s a clickable object, but you wouldn’t want to display feedback text in the hover state without also providing another way to access the information. One alternative for this example would be a keyboard shortcut that plays an audio version of the feedback for those not using a mouse.
5 Replies
Hi there, David!
Hovering over an object isn't recognized by a screen reader, so using selected may be a better option for what you're designing!
Additionally, here are a few more related thoughts and resources:
No that does not help me at all.
Hi David!
It sounds like you might have a specific use case in mind! Do you have a sample file that you can show us, and we can provide more details from there?
As my teammate, Katie explained, to meet accessibility guidelines which also include keyboard navigation compliance, you'll want to skip out on using the Mouse Hovers Over trigger.
I've recorded a short demo explaining how screen readers interact with a slide that has both a When Mouse Hovers Over trigger and a When User Clicks trigger. Here's the link!
This is the template that we use for all our courses.
Thanks, David.
I see that you were able to work with Cleo on our support team and a feature request has been filed.
As Katie and Lauren mentioned, we have the following information in our How to Design an Accessible Course article with regards to mobility and vision impairments:
While hover states (i.e., rollover effects that require a mouse) are great for conveying interactivity, don’t rely on them to display important information. If you do use hover states to display text or images, consider providing a keyboard-accessible alternative.
For example, it’s fine to change the color of a button when a mouse hovers over it to indicate that it’s a clickable object, but you wouldn’t want to display feedback text in the hover state without also providing another way to access the information. One alternative for this example would be a keyboard shortcut that plays an audio version of the feedback for those not using a mouse.
This discussion is closed. You can start a new discussion or contact Articulate Support.