Adobe Illustrator Accessibility Conformance Report International Edition

(Based on VPAT® Version 2.4)

Name of Product/Version: 

Adobe Illustrator (Windows/Mac OS)

Report Date:

April 2024

Product Description:

Adobe Illustrator is a vector graphics and illustration editing software.

Contact Information:

access@adobe.com

Notes:

The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.

 

Evaluation Methods Used:

Product testing involved use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well 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

Web Content Accessibility Guidelines 2.0

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Web Content Accessibility Guidelines 2.1

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018  

Yes

EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11)  AND EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03)

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.1 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.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 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

  • 9.1.1.1 (Web)
  • 10.1.1.1 (Non-web document)
  • 11.1.1.1.1 (Open Functionality Software)
  • 11.1.1.1.2 (Closed Functionality Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: The product provides sufficient text alternatives for most instances of functional and informative images. The following exceptions exist: 

  • Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image. This occurs on the following screens: Outline Mode; Import: File Place; Save the Document; Create New Document.
  • A decorative image is not hidden from screen readers, so people who are blind and/or use a screen reader will have to navigate through unnecessary and duplicative text. This occurs on the following screens:  Artboard Panel; Panel - Layers.

 

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

  • 9.1.2.1 (Web)
  • 10.1.2.1 (Non-web document)
  • 11.1.2.1.1 (Open Functionality Software)
  • 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not contain prerecorded audio-only or video-only media.

1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.2 (Web)
  • 10.1.2.2 (Non-web document)
  • 11.1.2.2 (Open Functionality Software)
  • 11.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not contain prerecorded synchronized media.

1.2.3 Audio Description or Media Alternative (Prerecorded (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.3 (Web)
  • 10.1.2.3 (Non-web document)
  • 11.1.2.3.1 (Open Functionality Software)
  • 11.1.2.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not contain prerecorded video content that would require audio description or a media alternative.

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

  • 9.1.3.1 (Web)
  • 10.1.3.1 (Non-web document)
  • 11.1.3.1.1 (Open Functionality Software)
  • 11.1.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: Most information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. The following exceptions exist:

  • Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following screen: Export for Screens.
  • Some sets of checkboxes are not programmatically grouped, so the group label for each set of checkboxes will not be conveyed to people who are blind and/or use a screen reader and they will not understand the purpose of the individual checkboxes. This occurs on the following screens: Artboard Panel; Preferences - Selection & Anchor Display; Save the Document.
  • Some groups of form controls are not programmatically associated with their group label, so the purpose of individual controls in each group cannot be understood people who are blind and/or use a screen reader. This occurs on the following screens: Export As; Panel - Properties - Selection; Preferences - Selection & Anchor Display; Create New Document; Panel - Properties – Text; Panel - Stand Alone Character.
  • Some sets of radio buttons are not programmatically grouped, so the group label for each set of radio buttons will not be conveyed to people who are blind and/or use a screen reader and they will not understand the purpose of the individual radio buttons. This occurs on the following screens: Export for Screens; Export As; Artboard Panel; Preferences - Selection & Anchor Display; Save the Document.
  • Visual list is not marked up as list. This occurs on the following screen:  Discover Panel.

 

1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.2 (Web)
  • 10.1.3.2 (Non-web document)
  • 11.1.3.2.1 (Open Functionality Software)
  • 11.1.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: The reading and navigation order of most content is logical and intuitive. The following exceptions exist:

  • Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the screen. This occurs on the following screens: Export for Screens; Presentation Mode; Panel – Layers; Save the Document.
  • The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following screens:  Invite to Edit; Artboard Panel; Save the Document; Create New Document; Home screen; Panel - Layers.

1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.3 (Web)
  • 10.1.3.3 (Non-web document)
  • 11.1.3.3 (Open Functionality Software)
  • 11.1.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: 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

  • 9.1.4.1 (Web)
  • 10.1.4.1 (Non-web document)
  • 11.1.4.1 (Open Functionality Software)
  • 11.1.4.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: For most content, color is not used as the only method to convey information, indicate an action, prompt a response, or distinguish visual elements. The following exceptions exist: 

  • Color is used as the only method to convey information, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following screens: Panel - Properties - Selection; Home screen; Panel - Properties - Text; Panel - Stand Alone Character.
  • Color is the only visual method used to identify a link, and the contrast ratio of some links' text with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify those links. This occurs on the following screens: Invite to Edit; Create New Document.
  • Color alone is used to visually convey the state of a control. This occurs on the following screens:  Export for Screens; Outline Mode; Invite to Edit; Export As; Artboard Panel; Preferences - Selection & Anchor Display; Save the Document.

1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.2 (Web)
  • 10.1.4.2 (Non-web document)
  • 11.1.4.2 (Open Functionality Software)
  • 11.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not contain audio that plays automatically.

Guideline 2.1 Keyboard Accessible:

Make all functionality available from a keyboard.

Criteria

Conformance Level

Remarks and Explanations

2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.1.1 (Web)
  • 10.2.1.1 (Non-web document)
  • 11.2.1.1.1 (Open Functionality Software)
  • 11.2.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Does Not Support

Software: On most screens, all functionality is available using only the keyboard (unless that functionality cannot be accomplished in any known way using a keyboard). If shortcut keys and accesskeys are present, some may conflict with existing operating system and screen reader shortcuts, and some functionality based on custom gestures may not be available when a screen reader is turned on. The following exceptions exist:

  • Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs on the following screens: Artboard Panel; Create New Document; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment; Export for Screens; Import: File Place; Outline Mode; Panel - Properties – Selection; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Status Bar; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creating: Editing Tool - Eraser, Scissor; Discover Panel; Header; Open saved document; Panel – Layers; Panel - Properties – Text; Panel - Stand Alone Character; Version History Panel.
  • The content in a scrollable region cannot be accessed using a keyboard, so people who use a keyboard to navigate will not be able to view this content. This occurs on the following screens:  Export for Screens; Save the Document.

2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.1.2 (Web)
  • 10.2.1.2 (Non-web document)
  • 11.2.1.2 (Open Functionality Software)
  • 11.2.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: Keyboard focus is never locked or trapped in a particular area, and the user is able to navigate to and from all navigable elements using only a keyboard.

2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.1.4 (Web)
  • 10.2.1.4 (Non-web document)
  • 11.2.1.4.1 (Open Functionality Software)
  • 11.2.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports 

Software: The product provides character key shortcuts, and each shortcut activates only when the appropriate user interface component receives focus.

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

  • 9.2.2.1 (Web)
  • 10.2.2.1 (Non-web document)
  • 11.2.2.1 (Open Functionality Software)
  • 11.2.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not include time limits. 

2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.2.2 (Web)
  • 10.2.2.2 (Non-web document)
  • 11.2.2.2 (Open Functionality Software)
  • 11.2.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: On most screens where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. The following exceptions exist: 

  • The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following screens: Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creating: Editing Tool - Eraser, Scissor; Creation: Shape Tool – Curvature; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil.

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

  • 9.2.3.1 (Web)
  • 10.2.3.1 (Non-web document)
  • 11.2.3.1 (Open Functionality Software)
  • 11.2.3.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not contain flashing content.

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

  • 9.2.4.1 (Web)
  • 10.2.4.1 (Non-web document) – Does not apply
  • 11.2.4.1 (Open Functionality Software) – Does not apply
  • 11.2.4.1 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Software: Supports (Not Applicable)

Software: This criterion does not apply to non-web software.

2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.2 (Web)
  • 10.2.4.2 (Non-web document)
  • 11.2.4.2 (Open Functionality Software) - Does not apply
  • 11.2.4.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: The title of the software and each screen describes its respective purpose.

2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.3 (Web)
  • 10.2.4.3 (Non-web document)
  • 11.2.4.3 (Open Functionality Software)
  • 11.2.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: The navigation order of interactive elements (such as links, buttons, or form elements) is logical and preserves meaning and operability.

2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.4 (Web)
  • 10.2.4.4 (Non-web document)
  • 11.2.4.4 (Open Functionality Software)
  • 11.2.4.4 (Closed Software
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. The following exceptions exist:

  • The purpose of the link is not made clear by its text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where the link goes. This occurs on the following screen: Export for Screens:

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)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.1 (Web)
  • 10.2.5.1 (Non-web document)
  • 11.2.5.1 (Open Functionality Software)
  • 11.2.5.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports (Not Applicable) 

Software: The product does not rely on multipoint or path-based gestures. 

2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.2 (Web)
  • 10.2.5.2 (Non-web document)
  • 11.2.5.2 (Open Functionality Software)
  • 11.2.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports

Software: For functionality that can be operated using a single pointer, the action triggers on the up event (i.e. when the user releases the pointer), and a mechanism is available to abort the function before completion or to undo the function after completion.

2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.3 (Web)
  • 10.2.5.3 (Non-web document)
  • 11.2.5.3.1 (Open Functionality Software)
  • 11.2.5.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Partially Supports

Software: For most user interface components that include visible text labels, the accessible name matches (or includes) the visible text in the label. The following exceptions exist:

  • The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following screens:  Export for Screens; Panel - Properties - Selection.
  • Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following screens:  Artboard Panel; Create New Document; Export As; Export for Screens; Invite to Edit; Panel - Properties – Selection; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Save the Document; Open saved document; Panel - Properties – Text; Panel - Stand Alone Character.

2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.2.5.4 (Web)
  • 10.2.5.4 (Non-web document)
  • 11.2.5.4 (Open Functionality Software)
  • 11.2.5.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports (Not Applicable)

Software: The product does not have functionality operated by device motion or user motion.

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

  • 9.3.1.1 (Web)
  • 10.3.1.1 (Non-web document)
  • 11.3.1.1.1 (Open Functionality Software)
  • 11.3.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: The language of each screen is correct and can be determined programmatically.

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

  • 9.3.2.1 (Web)
  • 10.3.2.1 (Non-web document)
  • 11.3.2.1 (Open Functionality Software)
  • 11.3.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: When an element receives focus, a change in context (such as a substantial change to the screen, the spawning of a pop-up window, or a change in focus) that may disorient the user does not occur.

3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.2 (Web)
  • 10.3.2.2 (Non-web document)
  • 11.3.2.2 (Open Functionality Software)
  • 11.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software When a user inputs information or interacts with a control, it does not result in a substantial change to the screen that could disorient the user unless the user is informed about the change ahead of time.

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

  • 9.3.3.1 (Web)
  • 10.3.3.1 (Non-web document)
  • 11.3.3.1.1 (Open Functionality Software)
  • 11.3.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: For form controls where an input error is automatically detected, a text message or alert is provided that identifies the field/control where the error was detected and describes the error.

3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.2 (Web)
  • 10.3.3.2 (Non-web document)
  • 11.3.3.2 (Open Functionality Software)
  • 11.3.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: For most form controls/input fields requiring user input, labels, instructions, and/or error messages are provided to identify the controls/input fields in the form so that users know what input data is expected. The following exceptions exist:

  • The label of an element is not persistent (always visible on the screen), so the element's purpose may be difficult to discover. This occurs on the following screen: Invite to Edit.
  • Some groups of elements are missing a visible group label, so the purpose of the elements in each group cannot be understood. This occurs on the following screens: Panel - Properties - Selection; Artboard Panel; Panel - Stand Alone Transform.
  • The label for a form field is missing, so the field's purpose is not clear. This occurs on the following screens: Status Bar; Open saved document; Panel - Properties – Text; Panel - Stand Alone Character.

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

  • 9.4.1.1 (Web)
  • 10.4.1.1 (Non-web document)
  • 11.4.1.1.1 (Open Functionality Software)
  • 11.4.1.1.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: For the WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. This criterion was removed from WCAG 2.2.

4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.4.1.2 (Web)
  • 10.4.1.2 (Non-web document)
  • 11.4.1.2.1 (Open Functionality Software)
  • 11.4.1.2.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Does Not Support

Software: The name, role, state, and/or value of most, if not all, user interface components cannot be programmatically determined. The following issues exist:

  • When some buttons are disabled, their disabled state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the buttons are disabled. This occurs on the following screens: Export for Screens; Artboard Panel; Save the Document; Status Bar; Panel – Layers.
  • A button does not have a programmatic role, so its role (usually “button,” but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following screens: Panel - Properties – Selection; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment; Panel - Properties – Text; Panel - Stand Alone Character.
  • Multiple buttons do not have a programmatic role and name, so each button's role (usually “button,” but sometimes “link” or something else) and its name (such as "Submit" or "Cancel") are not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following screens: Artboard Panel; Close; Creating: Editing Tool - Eraser, Scissor; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Export As; Export for Screens; Import: File Place; Invite to Edit; Outline Mode; Panel - Properties – Selection; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Save the Document; Status Bar; Create New Document; Discover Panel; Header; Home screen; Open saved document; Panel – Layers; Panel - Properties – Text; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment.
  • When some buttons are pressed, their pressed state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the buttons are pressed. This occurs on the following screens: Panel - Properties - Selection; Panel - Stand Alone Transform; Create New Document.
  • Multiple custom checkbox elements do not have a programmatic role and/or their current state (checked or not checked) is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be aware that each element is a checkbox or if the checkbox is checked. This occurs on the following screens: Export for Screens; Export As; Artboard Panel; Preferences - Selection & Anchor Display; Save the Document, Open saved document, Panel – Layers.
  • Multiple elements that appear and function like a combobox do not provide their programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it. This occurs on the following screens: Artboard Panel; Create New Document; Export As; Export for Screens; Invite to Edit; Panel - Properties – Selection; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Save the Document; Status Bar; Panel - Properties – Text; Panel - Stand Alone Character.
  • Some elements that appear and function like a modal dialog do not have the required programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it. This occurs on the following screens: Artboard Panel; Preferences - Selection & Anchor Display.
  • Multiple form fields are missing an accessible name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of each element and may not understand its purpose or content or how to interact with it. This occurs on the following screens: Artboard Panel; Create New Document; Export As; Export for Screens; Invite to Edit; Panel - Properties – Selection; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Save the Document; Open saved document; Panel – Layers; Panel - Properties – Text; Panel - Stand Alone Character.
  • Multiple custom radio buttons do not have a role and/or a state (checked/unchecked) that are conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each radio button, how to use it, and whether it is checked. This occurs on the following screens: Export for Screens; Export As; Panel - Properties - Selection; Artboard Panel; Preferences - Selection & Anchor Display; Save the Document; Panel - Stand Alone Transform; Create New Document.
  • An element does not have a programmatic role that will be conveyed to assistive technology, or the role assigned is not correct (like assigning a button the role of "checkbox”), so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following screen: Create New Document.
  • An element that appears and functions like a slider control does not have the required programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, or current value or how to interact with it. This occurs on the following screen: Preferences - Selection & Anchor Display.
  • The programmatic state of an element that reveals or hides content ("expanded" or "collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of the element or the state will be misrepresented. This occurs on the following screens: Create New Document, Creating: Editing Tool - Eraser, Scissor, Creating: Editing Tool - Rotate, Scale, Reflect, Shear, Creating: Editing Tool - Type, Type on Path, Vertical Type, Creation: Selection Tool, Direct Selection Tool, Lasso Tool, Creation: Shape Tool - Paintbrush, Blob Brush, Pencil, Creation: Shape Tool - Pen Tool, Anchor Point Tool, Export for Screens, Import: File Place, Panel - Properties – Selection, Panel - Stand Alone Transform, Status Bar, Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment, Discover Panel, Panel – Layers, Panel - Properties – Text.
  • For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked. This occurs on the following screens: Creating: Editing Tool - Eraser, Scissor; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Export for Screens; Panel - Properties – Selection; Status Bar; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment; Home screen; Open saved document; Panel - Properties – Text; Panel - Stand Alone Character; Creation: Shape Tool – Curvature; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment.
  • An element does not provide its programmatic state (such as "checked"/"not checked") to assistive technology, or the state assigned is not correct, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the current state of the element or how to interact with it. This occurs on the following screens: Export for Screens; Export As; Artboard Panel; Preferences - Selection & Anchor Display; Save the Document; Close.
  • Multiple elements that appear and function like a set of tabs with their associated tab panels do not have the required programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, content, structure, or current state or how to interact with the tabs and their associated content. This occurs on the following screens: Create New Document; Export for Screens; Outline Mode; Panel - Properties – Selection; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Panel - Stand Alone Character.
  • The content of a tooltip cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content. This occurs on the following screens: Create New Document; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creation: Shape Tool – Curvature; Creating: Editing Tool - Eraser, Scissor; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creating: Editing Tool - Rotate, Scale, Reflect, Shear.
  • An element that appears and functions like a switch control does not have the required programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, or current state (such as "On" or "Off") or how to interact with it. This occurs on the following screen: Invite to Edit.
  • In a table that can be sorted by column, the sorted state (ascending or descending) of the table's columns is not conveyed to assistive technology or the state conveyed is incorrect, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the order in which the table's content is presented and whether that order is meaningful when interpreting the data. This occurs on the following screen:  Open saved document.
  • The element's name is missing or incorrect. This occurs on the following screen: Artboard Panel; Create New Document; Export for Screens; Invite to Edit; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Save the Document.
  • A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following screens:  Header; Create New Document; Invite to Edit; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creation: Shape Tool – Curvature; Creating: Editing Tool - Eraser, Scissor; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creating: Editing Tool - Rotate, Scale, Reflect, Shear.
  • A link does not have discernible text, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the destination or function of the link. This occurs on the following screens:  Header; Create New Document; Invite to Edit; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creation: Shape Tool – Curvature; Creating: Editing Tool - Eraser, Scissor; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creating: Editing Tool - Rotate, Scale, Reflect, Shear.
  • A custom user interface component is not compatible with assistive technologies, so people who use assistive technology will not be able to interact with it. This occurs on the following screens: Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment; Creation: Shape Tool – Curvature; Creating: Editing Tool - Eraser, Scissor; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creating: Editing Tool - Rotate, Scale, Reflect, Shear.

Table 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

  •  9.1.2.4 (Web)
  • 10.1.2.4 (Non-web document)
  •  11.1.2.4 (Open Functionality Software)
  • 11.1.2.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not contain live synchronized media.

1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.5 (Web)
  • 10.1.2.5 (Non-web document)
  • 11.1.2.5 (Open Functionality Software)
  • 11.1.2.5 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not contain prerecorded video content that would require audio description. 

Criteria

Conformance Level

Remarks and Explanations

1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.4 (Web)
  • 10.1.3.4 (Non-web document)
  • 11.1.3.4 (Open Functionality Software)
  • 11.1.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports

Software: Orientation of the content is not locked to either landscape or portrait unless a specific orientation is essential for the functionality.

1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.5 (Web)
  • 10.1.3.5 (Non-web document)
  • 11.1.3.5.1 (Open Functionality Software)
  • 11.1.3.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports (Not Applicable)

Software: The product’s technology does not have support for programmatic identification of input purpose.

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

  • 9.1.4.3 (Web)
  • 10.1.4.3 (Non-web document)
  • 11.1.4.3 (Open Functionality Software)
  • 11.1.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) 
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Does Not Support

Software: Most, if not all, text and images of regular text does not have the required color contrast ratio with their backgrounds. The following issues exist: 

  • The color contrast ratio between placeholder text in multiple inputs and each input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following screens: Export for Screens; Panel - Properties – Selection, Discover Panel, Version History Panel.
  • The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following screens: Artboard Panel; Create New Document; Export As; Export for Screens; Import: File Place; Invite to Edit; Panel - Properties – Selection; Panel - Stand Alone Transform; Save the Document; Status Bar; Discover Panel; Panel – Layers; Panel - Properties – Text; Panel - Stand Alone Character; Version History Panel; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creating: Editing Tool - Eraser, Scissor; Creation: Shape Tool – Curvature; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil.
  • The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of the control. This occurs on the following screens:  Artboard Panel; Close; Create New Document; Export As; Export for Screens; Panel - Properties – Selection; Panel - Stand Alone Transform; Preferences - Selection & Anchor Display; Save the Document; Status Bar; Creating: Editing Tool - Eraser, Scissor; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment.
  • The color contrast ratio between large text placed over an image and the image background is less than 3:1, so people who are colorblind or have low vision may have difficulty reading the text. Large text is text over 18 points (24 pixels) or 14 points (19 pixels) if bold. This occurs on the following screen: Creating: Editing Tool - Type, Type on Path, Vertical Type.

1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.4 (Web)
  • 10.1.4.4 (Non-web document)
  • 11.1.4.4.1 (Open Functionality Software)
  • 11.1.4.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: The product allows operating system display scaling to resize text up to 200 percent without loss of content or functionality.

1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.5 (Web)
  • 10.1.4.5 (Non-web document)
  • 11.1.4.5.1 (Open Functionality Software)
  • 11.1.4.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: The product uses text instead of images of text, except for branding elements that are considered essential.

1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.10 (Web)
  • 10.1.4.10 (Non-web document)
  • 11.1.4.10.1 (Open Functionality Software)
  • 11.1.4.10.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports

Software: The content of each screen is viewable without scrolling horizontally when the viewport is set to 320 CSS pixels wide.

1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.11 (Web)
  • 10.1.4.11 (Non-web document)
  • 11.1.4.11 (Open Functionality Software)
  • 11.1.4.11 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Does Not Support

Software: Most, if not all, boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content do not have a 3:1 color contrast ratio with adjacent color(s) or their background. The following issues exist:

  • The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the boundaries of the interactive element. This occurs on the following screens: Export for Screens; Invite to Edit; Artboard Panel; Create New Document; Discover Panel.
  • An icon (or part of the icon required to understand its content) does not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able understand the information presented by the icon. This occurs on the following screens: Preferences - Selection & Anchor Display; Version History Panel.
  • Some images or graphics (like a chart) or parts of the image/graphic required to understand its content do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able understand the information presented by the image/graphic. This occurs on the following screens: Export for Screens; Save the Document; Status Bar.
  • The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the state of the interactive elements. This occurs on the following screens: Outline Mode; Panel - Properties - Selection; Preferences - Selection & Anchor Display; Home screen; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creating: Editing Tool - Eraser, Scissor; Creation: Shape Tool – Curvature; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment.
  • The focus indicators of some interactive elements (like buttons or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when each interactive element is receiving focus. This occurs on the following screens: Artboard Panel; Export As; Export for Screens; Import: File Place; Invite to Edit; Panel - Properties – Selection; Save the Document; Status Bar; Discover Panel; Version History Panel; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creating: Editing Tool - Eraser, Scissor.

1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.12 (Web)
  • 10.1.4.12 (Non-web document)
  • 11.1.4.12 (Open Functionality Software)
  • 11.1.4.12 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Supports (Not Applicable)

Software: The product is not implemented using markup languages.

1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.13 (Web)
  • 10.1.4.13 (Non-web document)
  • 11.1.4.13 (Open Functionality Software)
  • 11.1.4.13 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Partially Supports

Software: In most cases when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. The following exceptions exist:

  • Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the screen. This occurs on the following screens: Panel - Properties - Selection; Panel - Stand Alone Transform; Discover Panel.
  • Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs on the following screens: Export for Screens; Import: File Place; Panel - Properties - Selection; Artboard Panel; Panel - Stand Alone Transform.
  • Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) does not remain visible until dismissed or invalid, so people with some disabilities, especially motor or reading disabilities, may not be able to read this additional content. This occurs on the following screens: Panel - Properties - Selection; Artboard Panel; Panel - Stand Alone Transform.

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

  • 9.2.4.5 (Web)
  • 10.2.4.5 (Non-web document) – Does not apply
  • 11.2.4.5 (Open Functionality Software) – Does not apply
  • 11.2.4.5 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  •  501 (Web)(Software) – Does not apply to non-web software
  •  504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Software: Supports (Not Applicable)

Software: This criterion does not apply to non-web software. 

2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.6 (Web)
  • 10.2.4.6 (Non-web document)
  • 11.2.4.6 (Open Functionality Software)
  • 11.2.4.6 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  •  501 (Web)(Software)
  •  504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Partially Supports

Software: Most headings and labels for form and interactive controls are informative. The following exceptions exist:

  • Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs on the following screens: Export for Screens; Panel - Properties – Selection; Status Bar; Creation: Shape Tool - Rectangle, Ellipse, Polygon, Star, Line Segment; Creation: Shape Tool - Pen Tool, Anchor Point Tool; Creation: Selection Tool, Direct Selection Tool, Lasso Tool; Creating: Editing Tool - Rotate, Scale, Reflect, Shear; Creating: Editing Tool - Type, Type on Path, Vertical Type; Creation: Shape Tool - Paintbrush, Blob Brush, Pencil; Creating: Editing Tool - Eraser, Scissor.
  • Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following screens:  Panel - Properties - Selection.

 

2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.7 (Web)
  • 10.2.4.7 (Non-web document)
  • 11.2.4.7 (Open Functionality Software)
  • 11.2.4.7 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: It is visually apparent which screen element is currently receiving keyboard focus.

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

  • 9.3.1.2 (Web)
  • 10.3.1.2 (Non-web document)
  • 11.3.1.2 (Open Functionality Software) – Does not apply
  • 11.3.1.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: Content is only presented in one language at a time, and the default language of each screen is correctly identified and can be determined programmatically.

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

  • 9.3.2.3 (Web)
  • 10.3.2.3 (Non-web document) – Does not apply
  • 11.3.2.3 (Open Functionality Software) – Does not apply
  • 11.3.2.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Software: Supports (Not Applicable)

Software: This criterion does not apply to non-web software.

3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.4 (Web)
  • 10.3.2.4 (Non-web document) – Does not apply
  • 11.3.2.4 (Open Functionality Software) – Does not apply
  • 11.3.2.4 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Software: Supports (Not Applicable)

Software: This criterion does not apply to non-web software.

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

  • 9.3.3.3 (Web)
  • 10.3.3.3 (Non-web document)
  • 11.3.3.3 (Open Functionality Software)
  • 11.3.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports

Software: If input errors are automatically detected, suggestions are provided in text for correcting the input.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.4 (Web)
  • 10.3.3.4 (Non-web document)
  • 11.3.3.4 (Open Functionality Software)
  • 11.3.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Software: Supports (Not Applicable)

Software: The product does not initiate or modify legal commitments or financial transactions for the user. It also does not modify or delete user-controllable data in data storage systems, nor does it submit user test responses.

Criteria

Conformance Level

Remarks and Explanations

4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.4.1.3 (Web)
  • 10.4.1.3 (Non-web document) – Does not apply
  • 11.4.1.3 (Open Functionality Software) – Does not apply
  • 11.4.1.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Software: Partially Supports

Software: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. The following exceptions exist:

  • Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages or they may not hear them in a timely fashion. This occurs on the following screens: Invite to Edit; Save the Document; Discover Panel; Open saved document; Panel – Layers; Version History Panel.

Table 3: Success Criteria, Level AAA

Notes: Not applicable. Adobe Illustrator was not assessed for WCAG 2.1 Level AAA conformance.

 

Revised 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

Software: Most, if not all, functionality is not usable without vision. Examples are noted in:

  • 1.1.1 Non-Text Content
  • 1.3.1 Info and Relationships
  • 1.3.2 Meaningful Sequence
  • 1.4.1 Use of Color
  • 2.1.1 Keyboard
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 4.1.2 Name, Role, Value

302.2 With Limited Vision

Software: Does Not Support

Software: Most, if not all, functionality is not usable with limited vision. Examples are noted in:

  • 1.1.1 Non-Text Content
  • 1.3.1 Info and Relationships
  • 1.3.2 Meaningful Sequence
  • 1.4.1 Use of Color
  • 1.4.3 Contrast (minimum)
  • 2.1.1 Keyboard
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 3.3.2 Labels or Instructions
  • 4.1.2 Name, Role, Value

 

302.3 Without Perception of Color

Software: Partially Supports

Software: Most functionality is usable without perception of color. Exceptions are noted in:

  • 1.4.1 Use of Color
  • 1.4.3 Contrast (minimum)

302.4 Without Hearing

Software: Supports

Software: All functionality is usable without hearing.

302.5 With Limited Hearing

Software: Supports

Software: All functionality is usable with limited hearing.

302.6 Without Speech

Software: Supports

Software: All functionality is usable without speech.

302.7 With Limited Manipulation

Software: Does Not Support

Software: Most, if not all, functionality is not usable with limited manipulation and/or requires fine motor control or simultaneous manual operations. Examples are noted in:

  • 2.1.1 Keyboard
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 4.1.2 Name, Role, Value

302.8 With Limited Reach and Strength

Software: Supports

Software: All functionality is usable with limited reach and strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

Software: Does Not Support

Software: Most, if not all, functionality is not usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Examples are noted in:

  • 1.1.1 Non-Text Content
  • 1.3.1 Info and Relationships
  • 1.3.2 Meaningful Sequence
  • 1.4.1 Use of Color
  • 2.1.1 Keyboard
  • 2.2.2 Pause, Stop, Hide
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 3.3.2 Labels or Instructions
  • 4.1.2 Name, Role, Value

Chapter 4: Hardware

Notes: The ICT covered by this report is not hardware. As such, the requirements of this chapter do not apply.

Chapter 5: Software

Notes: 

Criteria

Conformance Level

Remarks and Explanations

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.1 section

See information in WCAG 2.1 section

502 Interoperability with Assistive Technology

Heading cell – no response required

Heading cell – no response required

502.2.1 User Control of Accessibility Features

Not Applicable

The product is not platform software, so this requirement does not apply.

502.2.2 No Disruption of Accessibility Features

Supports

The product does not disrupt platform features that are defined in the platform documentation as accessibility features.

502.3 Accessibility Services

Heading cell – no response required

Heading cell – no response required

502.3.1 Object Information

Does Not Support

The role, state(s), properties, boundary, name, and description of most, if not all, objects cannot be programmatically determined, so those attributes cannot be perceived and conveyed by assistive technology. Examples are noted in:

  • 4.1.2 Name, Role, Value

502.3.2 Modification of Object Information

Partially Supports

For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions are noted in:

  • 4.1.2 Name, Role, Value

502.3.3 Row, Column, and Headers

Partially Supports

In most instances when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions are noted in:

  • 1.3.1 Info and Relationships

502.3.4 Values

Supports

When objects are present that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology.

502.3.5 Modification of Values

Supports

When an object is present that allows the user to set or modify its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology.

502.3.6 Label Relationships

Does Not Support

For most, if not all, elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is not programmatically determinable, so it cannot be perceived and conveyed by assistive technology. Examples are noted in:

  • 4.1.2 Name, Role, Value

502.3.7 Hierarchical Relationships

Partially Supports

For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions are noted in:

  • 1.3.1 Info and Relationships

502.3.8 Text

Partially Supports

Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions are noted in:

  • 1.3.2 Meaningful Sequence

502.3.9 Modification of Text

Supports

When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology.

502.3.10 List of Actions

Does Not Support

For most, if not all, elements on which one or more actions may be performed, those actions are not programmatically determinable, so that each action cannot be perceived and conveyed by assistive technology. Examples are noted in:

  • 4.1.2 Name, Role, Value

502.3.11 Actions on Objects

Does Not Support

For most, if not all, elements on which one or more actions may be performed, those actions are not available programmatically, so that each action cannot be performed using assistive technology. Examples are noted in:

  • 2.1.1 Keyboard

502.3.12 Focus Cursor

Supports

The position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology.

502.3.13 Modification of Focus Cursor

Supports

When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.

502.3.14 Event Notification

Partially Supports

In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions are noted in:

  • 4.1.2 Name, Role, Value
  • 4.1.3 Status Messages

502.4 Platform Accessibility Features

Not Applicable

The product is not platform software, so this requirement does not apply.

503 Applications

Heading cell – no response required

Heading cell – no response required

503.2 User Preferences

Supports

The product allows users to set or modify color, contrast, font type and size, and focus cursor.

503.3 Alternative User Interfaces

Not Applicable

The product does not offer an alternative user interface.

503.4 User Controls for Captions and Audio Description

Heading cell – no response required

Heading cell – no response required

503.4.1 Caption Controls

Not Applicable

The product does not contain media with an audio component that has closed captions.

503.4.2 Audio Description Controls

Not Applicable

The product does not contain media with a video component that offers audio description.

504 Authoring Tools

Heading cell – no response required

Heading cell – no response required

504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”)

See WCAG 2.1 section

See information in WCAG 2.1 section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Not Applicable

The product is not an authoring tool.

504.2.2 PDF Export

Does Not Support

The product allows for exporting PDF files that conform to PDF 1.7 but not PDF/UA-1.

504.3 Prompts

Not Applicable 

The product is not an authoring tool.

504.4 Templates

Not Applicable

The product is not an authoring tool.

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: Functional Performance Statements (FPS)

Notes:

Criteria

Conformance Level

Remarks and Explanations

4.2.1 Usage without vision

Software: Does Not Support

Software: Most, if not all, functionality is not usable without vision. Examples are noted in:

  • 1.1.1 Non-Text Content
  • 1.3.1 Info and Relationships
  • 1.3.2 Meaningful Sequence
  • 1.4.1 Use of Color
  • 2.1.1 Keyboard
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 4.1.2 Name, Role, Value
  • 4.1.3 Status Messages

4.2.2 Usage with limited vision

Software: Does Not Support

Software: Most, if not all, functionality is not usable with limited vision. Examples are noted in:

  • 1.1.1 Non-Text Content
  • 1.3.1 Info and Relationships
  • 1.3.2 Meaningful Sequence
  • 1.4.1 Use of Color
  • 1.4.3 Contrast (minimum)
  • 1.4.13 Content on Hover or Focus
  • 2.1.1 Keyboard
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 3.3.2 Labels or Instructions
  • 4.1.2 Name, Role, Value

4.2.3 Usage without perception of colour

Software: Partially Supports

Software: Most functionality is usable without perception of color. Exceptions are noted in:

  • 1.4.1 Use of Color
  • 1.4.3 Contrast (minimum)
  • 1.4.11 Non-Text Contrast

4.2.4 Usage without hearing

Software: Supports

Software: All functionality is usable without hearing.

4.2.5 Usage with limited hearing

Software: Supports

Software: All functionality is usable with limited hearing.

4.2.6 Usage with no or limited vocal capability

Software: Supports

Software: All functionality is usable without speech or other vocal output.

4.2.7 Usage with limited manipulation or strength

Software: Does Not Support

Software: Most, if not all, functionality is not usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength. Examples are noted in:

  • 1.4.13 Content on Hover or Focus
  • 2.1.1 Keyboard
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 2.5.3 Label in Name
  • 4.1.2 Name, Role, Value

4.2.8 Usage with limited reach

Software: Partially Supports

Software: Most functionality is usable by people with limited reach. Exceptions are noted in:

  • 1.4.13 Content on Hover or Focus
  • 2.5.3 Label in Name

4.2.9 Minimize photosensitive seizure triggers

Software: Supports

Software: The product does not contain flashing content or media.

4.2.10 Usage with limited cognition, language or learning

Software: Does Not Support

Software: Most, if not all, functionality is not usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Examples are noted in:

  • 1.1.1 Non-Text Content
  • 1.3.1 Info and Relationships
  • 1.3.2 Meaningful Sequence
  • 1.4.1 Use of Color
  • 1.4.13 Content on Hover or Focus
  • 2.1.1 Keyboard
  • 2.2.2 Pause, Stop, Hide
  • 2.4.4 Link Purpose (in context)
  • 2.4.6 Headings and Labels
  • 3.3.2 Labels or Instructions
  • 4.1.2 Name, Role, Value
  • 4.1.3 Status Messages

4.2.11 Privacy

Software: Not Applicable

Software: The product does not provide any specific accessibility features that impact the user's privacy.

Chapter  5: Generic Requirements

Notes:

Criteria

Conformance Level

Remarks and Explanations

5.1 Closed Functionality

Heading cell – no response required

Heading cell – no response required

 5.1.2 General

Heading cell – no response required

Heading cell – no response required

 5.1.2.1 Closed functionality

See 5.2 through 13

See information in 5.2 through 13

 5.1.2.2 Assistive technology

See 5.1.3 through 5.1.6

See information in 5.1.3 through 5.1.6

 5.1.3 Non-visual access

Heading cell – no response required

Heading cell – no response required

5.1.3.1 Audio output of visual information

Not Applicable

The product does not have closed functionality.

 5.1.3.2 Auditory output delivery including speech

Not Applicable

The product does not have closed functionality.

 5.1.3.3 Auditory output correlation

Not Applicable

The product does not have closed functionality.

 5.1.3.4 Speech output user control

Not Applicable

The product does not have closed functionality.

5.1.3.5 Speech output automatic interruption

Not Applicable

The product does not have closed functionality.

5.1.3.6 Speech output for non-text content

Not Applicable

The product does not have closed functionality.

 5.1.3.7 Speech output for video information

Not Applicable

The product does not have closed functionality.

 5.1.3.8 Masked entry

Not Applicable

The product does not have closed functionality.

5.1.3.9 Private access to personal data

Not Applicable

The product does not have closed functionality.

5.1.3.10 Non-interfering audio output

Not Applicable

The product does not have closed functionality.

5.1.3.11 Private listening volume

Not Applicable

The product does not have closed functionality.

5.1.3.12 Speaker volume

Not Applicable

The product does not have closed functionality.

5.1.3.13 Volume reset

Not Applicable

The product does not have closed functionality.

5.1.3.14 Spoken languages

Not Applicable

The product does not have closed functionality.

5.1.3.15 Non-visual error identification

Not Applicable

The product does not have closed functionality.

5.1.3.16 Receipts, tickets, and transactional outputs

Not Applicable

The product does not have closed functionality.

 5.1.4 Functionality closed to text enlargement

Not Applicable

The product does not have closed functionality.

5.1.5 Visual output for auditory information

Not Applicable

The product does not have closed functionality.

5.1.6 Operation without keyboard interface

Heading cell – no response required

Heading cell – no response required

 5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

See information in 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus

Not Applicable

The product does not have closed functionality.

5.2 Activation of accessibility features

Not Applicable

The product does not have specific documented accessibility features.

5.3 Biometrics

Not Applicable

The product does not use biological characteristics for identification or to control any functionality.

5.4 Preservation of accessibility information during conversion

Not Applicable

The product does not have functionality that converts information or communication from one format to another.

 5.5 Operable parts

Heading cell – no response required

Heading cell – no response required

5.5.1 Means of operation

Not Applicable

The product is a software application and has no physical operable parts.

5.5.2 Operable parts discernibility

Partially Supports

The product is a software application and has no physical operable parts.

5.6 Locking or toggle controls

Heading cell – no response required

Heading cell – no response required

5.6.1 Tactile or auditory status

Not Applicable

The product is a software application and has no physical locking or toggle controls.

5.6.2 Visual status

Supports

The product is a software application and has no physical locking or toggle controls.

5.7 Key repeat

Not Applicable

The product is a software application and has no physical keyboard or keypad, so it has no key repeat function.

5.8 Double-strike key acceptance

Not Applicable

The product is a software application and has no physical keyboard or keypad, so it has no functionality related to accepting identical keystrokes that occur within a specific timeframe.

5.9 Simultaneous user actions

Not Applicable

The product has no functionality requiring simultaneous actions (such as having to press multiple keys at the same time) with no alternative.

Chapter 6: ICT with Two-Way Voice Communication

Notes: The ICT covered by this report does not have any functionality that supports two-way communication. As such, the requirements of this chapter do not apply.

Chapter 7: ICT with Video Capabilities

Notes: The ICT covered by this report does not have any functionality that displays video with synchronized audio or captions. As such, the requirements of this chapter do not apply.

Chapter 8: Hardware

Notes: The ICT covered by this report is not hardware. As such, the requirements of this chapter do not apply.

Chapter 9: Web (see WCAG 2.1 section)

Notes: See WCAG 2.1 section.

Chapter 10: Non-Web Documents

Notes: The ICT covered by this report is software and does not include any non-web documents. As such, the requirements of this chapter do not apply.

 

Chapter 11: Software

Notes: 

Criteria

Conformance Level

Remarks and Explanations

11.0 General (informative)

Heading cell – no response required

Heading cell – no response required

11.1.1.1 through 11.4.1.3

See WCAG 2.1 section

See information in WCAG 2.1 section

11.5 Interoperability with assistive technology

Heading cell – no response required

Heading cell – no response required

11.5.1 Closed functionality

Heading cell – no response required

Heading cell – no response required

11.5.2 Accessibility services

Heading cell – no response required

Heading cell – no response required

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

See information in 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.4 Assistive technology

Not Applicable

The product is not assistive technology.

11.5.2.5 Object information

Does Not Support

The role, state(s), properties, boundary, name, and description of most, if not all, objects cannot be programmatically determined, so those attributes cannot be perceived and conveyed by assistive technology. Examples are noted in:

  • 4.1.2 Name, Role, Value

11.5.2.6 Row, column, and headers

Partially Supports

In most instances when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions are noted in:

  • 1.3.1 Info and Relationships

11.5.2.7 Values

Supports 

When objects are present that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology.

11.5.2.8 Label relationships

Does Not Support

For most, if not all, elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is not programmatically determinable, so it cannot be perceived and conveyed by assistive technology. Examples are noted in:

  • 4.1.2 Name, Role, Value

11.5.2.9 Parent-child relationships

Partially Supports

For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions are noted in:

  • 1.3.1 Info and Relationships

11.5.2.10 Text

Partially Supports

Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions are noted in:

  • 1.3.2 Meaningful Sequence

11.5.2.11 List of available actions

Does Not Support

For most, if not all, elements on which one or more actions may be performed, those actions are not programmatically determinable, so that each action cannot be perceived and conveyed by assistive technology. Examples are noted in:

  • 4.1.2 Name, Role, Value

11.5.2.12 Execution of available actions

Does Not Support

For most, if not all, elements on which one or more actions may be performed, those actions are not available programmatically, so that each action cannot be performed using assistive technology. Examples are noted in:

  • 2.1.1 Keyboard

11.5.2.13 Tracking of focus and selection attributes

Supports

The position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology.

11.5.2.14 Modification of focus and selection attributes

Supports

When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.

11.5.2.15 Change notification

Partially Supports

In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions are noted in:

  • 4.1.2 Name, Role, Value
  • 4.1.3 Status Messages

11.5.2.16 Modifications of states and properties

Partially Supports

For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions are noted in:

  • 4.1.2 Name, Role, Value

11.5.2.17 Modifications of values and text

Supports

When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology.

11.6 Documented accessibility usage

Heading cell – no response required

Heading cell – no response required

11.6.1 User control of accessibility features

Not Applicable

The product is not platform software, so this requirement does not apply.

11.6.2 No disruption of accessibility features

Supports

The product does not disrupt platform features that are defined in the platform documentation as accessibility features.

11.7 User preferences

Supports

The website or application allows users to set or modify color, contrast, font type and size, and focus cursor.

11.8 Authoring tools

Heading cell – no response required

Heading cell – no response required

11.8.1 Content technology

Heading cell – no response required

Heading cell – no response required

11.8.2 Accessible content creation

See WCAG 2.1 section

(If not authoring tool, enter “Not Applicable”)

See information in WCAG 2.1 section

11.8.3 Preservation of accessibility information in transformations

Not Applicable

The product is not an authoring tool.

11.8.4 Repair assistance

Not Applicable

The product is not an authoring tool.

11.8.5 Templates

Not Applicable

The product is not an authoring tool.

Chapter 12: Documentation and Support Services

Notes: Information regarding Documentation and Support 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: The ICT covered by this report does have any functionality that supports two-way communication, including the provision of relay services or access to emergency services. As such, the requirements of this chapter do not apply.