Captivate HTML5 focus lost when using keyboard access

Forum|Forum|8 years ago
January 11, 2018
2 replies
777 views

We're currently having the issue of failing FEMA 508 Accessibility compliance as the focus is being lost between our Captivate SCORM lessons and the browser when published in HTML5. While focus may appear, there are times when the focus is lost on an object and you must hit the 'tab' key a few more times before the focus is obtained again. Any loss of focus is deemed not accessible (see keyboard access section here). We do not have this issue if we publish in flash, but must soon switch to HTML5 as flash becomes obsolete. For reference, our LMS is Canvas.

Has anyone else encountered this issue? Or does anyone know how to ensure that focus is maintained when publishing in HTML5?

This topic has been closed for replies.

AJIT_M

Inspiring

Hi There,

I have sent you a private message. Kindly provide the requested details so that we can connect and look into the issue.

Regards,

Ajit

M

mferguson192291

Inspiring

When you have focus on the object, are you having the object change states or disappear/reappear? If so, then you will lose focus on the screen and the user will have the tab until they get back on the browser screen. The way around this is to simply use the javascript code you mentioned seeing earlier with every advanced action that changes an object's state which you have focus on.

You can even so as far as using eventlisteners with the javascript and manipulate focus based on currentSlideframe.

If your complaint is due to the user being able to tab out of the course screen and into the browser. That is a non-problem. In fact, users should be able to tab out of the screen to access the browser - otherwise it fails compliance due to keyboard trap.

bgoff1Author

Participant

Thanks for your reply. It is not that we are losing focus on objects that we have appearing/reappearing. The issue is more in line with the second part of your answer, though not exactly.

Yes, the user can tab between the course screen and browser. However, by simply using the tab key there is loss of focus between the two. For instance, you press tab - focus is on a play button, press it again - focus continues to move along the controls. Then it gets to a point where you press tab again and you cannot see the focus. You must press tab a few more times before the focus is visible again. The loss of focus for those few key strokes are considered non-compliant.

M

mferguson192291

Inspiring

I just tested on mine using JAWS and keyboard. I tabbed through a course slide and after tabbing on the last item, the focus goes to the browser address window and then along the browser menu icons until it returns to the first thing in the course screen. Using IE 11. Are you sure it's a loss of focus. Use NVDA to see what the screen says is in focus when you have to tab those few more times. The focus on the browser items can be very faint sometimes and hard to see. That's not your problem. That's the browsers. But there are ways to fix that with code.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded