Adobe is changing the world through digital experiences. Our creative, marketing and document solutions empower everyone — from emerging artists to global brands — to bring digital creations to life and deliver them to the right person
at the right moment for the best results.

Preorder Estimated Availability Date. Your credit card will not be charged until the product is shipped. Estimated availability date is subject to change.Preorder Estimated Availability Date. Your credit card will not be charged until the product is ready to download. Estimated availability date is subject to change.

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.

(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

Supports with Exceptions

The vast majority of user interface elements and actions can be accessed via the keyboard in a logical tab order or through keystrokes.

Design view is not keyboard accessible. The tasks performed in Design view can also be performed through the Outline and Properties views as well as the Source view. It is not possible to drag and drop items from the Components view on the design view. Components can be added manually in the Source view.

There are several font buttons, color pickers, accordions, and drop downs in the Properties and Appearance views that can not be navigated to via the keyboard.

There does not appear to be a keystroke to show/hide folding in the Source view..

There is one combo box in the Properties view where focus is shifted away from the window when the user tabs out of the field.

Several links on the Welcome screen are not in the tab order but can be found on Adobe's website.

There is limited keyboard access in the Select Project Theme window.

(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.

Supports with Exceptions

Windows within the application follow operating system (OS) settings for accessibility with the small exceptions noted below:

The cursor in the Source editor and Design view does not increase in width based on the OS settings but a "thick caret" is provided for the source view to increase accessibility. The caret blink rate in the Design view does not follow the OS settings.

The width and blink rate of the caret is honored in other windows of the application.

(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes.

Supports

On-screen focus is provided for all user interface components with one exception, the "Control Bar" checkbox in the Properties view.

(d) Sufficient information about a user interface element including the identity, operation, and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text.

Supports with Exceptions

The majority of user interface elements expose accessibility information about their name, state, value, and role.

In the Source view, lines with errors and annotations can be reached via a keystroke. The error or annotation text then appears on the status line. However, some of the text on the status line is cutoff.

The font and alignment buttons in the Appearance and Properties views are missing accessible names.

Grouping for controls in the Properties and Appearance views are missing accessible names or are not grouped using a role of grouping.

The outline structure in the Select Project Theme window is missing accessible name, role, and state information.

Several links on the Welcome screen do not provide accessible names and roles.

(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.

Supports

Images are used consistently across the application.

(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.

Supports with Exceptions

All content except that in the Design view and the Welcome screen appears as text through the operating system.

Most screens and user interface elements in the Flash Builder follow the color and contrast settings of the OS. However the following screens do not:

Welcome screen

Design view

Content Assist

The following views contain a small number of elements that do not follow the color/contrast settings:

Source view

Properties

Appearance

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

Not Applicable

Flash Builder does not use Animation.

(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Supports

Annotations using color and icons are used throughout the Source view. In the Source view these annotations can be access by keystrokes for next and previous. For instance, variables and function names are highlighted while editing to indicate other occurrences of the object. The user however, can press the next annotation keystroke and the next occurrence of the variable, attribute, or function is highlighted visually and programmatically and the cursor is moved.

(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.

Supports

For the majority of screens, the application does not provide the user option to adjust color and contrast settings directly in the application. However, colors can be set for the Source view code highlighting and the user is able to choose colors from a wide range of colors.

(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.

Supports

The application does not cause blinking or flashing.

(l) When electronic forms are used, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Supports with Exceptions

The vast majority of form fields found in the user interface provide accessibility properties and can be completed by users with disabilities. There are however some fields in a limited number of screens indicated in Section 1194.21(d) above that are missing some information such as accessible name, or role which may prevent users from accessing these fields.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

Supports

Authors need to ensure that the content they create meets this requirement.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

Supports

Authors need to ensure that the content they create meets this requirement.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

Not Applicable

The SWF file format does not use separate style sheets.

(e) Redundant text links shall be provided for each active region of a server-side image map.

Not Applicable

Flex does not contain a server-side image map component.

(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

Not Applicable

Flex does not contain a server-side image map component.

(g) Row and column headers shall be identified for data tables.

Supports

The DataGrid and AdvancedDataGrid components support row and column headers. Header information is pre-pended to the values for cells and inserted in header data pairs for row selection.

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

Supports with Exceptions

The AdvancedDataGrid component supports multiple levels of hierarchy using an outline structure. The outline item grouping first column header does not appear as the accessible name of the outline item.

(i) Frames shall be titled with text that facilitates frame identification and navigation.

Not Applicable

The SWF file format does not use frames.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Supports

Authors need to ensure that the content they create meets this requirement.

(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

Supports

Authors need to ensure that the content they create meets this requirement.

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology.

Supports with Exceptions

Authors need to ensure that the content they create meets this requirement.

Menubar: A Focus event is not properly fired when focus is moved between menubar items. Focus is properly indicated when arrowing between menu items.

TitleWindow: Programmatic focus is not indicated on the first component of a TitleWindow on initial entry into the TitleWindow.

ColorPicker: The proper value change events on the combo box or list items do not fire when values are changed in the color picker.

(m) When a web page requires that an applet, plug-in, or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).

(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Supports with Exceptions

Flex form components support assistive technology.

DateField: Incorrect value, role, and name for controls are provided when in opened state. This information is correct when in closed state. The opened/closed state of the DateField is not indicated in an accessible manner.

Form: The name of form fields are not updated when dynamically changed.

DateChooser: The name of the DateChooser changes based on what is selected and thus the name of the control is replaced by the currently selected date. The role for this control is "window" which does not adequately describe the role of the component.

Numeric Stepper: The role of the numeric stepper is not indicated as a spinbox or spinner, but only as "edit".

Accordion: The reading order of content can not be set for accordion tabs and the tabs appear in the incorrect reading order in the document.

ComboBox: The text within the editable portion of the edit combo is not written through the OS and is not exposed in a manner that supports selection or navigation by character via assistive technology. The value as whole is exposed in an accessible manner.

(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.

Supports with Exceptions
(Application)

Supports with Exceptions
(Flex Content)

Users with visual impairments often rely on the keyboard or on assistive technology that emulates the keyboard. To support this most of the user interface elements in Flash Builder are keyboard accessible. A long list of keystrokes, key sequences, and shortcuts are provided to assist users. These keystrokes and sequences are customizable by the user. Different perspectives are available to allow the user to configure the views he/she needs to access.

There are however, some user interface elements that are not keyboard accessible. These include Design view, however, the tasks performed in Design view can also be performed through the Outline and Properties views as well as the Source view.

Several other areas are missing complete keyboard access such as font buttons, color pickers, accordions, and drop downs in the Properties and Appearance views, show/hide folding in the Source view, one combo box in the Properties view where focus is shifted away from the window when the user tabs out of the field, the Select Project Theme window, and several links on the Welcome screen are not in the tab order but can be found on Adobe's website. It is not possible to drag and drop items from the Components view on the Design view. Components can be added manually in the source view.

The majority of user interface elements expose accessibility information about their name, state, value, and role. There are however, some situations where this does not occur. For example, the Design view does not expose accessibility about its elements however, these elements can be accessed through the Outline view combined with the Property view. A small number of views/screen such as the Properties and Appearance View as well as the Select Project Theme screen have components that are missing completely accessible information. The icons in the Package Explorer and Quick Outline do not indicate textual descriptions, however, each outline item does contain text indicating its name. Several links in the Welcome screen do not expose accessibility information, however, this information can be found on Adobe's website.

By default most components expose accessibility in a manner that is compatible with assistive technology used by people with visual impairments. There are some exceptions as noted above in Section 1194.22. Additional methods of access can be built into an application by the author to accommodation for limitations in the components.

Flex content provides keyboard access for all accessible components by default. Additional keyboard access can be provided by the author of the application.

(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 with Exceptions
(Flex Content)

Users with low vision often choose to use custom color and contrast settings as well as other accessibility enhancements found in the operating system or in assistive technologies.

Most screens and user interface elements in the Flash Builder follow the color and contrast settings of the OS. However, the Welcome, Design view, and Content Assist do not. The following views contain a small number of elements that do not follow the color/contrast settings: Source View, Properties, and Appearance.

Annotations using color and icons are used throughout the Source view. In the Source view these annotations can be accessed by keystrokes for next and previous. For instance, variables and function names are highlighted while editing to indicate other occurrences of the object. The user however, can press the next annotation keystroke and the next occurrence of the variable, attribute, or function is highlighted visually and programmatically and the cursor is moved.

Windows within the application follow operating system (OS) settings for accessibility with the small exceptions noted below:

The cursor in the Source Editor and Design view does not increase in width based on the OS settings but a "thick caret" is provided for the Source view to increase accessibility. The caret blink rate in the Design view does not follow the OS settings. The width and blink rate of the caret is honored in other windows of the application.

Visual keyboard focus is provided for all components except for one known checkbox.

Authors of Flex based content must addressed color/contrast and font size issues in the application as Flex content currently does not inherit the color/contrast and font settings from the operating system.

Flex content provides keyboard access for all accessible components by default. Additional keyboard access can be provided by the author of the application.

(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.

Not Applicable
(Application)

Supports
(Flex Content)

Flash Builder does use not sound.

Flash Builder provides the means for Authors of Flex content to address this in an application.

(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.

Not Applicable
(Application)

Supports
(Flex Content)

Flash Builder does use not sound.

Flash Builder provides the means for Authors of Flex content to address this in an application.

(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.

Not Applicable
(Application)

Supports
(Flex Content)

Flash Builder does not require user speech.

Flash Builder provides the means for Authors of Flex content to address this in an application.

(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.

Supports with Exceptions
(Application)

Supports
(Flex Content)

Users with mobility impairments often rely on the keyboard or on assistive technology that emulates the keyboard and/or mouse. To support this most of the Flash Builder user interface elements are keyboard accessible. A long list of keystrokes, key sequences, and shortcuts are provided to assist users. These keystrokes and sequences are customizable by the user. Different perspectives are available to allow the user to configure the views he/she needs to access.

There are, however, some user interface elements that are not keyboard accessible. These includes Design view, however, the tasks performed in Design view can also be performed through the Outline and Properties views as well as the Source view.

Several other areas are missing complete keyboard access such as font buttons, color pickers, accordions, and drop downs in the Properties and Appearance views, show/hide folding in the Source view, one combo box in the Properties view where focus is shifted away from the window when the user tabs out of the field, the Select Project Theme window, and several links on the Welcome screen are not in the tab order but can be found on Adobe's website.

It is not possible to drag and drop items from the Components view on the Design view. Components can be added manually in the source view.

Flex content provides keyboard access for all accessible components by default. Additional keyboard access can be provided by the author of the application. Keyboard commands can be voiced by users of speech recognition software.