Skip to main content
Participant
January 10, 2017
Question

Tabbing through elements only highlights buttons (not images, text boxes, etc.)

  • January 10, 2017
  • 1 reply
  • 327 views

Hi,

I was recently handed a Captivate project that had failed 508 compliance.  The complaint was that the tester couldn't use their keyboard to highlight elements on the page, which is a requirement for using screen reader software.  Sure enough, when I tested it, tab would highlight the player's play/pause buttons, as well as some back and forward buttons we added, but nothing else.

I've done projects before where everything is accessible via tab, so I know it's not impossible.  But, as far as I can tell, everything is as it should be.  The main thing I've made sure of is that Accessibility is turned on, but I can't think of anything else to change.

I'm using Captivate 8 in Windows 7, testing in IE11.  Anyone have any suggestions for where I can look?

Thanks!

This topic has been closed for replies.

1 reply

Paul Wilson CTDP
Community Expert
Community Expert
January 11, 2017

The tab key will navigate through interactive objects. An image is not one of these interactive objects, however, visual multimedia does require that you provide the image a name and a description in order to be compatible with 508 compliance. You can add a name and description for all the images by using the following steps.

  1. Select the image
  2. From the properties panel, click the icon next to the image label and select Accessibility
  3. Enter in an Accessibility Name and Accessibility Description
  4. Click OK

2017-01-10 7-08-51 PM

2017-01-10 7-10-46 PM

If a name and description are given for visual elements, Adobe Captivate can send the information to the user through the screen reader.

Paul Wilson, CTDP
adambl86Author
Participant
January 18, 2017

Hi Paul,

I've worked on Captivate projects in the past where images etc. are tabbable.  Even when I manually enter descriptions as you suggest, for some reason I can't tab to anything besides buttons.  This issue seems unique to this project (as I mentioned, I inherited it from someone else).  Is there any sort of setting that might be interfering with this functionality?

Thanks for your suggestions!

Adam

adambl86Author
Participant
January 18, 2017

Another interesting thing: If I create a new slide, everything works ok.  It seems only existing slides are broken...