TIP #4 | Disabled Buttons
Monday, June 30th, 2008
When you are programming buttons dynamically, you might be enabling or disabling buttons that are not in use. For example, a back button can be greyed out and disabled on the first page of a slideshow. If you are leaving these buttons on the stage, and disabling them by button.enabled = false; code, then make sure to also set the button.tabEnabled = false; as well.
Buttons that are disabled, but still tabEnabled, form silent holes in the tab order. You still tab to them, but no yellow focusrect will appear. This might be confusing to users that use the tab key.
To read all the tips, select ‘Flash Accessibility Tips’ on the side bar.

We have just finished a project for
We have come across several Coming Soon rollover buttons. Sometimes button objects are used that do not actually have an OnRelease event, but just an OnRollOver state. Nothing happens when you click them, just when you roll over them. This is clear to a sighted user, but to a screen reader user it might be confusing when the button reads as a ‘button’, but nothing happens when it is clicked.
When you have ordered all the elements with .tabIndex, and you want to test out the Reading Order with a screen reader, you will have to publish and open your file in Internet Explorer. This is because the screen reader works with MSAA, that runs inside of the browser. MSAA pulls out the content of your Flash movie, and feeds it to the screen reader. But to test out the Tab Order, by tabbing through the movie, you don’t have to leave Flash.
When making Flash accessible, there are two things to consider: 1) The Reading Order. This is the order in which the screen reader reads the Flash content. 2) The Tab Order. This is the order in which a user would tab through the Flash movie by pressing the Tab key.