Adobe Accessibility Conformance Report
(Based on VPAT® Version 2.4)
Product Information
Name of Product/Version: AEM Core Components
Product Description: A set of standardized Web Content Management (WCM) components for Adobe Experience Manager (AEM) to speed up development time and reduce the maintenance cost of your websites.
Date: September 2021
Contact information: access@adobe.com
Notes: The information contained in this report applies only to the AEM Core Components. Information about other products, help, and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
Evaluation Methods Used: Testing Adobe AEM Core Components involved extensive use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, 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:
Standard/Guideline |
Included in Report |
Level A: Yes |
|
Level A: Yes |
|
Yes |
|
Yes |
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.1 Report
Tables 1 and 2 also 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.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 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.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: The product provides sufficient text alternatives for most instances of non-text content, such as images and icons. Exceptions include:
|
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not contain prerecorded audio-only or video-only media. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Web: 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) (Level A)
Revised Section 508
|
Web: 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) (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product does not contain live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Web: 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. |
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.3.1 Info and Relationships (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Most visual structure and relationship information, such as lists, headings, and landmarks, is provided through element semantics. Exceptions include:
|
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Web: Supports |
Web: The product presents content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Web: Supports |
Web: Instructions do not rely solely on sensory characteristics. |
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: Content does not restrict its view and operation to a single display orientation. |
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: Input fields that collect information about the user programmatically convey their purpose. |
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.1 Use of Color (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Most functions of the product do not convey information through color alone. Exception:
|
1.4.2 Audio Control (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not contain audio that plays automatically. |
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most text meets minimum contrast requirements. Exceptions include:
|
1.4.4 Resize text (Level AA)
Revised Section 508
|
Web: 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 (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product uses text instead of images of text. |
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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:
|
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Partially Supports |
Web: Most meaningful non-text content elements have sufficient contrast. Exceptions include:
|
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product supports the required text style properties without loss of content or functionality. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Most product functionality can be operated through a keyboard interface. Exceptions include:
|
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not include keyboard traps. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product does support character key shortcuts in accessible way. |
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.2.1 Timing Adjustable (Level A)
Revised Section 508
|
Web: Supports (Not Applicable) |
Web: The product does not include time limits. |
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not include elements which move, blink, scroll, or auto-update. |
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.3.1 Three Flashes or Below Threshold (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not contain flashing content. |
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.4.1 Bypass Blocks (Level A)
Revised Section 508
|
Web: 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 (Level A)
Revised Section 508
|
Web: Supports |
Web: The title of a page describes its purpose. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Most components receive focus in a meaningful order. Exceptions include:
|
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Web: 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:
|
2.4.5 Multiple Ways (Level AA)
Revised Section 508
|
Web: Supports |
Web: Users can locate web pages in the product through navigation and search. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most headings and labels are descriptive. Exception:
|
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
|
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.5.1 Pointer Gestures (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product does not rely on multipoint or path-based gestures. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: Product functions that use a single pointer are completed when the user releases the pointer. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Partially Supports |
Web: In most product functions, accessible names of controls contain the text of their visible labels. Exception:
|
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports (Not Applicable) |
Web: The product does not have functionality operated by device motion or user motion. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A)
Revised Section 508
|
Web: Supports |
Web: The language is programmatically determinable within the product. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Web: Supports |
Web: Content is only presented in one language at a time. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.2.1 On Focus (Level A)
Revised Section 508
|
Web: Supports |
Web: Components do not initiate a change of context when focused. |
3.2.2 On Input (Level A)
Revised Section 508
|
Web: Supports |
Web: Changes of context do not occur automatically on user input. |
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Web: Supports |
Web: When navigational mechanisms are repeated in the product they occur in a consistent relative order. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Web: Supports |
Web: Components with the same functionality are identified consistently. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A)
Revised Section 508
|
Web: 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 (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Labels are provided for most input fields. Exception:
|
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Web: 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) (Level AA)
Revised Section 508
|
Web: Supports (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. |
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)
Revised Section 508
|
Web: 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:
|
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Web: 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:
|
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: 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:
|
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
302.1 Without Vision |
Web: Partially Supports |
Web: Most functions of the product are usable without vision. Exceptions include:
|
302.2 With Limited Vision |
Web: Partially Supports |
Web: Most functions of the product are usable with limited vision.
|
302.3 Without Perception of Color |
Web: Partially Supports |
Web: Most functions of the product are usable without perception of color. Exception:
|
302.4 Without Hearing |
Web: Supports |
Web: The product does not require the use of hearing.
|
302.5 With Limited Hearing |
Web: Supports |
Web: The product does not require the use of hearing.
|
302.6 Without Speech |
Web: Supports |
Web: The product does not require the use of speech.
|
302.7 With Limited Manipulation |
Web: Partially Supports |
Web: Most functions of the product are usable without vision. Exceptions include:
|
302.8 With Limited Reach and Strength |
Web: Supports |
Web: The product is functional with limited reach and strength.
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Web: Partially Supports |
Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
|
Chapter 6: Support Documentation and Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
EN 301 549 Report
Notes:
Chapter 4: 4.2 Functional Performance Statements (FPS)
Notes: According to C.4 Functional Performance, this section is informative only.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Web: Partially Supports |
Web: Most functions of the product are usable without vision. Exceptions include:
|
4.2.2 Usage with limited vision |
Web: Partially Supports |
Web: Most functions of the product are usable with limited vision.
|
4.2.3 Usage without perception of colour |
Web: Partially Supports |
Web: Most functions of the product are usable without perception of color. Exception:
|
4.2.4 Usage without hearing |
Web: Supports |
Web: The product does not require the use of hearing. |
4.2.5 Usage with limited hearing |
Web: Supports |
Web: The product does not require the use of hearing. |
4.2.6 Usage without vocal capability |
Web: Supports |
Web: The product does not require the use of speech.. |
4.2.7 Usage with limited manipulation or strength |
Web: Partially Supports |
Web: Most functionality in the product is usable with limited manipulation and strength. Exceptions include:
|
4.2.8 Usage with limited reach |
Web: Partially Supports |
Web: Users with limited reach will have no difficulty navigating to controls. Exceptions include:
|
4.2.9 Minimize photosensitive seizure triggers |
Web: Supports |
Web: The product does not contain flashing content or media. |
4.2.10 Usage with limited cognition, language or learning |
Web: 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:
|
4.2.11 Privacy |
Web: Supports |
Web: The product maintains user privacy when accessibility features are used. Example:
|
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed Functionality |
Not Applicable |
5.1.2.2-5.1.7 are not applicable for this product, which has no closed functionality. |
5.2 Activation of accessibility features |
Not Applicable |
The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features. |
5.3 Biometrics |
Not Applicable |
The product does not use biological characteristics for user identification or for control of the product. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
The product is not an authoring tool. |
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:
|
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. |
5.7 Key repeat |
Not Applicable |
The product relies on platform software to turn off or adjust key repeat. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not provide a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
The product relies on platform software features, such as Sticky Keys, to ensure simultaneous user actions are not required. |
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
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. |
7.3 User controls for captions and audio description |
Partially Supports |
Embedded YouTube videos provide user controls for captions, but not for audio descriptions. |
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: See WCAG 2.x section
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes: Not Applicable
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)