Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.4Rev)
Product Information
Name of Product/Version: Adobe Experience Manager Sites / Cloud
Report Date: September 2024
Product Description: Deliver content faster using an AI-powered content management system that’s built on a scalable, agile, and secure cloud-native foundation. Experience Manager Sites gives you the robust features and flexible tools you need to create and deploy personalized experiences for your whole audience — on any screen.
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 Experience Manager involved extensive use of leading assistive technology such as screen readers and screen magnifiers, 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.X Report
The Guideline tables below 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.x Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Web: The product provides sufficient text alternatives for most instances of 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.
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 instructions are not linked to the field programmatically.
Some combobox components include groups of options where the group label is not announced by the screen reader.
Some tooltips are not accessible with a screen reader.
Some user interface components have incorrect ARIA roles and states applied.
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.
Web: The product uses text instead of images of text, except for branding elements that are considered essential.
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.1.4.10 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: 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 pane and has a horizontal scroll bar.
The Content Fragment Admin Table screen overruns the viewport when viewed at 320px width.
The Content Fragment Admin Toolbar overruns the viewport when viewed at a width of 320px.
Many popup containers do not fit within the viewport when viewed at 320px width. For example, Help and Notifications popup.
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 (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.1.4.12 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: 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.
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.
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
11.2.4.1 (Open Functionality Software) – Does not apply
11.2.4.1 (Closed Software) – Does not apply
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)
Revised Section 508
501 (Web)(Software) – Does not apply to non-web software
504.2 (Authoring Tool)
602.3 (Support Docs) – Does not apply to non-web docs
Web: 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.
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 static content such as plain text is included in the tab focus path.
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.
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.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
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.
Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data.
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.4.1.1.2 (Closed 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: 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.
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 components have incorrect ARIA attributes.
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 reader.
Some search results status messages are not announced, such as “No results found” or the number of results.
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 sequence that affects its meaning.
As noted in 2.1.1 Keyboard, many 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 keyboard focus is not managed well, which could be confusing and frustrating for people without vision.
As noted in 3.2.2 On Input, a switch on the CF Editor page causes a change in context without warning.
As noted in 4.1.2 Name, Role, Value, many user interface components are missing an accessible name, role or do not communicate state. Some components have the wrong role or state applied.
302.2 With Limited Vision
Web: Partially Supports
Web: Most of the 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 minimum contrast requirement for non-text objects.
302.3 Without Perception of Color
Web: 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.
302.4 Without Hearing
Web: Supports (Not Applicable)
Web: The product does not require the use of hearing.
302.5 With Limited Hearing
Web: Supports (Not Applicable)
Web: The product does not require the use of hearing.
302.6 Without Speech
Web: Supports (Not Applicable)
Web: The product does not require the use of speech.
302.7 With Limited Manipulation
Web: Partially Supports
Web: Most of the functions of the product are usable with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard, many 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. Other features such as annotations and demographics are not accessible using a keyboard.
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 interface components receive focus twice because they have other components nested inside of them. These issues increase the number of tab stops needed to navigate the site, which can cause discomfort to people with limited manipulation who rely solely on keyboard to use the site.
302.8 With Limited Reach and Strength
Web: Supports
Web: The functions of the product are usable with limited reach and strength.
302.9 With Limited Language, Cognitive, and Learning Abilities
Web: 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.
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 sequence that affects its meaning.
As noted in 2.1.1 Keyboard, many 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 keyboard focus is not managed well, which could be confusing and frustrating for people without vision.
As noted in 3.2.2 On Input, a switch on the CF Editor page causes a change in context without warning.
As noted in 4.1.2 Name, Role, Value, many user interface components are missing an accessible name, role or do not communicate state. Some components have the wrong role or state applied.
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.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 minimum contrast requirement for non-text objects.
4.2.3 Usage without perception of colou
Web: 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
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: 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 interface components receive focus twice because they have other components nested inside of them. These issues increase the number of tab stops needed to navigate the site, which can cause discomfort to people with limited manipulation who rely solely on keyboard to use the site.
4.2.8 Usage with limited reach
Web: Supports
Web: The product is functional with limited reach.
4.2.9 Minimize photosensitive seizure triggers
Web: 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
Web: 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
Web: Supports (Not Applicable)
Web: The product does not ask for or display legal, financial or personal data.
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)
Cookie Settings
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 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.
