Copy link to clipboard
Copied
Weird little glitch here - I was checking my project for accessibility/508 compliance and noticed that the tab order on some of my buttons was a little counter-intuitive. Everything worked and functioned properly, but the order was off. I opened the slide and selected the tab order drop-down to reconfigure it, and found several instances of one or more buttons missing from the list. As I said, since all the buttons are designed exactly the same way (text buttons) and all of them are accessible when I'm testing it in the browser, I don't understand how Captivate doesn't "see" them as part of the tab order sequence for interactives on the slide - any ideas as to what's happening here?
Justenuf
I had created slides that had buttons incorporated into groups that only appeared when certain variables were triggered or a shared action changed them to "show" and that caused the "glitch" I saw above.
So, here's the deal: when you create groups that divide up the buttons, the tab order tool in the slide dropdown fails - it can only see the first grouped set of buttons, the rest don't show up. The only way to tab order your buttons separated into groups is to do so within the timeline (at least
...Copy link to clipboard
Copied
I had created slides that had buttons incorporated into groups that only appeared when certain variables were triggered or a shared action changed them to "show" and that caused the "glitch" I saw above.
So, here's the deal: when you create groups that divide up the buttons, the tab order tool in the slide dropdown fails - it can only see the first grouped set of buttons, the rest don't show up. The only way to tab order your buttons separated into groups is to do so within the timeline (at least the most updated version of Cp8). Tab order (at least in the project I'm dealing with right now) is indicated from the bottom to the top of the time line. In the image below, the first button that is activated by tabbing is button 448 in group 456, the last is button 446 in group 454. (the click box never gets activated, it's hidden for accessibility purposes) Before anyone asks why I'm not just using smart shapes for buttons - they are NOT tabbable and don't meet my needs.