Adobe Accessibility Conformance Report
VPAT® Version 2.0 – November 2017
Product Information
Name of Product/Version: Adobe XD CC
Product Description: Adobe XD CC is a UX/UI solution for designing websites, mobile apps, and more.
Date: November 2017
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 XD 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.
Applicable Standards/Guidelines
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 |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Supports with Exceptions: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.0 Report
Sections 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Chapter 10 - Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 - Non-Web Software (closed functionality).
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
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.
Section 1: Success Criteria, Level A
Notes:
Guideline 1.1 Text Alternatives:
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: Supports with Exceptions Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: Text alternatives are provided for many instances of non-text content, with the following exceptions:
Authored Content (HTML): Most images, including image buttons within the content wrapper and images exported from the product, do not contain textual alternatives. Authored Content (PDF): Images exported from the product do not contain textual alternatives. |
Guideline 1.2 Time-based Media:
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 Authored Content (PDF): Supports |
Software: The product does not provide prerecorded audio-only or video-only content. Authored Content (HTML): Authored Content does not contain prerecorded audio-only or video-only content. Authored Content (PDF): Authored Content does not contain prerecorded audio-only or video-only content. |
1.2.2 Captions (Prerecorded) (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not provide prerecorded media that requires captions. Authored Content (HTML): Exported content does not contain prerecorded media that requires captions. Authored Content (PDF): Exported content does not contain prerecorded media that requires captions. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not provide prerecorded media that requires audio description. Authored Content (HTML): Authored Content does not contain prerecorded media that requires audio description. Authored Content (PDF): Authored Content does not contain prerecorded media that requires audio description. |
Guideline 1.3 Adaptable:
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: Does Not Support Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: Some form field controls are not accurately grouped, nor are other relationships, such as parent-child settings, accurately conveyed to users. Any relationship between settings and content within the main design pane is not able to be perceived or interacted with by users of assistive technologies. Authored Content (HTML): The content wrapper for authored HTML content conveys information about structure and relationships programmatically; however, artboard content is exported as an image. Interactive hotspots designed in the product are overlaid visually on top of the artboard image but are not programmatically connected to content. |
1.3.2 Meaningful Sequence (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports with Exceptions Authored Content (PDF): Does Not Support |
Software: The product presents content in a meaningful sequence. Authored Content (HTML): The content wrapper for authored HTML content presents a meaningful sequence for users; however, active content areas generated by authors will not be placed within a meaningful sequence. Authored Content (PDF): Active content areas will not be placed within a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Most content within the application’s settings and dialogs does not rely on spatial characteristics. However, tutorial information describing how to use the product consistently uses visual location, such as the “Left” and “Right” panel, to call out to users where they can find tools. Authored Content (HTML): Instructions for understanding and operating content within the content wrapper do not rely solely on sensory characteristics. Authored Content (PDF): Authors can ensure that content meets this criterion.
|
Guideline 1.4 Distinguishable:
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 Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: The user interface does not use color as the only means of conveying information. Authored Content (HTML): Authored content is contained exclusively within images. Any interactive content, such as a visually displayed button, is conveyed solely through the use of color. Authored Content (PDF): Authored content is contained exclusively within images. Any interactive content, such as a visually displayed button, is conveyed solely through the use of color. |
1.4.2 Audio Control (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not include audio that plays automatically. Authored Content (HTML): Authored Content does not contain audio that plays automatically. Authored Content (PDF): Authored Content does not contain audio that plays automatically.
|
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.1.1 Keyboard (Level A)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: The product does not support the operation of critical functionality through a keyboard interface, including:
Authored Content (HTML): Most content within the content wrapper is actionable from the keyboard; however, active content areas generated by authors are not within the focus order. Authored Content (PDF): Active content areas generated by authors are not within the focus order. |
2.1.2 No Keyboard Trap (Level A)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Most controls allow users to move to separate controls within the control’s respective panel. However, as noted in 2.1.1 Keyboard, there is no method to switch panels. Once focus has been placed on the main content area, there is no method to remove or adjust focus within the application. Authored Content (HTML): Authored content does not include keyboard traps. Authored Content (PDF): Authored content does not include keyboard traps.
|
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.2.1 Timing Adjustable (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not include time limits. Authored Content (HTML): The content wrapper and Authored content do not include time limits. Authored Content (PDF): Authored content does not include time limits. |
2.2.2 Pause, Stop, Hide (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not include elements which automatically move, blink, scroll, or auto-update. Some content can be manually set to provide animations between views, but will settle within 1 second, and only activate after being triggered by a user. Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion.
|
Guideline 2.3 Seizures:
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)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion.
|
Guideline 2.4 Navigable:
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)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): No repeated blocks of content are present within the content. Authored Content (PDF): This criterion does not apply to non-web documents. |
2.4.2 Page Titled (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Does Not Support |
Software: Windows contain visual and programmatic titles, and most panels contain a visual label describing their purpose. |
2.4.3 Focus Order (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Components receive focus in a meaningful order. Authored Content (HTML): Components receive focus in a meaningful order. Authored Content (PDF): Authored Content does not have focusable elements. |
2.4.4 Link Purpose (In Context) (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports with Exceptions Authored Content (PDF): Does Not Support |
Software: Links contain informative text that, when combined with the context surrounding a link, allows users to determine the purpose of an item. Authored Content (HTML): Exceptions include:
|
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.1.1 Language of Page (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The language is programmatically determinable within the product. All software provided content is in one primary language. Authored Content (HTML): The language is programmatically determinable within the product. Authored Content (PDF): The language is programmatically determinable within the product. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.2.1 On Focus (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
|
3.2.2 On Input (Level A)
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Exceptions include:
|
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.3.1 Error Identification (Level A)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: When a user inputs an invalid piece of data, no alert is provided to users. The product simply rejects the input when a user moves the focus away from the field. Authored Content (HTML): Authored Content does not detect input errors that will be displayed to users. Authored Content (PDF): Authored Content does not detect input errors that will be displayed to users. |
3.3.2 Labels or Instructions (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Labels are provided for input fields. Authored Content (PDF): Authored content does not require user input. |
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
4.1.1 Parsing (Level A)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The software is not implemented using markup languages. Authored Content (PDF): The authored content is not implemented using markup languages. |
4.1.2 Name, Role, Value (Level A)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: The majority of interactive elements contain appropriate role information, and additionally, some controls contain appropriate programmatic names. The alignment buttons, hide and lock buttons for displaying content, as well as all focusable content within the main design area do not contain programmatic names. |
Section 2: Success Criteria, Level AA
Notes:
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
1.2.4 Captions (Live) (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not provide live media that requires captions. Authored Content (HTML): The product does not provide live media that requires captions. Authored Content (PDF): The product does not provide live media that requires captions. |
1.2.5 Audio Description (Prerecorded) (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not provide prerecorded video content that requires audio description. Authored Content (HTML): The product does not export prerecorded video content that requires audio description. Authored Content (PDF): The product does not export prerecorded video content that requires audio description.
|
Guideline 1.4 Distinguishable:
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)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: In many instances text does not meet minimum contrast requirements, including:
Authored Content (HTML): Authors can ensure that content meets this criterion. Authored Content (PDF): Authors can ensure that content meets this criterion. |
1.4.4 Resize Text (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
|
1.4.5 Images of Text (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: The product uses text instead of images of text. Authored Content (HTML): The content wrapper includes no images of text; however, authored content, including text, is exported in an image format. Authored Content (PDF): Authored content, including text, is exported in an image format. |
Guideline 2.4 Navigable:
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)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): Authors can design content to ensure that all artboards can be accessed multiple ways. Authored Content (PDF): This criterion does not apply to non-web documents. |
2.4.6 Headings and Labels (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: When present, labels and headings are descriptive of the purpose of sections or form fields. Authored Content (HTML): A heading element will be automatically generated within the content wrapper based on the title of the source document. Authored Content (PDF): Authored content contains no programmatic headings or labels. |
2.4.7 Focus Visible (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The keyboard focus indicator is visible by default. Authored Content (HTML): Authored content that receives focus has focus visually displayed. Authored Content (PDF): Authored content does not contain focusable elements.
|
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.1.2 Language of Parts (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: Content is only presented in one language at a time. Authored Content (HTML): No method exists to identify languages outside the document’s default. Authored Content (PDF): No method exists to identify languages outside the document’s default.
|
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.2.3 Consistent Navigation (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): Navigational elements will be automatically generated and will appear in the same relative order each time they are repeated. Authored Content (PDF): This criterion does not apply to non-web documents. |
3.2.4 Consistent Identification (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web documents. Authored Content (HTML): Components within authored content will be automatically generated and will be consistently identified by the software. Authored Content (PDF): This criterion does not apply to non-web documents. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
3.3.3 Error Suggestion (Level AA)
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not process legal commitments or financial transactions. Changes to user-controllable data can be reversed. Authored Content (HTML): Authored content does not contain legal or financial data and does not have user-controllable data. Authored Content (PDF): Authored content does not contain legal or financial data and does not have user-controllable data. |
2017 Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
302.1 Without Vision |
Software: Does Not Support Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: The product provides users without vision some accessible names and some keyboard supported elements. However, a number of issues will prevent users without vision from fully using the product, like the inability to switch keyboard focus between panes Authored Content (HTML): The content wrapper for HTML authored content will provide users without vision some controls to interact with; however, as noted in 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value, core functionality is missing from authored content. Authored Content (PDF): Authored content contains images exclusively, and PDF content is not tagged. Both of these will prevent users without vision from fully using authored content. Authored content does not provide assistive technologies typically used by users without vision information on what content is interactive within a document. Additionally, all of the content is flattened into a single exposed image, preventing users from accessing the content, overall. |
302.2 With Limited Vision |
Software: Does Not Support Authored Content (HTML): Supports with Exceptions Authored Content (PDF): Does Not Support |
Software: Users with limited vision can use some of the product’s features. However, a number of potential issues will be encountered, including:
Authored Content (HTML): Users with limited vision will be able to use most features of authored content but may face some difficulties. The content wrapper contains a visual indication of focus; however, as noted in 2.1.1 Keyboard, not all interactive content receives keyboard focus. Authors can design content to ensure that sufficient color contrast is met for test. Within the content wrapper, no images of text are used, but any text on artboards will become converted to an image of text within authored content. Authored Content (PDF): Authored content will pose challenges for users with limited vision to use. While authors can design content to meet color contrast requirements, all text is presented as an image of text. |
302.3 Without Perception of Color |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Color is never used as a sole means of indicating information within the product. Some generated content contains or uses colors that a visually impaired user cannot perceive, but hex values and other non-color means will identify these if a user opens the relevant panes. Authored Content (HTML): Users without the perception of color will be able to interact with the content wrapper. Authored content appears as an image, but authors can create content that does not rely on color perception. Authored Content (PDF): Authors can create content that does not rely on color perception. |
302.4 Without Hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not output audio to users, and thus does not require user hearing to operate. Authored Content (HTML): Authored content does not output audio to users, and thus does not require user hearing to operate. Authored Content (PDF): Authored content does not output audio to users, and thus does not require user hearing to operate. |
302.5 With Limited Hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not output audio to users, and thus will be operable by users with limited hearing. Authored Content (HTML): Authored content does not output audio to users, and thus will be operable by users with limited hearing. Authored Content (PDF): Authored content does not output audio to users, and thus will be operable by users with limited hearing. |
302.6 Without Speech |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not require speech for input, control or operation. Authored Content (HTML): Authored content does not require speech for input, control or operation. Authored Content (PDF): Authored content does not require speech for input, control or operation. |
302.7 With Limited Manipulation |
Software: Does Not Support Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: Users with limited manipulation using the keyboard exclusively to interact with the product will encounter difficulties. Users of speech recognition software will encounter less issues, but may face problems calling controls by name. Authored Content (HTML): Users with limited manipulation that use either the keyboard exclusively or speech recognition software to interact with authored content will encounter difficulties due to a lack of programmatically defined information within authored content. Authored Content (PDF): Users with limited manipulation that use either the keyboard exclusively or speech recognition software to interact with authored content will encounter difficulties due to a lack of programmatically defined information within authored content. |
302.8 With Limited Reach and Strength |
Software: Supports with Exceptions Authored Content (HTML): Supports with Exceptions Authored Content (PDF): Supports with Exceptions |
Software: Users with limited reach using a mouse or pointer device will be able to access all content. However, as noted within sections on limited manipulation, users of the keyboard or speech recognition software may find issues interacting with content. Strength is not required to interact directly with the product. Authored Content (HTML): Users with limited reach using a mouse or pointer device will be able to access all content. However, as noted within sections on limited manipulation, users of the keyboard or speech recognition software may find issues interacting with content. Strength is not required to interact directly with authored content. Authored Content (PDF): Users with limited reach using a mouse or pointer device will be able to access all content. However, as noted within sections on limited manipulation, users of the keyboard or speech recognition software may find issues interacting with content. Strength is not required to interact directly with authored content. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: A number of features are incorporated to ensure that a mode is usable by individuals with limited language, cognitive and learning abilities. Icons used to describe most controls are provided with tooltips to ensure that users who would prefer reading words, rather than seeing icons, are aware what an icon’s function is. Similarly, content is designed to be as predictable to as possible. Navigation is laid out in a consistent manner, and wherever possible, components for similar functions are reused. Authored Content (HTML): Authors can design authored content in such a way that it will be usable by individuals with limited language, cognitive, and learning abilities. The content wrapper contains icons as well as tooltip text for most controls, which will assist users with limited language abilities. Authored Content (PDF): Authors can design authored content in such a way that it will be usable by individuals with limited language, cognitive, and learning abilities.. |
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes:
501 General
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 Interoperability with Assistive Technology
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 majority of the platform’s accessibility features are not disrupted by the product. However, with the exception of the initial new project screen, the software does not support Windows High Contrast Mode. |
502.3 Accessibility Services |
See 502.3.1-502.3.14 |
|
502.3.1 Object Information |
Does Not Support |
As noted in 4.1.2 Name, Role, Value, many controls do not supply appropriate roles or names to assistive technologies. |
502.3.2 Modification of Object Information |
Supports |
States for controls, such as radio buttons and checkboxes, are capable of being programmatically set by users, including those using assistive technologies. |
502.3.3 Row, Column, and Headers |
Not Applicable |
The product does not use table structures. |
502.3.4 Values |
Supports with Exceptions |
The values for all input elements can be programmatically set and are determinable. A rating of Supports with Exceptions has been given for the following reason: When only a specific range of values is allowed for text input, such as a hex color code, there is no programmatic indication of what range will be accepted. |
502.3.5 Modification of Values |
Supports |
Values of all controls can be programmatically set by users, including those using assistive technologies. |
502.3.6 Label Relationships |
Does Not Support |
Label relationships are not exposed to assistive technologies, as noted in 4.1.2 Name, Role, Value. |
502.3.7 Hierarchical Relationships |
Does Not Support |
As noted in 1.3.1 Info and Relationships, hierarchical relationships between components are not programmatically determinable. |
502.3.8 Text |
Supports |
The product UI exposes text content to assistive technologies. |
502.3.9 Modification of Text |
Supports |
The product UI allows assistive technologies to modify text content. |
502.3.10 List of Actions |
Supports with Exceptions |
The product provides a list of available actions for all controls containing appropriate programmatic roles. However, one notable exception exists within the main menu structure. No distinction is made between menu items that contain and spawn submenus, and those that activate a specific menu option. |
502.3.11 Actions on Objects |
Supports |
The product allows assistive technologies to perform actions on objects. |
502.3.12 Focus Cursor |
Supports |
When the focus cursor is placed on objects, focus is exposed both programmatically as well as visually to users. This is also true of text insertion point. |
502.3.13 Modification of Focus Cursor |
Supports with Exceptions |
The product will prevent users, both those with and without assistive technologies, from moving focus between panes in the software. |
502.3.14 Event Notification |
Does Not Support |
The product does not regularly notify assistive technologies when events occur either in response to a user interaction, such as when a menu expands or collapses. |
502.4 Platform Accessibility Features |
Not Applicable |
The product is not platform software. |
503 Applications
503.1 General. Applications shall conform to 503.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
503.2 User Preferences |
Supports with Exceptions |
User platform preferences for settings, such as font size and focus cursor, are supported. However, the software does not support preferences for color and themes. |
503.3 Alternative User Interfaces |
Not Applicable |
The product does not provide an alternative interface for users. |
503.4 User Controls for Captions and Audio Description |
See 503.4.1-503.4.2 |
|
503.4.1 Caption Controls |
Not Applicable |
The product does not contain content that provides for audio adjustment. |
503.4.2 Audio Description Controls |
Not Applicable |
The product does not display content that allows for program selection. |
504 Authoring Tools
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 the WCAG section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable |
The product does not convert files from one format to another. |
504.2.2 PDF Export |
Not Applicable |
The product allows users to export PDF content, but exports content to PDF 1.4, rather than 1.7. |
504.3 Prompts |
Does Not Support |
The product does not contain a mode to help prompt users to generate accessible versions of authored content. |
504.4 Templates |
Does Not Support |
The product provides templates to help users generate content for specific devices, but these do not allow content creation that conforms to WCAG A and AA. |
Chapter 6: Support Documentation and Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 4: 4.2 Functional Performance Statements (FPS)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
4.2.1 Usage without vision |
Software: Does Not Support Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: The product provides users without vision some accessible names and some keyboard supported elements. However, a number of issues will prevernt users without vision from fully using the profuct, like the inability to switch keyboard focus between planes. Authored Content (HTML): The content wrapper for HTML authored content will provide users without vision some controls to interact with; however, as noted in 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value, core functionality is missing from authored content. Authored Content (PDF): Authored content contains images exclusively, and PDF content is not tagged. Both of these will prevent users without vision from fully using authored content. Authored content does not provide assistive technologies typically used by users without vision information on what content is interactive within a document. Additionally, all of the content is flattened into a single exposed image, preventing users from accessing the content, overall. |
4.2.2 Usage with limited vision |
Software: Does Not Support Authored Content (HTML): Supports with Exceptions Authored Content (PDF): Does Not Support |
Software: Users with limited vision can use some of the product’s features. However, a number of potential issues will be encountered, including:
Authored Content (HTML): Users with limited vision will be able to use most features of authored content but may face some difficulties. The content wrapper contains a visual indication of focus; however, as noted in 2.1.1 Keyboard, not all interactive content receives keyboard focus. Authors can design content to ensure that sufficient color contrast is met for text. Within the content wrapper, no images of text are used, but any text on artboards will become converted to an image of text within authored content. Authored Content (PDF): Authored content will pose challenges for users with limited vision to use. While authors can design content to meet color contrast requirements, all text is presented as an image of text. |
4.2.3 Usage without perception of colour |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Color is never used as the sole means of indicating information within the product. Users without vision, or with limited perception of color, will not encounter issues within the UI of XD. Some generated content contains or uses colors that a visually impaired user cannot perceive, but hex values and other non-color means will identify these if a user opens the relevant panes. Authored Content (HTML): Users without the perception of color will be able to interact with the content wrapper. Authored content appears as an image, but authors can create content that does not rely on color perception. Authored Content (PDF): Authors can create content that does not rely on color perception. |
4.2.4 Usage without hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not output audio to users, and thus does not require user hearing to operate. Authored Content (HTML): Authored content does not output audio to users, and thus does not require user hearing to operate. Authored Content (PDF): Authored content does not output audio to users, and thus does not require user hearing to operate. |
4.2.5 Usage with limited hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not output audio to users, and thus will be operable by users with limited hearing. Authored Content (HTML): Authored content does not output audio to users, and thus will be operable by users with limited hearing. Authored Content (PDF): Authored content does not output audio to users, and thus will be operable by users with limited hearing. |
4.2.6 Usage without vocal capability |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not require vocal capability for input, control or operation. Authored Content (HTML): Authored content does not require vocal capability for input, control or operation. Authored Content (PDF): Authored content does not require vocal capability for input, control or operation. |
4.2.7 Usage with limited manipulation or strength |
Software: Does Not Support Authored Content (HTML): Does Not Support Authored Content (PDF): Does Not Support |
Software: Users with limited manipulation using the keyboard exclusively to interact with the product will encounter difficulties. Users of speech recognition software will encounter less issues, but may face problems calling controls by name. Strength is not required to interact directly with the product. Authored Content (HTML): Users with limited manipulation that use either the keyboard exclusively or speech recognition software to interact with authored content will encounter difficulties due to a lack of programmatically defined information within authored content. Strength is not required to interact directly with authored content. Authored Content (PDF): Users with limited manipulation that use either the keyboard exclusively or speech recognition software to interact with authored content will encounter difficulties due to a lack of programmatically defined information within authored content. Strength is not required to interact directly with authored content. |
4.2.8 Usage with limited reach |
Software: Supports with Exceptions Authored Content (HTML): Supports with Exceptions Authored Content (PDF): Supports with Exceptions |
Software: Users with limited reach using a mouse or pointer device will be able to access all content. However, as noted in 4.2.7 Usage with limited manipulation or strength, users of the keyboard or speech recognition software may find issues interacting with content. Authored Content (HTML): Users with limited reach using a mouse or pointer device will be able to access all content. However, as noted in 4.2.7 Usage with limited manipulation or strength, users of the keyboard or speech recognition software may find issues interacting with content. Authored Content (PDF): Users with limited reach using a mouse or pointer device will be able to access all content. However, as noted in 4.2.7 Usage with limited manipulation or strength, users of the keyboard or speech recognition software may find issues interacting with content. |
4.2.9 Minimize photosensitive seizure |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product contains no content within the UI that blinks or flashes in such a way that would trigger a photosensitive seizure. Authored Content (HTML): Authors will be able to design content to ensure that no content blinks or flashes, or contains transitions that might cause a blinking or flashing like experience for users. Authored Content (PDF): Authors will be able to design content to ensure that no content blinks or flashes, or contains transitions that might cause a blinking or flashing like experience for users. |
4.2.10 Usage with limited cognition |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product incorporates a number of features to ensure that a mode is usable by individuals with limited cognition. Icons used to describe most controls are provided with tooltips to ensure that users who would prefer reading words, rather than seeing icons, are aware what an icon’s function is. Similarly, content is designed to be as predictable to as possible. Navigation is laid out in a consistent manner, and wherever possible, components for similar functions are reused. Authored Content (HTML): Authors can design authored content in such a way that it will be usable by individuals with limited language, cognitive, and learning abilities. Authored Content (PDF): Authors can design authored content in such a way that it will be usable by individuals with limited language, cognitive, and learning abilities. |
4.2.11 Privacy |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not contain content that gives users, either of assistive technologies or not, an expectation of privacy. Authored Content (HTML): Authored content does not contain content that would give users, either of assistive technologies or not, an expectation of privacy. Authored Content (PDF): Authored content does not contain content that would give users, either of assistive technologies or not, an expectation of privacy. |
Chapter 5: Generic Requirements
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 |
Not Applicable |
The product does not have specific documented accessibility features. The software instead relies upon platform accessibility features. |
5.3 Biometrics |
Not Applicable |
The product does not rely on biological characteristics. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
The product does not allow for file formats to be converted. |
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 |
Supports |
The product relies on platform software to supply key repeat functionality. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not provide 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. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: See WCAG 2.0 section.
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.0 section. |
See information in the WCAG section |
11.2.2 Software success criteria (closed functionality) |
Not Applicable |
|
11.3.2.3 Use of accessibility services |
Supports |
The product utilizes platform accessibility services to expose controls to assistive technologies. |
11.3.2.4 Assistive technology |
Not Applicable |
The product is not an assistive technology. |
11.3.2.5 Object information |
Does Not Support |
As noted in 4.1.2 Name, Role, Value, many controls do not supply appropriate roles or names to assistive technologies. |
11.3.2.6 Row, column, and headers |
Not Applicable |
The product does not use table structures. |
11.3.2.7 Values |
Supports with Exceptions |
The values for all input elements can be programmatically set and are determinable. A rating of Supports with Exceptions has been given for the following reason: When only a specific range of values is allowed for text input, such as a hex color code, there is no programmatic indication of what range will be accepted. |
11.3.2.8 Label relationships |
Does Not Support |
As noted in 4.1.2 Name, Role, Value, the UI does not expose label relationships to assistive technologies. |
11.3.2.9 Parent-child relationships |
Does Not Support |
As noted in 1.3.1 Info and Relationships, parent-child relationships between components of the UI are not programmatically determinable. |
11.3.2.10 Text |
Supports |
The product exposes text content to assistive technologies. |
11.3.2.11 List of available actions |
Supports with Exceptions |
The product provides a list of available actions for all controls containing appropriate programmatic roles. However, one notable exception exists within the main menu structure. No distinction is made between menu items that contain and spawn submenus, and those that activate a specific menu option. |
11.3.2.12 Execution of available actions |
Supports |
The UI allows assistive technologies to perform actions on objects. |
11.3.2.13 Tracking of focus and selection attributes |
Supports |
When the focus cursor is placed on objects, focus is exposed both programmatically as well as visually to users. This is also true of text insertion point. |
11.3.2.14 Modification of focus and selection attributes |
Supports with Exceptions |
The product prevents users, both those with and without assistive technologies, from moving focus between panes in the software. |
11.3.2.15 Change notification |
Does Not Support |
The product does not regularly notify assistive technologies when changes in the application occur either in response to a user interaction, such as when a menu expands or collapses. |
11.3.2.16 Modifications of states and properties |
Supports |
States and properties for controls, such as radio buttons and checkboxes, are capable of being programmatically set by users, including those using assistive technologies. |
11.3.2.17 Modifications of values and text |
Supports |
The UI allows assistive technologies to modify both values of controls as well as text content. |
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 majority of platform accessibility features are not disrupted by the product. However, with the exception of the initial new project screen, the software does not support Windows High Contrast Mode. |
11.5 User preferences |
Supports with Exceptions |
The product supports user platform preferences for settings, such as font size and focus cursor. However, the software does not support preferences for color and themes. |
11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section. |
See information in the WCAG section |
11.6.3 Preservation of accessibility information in transformations |
Not Applicable |
The product does not convert files from one format to another. |
11.6.4 Repair assistance |
Not Applicable |
The product has no method of detecting that requirements for clauses 9 or 10 are met. |
11.6.5 Templates |
Does Not Support |
The product provides templates to help users generate content for specific devices, but these do not allow content creation that conforms to WCAG A and AA. |
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)