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: May 6, 2013

Name of product: Adobe® Dreamweaver® CC

Contact for more information: access@adobe.com

Summary
Guideline Applicable Compliance

Section 1194.21 – Software Applications and Operating Systems

Applicable

Supports with exceptions

Section 1194.22 – Web-based Intranet and Internet Information and Systems

Applicable

Supports

Section 1194.23 – Telecommunications Products

Not Applicable

Section 1194.24 – Video and Multimedia Products

Applicable

Section 1194.25 – Self-Contained, Closed Products

Not Applicable

Section 1194.26 – Desktop and Portable Computers

Not Applicable

Section 1194.31 – Functional Performance Criteria

Applicable

Supports with exceptions

Section 1194.41 – Information, Documentation, Support

Applicable

Supports

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

Customizable keyboard navigation is provided for all menu commands, as well as for commands in various panels in Dreamweaver CC. However, some elements of the interface are not keyboard accessible, including:

  • There is limited keyboard access to panels using the keyboard. For example, keyboard shortcuts can be used to place focus on the Files panel but it is not possible to get to controls beyond the panel title and menu. Focus has to be placed within the controls with a mouse first.

  • Some controls in dialog boxes are not operable using a keyboard, such as the color pickers in the Code Coloring section of the Preferences dialog. However, alternatives are usually available.

  • In some panes in dialog boxes it is not possible to move keyboard focus away from the panes, such as in the Edit Coloring Scheme section of the Preferences dialog box.

(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

Dreamweaver CC does not interfere with operating system accessibility features.

(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

Most user interface elements in the Dreamweaver CC interface provide a visual indication of focus with some exceptions, including:

  • Some controls in panels, such as the Log button in the Files panel or the Insert button in the Assets panel, do not provide a visual indication of focus.

  • Some controls in dialog boxes, such as the checkboxes in the Highlight section of the Preferences dialog, do not provide a visual indication of focus.

  • Add Item and Delete Item buttons in dialog boxes provide an indication of focus that may not be visible to all users.

  • Focus is programmatically exposed to assistive technology with the exception of objects on the canvas in Design view and some lists, such as the file explorer in the Site 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

Identity role and state information is available for most controls in the Dreamweaver CC interface with some exceptions including:

  • Tree controls in the Files panel and Site view and the list of Commands in the Keyboard Shortcuts dialog, do not provide sufficient information to assistive technology.

  • Links on the Welcome screen do not provide information.

  • Some controls in dialog boxes do not include labels, such as the Import Tabular Data dialog or combo boxes in the Keyboard Shortcuts dialog.

  • Content in Live View and Code View in Live mode do not provide information to assistive technology.

  • Objects, such as images, on the canvas in Design view, do not provide sufficient information.

(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

Bitmap images are used consistently in Dreamweaver CC.

(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

With the exception of text in Live modes, textual information in the Dreamweaver interface is available to assistive technology.

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

Supports with exceptions

Dreamweaver CC supports Windows High Contrast mode with some exceptions, including:

  • Some application menus, such as the Layout menu, have limited support for Windows High Contrast mode.

(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 Dreamweaver CC 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 Dreamweaver CC interface does not use color as the only means of conveying information, indicating an action, prompting a response with the exception of highlights for elements like Editable Regions. However, the colors used can be edited and there are alternative ways of conveying this information, such as Code View.

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

Not applicable

Dreamweaver CC does not permit the user to adjust color and contrast settings of the product with the exception of code coloring and Highlights.

(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

Dreamweaver CC 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

Form controls in the Dreamweaver CC interface are fully operable using assistive technology, with some exceptions, including:

  • Forms in Live View do not provide information to assistive technology.

  • Controls in some dialog boxes, such as the Clean Up Word HTML dialog, do not provide sufficient information to assistive technologies.

  • Controls in some panels are not reachable 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

Dreamweaver CC prompts users to enter image equivalents when inserting images.

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

Supports

Dreamweaver CC supports the inclusion of multimedia content created with other tools. Authors can add accessibility features to their multimedia utilizing the features of third party tools.

(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

Dreamweaver CC allows authors to convey meaning with alternatives or with additional text.

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

Supports

Dreamweaver CC allows authors to create pages that meet this requirement.

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

Supports

Dreamweaver CC allows authors to create pages that meet this requirement.

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

Supports

Dreamweaver CC allows authors to create pages that meet this requirement.

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

Supports

Dreamweaver CC supports the creation of row and column headers for tables.

(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

Dreamweaver CC supports the association of multiple row and column headers with related data cells.

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

Supports

Dreamweaver CC prompts authors to provide frame titles.

(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

Dreamweaver CC supports the creation of content that 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

Dreamweaver CC allows authors to create pages that meet 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

Authors can create their own scripts or use scripts generated by Dreamweaver CC. In all cases it is possible to edit scripts within Dreamweaver CC to ensure compliance with this standard.

(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

Dreamweaver CC allows authors to create pages that meet this requirement.

(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

Dreamweaver CC prompts authors to assist in the creation of form labels for controls.

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

Supports

Dreamweaver CC supports the inclusion of skip navigation links as well as headings and other structural elements that can help users skip repetitive elements.

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

Supports

Dreamweaver CC does not create time-based content by default. Authors need to verify compliance in content created in Dreamweaver.

 

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

Most controls and functions in the Dreamweaver CC user interface are accessible to screen readers with some exceptions including:

  • There is limited access to controls in panels using a keyboard alone.

  • Some controls in dialog boxes do not provide sufficient information to assistive technology.

  • Tree controls in the Files panel and Site view do not provide sufficient information.

  • Objects, such as images, on the canvas in Design or Live View, do not provide sufficient information.

(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

Dreamweaver CC supports the use of screen magnifiers.

However, some controls in panels and dialog boxes do not provide a clear visual indication of focus and focus is not  programmatically exposed in some cases, such as the tree control in Site view.

(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