Adobe AEM Core Components
Accessibility Conformance Report published by Adobe
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% coverage). The remainder are missing from our extraction, not necessarily from Adobe's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 30 criteria
- Supports
- 17
- Partially supports
- 11
- Does not support
- 0
- Not applicable
- 2
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 13
- Partially supports
- 6
- Does not support
- 0
- Not applicable
- 1
- 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 (73)
| 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, such as images and icons. Exceptions include: Some decorative icons, such as chevrons in the Breadcrumb and Accordion components, are not identified as decorative and have textual alternatives that are not descriptive. A linked logo image in the PDF viewer lacks a textual alternative. Product images in the Related Products and Product Carousel components lack alt attributes. Product images in the Product Teaser component have URLs for text alternatives, instead of text that describes the image or lin |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Web: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Web: Where the product contains audio content in video, such as YouTube videos in the Embed component, captions can be provided in the embedded media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Web: Where the product contains video content, such as YouTube videos in the Embed component, audio descriptions can be provided in the embedded media. |
| 1.2.4 | Captions (Live) | AA | Supports | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Web: Where the product contains video content, such as YouTube videos in the Embed component, audio descriptions can be provided in the embedded media. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Web: Most visual structure and relationship information, such as lists, headings, and landmarks, is provided through element semantics. Exceptions include: The Language Navigation component does not have a label to distinguish it from other navigation landmarks. Tables generated using the Text component lack programmatic row or column headers. Visible heading text for PDFs in the PDF Viewer component is hidden from assistive technology. Some changes in content, such as updates to the user's location in the search results in the PDF Viewer component, are not announced to screen reader users. He |
| 1.3.2 | Meaningful Sequence | A | Supports | Web: The product presents content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 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 | Supports | Web: Input fields that collect information about the user programmatically convey their purpose. |
| 1.4.1 | Use of Color | A | Partially Supports | Web: Most functions of the product do not convey information through color alone. Exception: Links in List and PDF Viewer components are distinguished from surrounding text by color alone. |
| 1.4.2 | Audio Control | A | Supports | Web: The product does not contain audio that plays automatically. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include: Text overlaid on background images, such as in the Product Teaser and Container components, lacks adequate color contrast depending on the colors in the background image. Text identifying image file information in the Download component does not provide adequate contrast against its background. |
| 1.4.4 | Resize text | AA | Supports | Web: The product allows browser zoom to resize text up to 200 percent without loss of content or functionality. |
| 1.4.5 | Images of Text | AA | Supports | Web: The product uses text instead of images of text. |
| 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: In the PDF Viewer component, controls are cut off and content requires scrolling in two dimensions. Embedded videos do not resize proportionally. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: Most meaningful non-text content elements have sufficient contrast. Exceptions include: Completed and remaining portions of the bar in the Progress Bar component do not provide adequate contrast against each other. Previous and Next icon buttons in the Product Carousel component, and navigation dot icon buttons in the Carousel component, lack adequate contrast. |
| 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.1.1 | Keyboard | A | Partially Supports | Web: Most product functionality can be operated through a keyboard interface. Exceptions include: In the PDF Viewer component, focus is not managed correctly for some interactions and several controls either cannot receive focus or cannot be activated with keyboard alone. In the Commerce Navigation component, focus is not managed correctly when the menu is opened and closed. Actions menus in the Mini Cart component cannot be dismissed with keyboard alone without selecting from the menu. In the Embed component, the Pinterest embed cannot be operated with a keyboard. |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Web: The product does support character key shortcuts in accessible way. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Web: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Web: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Web: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Partially Supports | Web: The product provides headings and landmarks, which allow assistive technology users to bypass repeated blocks, such as navigation. However, for users without assistive technology, a bypass mechanism is not provided. |
| 2.4.2 | Page Titled | A | Supports | Web: The title of a page describes its purpose. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: Most components receive focus in a meaningful order. Exceptions include: In the PDF Viewer component, an “Enable accessibility for screen readers” control receives focus although it is visually hidden and is placed in the focus order following the content that it would control, rather than preceding it. In the Mini Cart component, some controls receive focus when they are visually hidden or obscured. |
| 2.4.4 | Link Purpose (In Context) | A | Partially Supports | Web: 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: In the Social Sharing component, the Pinterest link does not identify its purpose. In the Quick Search component, some linked images have no textual alternative. |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through navigation and search. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most headings and labels are descriptive. Exception: In the Cart Trigger component, information about the number of items in the cart is visually part of the button, but it is not included in the accessible name or available to assistive technology. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: Linked images in the Teaser component. Some icon buttons in the PDF Viewer, Product Carousel, and Mini Cart components. Accordion buttons in the Accordion component. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: The product does not rely on multipoint or path-based gestures. |
| 2.5.2 | Pointer Cancellation | A | Supports | Web: Product functions that use a single pointer are completed when the user releases the pointer. |
| 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. Exception: In the Reset Password component, accessible names for fields do not match the visible label text. |
| 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.1.2 | Language of Parts | AA | Supports | Web: Content is only presented in one language at a time. |
| 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.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.1 | Error Identification | A | Supports | Web: Where input errors are automatically detected, such as in the Reset Password component, items in error are identified and error messages are provided as text. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: Labels are provided for most input fields. Exception: The coupon code input in the Checkout component is labelled only with placeholder text. |
| 3.3.3 | Error Suggestion | AA | Supports | Web: Where input errors are automatically detected, such as in the Reset Password component, suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | Web: The product does not process legal commitments or financial transactions. When modifying user data, such as user password in the Reset Password component, input is checked and is reversible. |
| 4.1.1 | Parsing | A | Partially Supports | Web: 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. Exception: The Product Carousel component includes duplicate IDs. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Web: Most user interface components in the product provide accessible names, appropriate roles, and expose their state and/or value to assistive technology. Exceptions include: Some icon buttons in the Product Carousel, PDF Viewer, Commerce Navigation, and Mini Cart components lack accessible names. The Quantity input in the Mini Cart lacks an accessible name. Progress bars in the Progress Bar component lack accessible names. Invalid roles are used in the Product Carousel and Related Products components. |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: Most product functions do not require status messages. In some cases, when status messages are present but do not receive focus, the update is not provided to assistive technology. Example: In the Quick Search and Reset Password components, screen reader users are not alerted to status updates. |
| 4.2.1 | Usage without vision | - | Partially Supports | Web: Most functions of the product are usable without vision. Exceptions include: As noted in 1.1.1 Non-text Content , some meaningful images lack textual alternatives, and some decorative images are not appropriately hidden from assistive technology. As noted in 1.3.1 Info and Relationships , some tables are not structured correctly, some heading information is not appropriately conveyed to assistive technology, a dialog lacks appropriate structure, a navigation landmark is not labeled to distinguish it from other navigation landmarks, and some error and constraint text is not associated with |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most functions of the product are usable with limited vision. As noted in 1.4.3 Contrast (Minimum) , text overlaid on background images may not provide adequate contrast, and some text in the Download component lacks adequate contrast. As noted in 1.4.10 Reflow , content in the PDF Viewer component and embedded video in the Embed component do not reflow without content loss. As noted in 1.4.11 Non-text Contrast , progress bars and navigation icon buttons in some components lack adequate contrast. |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most functions of the product are usable without perception of color. Exception: As noted in 1.4.1 Use of Color , some links are distinguished from surrounding text using color alone., some links are distinguished from surrounding text using color alone. |
| 4.2.4 | Usage without hearing | - | Supports | Web: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Web: The product does not require the use of hearing. |
| 4.2.6 | Usage without vocal capability | - | Supports | Web: The product does not require the use of speech.. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Web: Most functionality in the product is usable with limited manipulation and strength. Exceptions include: As noted in 2.1.1 Keyboard , focus is not managed correctly in some interface components, menus in one component cannot be dismissed with keyboard alone, and a Pinterest embed is not keyboard accessible. As noted in 2.4.1 Bypass Blocks , a mechanism is not provided to bypass repeated blocks of content for users without assistive technology. As noted in 2.4.3 Focus Order , focus order is not logical for a control in the PDF Viewer component, and some controls in the Mini Cart receive foc |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Web: Users with limited reach will have no 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 | - | Supports | Web: The product does not contain flashing content or media. |
| 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. Exception: As noted in 3.3.2 Labels and Instructions , an input in the Checkout component lacks a persistent visible label. |
| 4.2.11 | Privacy | - | Supports | Web: The product maintains user privacy when accessibility features are used. Example: The product gives screen reader users sufficient opportunity to use their own private listening devices when reading personal data. |
| 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. Exception: Some graphical on-screen buttons do not have an accessible name. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | The product does not have locking or toggle controls. |
| 5.6.2 | Visual status | - | Not Applicable | The product does not have locking or toggle controls. |
| 7.1.1 | Captioning playback | - | Supports | Captioning playback is supported in embedded YouTube videos. |
| 7.1.2 | Captioning synchronization | - | Supports | Synchronization is preserved between the captions and the corresponding audio in embedded YouTube videos. |
| 7.1.3 | Preservation of captioning | - | Not Applicable | The product does not transmit, convert, or record video with synchronized audio. |
| 7.1.4 | Captions characteristics | - | Supports | The product allows users to adapt the displayed characteristics of captions in embedded YouTube videos. |
| 7.1.5 | Spoken subtitles | - | Supports | If closed captions are provided in embedded YouTube videos, the product allows spoken output. |
| 7.2.1 | Audio description playback | - | Does Not Support | Embedded YouTube videos do not provide a mechanism to select and play closed audio description. |
| 7.2.2 | Audio description synchronization | - | Does Not Support | Embedded YouTube videos do not have a mechanism to play audio description. |
| 7.2.3 | Preservation of audio description | - | Not Applicable | The product does not transmit, convert, or record video. |
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 September 2021. 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.