How do you get the tabbed buttons on screen to highlight? This is important for 508.

Report · Aug 31, 2015

Am I missing the function that allows button on screen to highlight on screen when I tab through the buttons? This is important for 508 compliance. The toolbar buttons highlight no problem. The rollover options do not work with tabbing.

Report · Aug 31, 2015

I'm curious. Where in the 508 compliance rules does it state that rollovers need to be highlighted in a given colour?

Report · Sep 01, 2015

When you tab through all of the available options, it provides no indicator on any button screens which one you are on.

Report · Sep 01, 2015

Perhaps. But a blind user wouldn't notice that was missing would they? They'd be using a screen reader software app anyway.

So, where is the answer my original question. Where in the 508 documentation does it require this?

Report · Sep 01, 2015

508 is more than just for blind users.

See sections 2.4.3 and 2.4.7 n WCAG 2.0.

For the original 508 standards see Subpart B section 1194.22 (c) which explicitly relates to software programs and O/S but which is normally applied to web-based content as well.

The tabbing does highlight on the toolbar, but not on any buttons you create on screen.

Report · Sep 01, 2015

I agree that 508 is for more than blind users, but these standards are also used as guidelines for everything from a document to a software app to video movies. Some parts are simply NOT meant to be applied indiscriminately to e-learning. I find this whole Accessibility area is unfortunately full of misinformation.

You speak about '508' and then list WCAG sections. I sincerely hope you are not being required to meet BOTH accessibility standards? If you're in the USA then only one (508) is likely required.

You can compare the two competing standards here on Jim Thatcher's site: Comparison WCAG and Section 508 Web

You can check Adobe's Accessibility page here to see which parts of 508 1194.22 would be applicable to Captivate (the application) and it's output (the HTM/SWF or HTML5). You'll find Adobe clearly states that both the app and its output support this section BUT WITH EXCEPTIONS.

Report · Sep 01, 2015

By the way, the highlight colors on the Captivate playbar are also unlikely to be deemed 508 compliant if your tester decides to look at the aspect of having sufficient contrast with the background.

Report · Sep 29, 2015

Rod:

The issue here isn't necessarily the blind user - it's the mobility impaired user. How do you access a rollover if you can't use the mouse? The problem with roll-overs is simple - they're not 508 compliant by definition.

An interactive object needs to be accessible through a focus keystroke (the default is "tab" to get to the object) and then must have a method to activate the object to access the hidden content (the "enter" action in the default access process) The rollover (and the hot spot) isn't compliant for the same reason it doesn't work in HTML5 - it doesn't follow these rules.

depending on what organization the developer is building for, there are workarounds available - the simplest is to build a button that shows the content and insert a button in the content that hides it. Not as slick and pretty as the rollover, but it works in the mobile setting and is accessible to the mobility impaired user.

Another possibility, depending on the timelines and the money available for development, is to create a branched project that triggers alternate slides for individuals who need 508 accessible slides when the user selects a button at the beginning of the project. This allows you to build all the interactive stuff for the fully able learner into the project, and create alternate interactive versions of the content that meet 508 or WCAG standards.

As far as the contrast issue with the highlight color - if Adobe ever fixes this, I'll be a happy man - diving into the .css to get rid of the ridiculous pale blue outline for HTML 5 is a pain in the rear! I don't use the playbars unless absolutely required by a client - too restrictive!

Justenuf

Report · Sep 29, 2015

Go to File>Publish Settings. for reasons unknown to rational beings, Adobe has set the default setting to hide the selection rectangle you need for accessibility:

Uncheck the box and your interactives will now be highlighted as you tab through. The bad news? Adobe has set the default color (which can only be changed by diving into the .css files) to pale blue. Apparently, a high contrast color as required by 508 standards is too much to ask for (although i have, repeatedly, done just that)

Justenuf

Report · Jan 31, 2018

Thanks Justenuf, this was super helpful!