Creating A Tab Order Index For Keyboard Navigation In The Accessibility Panel (Flash Professional Only) - MACROMEDIA FLASH MX 2004-USING FLASH Use Manual

Creating a tab order index for keyboard navigation in the
Accessibility panel (Flash Professional only)
You can create a tab order index in the Accessibility panel for keyboard navigation. You can create
a custom tab order for the following objects:
•
Dynamic text
•
Input text
•
Buttons
•
Movie clips, including compiled movie clips
•
Components
•
Screens
Note: You can also use ActionScript to create a keyboard navigation tab order index. See
ActionScript to create a tab order for accessible objects" on page
Tab focus occurs in numerical order, starting from the lowest index number. Once tab focus
reaches the highest tab index, focus returns to the lowest index number.
When you move user-set tab indexed objects around in your document, or to another document,
Flash retains the index attributes. You should then check for and resolve index conflicts (for
example, two different objects on the Stage that have the same tab index number).
Caution: If two or more objects have the same tab index in any given frame, Flash follows the order in
which the objects were placed on the Stage. Therefore, you should resolve all tab index conflicts to
be sure the desired tab order index is achieved.
To create a tab order index:
Select the object in which to assign a tab order and do one of the following:
1.
Select Window > Properties if the inspector is not visible. In the Property inspector, click
the Accessibility button.
Select Window > Other Panels > Accessibility.
If you're providing an index for the selected object only, in the Tab Index text box, enter a
2.
positive integer (up to 65535) that reflects the order in which the selected object should
receive focus.
Note: For information about creating a tab order using ActionScript, see
create a tab order for accessible objects" on page
appear on Stage when the Show Tab Order option is enabled.

Creating a tab order index for keyboard navigation in the Accessibility panel (Flash Professional only)

371.
371. Tab indexes created in ActionScript do not
"Using
"Using ActionScript to
367