Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
Name of Product/Version: Adobe Commerce Storefront
Product Description: A collection of tools and technologies from Adobe designed to make it easy to create, manage, and customize modern, high-performance storefronts.
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: Testing Adobe Commerce Storefront involved extensive use of leading assistive technology such as screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
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 only be used in WCAG Level AAA criteria.
WCAG 2.2 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.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Web: The product provides sufficient text alternatives for most instances of non-text content,
Exceptions include:
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 page: Catalog (Product Listing Page (PLP)).
An active image has a text alternative that does not convey the same purpose as the image. People who are blind and/or use a screen reader will be given different information than sighted users. This occurs on the following page: Product details (Product Details Page (PDP)).
An image does not have a text alternative that contains essential text from the visual image, so people who are blind and/or use a screen reader will not understand the information available in the image. This occurs on the following page: Product Recommendations (PDP).
An image does 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 and if it is an active image, will not understand its function. This occurs on the following pages: Cart; Customer account; Create user; Password Reset (Create Password).
Web: Some structure and relationship information are provided through element semantics/object information or in text. However, most structure and relationship information are not provided programmatically or in text. Exceptions include:
A group of form controls is not programmatically associated with their group label, so the purpose of individual controls in the group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following page: Checkout (signed in).
Text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Cart; Orders _Order Details; Checkout (guest); Checkout (signed in); Customer account; Customer orders; Catalog (Product Listing Page (PLP)); Search results page; Product details (Product Details Page (PDP)); Mini Cart; Create user; Customer addresses; Edit Cart Item (pop up); Forgot password; Order confirmation; Order search; Password Reset (Create Password); Product Recommendations (PDP); Product Recommendations (PLP); Search - Order Details; Sign in popover; User sign in; Customer returns.
Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Customer orders.
A set of checkboxes is not programmatically grouped, so the group label for the 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 page: Search results page.
A set of radio buttons is not programmatically grouped, so the group label for the 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 pages: Checkout (guest); Checkout (signed in); Catalog (Product Listing Page (PLP)); Search results page.
Web: The product presents most content in a meaningful sequence. Exceptions include:
Screen readers can read content outside the modal dialog, so people who are blind and/or use a screen reader may become disoriented or confused. This occurs on the following pages: Cart; Orders _Order Details.
Web: Most functions of the product do not convey information through color alone. Exceptions include:
Color is the only visual method used to identify a link, and a link text's contrast ratio 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 the link. This occurs on the following page: Create user.
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 page: Product details (Product Details Page (PDP)).
Web: Most product functionality can be operated through a keyboard interface. Exceptions include:
A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following pages: Product details (Product Details Page (PDP)); Wishlist.
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
Web: Supports
Web: The product provides robust heading structure to bypass repeated blocks of navigation. A Skip to Main Content link is provided in global navigaiton.
Web: Most components receive focus in a meaningful order. Exceptions include:
Keyboard focus is lost or misplaced as a result of user interaction or content update or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following page: Cart.
Keyboard focus is not confined within a modal, so people who use the keyboard to navigate content (including screen reader users) will be able to navigate outside of the modal, which may cause them to become disoriented. This occurs on the following pages: Cart; Orders _Order Details; Product details (Product Details Page (PDP)).
Keyboard focus is not moved to a modal when the modal opens, so people who use the keyboard to navigate content (including screen reader users) may not be able to use the modal and in some cases may not know it is present on the page. This occurs on the following pages: Cart; Orders _Order Details.
When a modal closes, keyboard focus is not returned to the control that opened the modal or to another logical location, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following pages: Cart; Orders _Order Details; Product details (Product Details Page (PDP)).
Web: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. Exceptions include:
Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following page: Mini Cart.
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 pages: Checkout (guest); Checkout (signed in); Catalog (Product Listing Page (PLP)); Search results page; Search popover.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard
Web: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click.
Web: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:
An interactive element (such as a link, button, or form input) does not have an accessible name because its visible label is not programmatically associated with the element, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following page(s): Catalog (Product Listing Page (PLP)); Search results page.
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 pages: Cart; Orders _Order Details; Checkout (guest); Checkout (signed in); Customer account; Customer orders.
Web: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.
Web: Most input errors are identified and described to the users in text. Exceptions include:
A form field with an error is not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field the error occurred. This occurs on the following pages: Cart; Checkout (guest); Checkout (signed in); Customer account; Create user; Customer addresses; Forgot password; Order search; Password Reset (Create Password); Search Order; Sign in popover; User sign in.
Web: Labels are provided for most input fields. Exceptions include:
The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following pages: Cart; Checkout (guest); Checkout (signed in).
The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Cart; Product details (Product Details Page (PDP)).
Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique.
Web: User interface components in some product functions do not provide programmatic name, role, state, or value information. Examples include:
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 page: Header.
A button does not have a programmatic role and name, so its 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 page: Wishlist.
An element that appears and functions like a modal dialog does not have the required attributes in its HTML code needed to provide its 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 the element or how to interact with it. This occurs on the following pages: Cart; Orders _Order Details.
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 pages: Header; Cart.
For an element that allows 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 the element, the options available, and whether the element or an option is currently checked. This occurs on the following pages: Checkout (guest); Checkout (signed in); Catalog (Product Listing Page (PLP)); Search results page; Product details (Product Details Page (PDP)); Account Left Nav.
The state of the currently displayed carousel slide is indicated visually but not programmatically, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand which slide in the carousel is currently visible. This occurs on the following page: Wishlist.
A link does not have discernible link 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 pages: Catalog (Product Listing Page (PLP)); Search results page.
An element does not have an attribute in its HTML code that will 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 page: Header.
The total number of slides in the carousel is indicated visually but not programmatically, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand how many slides the carousel contains. This occurs on the following page: Wishlist.
Multiple iframes do not have a programmatic title that is 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 or content of each iframe without browsing its content. This occurs on the following pages: Checkout (guest); Checkout (signed in); Order confirmation.
Multiple links do not have discernible link 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 each link. This occurs on the following pages: Wishlist; Search popover.
Multiple select elements are missing a programmatic name, 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 form field or what input it requires. This occurs on the following pages: Catalog (Product Listing Page (PLP)); Search results page.
Web: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Examples include:
No programmatic purpose is provided for an input element (like a text input field), so browsers or assistive technology are not able to automatically suggest information to fill in the input. This occurs on the following pages: Cart; Checkout (guest); Checkout (signed in); Customer account; Create user; Customer addresses; Order search; Search Order.
The programmatic purpose provided for an input element (like a text input field) is not accurate, so information automatically suggested by the browser or assistive technology to fill in the input will be incorrect. This occurs on the following pages: Customer account; Create user; Forgot password; Order search; Search Order; Sign in popover; User sign in.
Web: Most text meets minimum contrast requirements. Exceptions include:
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 pages: Cart; Checkout (guest); Checkout (signed in); Customer account; Product details (Product Details Page (PDP)); Create user; Customer addresses; Edit Cart Item (pop up); Forgot password; Order search; Password Reset (Create Password); Search Order; Sign in popover; User sign in.
Web: Most content is readable and functional when browser zoom is set to 200% of its initial size. Exceptions include:
Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following page: Mini Cart.
Web: At the required width of 320 CSS pixels, most content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Exceptions include:
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs on the following pages: Mini Cart; Sign in popover; Search popover.
Web: 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. Examples include:
The visual boundary of an interactive element (like a radio button or input field) does 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 page: Wishlist.
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 pages: Cart; Checkout (guest).
The indicator for the state of an interactive element (like a checkbox or radio button) does 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 element. This occurs on the following pages: Catalog (Product Listing Page (PLP)); Search results page.
An image or graphic (like a chart) or part of the image/graphic 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 image/graphic. This occurs on the following page: Undo Delete Cart Item.
The focus indicator of an interactive element (like a button or input field) does 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 the interactive element is receiving focus. This occurs on the following pages: Footer; Cart; Orders _Order Details; Checkout (guest); Checkout (signed in); Customer account; Catalog (Product Listing Page (PLP)); Search results page; Product details (Product Details Page (PDP)); Wishlist; Mini Cart; Create user; Customer addresses; Edit Cart Item (pop up); Forgot password; Order confirmation; Order search; Password Reset (Create Password); Product Recommendations (PDP); Product Recommendations (PLP); Search - Order Details; Search Order; Sign in popover; User sign in.
The visual boundary of an interactive element (like a radio button or input field) does 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 page: Product details (Product Details Page (PDP)).
Web: Most headings and labels for form and interactive controls are informative. Exceptions include:
A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: Header; Cart; Checkout (guest); Checkout (signed in); Customer account; Catalog (Product Listing Page (PLP)); Search results page; Product details (Product Details Page (PDP)).
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 pages: Cart; Checkout (guest); Checkout (signed in); Customer account; Catalog (Product Listing Page (PLP)); Search results page; Wishlist; Mini Cart; Undo Delete Cart Item.
Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following page: Checkout (signed in).
Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include:
A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following pages: Cart; Orders _Order Details; Checkout (guest); Checkout (signed in); Customer account; Customer orders; Customer addresses.
Web: All functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
Web: he size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Exceptions include:
A target's hit area does not meet minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs on the following page: Wishlist.
Web: The product does not process legal commitments or financial transactions. [When editing files,] changes to user-controllable data are reversible or can be confirmed before finalizing.
Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the Web site.
Web: When status messages do not receive focus, the product does not provide the update to assistive technology. Exceptions include:
A status message is 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 message or they may not hear it in a timely fashion. This occurs on the following pages: Cart; Checkout (guest); Checkout (signed in); Customer account; Customer orders; Catalog (Product Listing Page (PLP)); Search results page; Product details (Product Details Page (PDP)); Wishlist; Mini Cart; Undo Delete Cart Item; Create user; Customer addresses; Edit Cart Item (pop up); Forgot password; Order search; Password Reset (Create Password); Search Order; Sign in popover; User sign in.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable. The product was not assessed for WCAG 2.2 AAA conformance.
Web: Most functionality is usable without vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.6 Headings and Labels
As noted in 3.3.1 Error Identification
As noted in 4.1.2 Name, Role, Value
302.2 With Limited Vision
Web: Partially Supports
Web: Most functionality is usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.4 Resize Text
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
302.3 Without Perception of Color
Web: Partially Supports
Web: Most functionality is usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
302.4 Without Hearing
Web: Supports (Not Applicable)
Web: The product does not require the use of hearing.
302.5 With Limited Hearing
Web: Supports (Not Applicable)
Web: The product does not require the use of hearing.
302.6 Without Speech
Web: Supports (Not Applicable)
Web: The product does not require the use of speech.
302.7 With Limited Manipulation
Web: Partially Supports
Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.3 Focus Order
As noted in 2.4.7 Focus Visible
As noted in 2.4.6 Headings and Labels
As noted in 4.1.2 Name, Role, Value
302.8 With Limited Reach and Strength
Web: Supports
Web: The product is functional with limited reach and strength.
302.9 With Limited Language, Cognitive, and Learning Abilities
Web: Partially Supports
Web: Most functionality is 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. Exceptions are noted in:
The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include:
As 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 include:
As noted in 4.1.2 Name, Role, Value
502.3.3 Row, Column, and Headers
Supports
In all 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.
502.3.4 Values
Partially Supports
For most objects 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. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.5 Modification of Values
Partially Supports
For most objects that allow 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. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.6 Label Relationships
Partially Supports
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
502.3.7 Hierarchical Relationships
Partially Supports
When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:
As 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 include:
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.1 Info and Relationships
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
Partially Supports
For most of the elements on which one or more actions may be performed, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.11 Actions on Objects
Partially Supports
For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:
As noted in 2.1.1 Keyboard Navigation
502.3.12 Focus Cursor
Partially Supports
For most of the elements 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. Exceptions include:
As noted in 2.4.7 Focus Visible
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 include:
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.
Web: Most functionality is usable without vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.6 Headings and Labels
As noted in 3.3.1 Error Identification
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
4.2.2 Usage with limited vision
Web: Partially Supports
Web: Most functionality is usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.4 Resize Text
As noted in 1.4.10 Reflow
As noted in 1.4.11 Non-Text Contrast
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
4.2.3 Usage without perception of colour
Web: Partially Supports
Web: Most functionality is usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.11 Non-Text Contrast
4.2.4 Usage without hearing
Web: Supports (Not Applicable)
Web: The product does not require the use of hearing.
4.2.5 Usage with limited hearing
Web: Supports (Not Applicable)
Web: The product does not require the use of hearing.
4.2.6 Usage with no or limited vocal capability
Web: Supports (Not Applicable)
Web: The product does not require the use of speech.
4.2.7 Usage with limited manipulation or strength
Web: Partially Supports
Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 1.3.5 Identify Input Purpose
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.3 Focus Order
As noted in 2.4.7 Focus Visible
As noted in 2.4.6 Headings and Labels
As noted in 2.5.3 Label in Name
As noted in 4.1.2 Name, Role, Value
4.2.8 Usage with limited reach
Web: Partially Supports
Web: Most of the product is functional with limited reach and strength. Exceptions include:
As noted in 1.3.5 Identify Input Purpose
As noted in 2.5.3 Label in Name
4.2.9 Minimize photosensitive seizure triggers
Web: Supports
Web: All functionality may be operated in a mode that minimizes the potential for triggering photosensitive seizures
4.2.10 Usage with limited cognition, language or learning
Web: Partially Supports
Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.5 Identify Input Purpose
As noted in 1.4.1 Use of Color
As noted in 1.4.10 Reflow
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
4.2.11 Privacy
Web: Supports (Not Applicable)
Web: The product does not ask for or display legal, financial, or personal data.
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.1.7 Access without speech
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. The product instead relies upon platform accessibility features.
5.3 Biometrics
Not Applicable
The product does not use biometric forms of user identification or control. All functionality is accessible through standard input methods (keyboard, mouse, UI).
5.4 Preservation of accessibility information during conversion
Not Applicable
The product does not convert the content.
5.5 Operable parts
Heading cell – no response required
Heading cell – no response required
5.5.1 Means of operation
Not Applicable
The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate.
5.5.2 Operable parts discernibility
Not Applicable
The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision.
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
Tactile or auditory status is not included in the product.
5.6.2 Visual status
Not Applicable
Visual status of controls isn’t discernible in the product
5.7 Key repeat
Not Applicable
Key repeat functionality is not found in the product.
5.8 Double-strike key acceptance
Not Applicable
Double -strike key acceptance is not found in the product.
5.9 Simultaneous user actions
Not Applicable
The product does not require simultaneous user actions for core functionality. All actions triggered by key combinations are also available via the graphical user interface using mouse or sequential keyboard navigation.
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.
You can control how Adobe websites use cookies and similar technologies by making choices below. But note that if you disable cookies and similar technologies entirely, Adobe websites may not function properly.
Cookies are small text files stored by your web browser when you use websites. There are also other technologies that can be used for similar purposes like HTML5 Local Storage and local shared objects, web beacons, and embedded scripts. These technologies help us do things like remembering you and your preferences when you return to our sites, measure how you use the website, conduct market research, and gather information about the ads you see and interact with.
You can make choices in the menu below about what cookies and other technologies you want us to use on Adobe sites when you visit them from this browser. You can always change those choices later by clicking on the Cookie Preferences link at the bottom of the page.
If enabled:
We can improve your experience by tailoring the site and the content to things we think might be of interest
We can better keep track of your preferences — like what language you prefer to use
We will better understand your likely interests so we can provide you more relevant Adobe ads and content on non-Adobe websites and in non-Adobe apps
It will help us improve the performance of our website and those of our partners who use the Adobe Experience Cloud
If disabled:
We won’t be able to remember you from session to session so the experience may not be tailored to your interests
You’ll still have access to the content of the site but certain features that depend on cookies may not function
You’ll still see ads, they just may not be as relevant to you
General information
You can control how Adobe websites use cookies and similar technologies by making choices below. But note that if you disable cookies and similar technologies entirely, Adobe websites may not function properly.
Cookies are small text files stored by your web browser when you use websites. There are also other technologies that can be used for similar purposes like HTML5 Local Storage, web beacons, and embedded scripts. These technologies help us do things like remembering you and your preferences when you return to our sites, measure how you use the website, conduct market research, and gather information about the ads you see and interact with.
You can make choices in the menu below about what cookies and other technologies you want us to use on Adobe sites when you visit them from this browser. You can always change those choices later by clicking on the Cookie Preferences link at the bottom of the page.
If enabled:
We can improve your experience by tailoring the site and the content to things we think might be of interest
We can better keep track of your preferences — like what language you prefer to use
We will better understand your likely interests so we can provide you more relevant Adobe ads and content on non-Adobe websites and in non-Adobe apps
It will help us improve the performance of our website and those of our partners who use the Adobe Experience Cloud
If disabled:
We won’t be able to remember you from session to session so the experience may not be tailored to your interests
We’ll still count your use of our site and services
You’ll still have access to the content of the site but certain features that depend on cookies may not function
You’ll still see ads, they just may not be as relevant to you
Operate the site and core servicesOperate site and measure engagement
Always active
These cookies are required, and they are used to enable the site and related services core functionality. Without them the site could not operate, so they cannot be disabled.
These cookies enable the site and related services’ core functionality and collect statistics about user engagement, such as counting active use to help us understand trends. These cookies cannot be disabled.
Measure performance
These cookies are used to analyze site usage to measure and improve performance. Without them Adobe cannot know what content is most valued and how often unique visitors return to the site, making it hard to improve information we offer to you.
These cookies are used to analyze site usage to measure and improve performance. Without them Adobe cannot know what content is most valued, making it hard to improve information we offer to you.
Extend functionality
These cookies are used to enhance the functionality of Adobe sites such as remembering your settings and preferences to deliver a personalized experience; for example, your username, your repeated visits, preferred language, your country, or any other saved preference.
Personalize advertising
These cookies are used to enable Adobe and our partners to serve ads more relevant to your interests. Without them you will still see ads, but they might not be as relevant to you.
