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: January 10, 2013

Name of product: Adobe® Flash® Builder® 4.7

Contact for more information: access@adobe.com

Section 1194.21 Software Applications and Operating Systems - Detail
Criteria Supporting features Remarks and explanations

(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

Controls in the Flash Builder 4.7 interface are fully operable using a keyboard alone with some exceptions including:

Some controls in panels, such as the close control in the Package Explorer panel, are not reachable using the keyboard alone. When tabbing through panels, focus switches to the main toolbar when it leaves a panel. However, it is possible to move focus to any open panel using a shortcut key.

The Description field in the New Task panel traps keyboard focus.

Some controls in dialog boxes, such as the Validation section in the Properties dialog box, are not operable using a keyboard alone.

Sort controls in tables in some dialog boxes, such as the Properties table in the External Tools Configurations dialog, are not operable using a keyboard alone.

The ‘expand/collapse’ controls in the Code Editor are not reachable using a keyboard alone.

(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

Flash Builder 4.7 does not interfere with operating system accessibility features with one exception:

The cursor in the Source editor does not increase in width based on the OS settings but a “thick caret” is provided for the source view to increase accessibility.

(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 with exceptions

With the exception of some controls in panels, there is a clear visual indication of focus for controls in the Flash Builder 4.7 interface.

Combo boxes in some dialog boxes, such as the New Flex Project dialog, do not provide a clear visual indication of focus.

Some links in the Welcome Screen do not provide a clear visual indication of focus.

When focus is on a panel tab, such as the History panel, there is a weak visual indication.

Focus is programmatically exposed to assistive technology.

(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

Sufficient information is available for controls in the Flash Builder 4.7 interface, with some exceptions, including:

Some controls in dialog boxes, such as the color pickers in the Run/Debug section of the Preferences dialog, do not provide identity information.

Some combo box controls in dialog boxes, such as the Connection Type control in the Debug Configurations (New Configuration) dialog, do not provide identity information.

Some controls in the Code Editor, such as the breakpoint icons or expand/collapse controls, do not provide identity, role or state information.

Some controls in panels, such as the Task Title input and the Priority Level menu in the Task panel, do not include identity information.

The ‘Don’t show this again’ checkbox in the Welcome screen does not include a label.

(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

 

(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

Textual information is available in the Flash Builder 4.7 interface with some exceptions.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

Supports with exceptions

Flash Builder 4.7 fully supports OS color and contrast settings with some exceptions including:

Some panels, such as the Properties panel, contain elements that do not fully support OS color and contrast settings.

Some dialog boxes, such as the External Tools Configurations dialog, do not fully inherit settings in all cases, such as the active state of tabs.

The Task panel does not inherit user display settings.

(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

The Flash Builder 4.7 interface 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

The Flash Builder 4.7 interface does not use color as the only means of conveying information that cannot be obtained via another method.

Source view does use color annotations but these colors can be modified and the information attained by other methods.

(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 with exceptions

Flash Builder 4.7 allows users to change color and contrast levels for the Source view, where a wide variety of color schemes are available.

(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

Flash Builder 4.7 does not use flashing or blinking text, objects, or other elements in the software's user interface.

(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

Flash Builder 4.7 provides sufficient information to assistive technology for most form controls with some exceptions, including:

Some controls in dialog boxes, such as the color pickers in the Run/Debug section of the Preferences dialog, do not provide identity information.

Some combo box controls in dialog boxes, such as the Connection Type control in the Debug Configurations (New Configuration) dialog, do not provide identity information.

Most form controls can be operated using a keyboard alone with some exceptions, including:

Some controls in panels are not reachable using the keyboard alone, such as the Enabled and onClick fields in the Properties panel, when an object is selected.

Sort controls in tables in some dialog boxes, such as the Properties table in the External Tools Configurations dialog, are not operable using a keyboard alone.

Section 1194.22 Web-based Internet information and applications - Detail
Criteria Supporting features Remarks and explanations

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

Supports

Authors can apply text equivalents to all Flex user interface components in Flash Builder 4.7.

(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

Flash Builder 4.7 allows authors to create content that meets this requirement.

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

Supports

Flash Builder 4.7 does not generate style sheets.

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

Not applicable

Flash Builder 4.7 does not generate image maps.

(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

Flash Builder 4.7 does not generate image maps.

(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 provides nested column headers, but only the top header will be associated with the column data cells. If authors create a component with multiple rows of header cells, this information should be combined with the accessible name of the associated row or cell (list item).

Flash does not provide components that use the accessible roles of header cell or data cell.

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

Not applicable

Flash Builder 4.7 does not create 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

Flash Builder 4.7 allows authors to create content that does not cause the screen to flicker.

(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 can create text-only equivalents for content created in Flash Builder 4.7, but equivalents should not be necessary.

(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

Flash Builder 4.7 allows for the creation of accessible content and interface elements that are available to assistive technology.

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

Supports

The default HTML template used by Flash Builder 4.7 to publish Flex projects automatically generates a link to the Flash Player plug-in if it is not already installed.

(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

Forms created with Flash Builder 4.7 support assistive technology with some exceptions, including:

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

DateChooser: 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".

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 a whole is exposed in an accessible manner.

(o) A method shall be provided that permits users to skip repetitive navigation links.

Supports

Authors can add links to content in Flash Builder 4.7.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Supports

Flash Builder 4.7 content does not require a timed response by default. Authors can build applications that comply with this requirement.

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.

Supports with exceptions

The Flash Builder 4.7 interface supports screen readers. However, in some cases sufficient information is not provided.

Most tasks and commands are operable using the keyboard alone with some exceptions, including:

Some controls in panels are not reachable using the keyboard alone, such as the Enabled and onClick fields in the Properties panel, when an object is selected. When tabbing through panels, focus switches to the main toolbar when it leaves a panel.

Some tasks in dialog boxes, such as selecting Manual and Build checkboxes in the Validation section of the Preferences dialog, are not operable using a keyboard alone.

(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

Flash Builder 4.7 supports the use of Screen Magnifiers. However, in some minor cases there is not a clear visual indication of focus and some controls in panels and dialog boxes do not inherit OS color and contrast settings.

(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

 

(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

 

(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

 

(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

Some operations in Flash Builder 4.7 may require fine motor control. However, there is usually an alternative available, such as Source view.

Section 1194.41 Information, Documentation, and Support - Detail
Criteria Supporting features Remarks and explanations

(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge.

Supports

Adobe provides electronic versions of all product support documentation.

(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.

Supports

Adobe provides information on accessibility features in the documentation. Electronic versions of all product support documentation are provided.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

Supports

Product support for Adobe products is available in a variety of formats and from a number of online sources available from Adobe Systems.