Adobe Experience Manager (AEM) Cloud Service Sites
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
- 6
- Partially supports
- 14
- Does not support
- 0
- Not applicable
- 10
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 6
- Partially supports
- 9
- Does not support
- 1
- Not applicable
- 4
- 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 (68)
| 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 images and non-text content, such as icon buttons. Exceptions include: Some meaningful images do not have a text alternative. Some decorative images are not hidden from assistive technologies. Some UI components that rely on icons for a label (such as buttons or checkboxes) have an accessible name that does not describe the action that it performs. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded prerecorded synchronized media. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded 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.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.1 | Info and Relationships | A | Partially Supports | Web: Most visual structure and relationship information is provided through element semantics or object information or available in text. Exceptions include: Some content contains text that functions as a heading but does not have the heading role. Some headings do not reflect the content structure. Some related items are not marked up in a list. A table does not have semantic table headings. Some elements have incorrect ARIA attributes. Some text is not accessible using a screen reader. Some buttons have other user interface components nested inside of them. Some error messages or instruction |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions include: In the Publication popup dialog, the table headers are presented out of sequence with the column data. |
| 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 | Not Applicable | Web: The product does not contain input fields that collect information about the user. |
| 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 used to indicate when an element has focus in Sites Homepage – List View. |
| 1.4.2 | Audio Control | A | Not Applicable | 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: Some plain text does not meet the minimum contrast requirement of 4.5:1 against the background colors for normal sized text (below 24px or 18.5px and bold). Some user interface components do not meet the minimum contrast requirements for text. This includes changes to states such as buttons that can be pressed or not pressed or when hovered over with a mouse. Annotations text do not meet the minimum contrast requirements. |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Exceptions include: The Search combobox overruns the viewport when viewed at 200% zoom. The Folder names in Asset Picker Tree are cut of when viewed at 200% zoom. The Date Picker Hours and Minute are cut off when viewed at 200% zoom. |
| 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 | Does Not Support | Web: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. Loss of information or functionality occurs and content which does not require two-dimensional layout for meaning relies on scrolling in two dimensions. Examples include: Many modals do not reflow when viewed at 320px width, content either overlaps, or overruns the viewport and cannot be brought into view. In some cases, a horizontal scroll bar is displayed. The Left Rail has a fixed width and covers up most of the screen when viewed at 320px. The main content area is reduced to a narrow pan |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: Most meaningful non-text content elements such as icons, or styling applied to communicate different states of user interface components, have sufficient contrast. Exceptions include: Some focus indicators do not meet the minimum contrast requirement. Some form field borders do not meet the minimum contrast requirement. Checkmarks on colours in the Annotation modal do not meet the minimum contrast requirement. The selected state in the Tree View in the Content Fragment Admin Folder navigation. |
| 1.4.12 | Text Spacing | AA | Partially Supports | Web: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include: In the Content Fragment Admin, Universal Editor WKND sample and Editor - Layout Preview when text spacing is increased, some of the text does not change. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: Exceptions include: Tooltips which appear on hover, become hidden when the mouse pointer moves over it. |
| 2.1.1 | Keyboard | A | Partially Supports | Web: Most product functionality can be operated through a keyboard interface. Exceptions include: The Universal Editor WKND sample canvas is not keyboard accessible. Some rich text editor toolbars are not accessible using a keyboard. Many drag and drop operations are not accessible using a keyboard. Annotations are not keyboard accessible. Some instances of tree directory are not keyboard accessible. Some window splitters are not focusable using a keyboard. Saved Search combobox options are not keyboard accessible. Many buttons are not keyboard accessible. Keyboard focus is not managed to some |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Partially Supports | Web: The product provides unmodified character key shortcuts for example, buttons in the side toolbar have single character key shortcuts that cannot be turned off or modified. |
| 2.2.1 | Timing Adjustable | A | Partially Supports | Web: Exceptions include: Some notifications are dismissed automatically after 5 seconds. |
| 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 | Partially Supports | Web: The product provides mechanisms such as skip links, headings and landmarks, which allows assistive technology users to bypass repeated blocks such as header and navigation elements. However, in some cases the skip link does not move keyboard focus to the target destination. |
| 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: Some visually hidden elements receive focus using a keyboard. Some interactive elements do not receive focus in a logical order. Sometimes a button will expand the left rail, but the left rail content does not follow the button in keyboard focus path. Sometimes activating a button reveals new content, such as a tool bar but places focus on the last element in the toolbar instead of the start of the new content. Some buttons within table cells have links nested inside them which makes them receive focus twice. Some st |
| 2.4.4 | Link Purpose (In Context) | A | Partially Supports | Web: Exceptions include: Some pages include cards which are clickable links. The link wraps all the card’s content which forms the accessible name for the link and is long and confusing. |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through the search, navigation, tree directory and various views. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Exceptions include: Some button labels are not descriptive of the action they perform. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: Some user interface components such as links and buttons, checkbox do not display a visible focus indicator when focused using a keyboard. Items in the Tree Directory in the Content Fragment Picker modal and Select Tags modal do not display a visible focus indicator when focused using a keyboard. |
| 2.5.1 | Pointer Gestures | A | Not Applicable | Web: The product does not rely on multipoint or path-based gestures. |
| 2.5.2 | Pointer Cancellation | A | Not Applicable | Web: Most 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. Exceptions include Some buttons have labels which are different to their accessible name. In the tree directory, a screen reader sometimes announces the last level items incorrectly. Some fields have labels that do not match the accessible name, or only part of the visible label is included in the accessible name, for example, the value of a drop down is the accessible name, but the label is not included. |
| 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 | Not Applicable | Web: The language is programmatically determinable within the product. |
| 3.1.2 | Language of Parts | AA | Supports | Web: The language is programmatically determinable within the product. |
| 3.2.1 | On Focus | A | Partially Supports | Web: In most product functions, components do not initiate a change of context when focused. Exceptions include: When the Filter field in the Left Rail receives focus it causes content to reload unexpectedly. When the Preview button in the Editor Layout Preview page receives focus it changes the state of the button unexpectedly. |
| 3.2.2 | On Input | A | Partially Supports | Web: Exceptions include: A switch on the CF Editor page causes a change in context without warning. |
| 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, items in error are identified and error messages are provided text. |
| 3.3.2 | Labels or Instructions | A | Supports | Web: Labels are provided for input fields. |
| 3.3.3 | Error Suggestion | AA | Partially Supports | Web: Where input errors are automatically detected, suggestions for correction are provided to the user. Exceptions include: In the Help popup dialog, the Description field in the Feedback tab displays error styles without an error message. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 4.1.1 | Parsing | A | Supports | Web: 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: Most user interface components have an accessible name, role and value. However, user interface components in some product functions do not provide programmatic name, role, state, or value information. Examples include: Some user interface components do not have an accessible name. Some user interface components do not have a role. Some user interface components do not communicate their state (expanded / collapsed or pressed / not pressed) or incorrectly communicate state. Some modal dialogs and toolbars do not have an accessible name. Some iFrames do not have a title. Some user interface |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: Exceptions include: Some loading states are not announced by the screen reader. When navigating child nodes of the Tree Directory the loading state is not announced by the screen reader. In the Publications popup dialog, when items are checked or unchecked, the number of items to be published are not announced by the screen reader. Character counts on Rich Text Editors are not announced by the screen reader. In the Image (metadata tab) and Teaser (text tab) modals, when an Error occurs, error styles are applied to a tab that is not active. The error state is not announced by the screen re |
| 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 do not have alternate text, and some decorative images are not hidden from assistive technologies. As noted in 1.1.1 Non-Text Content , the accessible name of some user interface components does not describe the action they perform. As noted in 1.3.1 Information and Relationships , some information that is provided visually is not available through semantic HTML or text. As noted in 1.3.2 Meaningful Sequence , some content is presented in the wrong seque |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most functions of the product are usable with limited vision. Exceptions include: As noted in 1.4.4 Resize Text , some content overruns the viewport or is covered up by sticky elements when the text is resized by 200%. As noted in 1.4.10 Reflow , some content overruns the viewport, or in some places text truncates or overlaps when the site is viewed at 320px width. As noted in 1.4.3 Contrast (minimum) , some text does not meet the minimum contrast requirement. As noted in 1.4.11 Non-text Contrast , some user interface components such as icons, form fields and focus styles do not meet the |
| 4.2.3 | Usage without perception of colou | - | Partially Supports | Web: Most functions of the product are usable without perception of color. Exceptions include: As described in 1.4.1 Use of Color , some user interface components use color to convey changes in state, such as when they are pressed or not pressed or receive focus using a keyboard. As described in 1.4.3 Contrast (minimum) , some text does not meet the minimum color contrast requirements. As described in 1.4.11 Non-text Contrast , some user interface components such icons, form field border or focus styles do not meet the minimum color contrast requirements for non-text objects. |
| 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 without 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 of the functions of the product are usable with limited manipulation. Exceptions include: As noted in 2.1.1 Keyboard , some user interface components are not accessible when using a keyboard. This includes the core functionality required to edit web pages, such as rich text editor toolbars and drag and drop functionality used to add and move components and assets. As noted in 2.4.3 Focus Order , some user interface components do receive focus in a logical order. With some components when an action is performed, keyboard focus is lost and sent to the top of the page. Some user interfa |
| 4.2.8 | Usage with limited reach | - | Supports | Web: The product is functional with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | Web: As noted in 2.3.1 Three Flashes or Below Threshold , content in the product does not flash. |
| 4.2.10 | Usage with limited cognition, language or learning | - | 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 or accessibility features of the platform. |
| 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 | |
| 5.1.5 | Visual output for auditory information | - | Not Applicable | |
| 5.1.7 | Access without speech | - | Not Applicable | |
| 5.5.1 | Means of operation | - | Not Applicable | |
| 5.5.2 | Operable parts discernibility | - | Partially Supports | |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | |
| 5.6.2 | Visual status | - | Supports |
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 2024. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.