Product Description: Adobe Commerce is a leading provider of cloud commerce innovation to merchants and brands across B2C and B2B industries and was recently named a leader in the 2020 Gartner Magic Quadrant for Digital Commerce. In addition to its flagship digital commerce platform, Adobe Commerce boasts a strong portfolio of cloud-based omnichannel solutions that empower merchants to successfully integrate digital and physical shopping experiences.
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 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 be used only in WCAG 2.0 Level AAA.
WCAG 2.1 Report
This section 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.
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 (Admin): The product provides sufficient text alternatives for most non-text content. Exceptions include:
Some icons, such as those identifying the sort order in table headers and star icons representing product ratings, lack textual alternatives.
Authored Content (Web - Luma): Authors can provide text alternatives for most non-text content, such as product images. Exceptions include: CAPTCHA in Sign in and Checkout relies on an image without an alternative challenge.
Authored Content (Web - Venia): Authors can provide text alternatives for most non-text content, such as product images. Exceptions include: Icon buttons, such as navigation controls for carousels and accordion expand/collapse controls, lack appropriate textual alternatives. In Order History, all product images in order summaries have the same alt text.
Web (Admin): The product does not contain prerecorded audio-only or video-only media.
Authored Content (Web - Luma): Authors can embed video with audio description for what would otherwise be video-only media. Authored content does not contain prerecorded audio-only media.
Authored Content (Web - Venia): Authors can embed video with audio description for what would otherwise be video-only media. Authored content does not contain prerecorded audio-only media.
Web (Admin): Most visual structure and relationship information is provided through element semantics. Exceptions include:
Groups of inputs, such as “From” and “To” date inputs in filter controls, are not grouped programmatically.
Heading structure is implied visually but not identified semantically on some pages, such as order detail pages.
The sort order of tables is indicated visually with an icon but is not identified programmatically or in text.
Authored Content (Web - Luma): Authors can provide appropriate semantics for most visual structure and relationship information, such as heading structure and lists in product descriptions. Exceptions include: Programmatic heading structure in Checkout does not accurately reflect the structure of the content.
Authored Content (Web - Venia): Authors can provide appropriate semantics for most visual structure and relationship information, such as heading structure and lists in product descriptions. Exceptions include:
Error messages are not associated with their inputs.
Some groups of controls, such as radio buttons to select Shipping Methods, are not grouped programmatically.
Some heading structure conveyed visually is not identified programmatically.
Web (Admin): The product does not contain input fields that collect information about the user.
Authored Content (Web - Luma): Most input fields collecting information about the user do not programmatically convey their purpose.
Authored Content (Web - Venia): Many input fields, such as those in the Sign In form and “Quick Checkout When You Return” form, programmatically convey their purpose. Exceptions include:
Input fields in Guest Checkout and Payment forms do not provide programmatic indication of their purpose.
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Web (Admin): Most text meets minimum contrast requirements. Exceptions include:
Orange text for headings in the Notifications dropdown in the site header and orange and white buttons throughout the site.
Gray text and orange links on gray background in the site footer.
Blue link text used throughout the site.
Gray text used for secondary labels in the Catalog and Stores Configuration pages.
Authored Content (Web - Luma): In the default configuration of the Luma storefront, authors can ensure that most text meets contrast requirements. Exceptions include:
Blue “skip to content” link text on gray background.
White text on red background for global messages in the site header.
Authored Content (Web - Venia): In the default configuration of the Venia storefront, authors can ensure that most text meets contrast requirements. Exceptions include:
Gray text on white background, such as number of items on Search Results page.
Light gray text, such as format constraints on Credit Card Expiration Date and CVV inputs in checkout.
Web (Admin): The product uses text instead of images of text.
Authored Content (Web - Luma): Authors can ensure that content meets this criterion.
Authored Content (Web - Venia): Authors can ensure that content meets this criterion.
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 (Open Functionality Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web (Admin): Does Not Support
Authored Content (Web - Luma): Supports
Authored Content (Web - Venia): Supports
Web (Admin): At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. Content which does not require two-dimensional layout for meaning either relies on scrolling in two dimensions or shrinks to fit the viewport instead of reflowing into a single column, making text size difficult to read without magnification.
Authored Content (Web - Luma): At the required width of 320 CSS pixels, authored content is presented without loss of information or functionality.
Authored Content (Web - Venia): At the required width of 320 CSS pixels, authored content is presented without loss of information or functionality.
Web (Admin): Most meaningful non-text content elements have sufficient contrast. Exceptions include:
Close icon buttons in the Notifications dropdown in the site header lack adequate contrast when in focused state.
Delete and Move Image icon buttons in Catalog pages lack adequate contrast against the page background color; this contrast ratio may be lower or higher depending on the image beneath the control.
Authored Content (Web - Luma): In the default configuration of the Luma storefront, authors can ensure that most content meets this criterion. Exceptions include:
Box shadow style custom focus indicators.
Stars to indicate product ratings.
Authored Content (Web - Venia): In the default configuration of the Venia storefront, authors can ensure that most content meets this criterion. Exceptions include:
Light blue box shadow style custom focus indicators.
Carousel navigation elements in some states.
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.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web (Admin): Supports
Authored Content (Web - Luma): Supports
Authored Content (Web - Venia): Supports
Web (Admin): The product supports the required text style properties without loss of content or functionality.
Authored Content (Web - Luma): Authors can ensure that content meets this criterion.
Authored Content (Web - Venia): Authors can ensure that content meets this criterion.
Web (Admin): Most product functionality can be operated through a keyboard interface. Exceptions include:
Focus is not returned correctly from the Confirm Scope Switching modal dialog.
Some controls cannot receive keyboard focus, such as options in some dropdowns, product image upload controls, and tooltip triggers.
Some controls, such as toggle switches, calendar date pickers, sortable table headers, and drag-and-drop controls to reorder product images, cannot be operated with keyboard alone.
Authored Content (Web - Luma): Most functionality in authored content can be operated through a keyboard interface. Exceptions include:
Primary navigation items cannot be activated with keyboard.
Authored Content (Web - Venia): Most functionality in authored content can be operated through a keyboard interface. Exceptions include:
Sub-navigation items cannot be activated with keyboard.
Some buttons cannot be activated with keyboard, such as actions buttons for items in the shopping cart.
11.2.4.1 (Open Functionality 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 (Admin): Supports
Authored Content (Web - Luma): Supports
Authored Content (Web - Venia): Supports
Web (Admin): The product provides headings, which allow assistive technology users to bypass repeated blocks. However, for users without assistive technology, a bypass mechanism is not provided.
Authored Content (Web - Luma): Authored content provides a skip link to bypass repeated header content.
Authored Content (Web - Venia): Authors can implement semantic structures, such as headings, for assistive technology users to bypass repeated blocks, and can customize the storefront template to provide bypass mechanisms, such as skip links, for users without assistive technology. However, the Venia storefront does not provide a skip navigation link mechanism by default.
Web (Admin): The titles of pages describe their purpose.
Authored Content (Web - Luma): The titles of pages describe their purpose.
Authored Content (Web - Venia): The titles of most pages describe their purpose, with the exception of the Search page which has a generic title of the store name.
Web (Admin): The purpose of most links in the product can be determined from the link text alone or from the programmatic context of the link. Exceptions include:
Links to trigger tooltips do not provide textual names.
Multiple “Edit” links on Order Detail pages and on Catalog Products landing pages do not provide enough information within their context to identify what content will be edited.
Authored Content (Web - Luma): Authors can provide the purpose of most links through link text alone or through programmatic context. Exceptions include:
Multiple “Edit” links on the My Account page do not provide enough information within their context to identify what content will be edited.
Authored Content (Web - Venia): Authors can provide the purpose of links through link text alone or through programmatic context.
11.2.4.5 (Open Functionality 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 (Admin): Does Not Support
Authored Content (Web - Luma): Supports
Authored Content (Web - Venia): Supports
Web (Admin): The primary navigation is the only mechanism to locate a page within a set of pages.
Authored Content (Web - Luma): Authored content provides more than one way to locate a page in a set of pages, such as primary navigation and site search.
Authored Content (Web - Venia): Authored content provides more than one way to locate a page in a set of pages, such as primary navigation and site search.
Web (Admin): Most headings and labels are descriptive. Exceptions include:
Split buttons with a text button and a down arrow icon button next to it both have the same accessible name, such as the “Add a Product” control on the Catalog Products landing page.
Multiple controls on the same page have the same text but perform different actions, such as “Delete” buttons for image and video assets which do not identify the specific image that will be deleted.
Authored Content (Web - Luma): Authors can ensure that most content meets this criterion. Exceptions include:
Image buttons in product image galleries do not describe the button’s purpose.
Authored Content (Web - Venia): Authors can ensure that most content meets this criterion. Exceptions include:
Labels for checkboxes in the “Has Video” section of filters are not descriptive.
Web (Admin): Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Some buttons, such as Edit and calendar date picker icon buttons on several pages and “Back” and other text buttons on Order Detail pages, lack a visible focus indicator.
Authored Content (Web - Luma): Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Pagination controls in list pages.
Close buttons on some dialogs.
Star controls for rating products.
Authored Content (Web - Venia): Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Carousel navigation controls.
Search results pagination controls.
Increase and decrease quantity buttons on Product Detail pages and in Shopping Bag.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
Web (Admin): In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:
Some custom selection controls, such as the “Scope” control on several pages, have a visible label which is not included in the control’s accessible name.
Some controls have visible labels but lack accessible names, such as some date inputs in Product Details and Marketing pages.
Authored Content (Web - Luma): Authors can ensure that the accessible names of most controls contain the text of their visible labels. Exceptions include:
The control to select the number of results per page on list pages has a visible label but lacks a valid accessible name.
Authored Content (Web - Venia): Authors can ensure that the accessible names of most controls contain the text of their visible labels. Exceptions include:
Some inputs, such as in site Search and Sign In forms, have visible labels but lack accessible names.
“Sign In” button in the header has an accessible name of “Toggle My Account Menu”.
11.3.1.2 (Open Functionality 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)
Web (Admin): Supports
Authored Content (Web - Luma): Supports
Authored Content (Web - Venia): Supports
Web (Admin): Content is only presented in one language at a time.
Authored Content (Web - Luma): Authors can ensure that content is only presented in one language at a time.
Authored Content (Web - Venia): Authors can ensure that content is only presented in one language at a time.
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.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)
Web (Admin): Supports
Authored Content (Web - Luma): Supports
Authored Content (Web - Venia): Supports
Web (Admin): Components do not initiate a change of context when focused.
Authored Content (Web - Luma): Authors can ensure that content meets this criterion.
Authored Content (Web - Venia): Authors can ensure that content meets this criterion.
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.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)
Web (Admin): Partially Supports
Authored Content (Web - Luma): Partially Supports
Authored Content (Web - Venia): Supports
Web (Admin): Changes of context do not occur automatically on most user input. Exceptions include:
The “Scope” control on several pages triggers a change of context on selection either by reloading the page or by shifting focus to a confirmation dialog.
Authored Content (Web - Luma): Authors can ensure that most content meets this criterion. Exceptions include:
Making a selection from the Sort control on list pages triggers a page reload.
Authored Content (Web - Venia): Authors can ensure that content meets this criterion.
Web (Admin): Components with the same functionality are identified consistently.
Authored Content (Web - Luma): Authors can ensure that components with the same functionality are identified consistently in a set of pages.
Authored Content (Web - Venia): Authors can ensure that most components with the same functionality are identified consistently in a set of pages. Exceptions include:
Inconsistent references to “Cart” and “Shopping bag” throughout the product
Web (Admin): Where input errors are automatically detected, items in error are identified and error messages are provided in text.
Authored Content (Web - Luma): Most input errors are identified and described to the users in text. Exceptions include:
When an error is identified in the Zip/Postal code field in the Estimate Shipping and Tax form, an error message becomes visible beneath the input, but no notification is provided to alert screen reader users to the presence of the error.
Authored Content (Web - Venia): Although input errors are identified in text beneath the input, no notification is provided to alert the user to the presence of errors.
Web (Admin): When processing returns and editing user-controllable data, data entered by the user is checked for input errors and the user is given an opportunity to correct them. Changes to user-controllable data are reversible.
Authored Content (Web - Luma): When modifying account information, data is checked for input errors and the user is given the opportunity to correct the errors, and their submission is reversible. When placing an order, data is checked and the user is given the opportunity to correct the errors, and a mechanism is available for users to review, confirm, and correct their information before finalizing the submission.
Authored Content (Web - Venia): When modifying account information, data is checked for input errors and the user is given the opportunity to correct the errors, and their submission is reversible. When placing an order, data is checked and the user is given the opportunity to correct the errors, and a mechanism is available for users to review, confirm, and correct their information before finalizing the submission.
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.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)
Web (Admin): Partially Supports
Authored Content (Web - Luma): Partially Supports
Authored Content (Web - Venia): Supports
Web (Admin): In most product functions, 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. Exceptions include:
Duplicate IDs are present in the DOM for some pages.
Checkboxes in tables have nested labels.
In Order Totals tables, the tfoot element precedes the tbody element.
Authored Content (Web - Luma): In most product functions, 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. Exceptions include:
Duplicate IDs are present in the DOM for some pages.
Invalid attributes are used in product image gallery markup.
Authored Content (Web - Venia): 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 (Admin): Most user interface components provide programmatic name, role, state, and value information. Exceptions include:
Some controls, such as inputs in tables, some Search and Close icon buttons, and date inputs, lack an accessible name.
Some controls that expand other content do not provide state information.
Some controls lack appropriate role information, such as image upload controls and options in some custom comboboxes.
Authored Content (Web - Luma): Most user interface components in authored content provide programmatic name, role, state, and value information. Exceptions include:
Some controls, such as the control to select the number of results per page on list pages, lack an accessible name.
Some input elements have an ID referenced by multiple label elements.
The main image in the product image gallery is interactive but lacks an appropriate role.
Authored Content (Web - Venia): Most user interface components in authored content provide programmatic name, role, state and value information. Exceptions include:
Some inputs, such as in site Search and Sign In forms, lack accessible names.
Modal dialogs, such as mobile navigation and filters flyout panels, do not provide an appropriate dialog role or name.
Buttons that expand other content, such as currency selector, Sign In, and mini cart controls in the header, do not identify their expanded or collapsed state.
Some icon buttons, such as navigation controls in product image galleries, lack accessible names.
Web (Admin): When status messages do not receive focus, the product does not provide the update to assistive technology. Examples include:
Results of searches, such as the keyword filter added and the number of results returned, are added to the page in text but are not announced by assistive technology.
Status notifications made visible after form submissions, such as success or general error messages, are not announced by assistive technology.
Authored Content (Web - Luma): Authored content does not contain status messages.
Authored Content (Web - Venia): Authored content does not contain status messages.
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
Criteria
Conformance Level
Remarks and Explanations
302.1 Without Vision
Web: Partially Supports
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, complex images are missing short and detailed text alternatives. Decorative image is missing empty text alternative.
As noted in 1.3.1 Info and Relationships, the data table not structured properly and most form controls do not have programmatic label and group label association. As noted in 1.3.2 Meaningful Sequence, the reading order is not logical and intuitive for the graph, tooltip, and menu contents. As noted in 2.1.1 Keyboard, most interactive elements are not operable by keyboard. As noted in 2.4.3 Focus Order, focus order is not logical when the modal is opened and closed. As noted in 3.3.2 Labels or Instructions, form controls do not have visual label and instructions missing for the drop area. As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
302.2 With Limited Vision
Web: Partially Supports
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.3.3 Sensory Characteristics, the today’s date information is not conveyed to screen reader users.
As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements. As noted in 1.4.4 Resize text, some part of the page content is lost, clipped off and overlapped when the page is zoomed to 200%. As noted in 2.4.7 Focus Visible, visible focus indicator is missing for the interactive elements such as tooltip button and menu item.
302.3 Without Perception of Color
Web: Partially Supports
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color, link text has insufficient contrast with the surrounding text and color alone is used to convey the selected state of the button.
As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements.
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: Users with limited manipulation who use speech recognition or switch control software will have difficulty navigating to controls. Exception:
As noted in 2.1.1 Keyboard, image buttons, menu, tooltips are not keyboard accessible, modal does not have a method to dismiss it using keyboard alone.
302.8 With Limited Reach and Strength
Web: Partially Supports
Web: Users with limited reach and strength will have difficulty navigating to controls. Exceptions:
As noted in 2.1.1 Keyboard, image buttons, menu, tooltips are not keyboard accessible, modal does not have a method to dismiss it using keyboard alone.
302.9 With Limited Language, Cognitive, and Learning Abilities
Web: Partially Supports
Web: The product is functional for users 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. The product provides labeling for most controls. However, some buttons label is not descriptive to convey its purpose and some form controls missing a visual label.
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.
Notes: According to C.4 Functional Performance, this section is informative only.
Criteria
Conformance Level
Remarks and Explanations
4.2.1 Usage without vision
Web: Partially Supports
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, complex images are missing short and detailed text alternatives. Decorative image is missing empty text alternative.
As noted in 1.3.1 Info and Relationships, the data table not structured properly and most form controls do not have programmatic label and group label association. As noted in 1.3.2 Meaningful Sequence, the reading order is not logical and intuitive for the graph, tooltip, and menu contents. As noted in 2.1.1 Keyboard, most interactive elements are not operable by keyboard. As noted in 2.4.3 Focus Order, focus order is not logical when the modal is opened and closed.As noted in 3.3.2 Labels or Instructions, form controls do not have visual label and instructions missing for the drop area. As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value. As noted in 4.1.3 Status Messages, the status messages like loading content, warnings, error and confirmation messages are not automatically announced.
4.2.2 Usage with limited vision
Web: Partially Supports
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.3.3 Sensory Characteristics, the today’s date information is not conveyed to screen reader users.
As noted in 1.4.3 Contrast (Minimum), some text does not meet the minimum contrast requirements. As noted in 1.4.4 Resize text, some part of the page content is lost, clipped off and overlapped when the page is zoomed to 200%. As noted in 1.4.10 Reflow, part of page content is does not reflow to fit horizontally and lost or clipped off at the required width of 320 CSS pixels. As noted in 1.4.11 Non-text Contrast, Icons, graph lines, focus indicator and visual boundaries does not meet the minimum contrast requirements. As noted in 2.4.7 Focus Visible, visible focus indicator is missing for the interactive elements such as tooltip button and menu item.
4.2.3 Usage without perception of colour
Web: Partially Supports
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color, link text has insufficient contrast with the surrounding text and color alone is used to convey the selected state of the button.
As noted in 1.4.3 Contrast (Minimum), some text does not meet the minimum contrast requirements. As noted in 1.4.11 Non-text Contrast, Icons, graph lines, focus indicator and visual boundaries does not meet the minimum contrast requirements.
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 without 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: Users with limited manipulation or strength who use speech recognition or switch control software will have difficulty navigating to controls. Exceptions include:
As noted in 2.1.1 Keyboard, image buttons, menu, tooltips are not keyboard accessible, modal does not have a method to dismiss it using keyboard alone.
As noted in 1.4.13 Content on Hover or Focus, the additional content disappears when the user moves the mouse pointer to the content and also it is not dismissible via keyboard without moving mouse hover or keyboard focus.
4.2.8 Usage with limited reach
Web: Partially Supports
Web: Users with limited reach will have difficulty navigating to controls. Exceptions include:
As noted in 2.1.1 Keyboard, image buttons, menu, tooltips are not keyboard accessible, modal does not have a method to dismiss it using keyboard alone.
As noted in 1.4.13 Content on Hover or Focus, the additional content disappears when the user moves the mouse pointer to the content and also it is not dismissible via keyboard without moving mouse hover or keyboard focus.
4.2.9 Minimize photosensitive seizure triggers
Web: Supports (Not Applicable)
Web: The product does not contain flashing content or media.
4.2.10 Usage with limited cognition, language or learning
Web: Partially Supports
Web: The product is functional for users 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. The product provides labeling for most controls. However, some button labels are not descriptive to convey their purpose and some form controls missing a visual label.
4.2.11 Privacy
Web: Supports (Not Applicable)
Web: The product does not provide any privacy features.
The product does have specific documented accessibility features and allows preferences to be set for accessibility.
5.3 Biometrics
Not Applicable
Biometrics is not included in the product.
5.4 Preservation of accessibility information during conversion
Not Applicable
The product does not convert content.
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
Partially Supports
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. Exceptions are noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.
5.6.1 Tactile or auditory status
Not Applicable
Tactile or auditory status is not included in the product.
5.6.2 Visual status
Supports
Visual status of controls is discernable 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 to achieve any functionality.
11.8.3 Preservation of accessibility information in transformations
Not Applicable
The product does not provide restructuring transformations or re-coding transformations.
11.8.4 Repair assistance
Not Applicable
The product does not have accessibility checking functionality.
11.8.5 Templates
Partially Supports
Storefronts Venia and Luma enable authors to create a range of web content. For most of these kinds of content, the product enables authors to create content which conforms to WCAG 2.1 Levels A and AA. Exceptions include:
As noted in 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.3.5 Identify Input Purpose, 1.4.1 Use of Color, 1.4.3 Contrast (Minimum), 1.4.11 Non-text Contrast, 2.1.1 Keyboard, 2.4.3 Focus Order, 2.4.4 Link Purpose (In Context), 2.4.6 Headings and Labels, 2.4.7 Focus Visible, 2.5.3 Label in Name, 3.2.2 On Input, 3.3.1 Error Identification, 3.3.2 Labels or Instructions, 4.1.1 Parsing, and 4.1.2 Name, Role, Value, the Luma storefront does not fully support authors in creating WCAG conformant web content.
As noted in 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 1.3.5 Identify Input Purpose, 1.4.3 Contrast (Minimum), 1.4.11 Non-text Contrast, 2.1.1 Keyboard, 2.4.1 Bypass Blocks, 2.4.2 Page Titled, 2.4.6 Headings and Labels, 2.4.7 Focus Visible, 2.5.3 Label in Name, 3.2.4 Consistent Identification, 3.3.1 Error Identification, 3.3.2 Labels or Instructions, and 4.1.2 Name, Role, Value, the Venia storefront does not fully support authors in creating WCAG conformant web content.
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.
