The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding the availability of commercial Electronic and Information Technology products and services with features that support accessibility. It is assumed that offerers will provide additional contact information to facilitate more detailed inquiries.

The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table. Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.

Date: 05/16/2011

Name of product: Adobe Flash Professional CS5.5

Contact for more information: access@adobe.com

 

Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following Priority 1 checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) – 1.1, (b) – 1.4, (c) – 2.1, (d) – 6.1, (e) – 1.2, (f) – 9.1, (g) – 5.1, (h) – 5.2, (i) – 12.1, (j) – 7.1, (k) – 11.4.

Section 1194.31 Functional Performance Criteria — Detail
Criteria Supporting features Remarks and explanations

(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided.

Does not support (Application)

 

Supports with exceptions (Flash based output)

Most actions in Flash CS5.5 related to timeline editing and content editing cannot be performed with a screen reader.

Some elements in the application interface do not provide sufficient accessible role, name or state information.

Panels and windows that do not expose sufficient information include: File Info, Check Spelling, Code Snippets, Duplicate Symbol, the Library, Color and Swatches, and Document Settings.

While keyboard access is provided to the Actions panel selecting particular frames and layers can be difficult. However, it is also possible to write ActionScript code in external files using an external text editor.

The workspace can be customized to only display the needed panels and allow for more efficient keyboard access.

Flash based Output:

Form controls can be made accessible for screen readers.

Some events used by assistive technology are not fired by default in the combo box. The text of an editable combo box cannot be reviewed character by character via a screen reader.

The role of the numeric stepper is not indicated to users of screen readers.

DataGrids that are editable are difficult to navigate via the keyboard by default. Authors are able to extend and customize the DataGrid component to improve the keyboard access.

(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided.

Supports with exceptions (Application)

 

Supports (Flash based content)

Focus is generally visually indicated, but not always exposed programmatically.

Some panels in the application interface do not inherit color and contrast settings specified by the operating system.

Flash based Output:

All elements in Flash based content can be made focusable and will provide a visual focus indication.

Although Flash content does not inherit color and contrast settings specified by the operating system, the Flash author can provide such color schemes manually.

(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided.

Supports (application)

Supports (Flash based content)

Flash CS5.5 does not require hearing for operation.

Flash based Output:

Flash CS5.5 allows caption files to be added to Flash multimedia content.

For content that uses auditory cues, the Flash author can provide visual cues manually.

(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

Supports (Application)

Supports (Flash based content)

Flash CS5.5 does not require hearing for operation.

Flash based Output:

Flash CS5.5 allows caption files to be added to Flash multimedia content.

For content that uses auditory cues, the Flash author can provide visual cues manually.

(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided.

Supports (Application)

Supports (Flash based content)

Flash CS5.5 does not require user speech.

Flash based Output:

Flash content can be created that does not require user speech.

(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Does not support (Application)

 

  

Supports (Flash based content)

Content editing often requires fine motor control using a mouse, or a combination of multiple keys and a mouse.

Selecting particular frames and layers can be difficult due to keyboard issues within the Actions panel. While most dialogs and panels support keyboard access there are some issues with illogical tab order and difficulty getting keyboard focus into a panel after switching panels.

The keystrokes to switch between panels do not always consistently work as expected.

The workspace can be customized to only display the needed panels and allow for more efficient keyboard access.

Flash based Output:

Flash provides built-in controls that are keyboard accessible, and allow authors to manually implement keyboard support for custom controls.