Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
- Name of Product/Version: Adobe Marketo Engage
- Product Description: Adobe Marketo Engage is a platform solution for managing B2B and B2C considered purchase marketing leads through all stages of buying journeys, which natively supports both demand- and account-based marketing strategies. Adobe Marketo Engage includes customization options and third-party integration capabilities to allow users to orchestrate personalized experiences, optimize content, and measure business impact across every channel.
- Date: December 2025
- 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 Marketo Engage 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 AA (Yes)
Level AAA (No)
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Level A (Yes)
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 only be used in WCAG Level AAA criteria.
WCAG 2.2 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.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements
Table 1: Success Criteria, Level A
Notes:
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 non-text content.
Exceptions include:
A complex image does not have a long description to convey the information presented by the image, so people who are blind and/or use a screen reader will not be able to understand the information presented by the image. This occurs on the following screen: Marketing Activities.
Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs in the following component: Header and following screens: Select email template; Tags - Edit Channel; Engagement Map; My Tokens tab; Edit user; Smart List tab; Admin - Home; Qualification Rules modal; Personal Detail Page; Smart Campaign - Home tab; Assets tab; All People; Landing Page Editor; Form Editor - Step 1; Flow tab; Create New Email (ACRITE).
An active image has a text alternative that does not convey the same purpose as the image. People who are blind and/or use a screen reader will be given different information than sighted users. This occurs in the following component: Left Navigation.
A decorative image is not hidden from screen readers, so people who are blind and/or use a screen reader will have to navigate through unnecessary and duplicative text. This occurs on the following pages: Engagement Map; Schedule tab.
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)
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: Some structure and relationship information are provided through element semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text. Examples include:
Some heading levels are out of order, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Engagement Map; Smart Campaign - Home tab.
Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Admin - Home.
Some blocks of text are marked up as headings but are not headings, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Edit email; Create Fragment modal; Edit user; New Email.
A group of navigation links is missing semantic markup, so people who are blind and/or use a screen reader may not understand how the links relate to each other or the page content. This occurs in the following component: Header.
Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following page: Design Studio - Forms.
Some text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs in the following components: Side Panel; Header; Left Navigation and following pages: Select email template; Landing Page Detail Page; Tags - Edit Channel; Email Program - Home tab; Engagement Map; Edit Qualifications Rules Modal; Form Editor - Step 1; New Smart Campaign Modal; Schedule tab; Create Fragment modal; Landing Page Editor; Form Editor - Step 3; Marketing Activities; Create New Email (ACRITE); Admin - Home; Assets tab; Edit user; Design Studio - Forms; Flow tab; Form Editor - Step 2; New Local Asset; Smart List tab.
An element's programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content. This occurs on the following pages: Landing Page Detail Page; Design Studio – Forms.
Some sets of checkboxes are not programmatically grouped, so the group label for each set of checkboxes will not be conveyed to people who are blind and/or use a screen reader, and they will not understand the purpose of the individual checkboxes. This occurs on the following pages: Qualification Rules modal; Edit Qualifications Rules Modal.
Some sets of radio buttons are not programmatically grouped, so the group label for each set of radio buttons will not be conveyed to people who are blind and/or use a screen reader, and they will not understand the purpose of the individual radio buttons. This occurs on the following pages: Edit Qualifications Rules Modal; Qualification Rules modal; Form Editor - Step 2.
Data is arranged visually like a data table, but the programmatic table header markup for some tables is missing or incomplete. People who are blind and/or use a screen reader will not be aware of the association between the headers for these tables and their related data. This occurs in the following component: Calendar Email Program and following pages: Setup tab; All People; Tags - Edit Channel; My Tokens tab; Landing Page Editor.
Content that is visually presented as a single table is marked up as more than one table element, so the table's structure and data relationships will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following page: All People.
An HTML list element contains content that is visually presented as a part of the list, but the content's HTML coding does not include it programmatically in that list, so the structure of the list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following components: Marketing Activities - Navigation; Left Navigation and following pages: Design Studio - Home; Form Detail Page; Edit user; Smart List tab; Flow tab; Personal Detail Page; My Tokens tab; Smart Campaign - Home tab.
Content that is visually presented as a list is not properly marked up as a list, so the structure of the list is not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Flow tab; Tree Menus; Landing Page Detail Page; My Tokens tab; Assets tab; Smart List tab; Design Studio - Forms; Edit user.
An HTML list element contains content that is visually presented as a part of the list, but the content's HTML coding does not include it programmatically in that list, so the structure of the list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Assets tab.
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:
The screen reader skips and does not announce informative static content (text or images), so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following page: Qualification Rules modal.
Screen readers can read content outside some modal dialogs, so people who are blind and/or use a screen reader may become disoriented or confused. This occurs on the following pages: Edit Qualifications Rules Modal; New Smart Campaign Modal; New Local Asset; Create New Email (ACRITE); Edit user; Tags - Edit Channel.
Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs in the following components: Side Panel; Left Navigation and following pages: Smart Campaign - Home tab; My Tokens tab; Default Program - Home tab; Edit user; Design Studio - Home; Setup tab; Global Search.
The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: Admin - Home; Personal Detail Page.
The correct reading order of dynamically changing content is not programmatically determinable by screen readers, so people who are blind and/or use a screen reader may not be made aware of new or changed content that is dynamically added to a page. This occurs on the following pages: Tree Menus; Landing Page Detail Page; Design Studio - Forms.
The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs in the following component: Left Navigation and following page: Analytics - Home tab.
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)
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 convey information through color alone. Examples include:
Color is used as the only method to identify errors on a form field, so the error will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following page: Form Editor - Step 2.
Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of some controls, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs in the following component: Calendar Email Program and following pages: Design Studio - Forms; Marketing Activities; Form Editor - Step 2; Tags - Edit Channel; Select email template; Form Editor - Step 3; Form Editor - Step 1; Default Program - Home tab; Smart Campaign - Home tab; Analytics - Home tab; Form Detail Page; Edit Qualification Rules Modal; Edit User.
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)
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 cannot be operated through a keyboard interface. Examples include:
Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs in the following components: Left Navigation; Side Panel; Calendar Email Program; Secondary Marketing Activities - Navigation and following pages: Edit email; Edit Qualifications Rules Modal; Design Studio - Forms; Tags - Edit Channel; Select email template; My Tokens tab; Flow tab; Form Editor - Step 1; Tree Menus; New Local Asset; All People; Email Program - Home tab; Setup tab; Landing Page Detail Page; Personal Detail Page; Edit user; Smart List tab; Form Editor - Step 2; New Smart Campaign Modal; Landing Page Editor; Assets tab; Smart Campaign - Home tab; Create New Email (ACRITE); Schedule tab.
The content in a scrollable region cannot be accessed using a keyboard, so people who use a keyboard to navigate will not be able to view this content. This occurs on the following page: Landing Page Editor.
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)
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
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)
Web: Most pages have descriptive and informative titles. Exceptions include:
The page's programmatic title does not identify the purpose of the page, so people who use a screen reader will not know the purpose of the page without reading its content. This occurs on the following pages: Engagement Map; Engagement Map - Settings tab; Global Search; Form Editor - Step 1; Edit email.
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. Examples include:
The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the following pages: Tree Menus; Design Studio - Forms.
Keyboard focus or touch screen swiping goes to multiple elements that are hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs in the following components: Side Panel; Left Navigation; Calendar Email Program; Secondary Marketing Activities - Navigation and following pages: Personal Detail Page; Smart Campaign - Home tab; Throughout the website; Setup tab; Global Search; New Email.
Keyboard focus is not confined within multiple modals, so people who use the keyboard to navigate content (including screen reader users) will be able to navigate outside of the modal, which may cause them to become disoriented. This occurs on the following pages: Edit Qualifications Rules Modal; Edit user; Tags - Edit Channel.
Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following page: Edit Qualifications Rules Modal.
When a modal closes, keyboard focus is not returned to the control that opened the modal or to another logical location, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following page: New Smart Campaign Modal.
Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs in the following component: Secondary Marketing Activities - Navigation and following pages: Throughout the website.
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:
Multiple links have identical link text but different destinations, and the context provided by the content that immediately surrounds each link does not provide any clarification, so people who are blind and/or use a screen reader will not know or may be confused about where each link goes. This occurs on the following page: Form Editor - Step 1.
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 and 2.2)
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 and 2.2)
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 and 2.2)
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
Web: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:
Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Tags - Edit Channel; All People; Edit Qualifications Rules Modal; Edit user; Design Studio - Forms.
The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: Edit email; Default Program - Home tab; Qualification Rules modal; Smart Campaign - Home tab.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
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)
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)
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.6 Consistent Help (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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)
Web: Most input errors are identified and described to the users in text. Exceptions include:
Some form fields with an error are not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field an error occurred. This occurs on the following pages: Edit Qualifications Rules Modal; My Tokens tab; Edit user.
An error for a form input (such as a text input field, radio button, select dropdown, or checkbox) is not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following page: Form Editor - Step 2.
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:
The labels for some form fields are missing, so each field's purpose is not clear. This occurs on the following pages: Default Program - Home tab; Design Studio - Forms; Smart Campaign - Home tab; My Tokens tab.
Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following pages: Flow tab; My Tokens tab; Landing Page Detail Page; Smart List tab.
A group of elements is missing a visible group label, so the purpose of the elements in the group cannot be understood. This occurs on the following page: New Email.
Select or dropdown control missing a visible label. This occurs in the following component: Header and following pages: Edit Qualifications Rules Modal; Smart List tab; Personal Detail Page; Edit email; Flow tab; Qualification Rules modal.
3.3.7 Redundant Entry (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Applies to:
WCAG 2.0 and 2.1 – Always answer ‘Supports’
WCAG 2.2 (obsolete and removed) - Does not apply
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) – 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)
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) – 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)
Web: User interface components in most product functions do not provide programmatic [name, role, state, or value] information. Examples include:
A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page: Design Studio - Home.
A link does not have discernible text, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the destination or function of the link. This occurs on the following pages: Setup tab; Tree Menus; My Tokens tab; Smart Campaign - Home tab; Default Program - Home tab.
Multiple buttons do not have a programmatic name, so each button's name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs in the following components: Calendar Email Program; Side Panel; Secondary Marketing Activities - Navigation and following pages: Edit email; Select email template; All People; Form Editor - Step 2; Design Studio - Forms; Landing Page Detail Page; Form Editor - Step 1; Setup tab; Smart Campaign - Home tab.
Multiple buttons do not have a programmatic role, so each button's role (usually button, but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Form Editor - Step 1; Edit email; Smart Campaign - Home tab; Select email template; Setup tab; All People; Assets tab; Landing Page Editor; My Tokens tab; Schedule tab.
An iframe does not have a programmatic title that is conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the iframe without browsing its content. This occurs on the following page: Marketing Activities; Email Program - Home tab; Assets tab; Setup tab; My Tokens tab; Smart Campaign - Home tab; Landing Page Editor; Schedule tab; All people; Design Studio - Home; Analytics - Home tab; Admin - Home.
An element has an invalid attribute in its HTML code that is intended to provide its programmatic role to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following component: Side Panel and following pages: Form Detail Page; Global Search.
An element with a "link," "button," or "menuitem" role is missing or has an incorrect programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of the element and may not understand its purpose or content or how to interact with it. This occurs on the following pages: Form Editor - Step 1; Email Program - Home tab.
When some buttons are pressed, their pressed state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the buttons are pressed. This occurs on the following pages: New Smart Campaign Modal; Email Program - Home tab; Select email template; Form Editor - Step 1.
An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following pages: Engagement Map; Engagement Map - Settings tab.
Multiple links do not have discernible link text, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the destination or function of each link. This occurs in the following component: Secondary Marketing Activities - Navigation and following pages: Design Studio - Home; Edit user; Email Program - Home tab; Throughout the website; All People; Edit Qualifications Rules Modal.
A select element does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the select control. This occurs on the following page: Edit Qualifications Rules Modal.
In a table that can be sorted by column, the sorted state (ascending or descending) of the table's columns is not conveyed to assistive technology or the state conveyed is incorrect, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the order in which the table's content is presented and whether that order is meaningful when interpreting the data. This occurs on the following pages: Landing Page Editor; All People; Design Studio - Forms.
Multiple buttons do not have a programmatic role and name, so each button's role (usually button, but sometimes link or something else) and its name (such as "Submit" or "Cancel") are not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Flow tab; Landing Page Editor; Smart List tab.
Multiple elements do not have an attribute in their HTML code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs in the following component: Left Navigation and following pages: Smart List tab; Personal Detail Page; Flow tab; Engagement Map.
An element that appears and functions like a modal dialog does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Form Inventory.
Multiple form fields are missing a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each form field or what input it requires. This occurs on the following pages: My Tokens tab; Email Program - Home tab; Landing Page Detail Page; Landing Page Editor; Default Program - Home tab; Personal Detail Page; Edit Qualifications Rules Modal; Design Studio - Forms; Edit user; All People; Tags - Edit Channel.
The HTML code for a link or button is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of the element. This occurs on the following page: Tree Menus.
The HTML code for a link or button is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of the element. This occurs on the following pages: Engagement Map - Settings tab; Engagement Map.
When some controls are disabled, their disabled state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the controls are disabled. This occurs in the following components: Secondary Marketing Activities - Navigation; Calendar Email Program and following pages: Smart List tab; All People; Setup tab; Design Studio - Forms.
An element that appears and functions like a menu does not have the required attributes in its HTML code needed to provide the programmatic role, name, state, and other properties for the menu and/or its options to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the menu and its options or how to interact with them. This occurs on the following pages: Tree Menus; Landing Page Detail Page.
Multiple custom checkbox elements do not have a programmatic role and/or their current state (checked or not checked) is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be aware that each element is a checkbox or if the checkbox is checked. This occurs on the following pages: Smart List tab; New Smart Campaign Modal; My Tokens tab; Setup tab.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked. This occurs in the following components: Marketing Activities - Navigation; Calendar Email Program and following pages: Default Program - Home tab; Form Detail Page; Landing Page Editor; Select email template; All People; Design Studio - Home; Assets tab; Smart Campaign - Home tab; Setup tab; My Tokens tab; Personal Detail Page; Form Editor - Step 1.
The content of multiple tooltips cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content. This occurs in the following component: Calendar Email Program and following pages: Smart Campaign - Home tab; Email Program - Home tab; Flow tab; Smart List tab; Landing Page Detail Page; All People; Create New Email (ACRITE); New Smart Campaign Modal; Edit user; Tags - Edit Channel.
An element that appears and functions like a switch control does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, or current state (such as "On" or "Off") or how to interact with it. This occurs on the following page: Form Editor - Step 2.
Multiple elements that appear and function like a set of tabs with their associated tab panels do not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, content, structure, or current state or how to interact with the tabs and their associated content. This occurs in the following component: Left Navigation and following page: Form Editor - Step 2.
Multiple elements that appear and function like a combo box do not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it. This occurs on the following pages: Personal Detail Page; Email Program - Home tab; Design Studio - Forms; New Smart Campaign Modal; Tags - Edit Channel; Create New Email (ACRITE); Form Editor - Step 1; Smart List tab; Flow tab; Form Editor - Step 2.
A custom radio button does not have a role and/or a state (checked/unchecked) that are conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the radio button, how to use it, and whether it is checked. This occurs on the following page: Form Editor - Step 2.
The programmatic state of some elements that reveal or hide content ("expanded" or "collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of each element or the state will be misrepresented. This occurs in the following components: Calendar Email Program; Side Panel; Left Navigation; Header; Secondary Marketing Activities - Navigation and following pages: Landing Page Editor; Personal Detail Page; All People; Flow tab; Setup tab; Email Program - Home tab; Smart List tab; Default Program - Home tab; Form Editor - Step 2; Assets tab; Select email template; Landing Page Detail Page; Design Studio - Forms; Engagement Map; My Tokens tab.
An element that is focusable or contains one or more focusable elements is programmatically hidden, so people who use the keyboard to navigate as well as people who are blind and/or use a screen reader or other assistive technology will not be able to perceive or interact with the element. This occurs on the following pages: Edit email; New Email.
Some elements that appear and function like a modal dialog do not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it. This occurs on the following pages: New Smart Campaign Modal; New Local Asset; Qualification Rules modal; Create New Email (ACRITE); Tags - Edit Channel; Edit user; Edit Qualifications Rules Modal.
An element that appears and functions like a tree view widget that presents a hierarchical list does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand name, purpose, structure, or content of the list or how to interact with it. This occurs on the following pages: Flow tab; Edit user; Smart List tab.
An element does not have an attribute in its HTML code that will provide its programmatic state (such as "checked"/"not checked") to assistive technology or the state assigned is not correct, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the current state of the element or how to interact with it. This occurs on the following page: Design Studio - Forms.
Table 2: Success Criteria, Level AA
Notes:
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)
1.3.4 Orientation (Level AA 2.1 and 2.2)
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 and 2.2)
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
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. Examples include:
The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs in the following components: Calendar Email Program; Left Navigation; Marketing Activities - Navigation and following pages: Form Detail Page; Landing Page Editor; My Tokens tab; Select email template; Design Studio - Home; Form Editor - Step 1; Engagement Map - Settings tab; Form Editor - Step 2; Edit user; Smart List tab; Edit Qualifications Rules Modal; Flow tab; Design Studio - Forms; All People; Marketing Activities; Smart Campaign - Home tab; Throughout the website; Analytics - Home tab; Default Program - Home tab; Personal Detail Page; Engagement Map; Tags - Edit Channel; Assets tab; Setup tab; Form Editor - Step 3; Schedule tab.
The color contrast ratio between large text and its background is less than 3:1, so people who are colorblind or have low vision may have difficulty reading the text. Large text is text over 18 points (24 pixels) or 14 points (19 pixels) if bold. This occurs on the following page: Marketing Activities.
The color contrast ratio between placeholder text in multiple inputs and each input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs in the following component: Left Navigation and following pages: Flow tab; Email Program - Home tab; Smart List tab; Landing Page Detail Page.
The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of each control. This occurs in the following component: Secondary Marketing Activities - Navigation and following pages: Select email template; Form Editor - Step 1; Design Studio - Home; Default Program - Home tab; Form Editor - Step 3; Landing Page Editor; Analytics - Home tab; Edit Qualification Rules; Edit user; Smart Campaign - Home tab; Tags - Edit Channel; Personal Detail Page; Marketing Activities; Email Program - Home tab.
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 does not provide its own text resizing function. When text is resized using [browser zoom | operating system display scaling content and functionality is lost in most product functions. Examples include:
Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs in the following components: Left Navigation; Calendar Email Program and following pages: Form Detail Page; Landing Page Editor; Landing Page Detail Page; Smart Campaign - Home tab; Form Editor - Step 1; New Email; Create New Email (ACRITE); Tags - Edit Channel; Form Inventory; Assets tab; Edit user; Analytics - Home tab; New Smart Campaign Modal.
Functionality is lost when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to this functionality. This occurs in the following component: Secondary Marketing Activities - Navigation and following pages: Form Editor - Step 2; Form Editor - Step 3; Smart List tab; Edit email; Flow tab; Select email template; Design Studio - Forms.
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)
Web: The product uses text instead of images of text most of the cases, except for branding elements that are considered essential. The product uses text instead of images of text most of the cases, except for branding elements that are considered essential. Exceptions include:
Text on the page is text embedded in an image instead of actual text. An image of text is difficult to zoom or otherwise modify, so people who have low vision and need to enlarge text to read it may not be able to read the text. People with other disabilities that need to otherwise modify text to read it also may not be able to read this text. This occurs on the following page: Form Editor - Step 1.
1.4.10 Reflow (Level AA 2.1 and 2.2)
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:
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs in the following components: Header; Marketing Activities - Navigation; Left Navigation; Calendar Email Program; Secondary Marketing Activities - Navigation and following pages: Analytics - Home tab; Smart Campaign - Home tab; New Local Asset; Landing Page Editor; Select email template; Form Editor - Step 3; Form Editor - Step 2; Edit Qualifications Rules Modal; Engagement Map; Setup tab; Personal Detail Page; All People; Create New Email (ACRITE); Schedule tab; Engagement Map - Settings tab; Form Inventory; New Email; Marketing Activities; Edit user; Design Studio - Home; Edit email; Form Editor - Step 1; Design Studio - Forms; Form Detail Page; Flow tab; Global Search; Admin - Home; Default Program - Home tab; Assets tab; Landing Page Detail Page; Tags - Edit Channel; Smart List tab; New Smart Campaign Modal.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following pages: Qualification Rules modal; My Tokens tab.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
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, if not all, boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content do not have a 3:1 color contrast ratio with adjacent color(s) or their background. Examples include:
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon. This occurs in the following components: Side Panel; Header; Secondary Marketing Activities - Navigation and following pages: Tags - Edit Channel; Personal Detail Page; Design Studio - Forms; Form Editor - Step 1; All People; Smart List tab; Flow tab; New Email; Global Search; Form Editor - Step 2; My Tokens tab; Landing Page Editor; Create New Email (ACRITE); Edit user; New Smart Campaign Modal; Email Program - Home tab; Setup tab; Form Detail Page.
The focus indicators of some interactive elements (like buttons or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when each interactive element is receiving focus. This occurs on the following pages: Email Program - Home tab; Marketing Activities; Select email template; My Tokens tab; Project wide issues; Design Studio - Forms; Default Program - Home tab; Setup tab; Form Editor - Step 1; Form Editor - Step 2; Landing Page Editor; Smart Campaign - Home tab; New Smart Campaign Modal.
Some images or graphics (like a chart) or parts of the image/graphic required to understand its content do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by the image/graphic. This occurs on the following pages: Marketing Activities; My Tokens tab; Setup tab; Landing Page Editor; All People; Edit user.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements. This occurs in the following components: Header; Secondary Marketing Activities - Navigation; Side Panel and following pages: My Tokens tab; Select email template; Global Search; Form Editor - Step 1; Form Editor - Step 2; Tags - Edit Channel; Setup tab; Assets tab; Edit email; Engagement Map.
The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs in the following components: Side Panel; Left Navigation and following pages: My Tokens tab; Email Program - Home tab; Select email template; Form Editor - Step 2; Personal Detail Page; Default Program - Home tab; Create New Email (ACRITE); Smart Campaign - Home tab; Smart List tab; Setup tab; Landing Page Detail Page; Form Editor - Step 1; Design Studio - Forms; Tags - Edit Channel; Edit email; New Smart Campaign Modal.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
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:
When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: Analytics - Home tab; Select email template; Form Inventory; Form Editor - Step 3; New Local Asset.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
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
Web: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include:
Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs in the following components: Secondary Marketing Activities - Navigation; Calendar Email Program and following pages: Assets tab; Email Program - Home tab; Smart List tab; All People; Tags - Edit Channel; Tree Menus; New Smart Campaign Modal; Create New Email (ACRITE); Landing Page Detail Page; Form Editor - Step 1; Edit user; Design Studio - Forms; Edit email; Flow tab.
Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs in the following component: Calendar Email Program and following pages: Assets tab; All People; Flow tab; Tree Menus; Tags - Edit Channel; Design Studio - Forms; Landing Page Detail Page; Email Program - Home tab.
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)
Web: Most headings and labels are descriptive. Exceptions include:
Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following pages: Form Inventory; Edit email; Smart List tab; New Email; Global Search.
Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs in the following component: Left Navigation and following pages: Engagement Map; Qualification Rules modal; Edit email.
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. Examples include:
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs in the following components: Left Navigation; Secondary Marketing Activities - Navigation; Marketing Activities - Navigation; Calendar Email Program; Side Panel and following pages: New Local Asset; Edit email; Default Program - Home tab; Edit Qualifications Rules Modal; Smart Campaign - Home tab; Admin - Home; My Tokens tab; Tags - Edit Channel; Select email template; Project wide issues; Form Editor - Step 2; Landing Page Editor; Marketing Activities; Assets tab; Setup tab; Edit user; Flow tab; Email Program - Home tab; Form Editor - Step 1; Smart List tab; All People; Analytics - Home tab; Design Studio - Home; Design Studio – Forms; Personal Detail Page.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include:
A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following page: Tags - Edit Channel.
2.5.7 Dragging Movements (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Most functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. Exceptions include:
Some functionality relies on a dragging movement with no single-pointer, single-touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture. This occurs in the following component: Side Panel and following pages: New Email; Edit email; Smart List tab; Assets tab; Setup tab; Design Studio - Forms; Landing Page Editor; Form Editor - Step 1; All People; Flow tab; Project wide issues; My Tokens tab.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: The size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Exceptions include:
Multiple target hit areas do not meet a minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs in the following component: Side Panel and following pages: Edit user; Flow tab; Smart List tab.
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)
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
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)
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
4.1.3 Status Messages (Level AA 2.1 and 2.2)
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) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include:
Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages, or they may not hear them in a timely fashion. This occurs in the following components: Header; Left Navigation; Side Panel and following pages: Setup tab; Global Search; My Tokens tab; Landing Page Detail Page; All People; New Smart Campaign Modal; Select email template; Edit Qualifications Rules Modal; Edit user; Edit email; Design Studio - Forms; Form Inventory; Flow tab; Create Fragment modal; Form Detail Page; Tags - Edit Channel; Qualification Rules modal; New Email; Smart List tab.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable.
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 3.3.1 Error Identification
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.4 Resize text
As noted in 1.4.5 Images of Text
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 3.3.1 Error Identification
Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
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:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.5 Images of Text
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
In most instances when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
For most objects that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set or modify its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
For most, if not all, elements on which one or more actions may be performed, those actions are not programmatically determinable, so that each action cannot be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:
As noted in 2.1.1 Keyboard Navigation
The position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 2.4.7 Focus Visible
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:
As noted in 4.1.3 Status Messages
Templates in the product enable authors to create a range of content which partially conforms to WCAG 2.2 Levels A and AA. Exceptions include in the Edit email page:
As noted in 1.4.11 Non-Text Contrast
As noted in 2.1.1 Keyboard
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
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: 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
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 3.3.1 Error Identification
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.4 Resize text
As noted in 1.4.5 Images of Text
As noted in 1.4.10 Reflow
As noted in 1.4.11 Non-text Contrast
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.11 Non-Text Contrast
As noted in 3.3.1 Error Identification
Web: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength . Excepti ons include:
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 4.1.2 Name, Role, Value
Web: All functionality is usable by people with limited reach. Exceptions include:
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.5.3 Label in Name
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:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.5 Images of Text
As noted in 1.4.10 Reflow
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.2 Page Titled
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (in context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
Chapter 5: Generic Requirements
Notes:
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: (see WCAG 2.2 section)
Chapter 10: Non-Web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
The product exposes the name, role and state or value of most objects to assistive technology. Exceptions include:
4.1.2 Name, Role, Value
In most instances when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
1.3.1. Info and Relationships
For most objects that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology. Exceptions include:
4.1.2. Name, Role, Value
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
1.3.1. Info and Relationships
4.1.2. Name, Role, Value
When a page contains elements that have a parent-child relationship, most of those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:
1.3.1 Info and Relationships
4.1.2 Name, Role, Value
Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions include:
1.3.1 Info and Relationships
Most controls in the product expose programmatic role information, which conveys available actions to assistive technology. Exceptions include:
4.1.2. Name, Role, Value
For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:
2.1.1 Keyboard Navigation
The position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 2.4.7 Focus Visible
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:
4.1.3. Status Messages
The product allows assistive technology to modify most states and properties of controls. Exceptions include:
4.1.2. Name, Role, Value
The product allows assistive technology to modify the values and text of most [input] controls. Exceptions include:
4.1.2. Name, Role, Value
Templates in the product enable authors to create a range of content which partially conforms to WCAG 2.2 Levels A and AA. Exceptions include in the Edit email page:
1.4.11 Non-Text Contrast
2.1.1 Keyboard
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
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