Adobe Accessibility Conformance Report
VPAT® Version 2.0 – October 2017
Product Information
Name of Product/Version: Adobe InDesign CC, Version 13
Product Description: Adobe InDesign CC is a page design and layout app that lets you create, preflight, and publish documents for print and digital media.
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 InDesign 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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Most images within the product, such as the images within the Control window, do not contain programmatic labels identifying their purpose. Authored Content (HTML): Authors can provide text alternatives for any non-text content within a document. Authored Content (PDF): Authors can provide text alternatives for any non-text content within a document. |
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) Also applies to: EN 301 549 Criteria
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): Authors can add text that sufficiently describes any pre-recorded audio-only or video-only content within HTML files exported from the product. Authored Content (PDF): Authors can add text that sufficiently describes any pre-recorded audio-only or video-only content within PDF files exported from the product. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
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): Authors can provide open captions within synchronized media imported to the product. Additionally, authors can supply custom HTML content, which allows embedding HTML video and track elements. Authored Content (PDF): Authors can provide open captions within synchronized media imported to the product. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
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): Authors can embed audio descriptions into any synchronized media imported to the product. Additionally, authors can supply custom HTML content, which allows embedding HTML video with multiple audio tracks. Authored Content (PDF): Authors can embed audio descriptions into any synchronized media imported to the product. |
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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Most relationships within the product interface are conveyed through presentation, but, they are not conveyed programmatically. Labels for controls, both those that are in text or are displayed as icons, are not programmatically associated with the controls they label. Authored Content (HTML): Authors can design content, through tags and formatting, so that all information, structure, and relationships are all conveyed explicitly within documents. Authored Content (PDF): Authors can design content, through tags and formatting, so that all information, structure, and relationships are all conveyed explicitly within documents. |
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product presents content in a meaningful sequence. Authored Content (HTML): The product allows authors to specify and update the reading order, so that when the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. Authored Content (PDF): The product allows authors to specify and update the reading order, so that when the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. |
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Instructions for understanding content, such as those within Preferences, do not rely on sensory characteristics. Authored Content (HTML): Authors can design content so that instructions do not rely solely on sensory characteristics. Authored Content (PDF): Authors can design content so that instructions do not rely solely on sensory characteristics. |
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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Within the product, color is often used to supplement meaning, but is not used as the sole means of identifying information. Selected background areas rely on font-bolding, in addition to background color changes, and the preflight error checker uses text in addition to color changes to imply meaning. Authored Content (HTML): Authors can design content so that color is never the sole means of communicating information. Authored Content (PDF): Authors can design content so that color is never the sole means of communicating information. |
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not automatically play audio for more than three seconds. Authored Content (HTML): Authors can design content that will not automatically play. However, player controls can be provided to allow users to stop or pause content. Authored Content (PDF): Authors can design content that will not automatically play. However, player controls can be provided to allow users to stop or pause content. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product contains keyboard shortcuts, allowing users to activate tools and settings that are not otherwise in the focus order. In addition to the default shortcuts, all tools and some settings can have custom keyboard shortcuts set. However, most elements and panes are not included within the tab order, and users cannot switch between panes within the user interface. By default, the tab key and shift + tab keyboard combination have been set to show and hide panels within the UI. Authored Content (HTML): Authors can use the “button and forms” panel, as well as other features, to ensure that interactive functionality exported to HTML is operable through a keyboard interface. Authored Content (PDF): Authors can use the “button and forms” panel, as well as other features, to ensure that interactive functionality exported to PDF is operable through a keyboard interface. |
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not trap keyboard focus on individual controls. Authored Content (HTML): Authors can ensure that any content they create and export from the product does not contain keyboard traps. Authored Content (PDF): Authors can ensure that any content they create and export from the product does not contain 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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not present users with time limits for functionality. Authored Content (HTML): Authors cannot set time limits on files exported from the product. Authored Content (PDF): Authors cannot set time limits on files exported from the product. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Within the product, some content will auto-update or blink, such as the Preflight Error Checker. However, this occurs due to user interaction, and can be turned off, if required. Some content will scroll, such as the product’s Terms of Service, but this too will begin scrolling on user interaction. Authored Content (HTML): Authors can design content that does not move, blink, scroll, or auto-update. Authored Content (PDF): Authors can design content that does not move, blink, scroll, or auto-update. |
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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product contains elements that may on occasion flash or blink, such as the error checking dot, but these will not flash more than three times per second. Authored Content (HTML): Authors can ensure that content inserted into their document does not contain anything that flashes more than three times in any one second period. Authored Content (PDF): Authors can ensure that content inserted into their document does not contain anything that flashes more than three times in any one second period. |
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) Also applies to: EN 301 549 Criteria
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 use multiple methods to allow users to bypass blocks of content, including not repeating blocks of content, providing links to skip past blocks of content, or providing headings before each section of content. Authored Content (PDF): Authors can use multiple methods to allow users to bypass blocks of content, including not repeating blocks of content, providing links to skip past blocks of content, or providing headings before each section of content. |
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Pages, modal dialogs, and other panes within the product contain appropriate and descriptive titles. Authored Content (HTML): The product will automatically assign a title for HTML content based on a document’s exported filename. Authors can ensure that filenames contain titles describe topic and purpose. Authored Content (PDF): Authors can set titles for files programmatically within a document’s Basic File Information. |
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The sequential navigation order within the product is consistent and logical. Authored Content (HTML): Authors can choose to either have the product automatically detect a focus order, or manually set a navigation sequence that preserves meaning and operability. Authored Content (PDF): Authors can choose to either have the product automatically detect a focus order, or manually set a navigation sequence that preserves meaning and operability. |
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 Authored Content (PDF): Supports |
Software: The purpose of link text can be determined in context. Authored Content (HTML): Authors can provide link text that ensures users can determine the purpose of links from the link text alone, or from the link text within context. Authored Content (PDF): Authors can provide link text that ensures users can determine the purpose of links from the link text alone, or from the link text within context. |
Guideline 3.1 Readable:
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): Does Not Support Authored Content (PDF): Supports |
Software: The language is programmatically identified within the product. Authored Content (HTML): No option exists to programmatically specify the default language of a page when exporting content. Authored Content (PDF): When exporting PDF content, authors can specify the language of a document within the Advanced settings. |
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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: No content within the product initiates a change of context on focus. Authored Content (HTML): Authors can choose to create content that does not initiate changes of context on focus. Authored Content (PDF): Authors can choose to create content that does not initiate changes of context on focus. |
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Many user interface components within the product are interrelated. Changing settings on some user interface components, such as a background color swatch, may cause other components to become enabled or changed in some way. Users are not alerted to any changes that have occurred when a setting is changed. Authored Content (HTML): Authors can create content that does not cause a change of context when changing the setting of any user interface component. Alternatively, authors can ensure users advised of behavior before using components. Authored Content (PDF): Authors can create content that does not cause a change of context when changing the setting of any user interface component. Alternatively, authors can ensure users are advised of behavior before using components. |
Guideline 3.3 Input Assistance:
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 Authored Content (PDF): Supports |
Software: When the product automatically detects an error, alert dialogs containing text will pop up and announce to users what input, such as the range of acceptable values, should be supplied. Authored Content (HTML): Authors designing forms can include messages that detect and identify form fields in error, and alert users to these errors. Authored Content (PDF): Authors designing forms can include messages that detect and identify form fields in error, and alert users to these errors. |
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 Authored Content (PDF): Supports |
Software: While in some cases, textual equivalents are displayed on mouse hover, some controls do not have programmatically associated labels. Sufficient information about controls must be found elsewhere for users to interact with a given control for many functions. Authored Content (HTML): Authors can provide labels or instructions when user input is required. Authored Content (PDF): Authors can provide labels or instructions when user input is required. |
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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The software is not implemented using markup languages. Authored Content (HTML): The product allows users to export content that will contain start and end tags, unique ID attributes, and elements that are nested according to the HTML specification. Authored Content (PDF): PDF content is not implemented with a markup language. |
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 (PDF): Supports |
Software: Most interactive components within the product contain programmatic roles. Most controls within the product’s primary interface do not have programmatic names. Labels displayed on mouse hover are not programmatically associated with form fields. Authored Content (HTML): Authors, using the Buttons and Forms and Links panels, can ensure that names and roles are programmatically supplied for all user interface components. Values, states, and properties will be able to be set by users within content exported through these means. Authored Content (PDF): Authors, using the Buttons and Forms and Links panels, can ensure that names and roles are programmatically supplied for all user interface components. Values, states, and properties will be able to be set by users within content exported through these means. |
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) Also applies to: EN 301 549 Criteria
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): HTML content output from the product will not contain any live audio content. Authored Content (PDF): PDF content output from the product will not contain any live audio content. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product will not present users with content requiring Audio Description. While video files can be imported into the product, these will not be able to be viewed until content is exported into another format. Authored Content (HTML): Authors can embed audio descriptions into any synchronized media imported to the product. Authored Content (PDF): Authors can embed audio descriptions into any synchronized media imported to the product. |
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) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product presents users with four color schemes to select from: Dark, Medium Dark, Medium Light, and Light. All observed content within the Dark, Medium Dark, and Light themes contain sufficient color contrast. While most content within the Medium Light theme contains sufficient color contrast, select panes within the right sidebar do not contain sufficient color contrast. Authored Content (HTML): Authors can select colors so that sufficient color contrast ratios are presented for text and any images of text. Authored Content (PDF): Authors can select colors so that sufficient color contrast ratios are presented for text and any images of text. |
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports with Exceptions Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product allows the user interface to be resized without assistive technology up to 200%. However, the application only supports scaling of 100, 150, and 200 percent. Other percentages, such as 125 or 175, are not supported. Authored Content (HTML): Authors can export explicit text so that HTML content can be resized to 200% without loss of functionality. Authored Content (PDF): Authors can export text so that PDF content can be resized to 200% without loss of functionality. Content can be exported to ensure that reflow functionality will work appropriately. |
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product uses text instead of images of text. Authored Content (HTML): Authors can choose to not include any images of text. Authored Content (PDF): Authors can choose to not include any images of text. |
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) Also applies to: EN 301 549 Criteria
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): Multi-page files with the product will export as a single HTML page. Authored Content (PDF): PDF content can be exported with bookmarks, allowing users to quickly access content within long 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 Authored Content (PDF): Supports |
Software: The product uses headings to clearly define sections of larger dialogs and labels to describe both purpose of components. Authored Content (HTML): Authors can supply descriptive headings and labels for all content. Authored Content (PDF): Authors can supply descriptive headings and labels for all content. |
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
2017 Section 508
|
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: A light blue, highly visual keyboard focus indicator is provided within all four themes within the product. Authored Content (HTML): Default browser focus indicators will be provided for links within HTML documents exported from the product. Authored Content (PDF): Default PDF viewer focus indicators will be provided for all keyboard accessible content within PDF files exported from the product. |
Guideline 3.1 Readable:
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 Authored Content (PDF): Supports |
Software: All observed content within the product is presented in the human language of the overall page. Authored Content (HTML): Paragraph styles can be used by authors to specify the human language for individual passages of text. These will export a programmatically determinable indication of the language selected in the style. Authored Content (PDF): Paragraph styles can be used by authors to specify the human language for individual passages of text. These will export a programmatically determinable indication of the language selected in the style. |
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) Also applies to: EN 301 549 Criteria
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): Content on multiple pages within the product will be exported into on single HTML page. Authored Content (PDF): Authors can present repeated components, such as headers and footers, in the same relative order each time they are repeated. |
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
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 choose to consistently identify any components that has the same functionality. Authored Content (PDF): Authors can choose to consistently identify any components that has the same functionality. |
Guideline 3.3 Input Assistance:
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 Authored Content (PDF): Supports |
Software: When an input error is automatically detected, the product will provide suggestions to correct the error, such as announcing the list of available values for an input field. Authored Content (HTML): Form fields will not be exported to HTML content. Authored Content (PDF): Authors can supply suggestions to users through alert boxes when form field errors are automatically detected, and solutions are known. |
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 Authored Content (PDF): Supports |
Software: The product does not cause legal commitments or financial transactions to occur. All observed user-controllable data that could be modified, such as preferences, were reversible. Authored Content (HTML): Authors can ensure that any content causing legal commitments or financial transactions to occur is either checked or confirmed. Authored Content (PDF): Authors can ensure that any content causing legal commitments or financial transactions to occur is either checked or confirmed. |
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): Supports Authored Content (PDF): Supports |
Software: Users without vision will be able to conduct some activities within the product, especially editing preferences and functionality within the menu bars. However, the main artboard is entirely inaccessible through the use of the keyboard, and the inability to navigate between panes inhibits their use by AT users. Authored Content (HTML): Authors can design content so that users without vision will be able to view page hierarchies through headings, navigate to and activate links through the use of a keyboard, and have all images contain alternative text. Authored Content (PDF): Authors can design content so that users without vision will be able to view page hierarchies through headings, navigate to and activate form fields and links through the use of a keyboard, enter data into form fields, and have all images contain alternative text. |
302.2 With Limited Vision |
Software: Supports with Exceptions Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product will support most features required by users with low vision, but some exceptions do exist. The software supports magnification by both platform features and assistive technology. Visual indications of focus are provided, and multiple UI color schemes are available to choose from. However, native high contrast theming is not supported in Windows, and a few areas within one theme contain low color contrast. Authored Content (HTML): Authors can create documents to ensure that users with limited vision will be able to enlarge page content without loss of functionality, track keyboard focus, and view content with sufficient color contrast. Authored Content (PDF): Authors can create documents to ensure that users with limited vision will be able to enlarge page content without loss of functionality, reflow pages, track keyboard focus, and view content with sufficient color contrast. |
302.3 Without Perception of Color |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product uses color to supplement meaning within the main user interface. When color selection is important to functionality, options to view alternatives, such as hex values, are available to help users differentiate colors. Authored Content (HTML): Authors can create content that does not use color to imply meaning to users. Authored Content (PDF): Authors can create content that does not use color to imply meaning to users. |
302.4 Without Hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not rely on hearing to present information to users. Some sounds are used to supplement on-screen information when an error or invalid entry occurs, but sound is not used as the sole means of communicating information. Authored Content (HTML): Authors can design content for users without hearing, including supplying closed captioning or transcripts for any audio content. Authored Content (PDF): Authors can design content for users without hearing, including supplying closed captioning or transcripts for any audio content. |
302.5 With Limited Hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not rely on hearing to present information to users. Some sounds are used to supplement on-screen information when an error or invalid entry occurs, but sound is not used as the sole means of communicating information. Authored Content (HTML): Authors can design content for users with limited hearing, including supplying closed captioning or transcripts for any audio content. Authored Content (PDF): Authors can design content for users with limited hearing, including supplying closed captioning or transcripts for any audio content. |
302.6 Without Speech |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Speech is not required to operate the product. Authored Content (HTML): Speech is not required to interact with HTML content exported from the product. Authored Content (PDF): Speech is not required to interact with PDF content exported from the product. |
302.7 With Limited Manipulation |
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Users with limited manipulation relying on speech recognition software will be able to interact with some components within the product, but most content will be inaccessible. Users will be able to call items within the menu structure through normal methods. However, many items do not contain programmatic roles, or contain insufficiently descriptive names. Authored Content (HTML): Authors can design content that will be usable by people with limited manipulation and speech recognition software by ensuring all content is within the focus order, contains programmatic roles and names. Authored Content (PDF): Authors can design content that will be usable by people with limited manipulation and speech recognition software by ensuring all content is within the focus order, contains programmatic roles and names. |
302.8 With Limited Reach and Strength |
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Users with limited reach will be able to interact with some content within the product, but most content will not be accessible. Users will be able to place keyboard focus on content sometimes, but the capturing of the tab key and inability to switch between panes in the interface will prevent access to content. Strength is never required to interact with content. Authored Content (HTML): Authors can design content that will be usable by people with limited reach by ensuring all content is within the focus order. Strength is never required to interact with content. Authored Content (PDF): Authors can design content that will be usable by people with limited reach by ensuring all content is within the focus order. Strength is never required to interact with content. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product supplies features to assist users with limited language, cognitive, and learning abilities. Tools appear in similar places across sessions of the program, users can select which options to display or hide as they work, and icons are used in addition to text to describe functional content. Authored Content (HTML): Authors can design content that will be usable by users with limited language, cognitive, and learning abilities through the use of repeated elements, icons to supplement textual content, and line spacing and formatting. Authored Content (PDF): Authors can design content that will be usable by users with limited language, cognitive, and learning abilities through the use of repeated elements, icons to supplement textual content, and line spacing and formatting. |
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 product supports the use of most platform accessibility features, including text size adjustment. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors. |
502.3 Accessibility Services |
See 502.3.1-502.3.14 |
|
502.3.1 Object Information |
Does Not Support |
Text input elements within the product expose their roles and often contain informative labels. Similarly, menu items contain appropriate names, roles and states. However, most other objects do not contain appropriate roles, names, or descriptions. |
502.3.2 Modification of Object Information |
Does Not Support |
Users, including those using assistive technologies, are able to modify values for text input fields. However, within the main interface, users cannot programmatically set values of many controls, including combo boxes and image buttons, in particular. |
502.3.3 Row, Column, and Headers |
Does Not Support |
Tables are used within the product’s pasteboard, but do not programmatically expose row, column, and header relationships to users. |
502.3.4 Values |
Supports with Exceptions |
Current values are programmatically determinable for objects. However, the range of allowable values was not programmatically determinable for all controls encountered during testing. |
502.3.5 Modification of Values |
Supports |
Values for text input are able to be programmatically set, including through the use of assistive technologies. |
502.3.6 Label Relationships |
Does Not Support |
Text and Icons serve as visual labels for all observed components. However, most components do not have a programmatically determinable relationship with their labels. |
502.3.7 Hierarchical Relationships |
Does Not Support |
As noted within 1.3.1 Info and Relationships, most hierarchical relationships, such as those used in nested preferences settings, are not programmatically determinable. |
502.3.8 Text |
Supports |
The content of text objects, text attributes, and the boundaries of text is all programmatically determinable. |
502.3.9 Modification of Text |
Supports |
All observed text that could be set by users could be set programmatically, including through assistive technologies. |
502.3.10 List of Actions |
Supports with Exceptions |
As noted in 4.1.2 Name, Role, Value, the majority of objects contain programmatic roles that will list actions that can be executed on the object. However, some controls, including the Reference Point selector, the constrain proportions controls, and buttons used for rotation do not announce to users what actions can be executed on these objects. |
502.3.11 Actions on Objects |
Supports with Exceptions |
Most objects within the product allow assistive technologies to perform actions on objects. However, the Reference Point Selector and other objects that do not properly list their actions do not allow assistive technologies to perform actions successfully. |
502.3.12 Focus Cursor |
Supports |
The product exposes information to track focus, text insertion point, and selection through native Operating System features. |
502.3.13 Modification of Focus Cursor |
Does Not Support |
Users, including those with assistive technologies, can modify the focus cursor and text insertion point within individual panes, but will not be able to navigate between panes. |
502.3.14 Event Notification |
Supports |
The product supplies information to users when events, including changes in state and value, occur. No instances of description, name, or boundary changing were observed during testing. |
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 |
The product supports platform accessibility settings, except in Windows High Contrast Mode. Most content, except the menu bars, does not respond to Windows High Contrast Mode or user selected color settings. |
503.3 Alternative User Interfaces |
Not Applicable |
The product does not provide an alternative user interface. |
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 provide volume adjustment. |
503.4.2 Audio Description Controls |
Not Applicable |
The product does not provide controls 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 WCAG section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Supports |
The product will preserve information, including tags used for accessibility from XML files, imported to the program. |
504.2.2 PDF Export |
Supports |
The product can export files that conform to PDF 1.7 and is capable of exporting PDF files that conform to PDF/UA-1. |
504.3 Prompts |
Does Not Support |
The product provides Preflight functionality which can assist authors in creating some content more accessibly. However, no mode of operation prompts users to create content in conformance to WCAG 2.0 success criteria. |
504.4 Templates |
Not Applicable |
Templates of content can be used, but are not provided by Adobe within the product, directly. |
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.
EN 301 549 Report
Notes:
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): Supports Authored Content (PDF): Supports |
Software: Users without vision will be able to conduct some activities within the product, especially editing preferences and functionality within the menu bars. However, the main artboard is entirely inaccessible through the use of the keyboard and the inability to navigate between panes inhibits the use by users. Authored Content (HTML): Authors can design content so that users without vision will be able to view page hierarchies through headings, navigate to and activate links through the use of a keyboard, and have all images contain alternative text. Authored Content (PDF): Authors can design content so that users without vision will be able to view page hierarchies through headings, navigate to and activate form fields and links through the use of a keyboard, enter data into form fields, and have all images contain alternative text. |
4.2.2 Usage with limited vision |
Software: Supports with Exceptions Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product supports most features required by users with low vision, but some exceptions do exist. The software supports magnification by both platform features and assistive technology. Visual indications of focus are provided, and multiple UI color schemes are available to choose from. However, native high contrast theming is not supported in Windows, and a few areas within one theme contain low color contrast. Authored Content (HTML): Authors can create documents to ensure that users with limited vision will be able to enlarge page content without loss of functionality, track keyboard focus, and view content with sufficient color contrast. Authored Content (PDF): Authors can create documents to ensure that users with limited vision will be able to enlarge page content without loss of functionality, reflow pages, track keyboard focus, and view content with sufficient color contrast. |
4.2.3 Usage without perception of colour |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product uses color to supplement meaning within the main user interface. When color selection is important to functionality, options to view alternatives, such as hex values, are available to help users differentiate colors. Authored Content (HTML): Authors can create content that does not use color to imply meaning to users. Authored Content (PDF): Authors can create content that does not use color to imply meaning to users. |
4.2.4 Usage without hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not rely on hearing to present information to users. Some sounds are used to supplement on-screen information when an error or invalid entry occurs, but sound is not used as the sole means of communicating information. Authored Content (HTML): Authors can design content for users without hearing, including supplying closed captioning or transcripts, for any audio content. Authored Content (PDF): Authors can design content for users without hearing, including supplying closed captioning or transcripts, for any audio content. |
4.2.5 Usage with limited hearing |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not rely on hearing to present information to users. Some sounds are used to supplement on-screen information when an error or invalid entry occurs, but sound is not used as the sole means of communicating information. Authored Content (HTML): Authors can design content for users with limited hearing, including supplying closed captioning or transcripts for any audio content. Authored Content (PDF): Authors can design content for users with limited hearing, including supplying closed captioning or transcripts for any audio content. |
4.2.6 Usage without vocal capability |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Speech is not required to operate the product. Authored Content (HTML): Speech is not required to interact with HTML content exported from the product. Authored Content (PDF): Speech is not required to interact with PDF content exported from the product. |
4.2.7 Usage with limited manipulation or strength |
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Users with limited manipulation relying on speech recognition software will be able to interact with some components within the product, but most content will be inaccessible. Users will be able to call items within the menu structure through normal methods. However, many items do not contain programmatic roles, or contain insufficiently descriptive names. Strength is never required to interact with content. Authored Content (HTML): Authors can design content that will be usable by people with limited manipulation and speech recognition software by ensuring all content is within the focus order and contains programmatic roles and names. Strength is never required to interact with content. Authored Content (PDF): Authors can design content that will be usable by people with limited manipulation and speech recognition software by ensuring all content is within the focus order contains programmatic roles and names. Strength is never required to interact with content. |
4.2.8 Usage with limited reach |
Software: Does Not Support Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: Users with limited reach will be able to interact with some content within the product, but most content will not be accessible. Users will be able to place keyboard focus on sometimes, but the capturing of the tab key, and inability to switch between panes in the interface will prevent access to content. Authored Content (HTML): Authors can design content that will be usable by people with limited reach by ensuring all content is within the focus order. Authored Content (PDF): Authors can design content that will be usable by people with limited reach by ensuring all content is within the focus order. |
4.2.9 Minimize photosensitive seizure |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not contain content that will flash at an unsafe threshold. Authored Content (HTML): Authors can design blinking or flashing content which does not trigger photosensitive seizures. Authored Content (PDF): Authors can design content to ensure that no blinking or flashing that may trigger photosensitive seizures is caused. |
4.2.10 Usage with limited cognition |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product supplies features to assist users with limited language, cognitive, and learning abilities. Tools appear in similar places across sessions of the program, users can select which options to display or hide as they work, and icons are used in addition to text to describe functional content. Authored Content (HTML): Authors can design content that will be usable by users with limited language, cognitive, and learning abilities through the use of repeated elements, icons to supplement textual content, and line spacing and formatting. Authored Content (PDF): Authors can design content that will be usable by users with limited language, cognitive, and learning abilities through the use of repeated elements, icons to supplement textual content, and line spacing and formatting. |
4.2.11 Privacy |
Software: Supports Authored Content (HTML): Supports Authored Content (PDF): Supports |
Software: The product does not ask for legal, financial, or personal data. Authored Content (HTML): Authors can design content exported from the product to assist in user privacy, such as by granting users control of legal and financial data. Authored Content (PDF): Authors can design content exported from the product to assist in user privacy, such as by granting users control of legal and financial data. |
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 contain documented accessibility features, instead the software relies on platform accessibility features. |
5.3 Biometrics |
Not Applicable |
The product does not rely on biological characteristics. |
5.4 Preservation of accessibility information during conversion |
Supports |
The product will preserve information, including tags used for accessibility from XML files, imported to the program. |
5.5.1 Means of operation |
Not Applicable |
The product does not have operable parts. |
5.5.2 Operable parts discernibility |
Not Applicable |
The product does not have operable parts. |
5.6.1 Tactile or auditory status |
Not Applicable |
The product does not have locking or toggle controls. |
5.6.2 Visual status |
Not Applicable |
The product does not have 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, by itself, supply a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
The product contains some keyboard shortcuts that require simultaneous user action. However, keyboard shortcuts are also available through menu structures or buttons, not requiring simultaneous actions. Additionally, users can customize keyboard shortcuts. |
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:
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
10.2.1 - 10.2.38 |
See WCAG 2.0 section. |
See information in the WCAG section |
10.2.39 Caption positioning |
Supports |
Authors exporting content that contains any form of closed captioning can ensure that open captions do not obscure relevant information within the synchronized media. |
10.2.40 Audio description timing |
Supports |
Authors exporting content can ensure that audio description they supply will not interfere with relevant audio information. |
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 WCAG section |
11.2.2 Software success criteria (closed functionality) |
Not Applicable |
|
11.3.2.3 Use of accessibility services |
Supports |
The product uses native platform accessibility services to expose elements to assistive technologies. |
11.3.2.4 Assistive technology |
Not Applicable |
The product is not assistive technology. |
11.3.2.5 Object information |
Does Not Support |
Text input elements within the product expose their roles and often contain informative labels. Similarly, menu items contain appropriate names, roles and states. However, most other objects do not contain appropriate roles, names, or descriptions. |
11.3.2.6 Row, column, and headers |
Does Not Support |
Tables are used within the product’s pasteboard, but do not programmatically expose row, column, and header relationships to users. |
11.3.2.7 Values |
Supports with Exceptions |
Current values are programmatically determinable for objects. However, the range of allowable values was not programmatically determinable for all controls encountered during testing. |
11.3.2.8 Label relationships |
Does Not Support |
Text and Icons serve as visual labels for all observed components. However, most components do not have a programmatically determinable relationship with their labels. |
11.3.2.9 Parent-child relationships |
Does Not Support |
As noted within 1.3.1 Info and Relationships, most hierarchical relationships, such as those used in nested preferences settings, are not programmatically determinable. |
11.3.2.10 Text |
Supports |
The content of text objects, text attributes, and the boundaries of text is all programmatically determinable. |
11.3.2.11 List of available actions |
Supports with Exceptions |
As noted in 4.1.2 Name, Role, Value, the majority of objects contain programmatic roles that will list actions that can be executed on the object. However, some controls, including the Reference Point selector, the constrain proportions controls, and buttons used for rotation do not announce to users what actions can be executed on these objects. |
11.3.2.12 Execution of available actions |
Supports with Exceptions |
Most objects within the product allow assistive technologies to perform actions on objects. However, the Reference Point Selector and other objects that do not properly list their actions do not allow assistive technologies to perform actions successfully. |
11.3.2.13 Tracking of focus and selection attributes |
Supports |
The product exposes information to track focus, text insertion point, and selection through native Operating System features. |
11.3.2.14 Modification of focus and selection attributes |
Does Not Support |
Users, including those with assistive technologies, can modify the focus cursor and text insertion point within individual panes, but will not be able to navigate between panes. |
11.3.2.15 Change notification |
Supports |
The product supplies information to users when events, including changes in state and value, occur. No instances of description, name, or boundary changing were observed during testing. |
11.3.2.16 Modifications of states and properties |
Does Not Support |
Users, including those using assistive technologies, are able to modify values for text input fields. However, within the main interface users cannot programmatically set values of many controls, including combo boxes and image buttons in particular. |
11.3.2.17 Modifications of values and text |
Supports |
Values for text input are able to be programmatically set, including through the use of assistive technologies. All observed text that could be set by users could be set programmatically, including through assistive technologies. |
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 supports the use of most platform accessibility features, including text size adjustment. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors. |
11.5 User preferences |
Supports with Exceptions |
The product supports the use of most platform accessibility features, including text size adjustment. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors. |
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 |
The product will preserve information, including tags used for accessibility from XML files, imported to the program. |
11.6.4 Repair assistance |
Does Not Support |
The product provides Preflight functionality which can assist authors in creating some content more accessibly. However, no functionality provides repair suggestions for content that does not conform with WCAG 2.0 success criteria. |
11.6.5 Templates |
Not Applicable |
Templates of content can be used but are not provided by Adobe within the product directly. |
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)