Flash Accessibility Standards v1.0
Note
This standard has been replaced by the Multimedia Accessibility Standards.
1. Definitions
1.1. In this document, we use the following definitions:
1.1.1. A "Flash movie" is the SWF container you put on a HTML page.
1.1.2. A "Flash Object" is an item contained within a Flash movie e.g. a video clip or button.
1.1.3. A "Stage" is the visible area of a Flash movie.
2. In general
2.1. Flash movies MUST always be embedded using JavaScript. If the user doesn't get the JavaScript, they don't get the Flash
2.2. Any Flash movie which is core content MUST have an HTML equivalent UNLESS it can be proven to be impossible to deliver for technical or practical reasons.
2.3. Any Flash video content MUST have keyboard-accessible transport controls, or alternatively provide an accessible alternative (usually a Real Media version using Media Selector).
2.4. A mute button MUST be available for any Flash objects that contain audio, including during download.
2.5. A visible link MUST be provided wherever there is an alternative to a Flash movie. Users MUST be able to access the HTML or Real non-Flash alternative, even if they have Flash installed see Plug-In Standards (3.1.1.3.4.)
2.6. A user MUST always be able to access the default functionality provided in the context (right-click) menu.
2.7. All graphic interface elements MUST comply with the Colour Contrast Standards.
2.8. Flash objects MUST NOT cause the page containing it to auto refresh.
3. Movement
3.1. Users MUST be able to be freeze or pause all moving clickable content contained within the flash movie, unless the clickable content is part of a game which doesn't make sense if you allow freezing content. This will enable users with poor motor skills to have better access. This is in addition to the movement standards in the Accessibility Guidelines.
3.2. You MUST ensure that when a user has tabbed to an interactive element outside of the visible area, the interactive element MUST come into view
4. Keyboard requirements
4.1. A user MUST be able to access content using the keyboard only UNLESS it can be proven to be impossible to deliver for technical or practical reasons (see Accessibility Guidelines).
4.2. The user MUST be able to play Flash games using solely the keyboard.
4.3. Keyboard controls SHOULD be chosen which allow users with switches to use their switches to control Flash movies:
4.3.1. Double switch access: tab key (for moving from selectable object to selectable object), and space bar or return key (to select).
5. Text equivalents
5.1. The name property of all accessibility controls featured in a Flash movie MUST reflect the functionality rather than the control's design.
5.2. A description of the object MAY be placed in the "description" field, so it can be read by a screen reader. The description SHOULD be concise.
5.3. Flash objects or elements which are not editorially significant MUST NOT have text equivalents. Any object that does not provide user interaction or is not editorially significant SHOULD have its accessibility properties left as silent by default.
5.4. Any text contained within a button MUST feature in its text equivalent.
6. Flash marketing banners
6.1. There MUST be an HTML equivalent to each banner.
6.2. Animations MUST stop after a maximum of two loops.
6.3. All banners MUST comply with the Flicker Standards.
6.4. Additional functionality such as expanding panels including surveys or competitions MUST NOT be triggered by a mouse over, and MUST be launched by clicking (or equivalent action) the banner.
6.5. Additional functionality MUST be available as a text equivalent.
7. Document history
| Date | Version | Change | Author |
|---|---|---|---|
| 24/9/2007 | v1.0 | First version of the standards | Gareth Ford Williams, ed. Jonathan Hassell |
Document editor: Editor, Standards & Guidelines. If you have any comments, questions or requests relating to this document, please contact the Editor, Standards & Guidelines.
Like all other Future Media Standards & Guidelines, this page is updated on a regular basis, through the process described on About Standards & Guidelines.
© MMIX