VPAT® Version 2.0 – October 2017
Name of Product/Version: Adobe Dreamweaver CC 2017, Version 18
Product Description: Create, code, edit and manage responsive HTML websites that look amazing on any size screen.
Date: February 2018
Contact information: access@adobe.com
Notes: The information contained in this report applies to the product itself. Information about product help and support documentation related to 602.3 (Support Docs) for Section 508 as published in 2017 is located at: http://www.adobe.com/accessibility/compliance.html.
Evaluation Methods Used: Testing Adobe Dreamweaver CC involved extensive use of leading assistive technologies, such as screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
This report covers the degree of conformance for the following accessibility standards/guidelines:
Standard/Guideline |
Included In Report |
|---|---|
Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/ |
Level A - Yes Level AA - Yes Level AAA - No |
Section 508 as published in 2017, at http://www.Section508.gov |
Yes |
EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, at http://mandate376.standards.eu/standard |
Yes |
The terms used in the Conformance Level information are defined as follows:
Sections 1 and 2 also document conformance with:
Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Notes:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
1.1.1 Non-text Content (Level A)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not provide prerecorded audio-only or video-only content. |
1.2.2 Captions (Prerecorded) (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product includes audio content in synchronized media and captions are provided. Authored Content (HTML): Authors can provide captioned audio in authored content, but the captions must be authored and embedded using separate software. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Software: The Quick Tutorial videos found in the Help Menu do not provide any audio description. |
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
1.3.1 Info and Relationships (Level A)
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Many user interface elements provide programmatic information about structure and relationships. Exceptions include:
|
1.3.2 Meaningful Sequence (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product presents content in a meaningful sequence. Authored Content (HTML): The product allows authors the ability to present content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A)
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Exceptions include: Referring to the “Add Media Query” button exclusively through its visual icon. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
1.4.1 Use of Color (Level A)
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.2 Audio Control (Level A)
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.1.1 Keyboard (Level A)
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most product functionality can be operated through a keyboard interface. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not include keyboard traps. Authored Content (HTML): Authored content does not include keyboard traps. |
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not include time limits. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Moving, blinking, scrolling, and auto-updating information can be paused, stopped or hidden by the user. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Do not design content in a way that is known to cause seizures.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain flashing content. |
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
|
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Components receive focus in a meaningful order. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The language is programmatically determinable within the product. Additional remarks:
Authored Content (HTML): Authors can set the language for content. |
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
|
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
|
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
|
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Authored Content (HTML): Authors can ensure that content meets this criterion. |
Notes:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not provide live media that requires captions. Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Software: The Quick Tutorial videos found in the Help Menu do not provide any audio description. Authored Content (HTML): Users can include an additional audio track for audio description information that will be included as part of the media. |
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most text meets minimum contrast requirements. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
|
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product uses text instead of images of text. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. |
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Headings and labels are descriptive. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: The keyboard focus indicator is generally visible. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Content is only presented in one language at a time. Authored Content (HTML): Authors can set the language for individual phrases within content. |
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. |
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web documents. |
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not process legal commitments or financial transactions or modify user-controllable data. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Notes:
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
302.1 Without Vision |
Software: Does Not Support Authored Content (HTML): Supports |
Software: Most functions of the product are not functional for users without vision primarily due to insufficient element roles, descriptive labels, state information, and keyboard behaviors. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.2 With Limited Vision |
Software: Does Not Support Authored Content (HTML): Supports |
Software: For users with limited vision, some core functions of the product are not functional. Dreamweaver will consistently stop responding when ZoomText 11 users open the “Preferences” dialog from the Edit menu or when other dialog windows are encountered. This behavior could not be reproduced while using other screen magnification software solutions, including MAGic 13.1 and Windows Magnifier. As previously stated in 1.4.3 Contrast (Minimum), some text elements do not provide sufficient contrast. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.3 Without Perception of Color |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most functions of the product are functional without perception of color. As previously stated in 1.4.1 Use of Color, some elements use color alone as the sole means of indicating selected state and check box controls use color alone for the visible indication of focus. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.4 Without Hearing |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not require hearing for use. Pre-recorded video content provides captioning. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.5 With Limited Hearing |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not require hearing for use. Pre-recorded video content provides captioning and independent volume control slider. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.6 Without Speech |
Software: Supports Authored Content (HTML): Supports |
Software: Product features do not require speech input. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.7 With Limited Manipulation |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: While the product will frequently require users to simultaneously press modifier keys to execute commands from the keyboard, platform features, such as Sticky Keys, are supported. As previously stated in 2.1.1 Keyboard, some controls cannot receive focus from or be interacted with the keyboard. As previously stated in 2.4.7 Focus Visible, some elements can receive focus, but do not provide a clearly visible indication of focus for sighted keyboard only users. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.8 With Limited Reach and Strength |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most controls in the product interface provide keyboard access; however, as previous stated in 2.1.1 Keyboard, some interactive elements cannot receive focus from or be interacted with the keyboard. As previously stated in 2.4.7 Focus Visible, some elements can receive focus, but do not provide a clearly visible indication of focus for sighted keyboard-only users. Authored Content (HTML): Authors can ensure that content meets this criterion. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Supports Authored Content (HTML): Supports |
Software: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product offers simplified views and window layouts, allowing users to hide or minimize unused windows. The product offers templates and allows users to insert “code snippets” and complex widgets into web pages. Consistent language is used throughout the application, clear titles are used on dialog windows, and error message alerts explain what caused the alert. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Notes: Not Applicable
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.0 section. |
See information in the WCAG section |
502.1 General. Software shall interoperate with assistive technology and shall conform to 502.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
502.2 Documented Accessibility Features |
See 502.2.1-502.2.2 |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
The product is not platform software. |
502.2.2 No Disruption of Accessibility Features |
Supports with Exceptions |
The product does not disrupt most platform accessibility features; however, the high contrast desktop theme features offered by Windows do not perform sufficiently on the product. Many of the icons used for image buttons are not visible when a Windows High Contrast theme is applied, including the buttons on the vertical left-hand navigation bar, the toolbar icons shown below the menu bar, the linked CSS and JavaScript file tabs, and the minimize, maximize, and close controls. The product does not disrupt equivalent features provided on the macOS platform, including Zoom, Invert Color, and Enhanced Contrast. |
502.3 Accessibility Services |
See 502.3.1-502.3.14 |
|
502.3.1 Object Information |
Does Not Support |
Most core functions of the product contain functional components which lack role, state, or accessible name information. Most interactive elements on the “Work” tab of the Welcome screen are not sufficiently described. Controls do not provide programmatic roles or states, and image buttons do not provide descriptive labels. The Categories list found in the “Preferences” dialog is incorrectly described as a “tree view”, without announcing the selected value in the list. As previously stated in 1.3.1 Info and Relationships, on the Highlighting category of the “Preferences” dialog, the edit input fields and check box controls do not provide programmatic labels. |
502.3.2 Modification of Object Information |
Supports with Exceptions |
In most cases, these states and properties can be modified by assistive technology. Exceptions include the toggle buttons displayed on the left-hand navigation bar which cannot be modified by the keyboard. The check box controls displayed in the Extract Category of the “Preferences” dialog cannot be modified without a pointing device. |
502.3.3 Row, Column, and Headers |
Does Not Support |
In a few cases, the product displays elements arranged visually in rows and columns which cannot be programmatically determined by assistive technologies. As previously stated in 1.3.1 Info and Relationships, the “Recents” table on the “Work” tab of the Welcome screen and the “Extract” category of the “Preferences” dialog window do not provide programmatically determinable rows, columns, or column headers. |
502.3.4 Values |
Supports with Exceptions |
The values of most input controls in the product are programmatically determinable; however, some values are not. The Categories list provided on the “Preferences” dialog does not provide the currently selected programmatically. Similar issues with these list views may be observed on the File Types category and the Linting category. |
502.3.5 Modification of Values |
Supports |
When the value of an input control in the product can be modified by users in general, the value can be modified by assistive technology. |
502.3.6 Label Relationships |
Supports with Exceptions |
Most form fields in the product provide an associated programmatic label; however, as previously stated in 1.3.1 Info and Relationships, input fields and checkbox controls are not associated to the visible labels to the left of the fields. Screen reader software does not provide a meaningful or informative label for these input fields. |
502.3.7 Hierarchical Relationships |
Supports with Exceptions |
Some tree view controls, such as those used for browsing the file system and browsing the DOM in the right-hand side panels, provide sufficient text alternatives for the elements in the tree view. However, as previously stated in 1.3.1 Info and Relationships, the hierarchal relationships shown visually in the HTML on the code view do not effectively communicate the same hierarchy in a non-visual manner. |
502.3.8 Text |
Does Not Support |
The text displayed in the code view of this product cannot be programmatically determined by assistive technologies. Screen reader software does not provide accurate audio feedback or does not provide any audio feedback while traversing the text. |
502.3.9 Modification of Text |
Supports |
The text content of text input controls in the product can be modified by assistive technology. |
502.3.10 List of Actions |
Supports with Exceptions |
Most actionable controls provide a common role, such as “button”, which informs the user what actions are available. As previously stated in 502.3.1 Object Information, some actionable controls do not provide a programmatic role nor a list of actions. |
502.3.11 Actions on Objects |
Supports with Exceptions |
Most actionable controls can be activated by assistive technology; however, some controls either lack programmatic roles or are not exposed to assistive technologies altogether cannot be activated by alternative input methods. |
502.3.12 Focus Cursor |
Supports with Exceptions |
Some controls in the product can gain focus, but do not indicate the focus location visually. As previously stated in 2.4.7 Focus Visible, focus is not highly visible on the menu bar and submenu items. On the “Work” tab of the Welcome screen, the Search image button and user profile image icon also do not provide any visible indication of focus. The Code View does not provide a clearly visible indication of the text insertion cursor while the opening and closing HTML tags are highlighted. |
502.3.13 Modification of Focus Cursor |
Supports |
When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically. Non-standard keyboard commands are provided for moving focus between the displayed windows, including the opened documents tabs and right-hand side panels. |
502.3.14 Event Notification |
Supports with Exceptions |
In most cases, when components in the product change their programmatic states and values the changes are available to assistive technology; however, toggle button controls and options on the Welcome screen show a visible selected state that is not available to assistive technologies. Similarly, changes in available controls on a dialog are not available to assistive technology, including the list box elements on the “Create New” dialog and the “Preferences” dialog. |
502.4 Platform Accessibility Features |
Not Applicable |
The product is not platform software. |
503.1 General. Applications shall conform to 503.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
503.2 User Preferences |
Supports with Exceptions |
The product permits most platform user preferences; however, the high contrast desktop theme features offered by Windows do not perform sufficiently on the product. Many of the icons used for image buttons are not visible when a Windows High Contrast theme is applied, including the buttons on the vertical left-hand navigation bar, the toolbar icons shown below the menu bar, the linked CSS and JavaScript file tabs, and the minimize, maximize, and close controls. The product permits the equivalent user preferences provided on the macOS platform. |
503.3 Alternative User Interfaces |
Not Applicable |
The product does not function as an assistive technology. |
503.4 User Controls for Captions and Audio Description |
See 503.4.1-503.4.2 |
|
503.4.1 Caption Controls |
Supports |
The Quick Tutorial videos found in the Help Menu provide closed captioning controls at the same level as the volume and other playback controls. |
503.4.2 Audio Description Controls |
Not Applicable |
Program Selection is not provided for the Quick Tutorial videos found in the Help Menu. |
504.1 General. Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section. |
See information in WCAG section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Supports |
Authors can ensure the information required for accessibility is preserved to the extent the information is supported by the destination format while converting content from one format to another. |
504.2.2 PDF Export |
Not Applicable |
The product does not include functionality for exporting PDF files. |
504.3 Prompts |
Does Not Support |
The product provides functionality for authors to run reports on sites to help identify missing alt attributes and untitled documents; however, this functionality is not comprehensive enough to assist authors in meeting the WCAG 2.0 guidelines. The product provides tag editor windows for authors to add attributes necessary for accessibility. When an image is inserted and the tag editor is displayed, no indication is made to inform authors that it is necessary to provide a valid alt attribute to ensure accessibility. |
504.4 Templates |
Supports with Exceptions |
The product provides templates to assist authors in the creation of content. Authors can ensure the WCAG 2.0 level A and AA requirements are satisfied. Templates make use of ARIA landmarks and structural heading markup. However, the templates provided by the product fall short of the WCAG 2.0 level A and AA requirements. Some templates do not set a default language for the document, do not provide valid labels for Search input edit fields, and lack explicit column headers for data tables. |
Notes: Conformance information for Support Documentation and Services is available in the Adobe Accessibility Conformance Report for HelpX documentation.
Notes:
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
4.2.1 Usage without vision |
Software: Does Not Support Authored Content (HTML): Supports |
Software: Most functions of the product are not accessible for users without vision, primarily due to insufficient element roles, descriptive labels, state information, and keyboard behaviors. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.2 Usage with limited vision |
Software: Does Not Support Authored Content (HTML): Supports |
Software: For users with limited vision, some core functions of the product are not accessible. For example, Dreamweaver will consistently stop responding when ZoomText 11 users open the “Preferences” dialog from the Edit menu or when other dialog windows are encountered. This behavior could not be reproduced while using other screen magnification software solutions, including MAGic 13.1 and Windows Magnifier. As previously stated in 1.4.3 Contrast (Minimum), some text elements do not provide sufficient contrast. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.3 Usage without perception of colour |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: Most functions of the product are functional without perception of color. As previously stated in 1.4.1 Use of Color, some elements use color alone as the sole means of indicating selected state and check box controls use color alone for the visible indication of focus. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.4 Usage without hearing |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not require hearing for use. Pre-recorded video content provides captioning. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.5 Usage with limited hearing |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not require hearing for use. Pre-recorded video content provides captioning and independent volume control slider. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.6 Usage without vocal capability |
Software: Supports Authored Content (HTML): Supports |
Software: Product features do not require speech input. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.7 Usage with limited manipulation or strength |
Software: Supports with Exceptions Authored Content (HTML): Supports |
Software: While the product will frequently require users to simultaneously press modifier keys to execute commands from the keyboard, platform features, such as Sticky Keys, are supported. As previously stated in 2.1.1 Keyboard, some controls cannot receive focus from or be interacted with the keyboard. As previously stated in 2.4.7 Focus Visible, some elements can receive focus, but do not provide a clearly visible indication of focus for sighted keyboard-only users. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.8 Usage with limited reach |
Software: Supports Authored Content (HTML): Supports |
Software: The product is functional with limited reach. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.9 Minimize photosensitive seizure |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.10 Usage with limited cognition |
Software: Supports Authored Content (HTML): Supports |
Software: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product offers simplified views and window layouts, allowing users to hide or minimize unused windows. The product offers templates and allows users to insert “code snippets” and complex widgets into web pages. Consistent language is used throughout the application, clear titles are used on dialog windows, and error message alerts explain what caused the alert. Authored Content (HTML): Authors can ensure that content meets this criterion. |
4.2.11 Privacy |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not process legal commitments or financial transactions or modify user-controllable data. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
5.1 Closed Functionality |
Not Applicable |
5.1.2.2-5.1.6.2 are not applicable for this product. |
5.2 Activation of accessibility features |
Does Not Support |
The documented accessibility features for optimization with screen reader software require users to navigate to the “Preferences” dialog where the Category list view does not provide role, states, or notification of changes to assistive technologies. The creation, deletion, and modification of custom keyboard commands requires the use of a pointing device. |
5.3 Biometrics |
Not Applicable |
The product does not rely on biological characteristics. |
5.4 Preservation of accessibility information during conversion |
Supports |
Authors can ensure the information required for accessibility is preserved to the extent the information is supported by the destination format while converting content from one format to another. |
5.5.1 Means of operation |
Not Applicable |
The product does not contain operable parts. |
5.5.2 Operable parts discernibility |
Not Applicable |
The product does not contain operable parts. |
5.6.1 Tactile or auditory status |
Not Applicable |
The product does not contain locking or toggle controls. |
5.6.2 Visual status |
Not Applicable |
The product does not contain locking or toggle controls. |
5.7 Key repeat |
Not Applicable |
The product relies on platform software to supply key repeat functionality. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not supply a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
The product relies on platform software features, such as Sticky Keys, to ensure simultaneous user actions are not required. |
Notes: Not Applicable
Notes: Not Applicable
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
7.1.1 Captioning playback |
Supports |
As previously stated in 1.2.2 Captions (Prerecorded), the Quick Tutorial videos found in the Help Menu provide captioning. |
7.1.2 Captioning synchronization |
Supports |
As previously stated in 1.2.2 Captions (Prerecorded), the captions provided for the Quick Tutorial videos found in the Help Menu are synchronized. |
7.1.3 Preservation of captioning |
Not Applicable |
The product does not transmit, convert, or record video content. |
7.2.1 Audio description playback |
Does Not Support |
As previously stated in 1.2.3 Audio Description or Media Alternative (Prerecorded), the product does not provide a mechanism to select and play audio description embedded in the Quick Tutorial videos found in the Help Menu. |
7.2.2 Audio description synchronization |
Not Applicable |
The product does not provide audio descriptions, the synchronization requirement is not applicable. |
7.2.3 Preservation of audio description |
Not Applicable |
The product does not transmit, convert, or record video content. |
7.3 User controls for captions and audio description |
Supports with Exceptions |
As previously stated in 503.4.1 Caption Controls, controls are provided for users to display synchronized captioning for the Quick Tutorial videos found in the Help menu. However, program selection controls for audio description are not provided. |
Notes: See WCAG 2.0 section.
Notes: Not Applicable
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.0 section. |
See information in WCAG section |
11.2.2 Software success criteria (closed functionality) |
Not Applicable |
|
11.3.2.3 Use of accessibility services |
Supports |
The product uses documented accessibility services within the user interface. |
11.3.2.4 Assistive technology |
Not Applicable |
The product is not assistive technology. |
11.3.2.5 Object information |
Does Not Support |
Most core functions of the product contain functional components which lack role, state, or accessible name information. Most interactive elements on the “Work” tab of the Welcome screen are not sufficiently described. Controls do not provide programmatic roles or states, and image buttons do not provide descriptive labels. The Categories list found in the “Preferences” dialog is incorrectly described as a “tree view”, without announcing the selected value in the list. As previously stated in 1.3.1 Info and Relationships, on the “Highlighting” category of the “Preferences” dialog, the edit input fields and check box controls do not provide programmatic labels. |
11.3.2.6 Row, column, and headers |
Does Not Support |
In a few cases, the product displays elements arranged visually in rows and columns which cannot be programmatically determined by assistive technologies. As previously stated in 1.3.1 Info and Relationships, the “Recents” table on the “Work” tab of the Welcome screen, and the “Extract” category of the Preferences dialog window do not provide programmatically determinable rows, columns, or column headers. |
11.3.2.7 Values |
Supports with Exceptions |
The values of most input controls in the product are programmatically determinable; however, some values are not. The Categories list provided on the “Preferences” dialog does not provide the currently selected programmatically. Similar issues with these list views may be observed on the File Types category and the Linting category. |
11.3.2.8 Label relationships |
Supports with Exceptions |
Most form fields in the product provide an associated programmatic label; however, as previously stated in 1.3.1 Info and Relationships, input fields and checkbox controls are not associated to the visible labels to the left of the fields. Screen reader software does not provide a meaningful or informative label for these input fields. |
11.3.2.9 Parent-child relationships |
Supports with Exceptions |
Some tree view controls, such as those used for browsing the file system and browsing the DOM in the right-hand side panels, provide sufficient text alternatives for the elements in the tree view. However, as previously stated in 1.3.1 Info and Relationships, the parent child relationships shown visually in the HTML on the code view do not effectively communicate the same relationships in a non-visual manner. |
11.3.2.10 Text |
Does Not Support |
The text displayed in the code view of this product cannot be programmatically determined by assistive technologies. Screen reader software does not provide accurate audio feedback or does not provide any audible feedback at all while traversing the text. |
11.3.2.11 List of available actions |
Supports with Exceptions |
Most actionable controls provide a common role, such as “button”, which informs the user what actions are available. As previously stated in 502.3.1 Object Information, some actionable controls do not provide a programmatic role nor a list of actions. |
11.3.2.12 Execution of available actions |
Supports with Exceptions |
Most actionable controls can be activated by assistive technology; however, some controls that either lack programmatic roles or are not exposed to assistive technologies altogether cannot be activated by alternative input methods. |
11.3.2.13 Tracking of focus and selection attributes |
Supports with Exceptions |
Some controls in the product can gain focus, but do not indicate the focus location visually. As previously stated in 2.4.7 Focus Visible, focus is not highly visible on the menu bar and submenu items. On the “Work” tab of the Welcome screen, the Search image button and user profile image icon also do not provide any visible indication of focus. The Code View does not provide a clearly visible indication of the text insertion cursor while the opening and closing HTML tags are highlighted. |
11.3.2.14 Modification of focus and selection attributes |
Supports |
When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically. Non-standard keyboard commands are provided for moving focus between the displayed windows including the opened documents tabs and right-hand side panels. |
11.3.2.15 Change notification |
Supports with Exceptions |
In most cases, when components in the product change their programmatic states and values the changes are available to assistive technology; however, toggle button controls and options on the Welcome screen show a visible selected state that is not available to assistive technologies. Similarly, changes in available controls on a dialog are not available to assistive technology, including the list box elements on the “Create New” dialog and the “Preferences” dialog. |
11.3.2.16 Modifications of states and properties |
Supports with Exceptions |
In most cases, these states and properties can be modified by assistive technology. Exceptions include the toggle buttons displayed on the left-hand navigation bar that cannot be modified by the keyboard. The check box controls displayed in the Extract Category of the “Preferences” dialog cannot be modified without a pointing device. |
11.3.2.17 Modifications of values and text |
Supports |
When the value or text of an input control in the product can be modified by users in general, the value can be modified by assistive technology. |
11.4.1 User control of accessibility features |
Not Applicable |
The product is not platform software. |
11.4.2 No disruption of accessibility features |
Supports with Exceptions |
The product does not disrupt most platform accessibility features; however, the high contrast desktop theme features offered by Windows do not perform sufficiently on the product. Many of the icons used for image buttons are not visible when a Windows High Contrast theme is applied including the buttons on the vertical left-hand navigation bar, the toolbar icons shown below the menu bar, the linked CSS and JavaScript file tabs, and the minimize, maximize, and close controls. The product does not disrupt equivalent features provided on the macOS platform including Zoom, Invert Color, and Enhanced Contrast. |
11.5 User preferences |
Supports with Exceptions |
The product permits most platform user preferences; however, the high contrast desktop theme features offered by Windows do not perform sufficiently on the product. Many of the icons used for image buttons are not visible when a Windows High Contrast theme is applied, including the buttons on the vertical left-hand navigation bar, the toolbar icons shown below the menu bar, the linked CSS and JavaScript file tabs, and the minimize, maximize, and close controls. The product permits the equivalent user preferences provided on the macOS platform. |
11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section. |
See information in WCAG section |
11.6.3 Preservation of accessibility information in transformations |
Supports |
Authors can ensure the information required for accessibility is preserved to the extent the information is supported by the destination format while converting content from one format to another. |
11.6.4 Repair assistance |
Does Not Support |
The product provides functionality for authors to run reports on sites to help identify missing alt attributes and untitled documents; however, this functionality is not comprehensive enough to assist authors in meeting the WCAG 2.0 guidelines. The product provides tag editor windows for authors to add attributes necessary for accessibility. When an image is inserted and the tag editor is displayed, no indication is made to inform authors that it is necessary to provide a valid alt attribute to ensure accessibility. |
11.6.5 Templates |
Supports with Exceptions |
The product provides templates to assist authors in the creation of content. Authors can ensure the WCAG 2.0 level A and AA requirements are satisfied. Templates make use of ARIA landmarks and structural heading markup. However, the templates provided by the product fall short of the WCAG 2.0 level A and AA requirements. Some templates do not set a default language for the document, do not provide valid labels for Search input edit fields, and lack explicit column headers for data tables. |
Notes: Conformance information for Documentation and Support Services is available in the Adobe Accessibility Conformance Report for HelpX documentation.
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)