Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.4Rev)
Product Information
- Name of Product/Version: Adobe Experience Manager Sites / Service Pack 6.5
- 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.
- Date: September 2024
- Contact information: access@adobe.com
- 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:
Level AA (Yes)
Level AAA (No)
Level AA (Yes)
Level AAA (No)
Terms
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.
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.1.1 (Web)
- 10.1.1.1 (Non-web document)
- 11.1.1.1.1 (Open Functionality Software)
- 11.1.1.1.2 (Closed Functionality Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: The product provides sufficient text alternatives for most instances of images and non-text content, such as icon buttons. Exceptions include:
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.
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.1 (Web)
- 10.1.2.1 (Non-web document)
- 11.1.2.1.1 (Open Functionality Software)
- 11.1.2.1.2.1 and 11.1.2.1.2.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)
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.2 (Web)
- 10.1.2.2 (Non-web document)
- 11.1.2.2 (Open Functionality Software)
- 11.1.2.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)
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.3 (Web)
- 10.1.2.3 (Non-web document)
- 11.1.2.3.1 (Open Functionality Software)
- 11.1.2.3.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)
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.4 (Web)
- 10.1.2.4 (Non-web document)
- 11.1.2.4 (Open Functionality Software)
- 11.1.2.4 (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)
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.5 (Web)
- 10.1.2.5 (Non-web document)
- 11.1.2.5 (Open Functionality Software)
- 11.1.2.5 (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)
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.1 (Web)
- 10.1.3.1 (Non-web document)
- 11.1.3.1.1 (Open Functionality Software)
- 11.1.3.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: 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 have nested elements that should not be part of the heading.
Some related items are not marked up in a list.
Some buttons have the appearance of checkboxes but do not function as checkboxes.
Some radio buttons are not grouped programmatically.
A table does not have semantic table headings.
Some elements have incorrect ARIA attributes.
Some text is not accessible using a screen reader.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.2 (Web)
- 10.1.3.2 (Non-web document)
- 11.1.3.2.1 (Open Functionality Software)
- 11.1.3.2.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: The product presents most content in a meaningful sequence. Exceptions include:
In the (Service pack) Editor - Edit Layout screen, a ruler that shows pixel measurements includes a marker for smaller screens and tablets which are presented to screen reader users after the ruler instead of at the correct measurement.
The number of results found for the filter are presented without context in amongst other user interface components and away from the search results.
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.3 (Web)
- 10.1.3.3 (Non-web document)
- 11.1.3.3 (Open Functionality Software)
- 11.1.3.3 (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)
1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.3.4 (Web)
- 10.1.3.4 (Non-web document)
- 11.1.3.4 (Open Functionality Software)
- 11.1.3.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.3.5 (Web)
- 10.1.3.5 (Non-web document)
- 11.1.3.5.1 (Open Functionality Software)
- 11.1.3.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.1 (Web)
- 10.1.4.1 (Non-web document)
- 11.1.4.1 (Open Functionality Software)
- 11.1.4.1 (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: Most functions of the product do not convey information through color alone. Exceptions include:
Color is used to convey the state of buttons in the rich text editor of the Teaser modal.
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.2 (Web)
- 10.1.4.2 (Non-web document)
- 11.1.4.2 (Open Functionality Software)
- 11.1.4.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)
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.3 (Web)
- 10.1.4.3 (Non-web document)
- 11.1.4.3 (Open Functionality Software)
- 11.1.4.3 (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: 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 non-text objects such as meaningful icons do not meet the minimum contrast requirement of 3:1 against the background colors.
Some user interface components do not meet the minimum contrast requirements for text or non-text objects. This includes changes to states such as buttons that can be pressed or not pressed or when hovered over with a mouse.
The focus indicator for some user interface components does not meet the minimum contrast requirement of 3:1 against the background colors.
Annotations text and colors do not meet the minimum contrast requirements.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.4 (Web)
- 10.1.4.4 (Non-web document)
- 11.1.4.4.1 (Open Functionality Software)
- 11.1.4.4.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: The product allows browser zoom to resize text up to 200 percent without loss of content or functionality. Exceptions include:
The Demographics and Edit Layout toolbars overrun the viewport when the page is viewed at 200% zoom.
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.5 (Web)
- 10.1.4.5 (Non-web document)
- 11.1.4.5.1 (Open Functionality Software)
- 11.1.4.5.2 (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)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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: 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.
1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.4.11 (Web)
- 10.1.4.11 (Non-web document)
- 11.1.4.11 (Open Functionality Software)
- 11.1.4.11 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
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.
In the (Service Pack) Editor - Annotation Modal, the selected state of colors and the annotation arrows do not meet the minimum contrast requirement.
In the (Service Pack) Sites Home Page - List View, the table row unselected state does not meet the minimum contrast requirement
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: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include:
In some of the Service Pack screens, text truncates when text size is increased.
In the Service Pack Editor – Canvas, text in the Search modal is cut off when text spacing is increased.
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.1.4.13 (Web)
- 10.1.4.13 (Non-web document)
- 11.1.4.13 (Open Functionality Software)
- 11.1.4.13 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.1 (Web)
- 10.2.1.1 (Non-web document)
- 11.2.1.1.1 (Open Functionality Software)
- 11.2.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: Most product functionality can be operated through a keyboard interface, however many of the editing features are not accessible using only a keyboard. Exceptions include:
The editable sections in canvas in the (Service Pack) editor screens are not keyboard accessible.
Some rich text editor toolbars are not accessible using a keyboard.
Drag and drop operations are not accessible using a keyboard.
Annotations are not keyboard accessible.
Many user interface components in the Demographic toolbar are not keyboard accessible.
Some instances of tree directory are not keyboard accessible.
Title attributes used to label icon buttons are not keyboard accessible.
Some window splitters are not focusable using a keyboard.
Saved Search options are not keyboard accessible.
Many buttons are not keyboard accessible.
Keyboard focus is not managed to some modal dialogs upon opening or while they are open.
In some places keyboard focus is unexpectedly sent to the top of the page or the start of a region when an action is performed.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.2 (Web)
- 10.2.1.2 (Non-web document)
- 11.2.1.2 (Open Functionality Software)
- 11.2.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: Exceptions include:
Keyboard focus gets trapped when selecting a device in the Edit Layout Toolbar while using a screen reader.
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.1.4 (Web)
- 10.2.1.4 (Non-web document)
- 11.2.1.4.1 (Open Functionality Software)
- 11.2.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.1 (Web)
- 10.2.2.1 (Non-web document)
- 11.2.2.1 (Open Functionality Software)
- 11.2.2.1 (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)
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.2 (Web)
- 10.2.2.2 (Non-web document)
- 11.2.2.2 (Open Functionality Software)
- 11.2.2.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)
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.3.1 (Web)
- 10.2.3.1 (Non-web document)
- 11.2.3.1 (Open Functionality Software)
- 11.2.3.1 (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)
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.1 (Web)
- 10.2.4.1 (Non-web document) – Does not apply
- 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
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.2 (Web)
- 10.2.4.2 (Non-web document)
- 11.2.4.2 (Open Functionality Software) - Does not apply
- 11.2.4.2 (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)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.3 (Web)
- 10.2.4.3 (Non-web document)
- 11.2.4.3 (Open Functionality Software)
- 11.2.4.3 (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: Most components receive focus in a meaningful order. Exceptions include:
Some interactive elements do not receive focus in a logical order. For example, when Annotations mode is activated, focus is placed on the Close button at the end of the new content instead of the beginning.
Sometimes a button will expand the left rail, but the left rail content does not follow the button in keyboard focus path.
Sometimes when an action is performed, focus is lost or not managed correctly.
Some visually hidden user interface components receive focus using a keyboard.
Focus is not restricted inside of some modal dialogs.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.4 (Web)
- 10.2.4.4 (Non-web document)
- 11.2.4.4 (Open Functionality Software)
- 11.2.4.4 (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: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. 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 (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.5 (Web)
- 10.2.4.5 (Non-web document) – Does not apply
- 11.2.4.5 (Open Functionality Software) – Does not apply
- 11.2.4.5 (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
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.6 (Web)
- 10.2.4.6 (Non-web document)
- 11.2.4.6 (Open Functionality Software)
- 11.2.4.6 (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)
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.7 (Web)
- 10.2.4.7 (Non-web document)
- 11.2.4.7 (Open Functionality Software)
- 11.2.4.7 (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: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
The focus indicator for the Device button in the Edit Layout toolbar wraps multiple user interface components making it difficult to track focus.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.1 (Web)
- 10.2.5.1 (Non-web document)
- 11.2.5.1 (Open Functionality Software)
- 11.2.5.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.2 (Web)
- 10.2.5.2 (Non-web document)
- 11.2.5.2 (Open Functionality Software)
- 11.2.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.3 (Web)
- 10.2.5.3 (Non-web document)
- 11.2.5.3.1 (Open Functionality Software)
- 11.2.5.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.4 (Web)
- 10.2.5.4 (Non-web document)
- 11.2.5.4 (Open Functionality Software)
- 11.2.5.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Guideline 3.1 Readable:
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.1.1 (Web)
- 10.3.1.1 (Non-web document)
- 11.3.1.1.1 (Open Functionality Software)
- 11.3.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)
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.1.2 (Web)
- 10.3.1.2 (Non-web document)
- 11.3.1.2 (Open Functionality Software) – Does not apply
- 11.3.1.2 (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)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.1 (Web)
- 10.3.2.1 (Non-web document)
- 11.3.2.1 (Open Functionality Software)
- 11.3.2.1 (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: 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 (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.2 (Web)
- 10.3.2.2 (Non-web document)
- 11.3.2.2 (Open Functionality Software)
- 11.3.2.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)
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.3 (Web)
- 10.3.2.3 (Non-web document) – Does not apply
- 11.3.2.3 (Open Functionality Software) – Does not apply
- 11.3.2.3 (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
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.4 (Web)
- 10.3.2.4 (Non-web document) – Does not apply
- 11.3.2.4 (Open Functionality Software) – Does not apply
- 11.3.2.4 (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
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.1 (Web)
- 10.3.3.1 (Non-web document)
- 11.3.3.1.1 (Open Functionality Software)
- 11.3.3.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)
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.2 (Web)
- 10.3.3.2 (Non-web document)
- 11.3.3.2 (Open Functionality Software)
- 11.3.3.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: Labels are provided for most input fields. Exceptions include:
Some fields do not have a visible label.
Some fields rely on placeholder text for a visible label.
3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.3 (Web)
- 10.3.3.3 (Non-web document)
- 11.3.3.3 (Open Functionality Software)
- 11.3.3.3 (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)
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.4 (Web)
- 10.3.3.4 (Non-web document)
- 11.3.3.4 (Open Functionality Software)
- 11.3.3.4 (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)
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
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)
4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria
- 9.4.1.2 (Web)
- 10.4.1.2 (Non-web document)
- 11.4.1.2.1 (Open Functionality Software)
- 11.4.1.2.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: 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.
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.4.1.3 (Web)
- 10.4.1.3 (Non-web document)
- 11.4.1.3 (Open Functionality Software)
- 11.4.1.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Exceptions include:
On the Filter page, the loading status message when switching between views is not announced by the screen reader.
Some search results status messages are not announced by the screen reader, such as “No results found” or the number of results.
Some loading states are not announced by the screen reader.
An error state in the References Rail is not announced by the screen reader.
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Web: Most functions of the product are usable without vision. Examples include:
As noted in 1.1.1 Non-Text Content, some decorative images are not hidden from assistive technologies and 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. 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 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.
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.
Web: Most of the 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.
Web: Most of the functions of the product are usable with limited manipulation.
However, some core functionality such as adding and removing assets and components, editing layouts and web content, reviewing demographics or annotations are not accessible using a keyboard. 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.
Web: Most of the functions of the product are usable with limited language, cognitive and learning abilities. Exceptions include:
As described in 3.3.2 Labels or Instructions, some form fields do not have a visible label, or the label is not provided through placeholder text and is not permanently visible.
Chapter 4: Hardware
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Chapter 5: Software
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Chapter 6: Support Documentation and Services
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
EN 301 549 Report
Notes:
Chapter 4: Functional Performance Statements (FPS)
Notes:
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. 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 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.
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.
Web: Web: Most of the 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.
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.
Web: Most of the functions of the product are usable with limited language, cognitive and learning abilities. Exceptions include:
As described in 3.3.2 Labels or Instructions, some form fields do not have a visible label, or the label is not provided through placeholder text and is not permanently visible.
Chapter 5: Generic Requirements
Notes:
Chapter 6: ICT with Two-Way Voice Communication
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Chapter 7: ICT with Video Capabilities
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Chapter 8: Hardware Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Chapter 9: Web
Notes: (see WCAG 2.x section)
Chapter 10: Non-web Documents
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Chapter 11: Software
Notes: Adobe Experience Manager Sites is a website (or web application) and is not subject to the requirements of this section.
Chapter 12: Documentation and Support Services
Notes:
Chapter 13: ICT Providing Relay or Emergency Service Access
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)