Adobe Accessibility Conformance Report
VPAT® Version 2.3 (Revised) – April 2019
Product Information
Name of Product/Version: InDesign 19.0.1
Product Description: InDesign is a page design software and layout application that lets you create, preflight, and publish documents for print and digital media. It is an industry wide used application for creating layouts for Magazines, Brochures, Newspapers, Books, advertisements etc.
Date: November 2023
Contact information: access@adobe.com
Notes: Tested using the most common user journeys: create layout from scratch and aggregate content from stakeholders; add to the existing layout from the template and aggregate the content; copy or bring in content from another source; create template of the created layout or design; publish online; export as various outputs and validate them.
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 involved extensive use of leading assistive technology 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 standard/guidelines:
Standard/Guideline |
Included in Report |
---|---|
Level A: Yes |
|
Level A: Yes |
|
Yes |
|
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.
- Partially Supports: 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.x Report
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
- 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.x 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.
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)
Revised Section 508
|
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not provide sufficient text alternatives for most images, such as the icon buttons used in the user interface. Authored Content (PDF): Authors can add alternative text to any non-text content. Authored Content (HTML): Authors can add alternative text to any non-text content. Authored Content (ePub): Authors can add alternative text to any non-text content.
|
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)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain prerecorded audio-only or video-only media. Authored Content (PDF): Authors can provide text that sufficiently describes any prerecorded audio-only or video-only media within exported PDF files. Authored Content (HTML): Authors can provide text that sufficiently describes any prerecorded audio-only or video-only media within exported HTML files. The HTML can also be altered in the product to include other options. Authored Content (ePub): Authors can provide text that sufficiently describes any prerecorded audio-only or video-only media within exported ePub files. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain prerecorded synchronized media. Authored Content (PDF): Authors can provide open captions within synchronized media imported to the product. Authored Content (HTML): Authors can provide captions for all prerecorded audio in synchronized media within HTML files. The HTML can also be altered in the product to include other options. Authored Content (ePub): Authors can provide open captions within synchronized media imported to the product. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain prerecorded video content that would require audio description or a media alternative. Authored Content (PDF): Authors can embed audio descriptions into any synchronized media imported to the product. Authored Content (HTML): Authors can embed audio descriptions into any synchronized media imported to the product. The HTML can also be altered in the product to include other options. Authored Content (ePub): Authors can embed audio descriptions into any synchronized media imported to the product. |
1.2.4 Captions (Live) (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain live synchronized media. Authored Content (PDF): PDF content output from the product will not contain any live synchronized media. Authored Content (HTML): HTML content output from the product will not contain any live synchronized media. Authored Content (ePub): ePub content output from the product will not contain any live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain prerecorded video content that would require audio description. Authored Content (PDF): Authors can provide audio description for video. Authored Content (HTML): Authors can provide audio description for video. Authored Content (ePub): Authors can provide audio description for video. |
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)
Revised Section 508
|
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most structure and relationship information are not provided programmatically, such as text input and button labels. Authored Content (PDF): Authors can provide appropriate element semantics, object information and textual equivalents for visual structure and relationships within PDF files. Authored Content (HTML): Authors can provide appropriate element semantics, object information and textual equivalents for visual structure and relationships within HTML files. Authored Content (ePub): Authors can provide appropriate element semantics, object information and textual equivalents for visual structure and relationships within ePub files. |
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Many components are not presented in a meaningful sequence due to being hidden from assistive technology. Authored Content (PDF): The product allows authors to present content in a meaningful sequence within PDF files. Authored Content (HTML): The product allows authors to present content in a meaningful sequence within HTML files. Authored Content (ePub): The product allows authors to present content in a meaningful sequence within ePub files. |
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Instructions do not rely solely on sensory characteristics. Authored Content (PDF): Authors can ensure that instructions do not rely solely on sensory characteristics within PDF files. Authored Content (HTML): Authors can ensure that instructions do not rely solely on sensory characteristics within HTML files. Authored Content (ePub): Authors can ensure that instructions do not rely solely on sensory characteristics within ePub files. |
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product allows for screen orientation changes. Authored Content (PDF): Authored PDF files are not locked to a single display orientation. Authored Content (HTML): Authored HTML files are not locked to a single display orientation. Authored Content (ePub): Authored ePub files are not locked to a single display orientation. |
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not support identifying the expected meaning of form input data. Authored Content (PDF): PDF files do not support identifying the expected meaning of form input data. Authored Content (HTML): Authors can ensure that HTML forms utilize Autocomplete correctly. Authored Content (ePub): ePub files do not support identifying the expected meaning of form input data. |
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)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Color is not used as the sole means of identifying information. Authored Content (PDF): Authors can ensure that color is not used as the sole means of identifying information within PDF files. Authored Content (HTML): Authors can ensure that color is not used as the sole means of identifying information within HTML files. Authored Content (ePub): Authors can ensure that color is not used as the sole means of identifying information within ePub files. |
1.4.2 Audio Control (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain audio that plays automatically. Authored Content (PDF): Authored PDF content does not contain audio that plays automatically. Authored Content (HTML): Authors can ensure that audio content does not play automatically within HTML files. Authored Content (ePub): Authored ePub content does not contain audio that plays automatically. |
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most text meets minimum contrast requirements. Exceptions include:
Authored Content (PDF): Authors can choose their own color schemes in order to meet this criterion within PDF files. Authored Content (HTML): Authors can choose their own color schemes in order to meet this criterion within HTML files. Authored Content (ePub): Authors can choose their own color schemes in order to meet this criterion within ePub files. |
1.4.4 Resize text (Level AA)
Revised Section 508
|
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not resize the user interface text to match the text scaling applied by the operating system. However there is functionality to increase text size within the product itself supporting 110, 150, and 200 percent scaling. Authored Content (PDF): Authored content can be resized up to 200% within PDF files. Authored Content (HTML): Authored content can be resized up to 200% within HTML files. Authored Content (ePub): Authored content can be resized up to 200% within ePub files. |
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product uses text instead of images of text. Authored Content (PDF): Authors can ensure that content contains text instead of images of text within PDF files. Authored Content (HTML): Authors can ensure that content contains text instead of images of text within HTML files. Authored Content (ePub): Authors can ensure that content contains text instead of images of text within ePub files. |
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product is designed for a desktop environment that cannot show a viewport width of less than 800 pixels. Authored Content (PDF): Do not by default include the ability to reflow content. Authored Content (HTML): Authors can add a liquid layout to allow exported content to reflow. Authored Content (ePub): Authors can add a liquid layout to allow exported content to reflow. |
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most components and meaningful graphics have a contrast ratio of at least 3:1 against adjacent colors. Exceptions include:
Authored Content (PDF): Authors can choose their own color schemes in order to meet this criterion within PDF files. Authored Content (HTML): Authors can choose their own color schemes in order to meet this criterion within HTML files. Authored Content (ePub): Authors can choose their own color schemes in order to meet this criterion within ePub files. |
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product is not implemented using markup languages. Authored Content (PDF): PDF files are not implemented using markup languages. Authored Content (HTML): Text spacing within authored HTML files can be modified in order to meet the criterion. Authored Content (ePub): Text spacing within authored ePub files can be modified in order to meet the criterion. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product’s additional content that appears on hover or focus is controlled by the user agent. Authored Content (PDF): The format of hoverable items cannot be defined by the author. Authored Content (HTML): Authors can ensure that any content that appears/disappears on hover/focus is dismissible, hoverable and persistent within HTML files. Authored Content (ePub): The format of hoverable items cannot be defined by the author. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A)
Revised Section 508
|
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Many interactive elements are not within the keyboard tab order and so cannot be focused by keyboard users. Furthermore, it is difficult to navigate from one panel to another in the user interface, even when using the available keyboard shortcuts. Authored Content (PDF): Authors can ensure that content is accessible using a keyboard alone within PDF files. Authored Content (HTML): Authors can ensure that content is accessible using a keyboard alone within HTML files. Authored Content (ePub): Authors can ensure that content is accessible using a keyboard alone within ePub files. |
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not include keyboard traps. Authored Content (PDF): Authors can ensure that content does not contain keyboard traps within PDF files. Authored Content (HTML): Authors can ensure that content does not contain keyboard traps within HTML files. Authored Content (ePub): Authors can ensure that content does not contain keyboard traps within ePub files. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: While keyboard shortcuts have been implemented using only letter characters, there is the facility to either turn off or remap each individual shortcut. Authored Content (PDF): Authored PDF files do not contain custom keyboard shortcuts. Authored Content (HTML): Authors can choose whether to include additional non-standard keyboard shortcuts. Authored Content (ePub): Authored ePub files do not contain custom keyboard shortcuts. |
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)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not include time limits. Authored Content (PDF): Authored PDF files do not include time limits. Authored Content (HTML): Authors can choose whether to include time limits within HTML files. Authored Content (ePub): Authored ePub files do not include time limits. |
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not include elements which move, blink, scroll, or auto-update that start automatically or last longer than 5 seconds. Authored Content (PDF): Authors can ensure that any content within PDF files meets this criterion. Authored Content (HTML): Authors can ensure that any content within HTML files meets this criterion. Authored Content (ePub): Authors can ensure that any content within ePub files 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)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain any content that flashes more than three times in any one second. Authored Content (PDF): Authors can ensure that content does not flash within PDF files. Authored Content (HTML): Authors can ensure that content does not flash within HTML files. Authored Content (ePub): Authors can ensure that content does not flash within ePub files. |
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)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain repeated blocks that would require a skip mechanism. Authored Content (PDF): Authors can ensure that content either does not contain repeated blocks or a skip mechanism is provided within PDF files. Authored Content (HTML): Authors can ensure that content either does not contain repeated blocks or a skip mechanism is provided within HTML files. Authored Content (ePub): Authors can ensure that content either does not contain repeated blocks or a skip mechanism is provided within ePub files. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Modals and other panels within the product have appropriately named titles that describe the topic or function. Authored Content (PDF): Authors can ensure that a title is set for each authored PDF file. Authored Content (HTML): Authors can ensure that a title is set for each HTML page. Authored Content (ePub): Authors can ensure that a title is set for each ePub file. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Authored Content (HTML): Authored Content (ePub): |
Software: Components receive focus in a meaningful order. Authored Content (PDF): Authors can ensure that focusable content receives focus in a meaningful way within PDF files. Authored Content (HTML): Authors can ensure that focusable content receives focus in a meaningful way within HTML files. Authored Content (ePub): Authors can ensure that focusable content receives focus in a meaningful way within ePub files. |
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Authored Content (HTML): Authored Content (ePub): |
Software: The product does not contain links. Authored Content (PDF): Authors can set the link text as well as the programmatically determined link context within PDF files. Authored Content (HTML): Authors can set the link text as well as the programmatically determined link context within HTML files. Authored Content (ePub): Authors can set the link text as well as the programmatically determined link context within ePub files. |
2.4.5 Multiple Ways (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: This criterion does not apply to non-web software. Authored Content (PDF): The author can add bookmarks to the file to be used in the exported PDF. Authored Content (HTML): Authors can ensure that multiple ways are provided to reach a page within HTML files. Authored Content (ePub): The author can add bookmarks to the file to be used in the exported ePub. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Headings and labels are descriptive. Authored Content (PDF): Authors can ensure that headings and labels used within PDF files are descriptive. Authored Content (HTML): Authors can ensure that headings and labels used within HTML files are descriptive. Authored Content (ePub): Authors can ensure that headings and labels used within ePub files are descriptive. |
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The keyboard focus indicator is visible on all interactive components. Authored Content (PDF): PDF files have default keyboard focus indicators on all interactive components. Authored Content (HTML): Authors can ensure that native focusable elements are used within HTML files which will use the default keyboard focus indicator. Authored Content (ePub): Authors can ensure that native focusable elements are used within ePub files which will use the default keyboard focus indicator. |
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.5.1 Pointer Gestures (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Elements in the product can be used with required pointer gestures. However, the canvas requires specific pointer actions for adding, moving and editing content. Authored Content (PDF): Authored content does not contain multi-point or path-based gestures within PDF files. Authored Content (HTML): Authors can choose whether to include multi-point or path-based gestures within HTML files. Authored Content (ePub): Authored content does not contain multi-point or path-based gestures within ePub files. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product contains only functionality that can be activated on the up-event of a single pointer, with the exception of actions that are required to operate the user agent (e.g. native Windows menus). Authored Content (PDF): Authors can ensure that native elements are used within PDF files, which meet the criterion of this checkpoint. Authored Content (HTML): Authors can ensure that native elements are used within HTML files, which meet the criterion of this checkpoint. Authored Content (ePub): Authors can ensure that native elements are used within ePub files, which meet the criterion of this checkpoint. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product includes the visible label of user interface controls within the accessible name, except in cases where there is no programmatic association, such as:
Authored Content (PDF): Authors can ensure that the accessible name for each component within PDF files includes the visible label. Authored Content (HTML): Authors can ensure that the accessible name for each component within HTML files includes the visible label. Authored Content (ePub): Authors can ensure that the accessible name for each component within ePub files includes the visible label. |
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not contain functionality that can be operated by device motion or user motion. Authored Content (PDF): Authored PDF files do not contain motion actuation functionality. Authored Content (HTML): Authored HTML files do not contain motion actuation functionality. Authored Content (ePub): Authored ePub files do not contain motion actuation functionality. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product relies on the features of the underlying operating system to set and indicate the language of the user interface. Authored Content (PDF): The language of authored content in PDF files can be programmatically determined, and is set by the author. Authored Content (HTML): The language of authored content in HTML files can be programmatically determined, and is set by the current language used in the authoring software. Authored Content (ePub): The language of authored content in ePub files can be programmatically determined, and is set by the current language used in the authoring software. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Content is only presented in one language at a time. Authored Content (PDF): Authors can ensure that individual text containers within PDF files have a programmatically determinable language. Authored Content (HTML): Authors can ensure that individual text containers within HTML files have a programmatically determinable language. Authored Content (ePub): Authors can ensure that individual text containers within ePub files have a programmatically determinable language. |
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)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Components do not initiate a change of context when focused. Authored Content (PDF): Authors can ensure that focusable components do not cause a change of context within PDF files. Authored Content (HTML): Authors can ensure that focusable components do not cause a change of context within HTML files. Authored Content (ePub): Authors can ensure that focusable components do not cause a change of context within ePub files. |
3.2.2 On Input (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Changes of context do not occur automatically on user input. Authored Content (PDF): Authors can ensure that user input does not cause a change of context within PDF files. Authored Content (HTML): Authors can ensure that user input does not cause a change of context within HTML files. Authored Content (ePub): Authors can ensure that user input does not cause a change of context within ePub files. |
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: This criterion does not apply to non-web software. Authored Content (PDF): Authored content within PDF files does not contain a navigational mechanism that is repeated on multiple pages. Authored Content (HTML): Authored content within HTML files does not contain a navigational mechanism that is repeated on multiple pages. Authored Content (ePub): Authored content within ePub files does not contain a navigational mechanism that is repeated on multiple pages. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: This criterion does not apply to non-web software. Authored Content (PDF): This criterion does not apply to non-web documents. Authored Content (HTML): This criterion does not apply to non-web documents. Authored Content (ePub): 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.1 Error Identification (Level A)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not detect input errors. Authored Content (PDF): Authors can ensure that errors are made known to the user and identified in text within PDF files. Authored Content (HTML): Authors can ensure that errors are made known to the user and identified in text within HTML files. Authored Content (ePub): Authors can ensure that errors are made known to the user and identified in text within ePub files. |
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Visual labels are provided for input fields, however many elements do not have a programmatic association between the visible label and the input field and so are not conveyed to assistive technology, such as:
Authored Content (PDF): Authors can ensure that labels and instructions are provided within PDF files. Authored Content (HTML): Authors can ensure that labels and instructions are provided within HTML files. Authored Content (ePub): Authors can ensure that labels and instructions are provided within ePub files. |
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not detect input errors that are displayed to users. Authored Content (PDF): Authors can ensure that error suggestions are provided to the user within PDF files. Authored Content (HTML): Authors can ensure that error suggestions are provided to the user within HTML files. Authored Content (ePub): Authors can ensure that error suggestions are provided to the user within ePub files. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing. Authored Content (PDF): Authors can ensure that authored content meets this criterion within PDF files. Authored Content (HTML): Authors can ensure that authored content meets this criterion within HTML files. Authored Content (ePub): Authors can ensure that authored content meets this criterion within ePub files. |
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)
Revised Section 508
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product is not implemented using markup languages. Authored Content (PDF): Authored PDF content is not implemented using markup languages. Authored Content (HTML): Authored HTML content contains elements that have complete start and end tags; are nested according to their specifications; do not contain duplicate attributes, and use IDs that are unique. Authored Content (ePub): Authored ePub content contains elements that have complete start and end tags; are nested according to their specifications; do not contain duplicate attributes, and use IDs that are unique. |
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most user interface components do not convey their name, role or value to assistive technology, such as:
Authored Content (PDF): Authors can ensure that all names, roles and values are programmatically determinable within PDF files. Authored Content (HTML): Authors can ensure that all names, roles and values are programmatically determinable within HTML files. Authored Content (ePub): Authors can ensure that all names, roles and values are programmatically determinable within ePub files. |
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product is not implemented using markup languages. Authored Content (PDF): PDF files are not implemented using markup languages. Authored Content (HTML): Authors can ensure that any status messages are programmatically determinable within HTML files. Authored Content (ePub): Authors can ensure that any status messages are programmatically determinable within ePub files. |
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
302.1 Without Vision |
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most functionality within the product is inaccessible to users without vision, as shown in 1.1.1 Non-text content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value. Authored Content (PDF): Authors can ensure that users without vision are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users without vision are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users without vision are able to view and interact with ePub files. |
|
302.2 With Limited Vision |
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most of the product can be used by users with low vision. Exceptions are listed in 1.4.3 Contrast (Minimum), 1.4.4 Resize Text, and 1.4.11 Non-text Contrast. Authored Content (PDF): Authors can ensure that users with limited vision are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users with limited vision are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users with limited vision are able to view and interact with ePub files. |
|
|
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): 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 (PDF): Authors can ensure that users who cannot perceive color are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users who cannot perceive color are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users who cannot perceive color are able to view and interact with ePub files. |
|
302.4 Without Hearing |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: No functionality within the product requires hearing Authored Content (PDF): Authors can ensure that PDF files can be perceived by users without hearing, such as by adding captions. Authored Content (HTML): Authors can ensure that HTML files can be perceived by users without hearing, such as by adding captions. Authored Content (ePub): Authors can ensure that ePub files can be perceived by users without hearing, such as by adding captions. |
|
302.5 With Limited Hearing |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: No functionality within the product requires hearing Authored Content (PDF): Authors can ensure that PDF files can be perceived by users without hearing, such as by adding captions. Authored Content (HTML): Authors can ensure that HTML files can be perceived by users without hearing, such as by adding captions. Authored Content (ePub): Authors can ensure that ePub files can be perceived by users without hearing, such as by adding captions. |
|
302.6 Without Speech |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not require user speech. Authored Content (PDF): Speech is not required to interact with PDFs. Authored Content (HTML): Speech is not required to interact with HTML files. Authored Content (ePub): Speech is not required to interact with ePubs. |
|
302.7 With Limited Manipulation |
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most users with limited manipulation would have difficulty navigating through the user interface, as described in 2.1.1 Keyboard. Authored Content (PDF): Authors can ensure that users with limited manipulation are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users with limited manipulation are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users with limited manipulation are able to view and interact with ePub files. |
|
302.8 With Limited Reach and Strength |
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most users with limited reach and strength would have difficulty navigating through the user interface, as described in 2.1.1 Keyboard. Authored Content (PDF): Authors can ensure that users with limited reach and strength are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users with limited reach and strength are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users with limited reach and strength are able to view and interact with ePub files. |
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product provides icons and supplements these with text. Authored Content (PDF): Authors can ensure that PDF files contain easy to understand language and that icons are explained in text. Authored Content (HTML): Authors can ensure that HTML files contain easy to understand language and that icons are explained in text. Authored Content (ePub): Authors can ensure that ePub files contain easy to understand language and that icons are explained in text. |
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.x section |
See information in WCAG 2.x section. |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
The product is not platform software. |
|
502.2.2 No Disruption of Accessibility Features |
Partially Supports |
The product supports the use of most platform accessibility features, screen reader usage. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors and partially supports operating system text resizing. |
|
502.3.1 Object Information |
Does Not Support |
Navigation controls and edit fields will have meaningful labels and roles described. There are exceptions for elements not having their label and role defined throughout the product. |
|
502.3.2 Modification of Object Information |
Partially Supports |
Not all elements can be focused or used with the keyboard. |
|
502.3.3 Row, Column, and Headers |
Supports |
Tables are not used in the product. |
|
502.3.4 Values |
Partially Supports |
Values have a meaningful description for most items. There are fields where the value and the label of the value are not programmatically defined. |
|
502.3.5 Modification of Values |
Partially Supports |
Values used in the product can be modified within the product except for users of the keyboard cannot change some items. |
|
502.3.6 Label Relationships |
Does Not Support |
Some objects are visually labelled correctly. The labels do not get associated to the items or icons have no alternatives. |
|
502.3.7 Hierarchical Relationships |
Does Not Support |
Relationships cannot be programmatically determined for nested items like checkboxes and radio buttons. |
|
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 |
Text can be modified within the product. |
|
502.3.10 List of Actions |
Partially Supports |
Actions that can be used require specific shortcuts for keyboard users to access them that may not be well known. |
|
502.3.11 Actions on Objects |
Partially Supports |
Not all elements can be focused or used with the keyboard. |
|
502.3.12 Focus Cursor |
Supports |
The focus cursor tracks current focus as expected. |
|
502.3.13 Modification of Focus Cursor |
Does Not Support |
The focus does not easily move into a new pane or into the main screen using the keyboard. |
|
502.3.14 Event Notification |
Supports |
The product supplies information to users when events, including changes in state and value, occur. |
|
502.4 Platform Accessibility Features |
Not Applicable |
The product is not platform software. |
|
503.2 User Preferences |
Partially Supports |
The product supports the use of most platform accessibility features, screen reader usage. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors and partially supports operating system text resizing. |
|
503.3 Alternative User Interfaces |
Not Applicable |
The product does not include an alternative user interface. |
|
503.4.1 Caption Controls |
Not Applicable |
The product does not include volume controls to align the captions alongside. |
|
503.4.2 Audio Description Controls |
Not Applicable |
The product does not have controls to allow program selection. |
|
504.2 Content Creation or Editing |
|
See information in WCAG 2.x section |
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Supports |
Authored content keeps the settings provided in the application when they are exported. This includes captions, tags and bookmarks. |
|
504.2.2 PDF Export |
Supports |
The product can export content into files that conform to ISO 32000-1:2008 or PDF 1.7 and export content into files that conform to ANSI/AIIM/ISO 14289-1:2016 or PDF/UA-1. |
|
504.3 Prompts |
Does Not Support |
The product provides ways to make content accessible with a few checks before an export is complete. It does not enforce these checks and the product does not provide a tool to check for technical infringements of the content. |
|
504.4 Templates |
Does Not Support |
The product allows for the use of templates in creating documents but does not provide accessible templates in the shipped product. |
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.
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 (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most functionality within the product is inaccessible to users without vision, as shown in 1.1.1 Non-text content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, and 4.1.2 Name, Role, Value. Authored Content (PDF): Authors can ensure that users without vision are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users without vision are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users without vision are able to view and interact with ePub files. |
4.2.2 Usage with limited vision |
Software: Partially Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most of the product can be used by users with low vision. Exceptions are listed in 1.4.3 Contrast (Minimum), 1.4.4 Resize Text, and 1.4.11 Non-text Contrast. Authored Content (PDF): Authors can ensure that users with limited vision are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users with limited vision are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users with limited vision are able to view and interact with ePub files. |
4.2.3 Usage without perception of colour |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): 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 (PDF): Authors can ensure that users who cannot perceive color are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users who cannot perceive color are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users who cannot perceive color are able to view and interact with ePub files. |
4.2.4 Usage without hearing |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: No functionality within the product requires hearing Authored Content (PDF): Authors can ensure that PDF files can be perceived by users without hearing, such as by adding captions. Authored Content (HTML): Authors can ensure that HTML files can be perceived by users without hearing, such as by adding captions. Authored Content (ePub): Authors can ensure that ePub files can be perceived by users without hearing, such as by adding captions. |
4.2.5 Usage with limited hearing |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: No functionality within the product requires hearing Authored Content (PDF): Authors can ensure that PDF files can be perceived by users without hearing, such as by adding captions. Authored Content (HTML): Authors can ensure that HTML files can be perceived by users without hearing, such as by adding captions. Authored Content (ePub): Authors can ensure that ePub files can be perceived by users without hearing, such as by adding captions. |
4.2.6 Usage without vocal capability |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not require user speech. Authored Content (PDF): Speech is not required to interact with PDFs. Authored Content (HTML): Speech is not required to interact with HTML files. Authored Content (ePub): Speech is not required to interact with ePubs. |
4.2.7 Usage with limited manipulation or strength |
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most users with limited manipulation or strength would have difficulty navigating through the user interface, as described in 2.1.1 Keyboard. Authored Content (PDF): Authors can ensure that users with limited manipulation or strength are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users with limited manipulation or strength are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users with limited manipulation or strength are able to view and interact with ePub files. |
4.2.8 Usage with limited reach |
Software: Does Not Support Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: Most users with limited reach would have difficulty navigating through the user interface, as described in 2.1.1 Keyboard. Authored Content (PDF): Authors can ensure that users with limited reach are able to view and interact with PDF files. Authored Content (HTML): Authors can ensure that users with limited reach are able to view and interact with HTML files. Authored Content (ePub): Authors can ensure that users with limited reach are able to view and interact with ePub files. |
4.2.9 Minimize photosensitive seizure triggers |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product, as noted in 2.3.1 Three Flashes or Below Threshold, does not contain flashing content. Authored Content (PDF): Authors can ensure that content does not flash within PDF files. Authored Content (HTML): Authors can ensure that content does not flash within HTML files. Authored Content (ePub): Authors can ensure that content does not flash within ePub files. |
4.2.10 Usage with limited cognition |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product provides icons and supplements these with text. Authored Content (PDF): Authors can ensure that PDF files contain easy to understand language and that icons are explained in text. Authored Content (HTML): Authors can ensure that HTML files contain easy to understand language and that icons are explained in text. Authored Content (ePub): Authors can ensure that ePub files contain easy to understand language and that icons are explained in text. |
4.2.11 Privacy |
Software: Supports Authored Content (PDF): Supports Authored Content (HTML): Supports Authored Content (ePub): Supports |
Software: The product does not require legal, financial or personal data. Authored Content (PDF): Authors can ensure that PDF files contain assistance if legal, financial or personal data are required. Authored Content (HTML): Authors can ensure that HTML files contain assistance if legal, financial or personal data are required. Authored Content (ePub): Authors can ensure that ePub files contain assistance if legal, financial or personal data are required. |
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed Functionality |
Not Applicable |
The product does not have closed functionality. |
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 |
Authored content keeps the settings provided in the application when they are exported. This includes captions, tags and bookmarks. |
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 |
Key repeat functionality is not supplied by the product. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not include a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
Users can navigate with the mouse instead, or amend the keyboard shortcuts if 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 (see WCAG 2.x section)
Notes:
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.1.1.1 through 11.4.1.3 |
See WCAG 2.x section |
See information in WCAG 2.x section |
11.5.2.1 Platform accessibility service support for software that provides a user interface |
See 11.5.2.5 through 11.5.2.17 |
See information in 11.5.2.5 through 11.5.2.17 |
11.5.2.2 Platform accessibility service support for assistive technologies |
See 11.5.2.5 through 11.5.2.17 |
See information in 11.5.2.5 through 11.5.2.17 |
11.5.2.3 Use of accessibility services |
Partially Supports |
The product supports the use of most platform accessibility features, screen reader usage. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors and partially supports operating system text resizing. |
11.5.2.4 Assistive technology |
Not Applicable |
The product is not assistive technology. |
11.5.2.5 Object information |
Does Not Support |
Navigation controls and edit fields will have meaningful labels and roles described. There are exceptions for elements not having their label and role defined throughout the product. |
11.5.2.6 Row, column, and headers |
Supports |
Tables are not used in the product. |
11.5.2.7 Values |
Partially Supports |
Values have a meaningful description for most items. There are fields where the value and the label of the value are not programmatically defined. |
11.5.2.8 Label relationships |
Does Not Support |
Some objects are visually labelled correctly. The labels do not get associated to the items or icons have no alternatives. |
11.5.2.9 Parent-child relationships |
Does Not Support |
Relationships cannot be programmatically determined for nested items like checkboxes and radio buttons. |
11.5.2.10 Text |
Supports |
The content of text objects, text attributes, and the boundaries of text is all programmatically determinable. |
11.5.2.11 List of available actions |
Partially Supports |
Actions that can be used require specific shortcuts for keyboard users to access them that may not be well known. |
11.5.2.12 Execution of available actions |
Partially Supports |
Not all elements can be focused or used with the keyboard. |
11.5.2.13 Tracking of focus and selection attributes |
Supports |
The focus cursor tracks current focus as expected. |
11.5.2.14 Modification of focus and selection attributes |
Partially Supports |
Not all elements can be focused or used with the keyboard. |
11.5.2.15 Change notification |
Supports |
The product supplies information to users when events, including changes in state and value, occur. |
11.5.2.16 Modifications of states and properties |
Partially Supports |
Not all elements can be focused or used with the keyboard. |
11.5.2.17 Modifications of values and text |
Partially Supports |
Text can be amended. Values have a meaningful description for most items. There are fields where the value and the label of the value are not programmatically defined. |
11.6.1 User control of accessibility features |
Not Applicable |
The product is not platform software. |
11.6.2 No disruption of accessibility features |
Partially Supports |
The product supports the use of most platform accessibility features, screen reader usage. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors and partially supports operating system text resizing. |
11.7 User preferences |
Partially Supports |
The product supports the use of most platform accessibility features, screen reader usage. However, the product does not support the use of Windows High Contrast Mode to override the UI designated colors and partially supports operating system text resizing. |
11.8.2 Accessible content creation |
See WCAG 2.x section |
See information in WCAG 2.x section |
11.8.3 Preservation of accessibility information in transformations |
Supports |
Authored content keeps the settings provided in the application when they are exported. This includes captions, tags and bookmarks. |
11.8.4 Repair assistance |
Does Not Support |
The product provides ways to make content accessible with a few checks before an export is complete. It does not enforce these checks and the product does not provide a tool to check for technical infringements of the content. |
11.8.5 Templates |
Does Not Support |
The product allows for the use of templates in creating documents but does not provide accessible templates in the shipped product. |
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.
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)