ACR Index Accessibility Conformance Reports for software

Adobe Illustrator 2024

Accessibility Conformance Report published by Adobe

Partial extraction. We read 30 of 31 Level A and 19 of 24 Level AA criteria from this document (89% coverage). The remainder are missing from our extraction, not necessarily from Adobe's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.

Conformance by level

Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.

Source: View the original report published by Adobe.

These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.

All reported criteria (91)

Conformance as stated by Adobe in its published report.
CriterionNameLevel ConformanceRemarks from vendor
1.1.1 Non-text Content A 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 occ
1.2.1 Audio-only and Video-only (Prerecorded) A Not Applicable Software: The product does not contain prerecorded audio-only or video-only media.
1.2.2 Captions (Prerecorded) A Not Applicable Software: The product does not contain prerecorded synchronized media.
1.2.3 Audio Description or Media Alternative (Prerecorded A Not Applicable Software: The product does not contain prerecorded video content that would require audio description or a media alternative.
1.3.1 Info and Relationships A 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 a
1.3.2 Meaningful Sequence A 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
1.3.3 Sensory Characteristics A Supports Software: Instructions do not rely solely on sensory characteristics.
1.4.1 Use of Color A 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
1.4.2 Audio Control A Not Applicable Software: The product does not contain audio that plays automatically.
2.1.1 Keyboard A 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
2.1.2 No Keyboard Trap A 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 A Supports Software: The product provides character key shortcuts, and each shortcut activates only when the appropriate user interface component receives focus.
2.2.1 Timing Adjustable A Not Applicable Software: The product does not include time limits.
2.2.2 Pause, Stop, Hide A 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: Editi
2.3.1 Three Flashes or Below Threshold A Not Applicable Software: The product does not contain flashing content.
2.4.1 Bypass Blocks A Not Applicable Software: This criterion does not apply to non-web software.
2.4.2 Page Titled A Supports Software: The title of the software and each screen describes its respective purpose.
2.4.3 Focus Order A 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) A 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:
2.5.1 Pointer Gestures A Not Applicable Software: The product does not rely on multipoint or path-based gestures.
2.5.2 Pointer Cancellation A 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 A 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 acce
2.5.4 Motion Actuation A Not Applicable Software: The product does not have functionality operated by device motion or user motion.
3.1.1 Language of Page A Supports Software: The language of each screen is correct and can be determined programmatically.
3.2.1 On Focus A 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 A 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.
3.3.1 Error Identification A 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 A 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:
4.1.1 Parsing A 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 A 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 so
1.2.4 Captions (Live) AA Not Applicable Software: The product does not contain live synchronized media.
1.2.5 Audio Description (Prerecorded) AA Not Applicable Software: The product does not contain prerecorded video content that would require audio description.
1.3.4 Orientation AA 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 AA Not Applicable Software: The product’s technology does not have support for programmatic identification of input purpose.
1.4.3 Contrast (Minimum) AA 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 c
1.4.4 Resize text AA 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 AA Supports Software: The product uses text instead of images of text, except for branding elements that are considered essential.
1.4.10 Reflow AA 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 AA 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; Invit
1.4.12 Text Spacing AA Not Applicable Software: The product is not implemented using markup languages.
1.4.13 Content on Hover or Focus AA 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,
2.4.5 Multiple Ways AA Not Applicable Software: This criterion does not apply to non-web software.
2.4.6 Headings and Labels AA 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, Dir
2.4.7 Focus Visible AA Supports Software: It is visually apparent which screen element is currently receiving keyboard focus.
3.2.3 Consistent Navigation AA Not Applicable Software: This criterion does not apply to non-web software.
3.2.4 Consistent Identification AA Not Applicable Software: This criterion does not apply to non-web software.
3.3.3 Error Suggestion AA 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) AA 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.
4.1.3 Status Messages AA 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.
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.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
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.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.
4.2.1 Usage without vision - 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 - 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 - 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 - Supports Software: All functionality is usable without hearing.
4.2.5 Usage with limited hearing - Supports Software: All functionality is usable with limited hearing.
4.2.6 Usage with no or limited vocal capability - Supports Software: All functionality is usable without speech or other vocal output.
4.2.7 Usage with limited manipulation or strength - 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 - 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 - Supports Software: The product does not contain flashing content or media.
4.2.10 Usage with limited cognition, language or learning - 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 - Not Applicable Software: The product does not provide any specific accessibility features that impact the user's privacy.
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.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.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.
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.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.

Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.

Get told when this changes

This report is dated April 2024. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.

Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.