Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Captivate 9 text in interactions not recognized in JAWS screen reader

Explorer ,
Feb 07, 2017 Feb 07, 2017

Has anyone solved the 508 issues in Captivate? I feel like I've combed the forums for an answer only to come up empty-handed.

Here's the issue. I have several interactions where the user must click on a button to show content on the screen while hiding something else. The content is a grouping of text captions and images. The screen reader is picking up the smart shape buttons because I added acc text. The user cannot hit enter to display the content. They must use shift+enter to access it. Then, when I would expect the reader to call out the text and images, nothing. Nada. The tab order is set. EVERYTHING has accessibility text.  The acc checkbox is on. I'm using Flash output (because HTML5 doesn't let me use the keyboard to select items on the screen.)

It's possible to convert all the text to a smart shape, use as a button, then add accessibility text. That will force JAWS to see it. But that is a TON of work! Is there another solution to force JAWS to read text captions? Is there a way to edit the DOM so JAWS will read things correctly?

Here's an example. It's from eLearning Brothers.

elb_interaction_Capture.PNG

elb_interaction_actions_Capture.PNG

394
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , Feb 21, 2017 Feb 21, 2017

Posting for others who have this issue. I've discovered a work around. It's a pain. But it works. You have to use smart shapes that are coded as a button. Then, delete the rollovers. Add the text in the smart shape to the accessibility description. Then, set the tab order so the smart shape button appears after the tab it relates to.

Translate
Explorer ,
Feb 21, 2017 Feb 21, 2017

Posting for others who have this issue. I've discovered a work around. It's a pain. But it works. You have to use smart shapes that are coded as a button. Then, delete the rollovers. Add the text in the smart shape to the accessibility description. Then, set the tab order so the smart shape button appears after the tab it relates to.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 09, 2017 May 09, 2017

Thank you so much for this work around!! So weird but it does work.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 09, 2017 May 09, 2017
LATEST

The only issue with this is that the text looks fuzzy instead of crisp now, which may not be workable for me.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Help resources