Adobe-commerce-storefront-2025
Accessibility Conformance Report published by Adobe
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.
Level A — 32 criteria
- Supports
- 12
- Partially supports
- 10
- Does not support
- 1
- Not applicable
- 9
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 12
- Partially supports
- 8
- Does not support
- 2
- Not applicable
- 2
- Not evaluated
- 0
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 (94)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | 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 detai |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.3.1 | Info and Relationships | A | Does Not Support | 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 |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | 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. |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | Partially Supports | 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: Pr |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | Partially Supports | 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. |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | Web: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Web: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | Web: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Web: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | 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. |
| 2.4.2 | Page Titled | A | Supports | Web: The titles of pages describe their purpose. |
| 2.4.3 | Focus Order | A | Partially Supports | 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 _Orde |
| 2.4.4 | Link Purpose (In Context) | A | Partially Supports | 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 surro |
| 2.5.1 | Pointer Gestures | A | Supports | Web: All functionality that can be operated with a pointer can be operated with single-point actions. |
| 2.5.2 | Pointer Cancellation | A | Supports | 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. |
| 2.5.3 | Label in Name | A | Partially Supports | 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 |
| 2.5.4 | Motion Actuation | A | Not Applicable | Web: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Web: The language is programmatically determinable within the product. |
| 3.2.1 | On Focus | A | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Web: Changes of context do not occur automatically on user input. |
| 3.2.6 | Consistent Help | A | Supports | 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. |
| 3.3.1 | Error Identification | A | Partially Supports | 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 |
| 3.3.2 | Labels or Instructions | A | Partially Supports | 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)). |
| 3.3.7 | Redundant Entry | A | Supports | 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. |
| 4.1.1 | Parsing | A | Supports | 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. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | 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 con |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description. |
| 1.3.4 | Orientation | AA | Supports | Web: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Partially Supports | 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 fo |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | 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. |
| 1.4.4 | Resize text | AA | Partially Supports | 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. |
| 1.4.5 | Images of Text | AA | Supports | Web: The product uses text instead of images of text, except for branding elements that are considered essential. |
| 1.4.10 | Reflow | AA | Partially Supports | 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 popove |
| 1.4.11 | Non-text Contrast | AA | Does Not Support | 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 |
| 1.4.12 | Text Spacing | AA | Supports | Web: The product supports the required text style properties without loss of content or functionality. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Web: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion. |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through multiple ways |
| 2.4.6 | Headings and Labels | AA | Partially Supports | 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 differe |
| 2.4.7 | Focus Visible | AA | Partially Supports | 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). |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Partially Supports | 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. |
| 2.5.7 | Dragging Movements | AA | Supports | 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. |
| 2.5.8 | Target Size (Minimum) | AA | Partially Supports | 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 |
| 3.1.2 | Language of Parts | AA | Supports | Web: Changes of language for passages or phrases can be programmatically determined. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Components with the same functionality are identified consistently. |
| 3.3.3 | Error Suggestion | AA | Supports | Web: Where input errors are automatically detected, suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | 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. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | 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. |
| 4.1.3 | Status Messages | AA | Does Not Support | 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; |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.3.1 | Object Information | - | Partially Supports | 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: As noted in 4.1.3 Status Messages |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not display video. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not provide prerecorded media that requires 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 | - | Not Applicable | The product is not an authoring tool. |
| 4.2.1 | Usage without vision | - | Partially Supports | 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 | - | 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 i |
| 4.2.3 | Usage without perception of colour | - | 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 | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.6 | Usage with no or limited vocal capability | - | Not Applicable | Web: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | 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 | - | 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 | - | 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 | - | 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 Co |
| 4.2.11 | Privacy | - | Not Applicable | Web: The product does not ask for or display legal, financial, or personal data. |
| 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.7 | Access without speech | - | Not Applicable | The product does not have closed functionality. |
| 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.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 |
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 November 2025. 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.