Adobe Accessibility Conformance Report International Edition

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:

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 on the following pages: Email Designer - Personalization Editor; Journey Properties flyout; Create offer workflow - Step 1: Details; Campaign report; Channel configurations: Creation flow for email channel; Content fragments: creation; Create audience - build rule; Create offer workflow - Step 3: Add Representations; Content creation in email designer; Create decision policy Workflow - Step 1: Details.

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 on the following page: Email Designer - Personalization Editor.

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 on the following pages: This occurs on the following pages: Create offer workflow - Step 3: Add Representations; Create decision policy Workflow - Step 2: Add Decision Scopes; Create decision policy Workflow - Step 3: Add Fallback Offer; Campaign report; Create offer workflow - Audiences panel.

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 page: Campaign report.

The long description for a complex image does not adequately 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 available in the image. This occurs on the following page: Draft journey.

A decorative image is not hidden from assistive technologies, so a screen reader will announce it unnecessarily. This occurs on the following page: Create Campaign workflow-Actions tab.

A complex image has a short text alternative that is not meaningful, so people who are blind and/or use a screen reader may not be able to understand the information available in the image. This occurs on the following page: Campaign report.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.2.1 (Web)
• 10.1.2.1 (Non-web document)
• 11.1.2.1.1 (Open Functionality Software)
• 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.2.2 Captions (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.2.2 (Web)
• 10.1.2.2 (Non-web document)
• 11.1.2.2 (Open Functionality Software)
• 11.1.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.2.3 (Web)
• 10.1.2.3 (Non-web document)
• 11.1.2.3.1 (Open Functionality Software)
• 11.1.2.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.3.1 Info and Relationships (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.3.1 (Web)
• 10.1.3.1 (Non-web document)
• 11.1.3.1.1 (Open Functionality Software)
• 11.1.3.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Most visual structure and relationship information is not provided through semantics. Examples include:

Some content that is visually presented as multiple lists is not marked up as a list, so the presence and structure of each list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Create decision policy Workflow - Step 4: Summary; Create decision policy Workflow - Step 2: Add Decision Scopes.

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 on the following pages: Create audience - build rule-Attributes tab; Create decision policy Workflow - Step 2: Add Decision Scopes; Create audience - build rule; Content creation in email designer; Create audience - build rule-Audiences tab; Create offer workflow - Step 2: Add Constraints; Create Campaign workflow-Properties tab; Create audience - build rule-Events tab; Campaign report.

Some blocks of content have incorrect semantic markup, so each block's meaning, structure, or relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Create Campaign workflow-Properties tab; Email Designer - Personalization Editor.

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: Create Journey; Create offer workflow - Step 2: Add Constraints; Campaign report; Create decision policy Workflow - Step 1: Details; Create Journey workflow-Exit Criteria; Create decision policy Workflow - Step 3: Add Fallback Offer; Content fragments: creation; Channel configurations: Creation flow for email channel.

An element's programmatic role requires that the element have a parent element, but the parent element is 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 without the context provided by the parent. This occurs on the following page: Create offer workflow - Step 3: Add Representations.

One or more data cells is incorrectly marked up as a header cell in a table, so the table structure and the header/data relationship between the cell(s) and other cells in the table will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following page: Journey inventory page (Browse tab)-List View.

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: Email Designer - Personalization Editor; Orchestration; Campaign report; Create decision policy Workflow - Step 1: Details; Create Journey workflow-Exit Criteria; Create audience - build rule-Attributes tab; Create offer workflow - Step 4: Review; Channel configurations: Creation flow for email channel; Journey Properties flyout; Create decision policy Workflow - Step 3: Add Fallback Offer; Create offer workflow - Step 2: Add Constraints; Create offer workflow - Step 1: Details; Create offer workflow - Audiences panel.

Some groups of form controls are not programmatically associated with their group label, so the purpose of individual controls in each group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following pages: Campaign report; Create offer workflow - Step 3: Add Representations; Home page.

Data is arranged visually like a data table, but the programmatic table header markup is missing or incomplete. People who are blind and/or use a screen reader will not be aware of the association between the table headers and their related data. This occurs on the following page: Create decision policy Workflow - Step 3: Add Fallback Offer.

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: Campaign report.

Some information, structure, and/or relationships are only presented visually but not conveyed programmatically, so context provided to sighted users is not available to people who are blind. This occurs on the following pages: Create audience - build rule-Audiences tab; Create audience - build rule-Attributes tab; Create audience - compose audience.

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: Create offer workflow - Step 3: Add Representations; Create decision policy Workflow - Step 2: Add Decision Scopes; Channel configurations: Creation flow for email channel.

A set of checkboxes is not programmatically grouped, so the group label for the 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 page: Channel configurations: Creation flow for email channel.

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 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 page: Create audience - build rule.

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: Journey Properties flyout.

1.3.3 Sensory Characteristics (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.3.3 (Web)
• 10.1.3.3 (Non-web document)
• 11.1.3.3 (Open Functionality Software)
• 11.1.3.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

1.4.1 Use of Color (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.4.1 (Web)
• 10.1.4.1 (Non-web document)
• 11.1.4.1 (Open Functionality Software)
• 11.1.4.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Most functions of the product do not convey information through color alone. Exceptions include:

Color is used 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 on the following pages: Journey Properties flyout; Create offer workflow - Audiences panel; Create decision policy Workflow - Step 2: Add Decision Scopes.

Color is used as the only method to convey information 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: Creation flow header and following page: Campaign report.

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)

2.1.1 Keyboard (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.1.1 (Web)
• 10.2.1.1 (Non-web document)
• 11.2.1.1.1 (Open Functionality Software)
• 11.2.1.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Most product functionality can be operated through a keyboard interface. Exception includes:

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 on the following pages: Campaign report; Create Journey; Email Designer - Personalization Editor; Orchestration; Create audience - compose audience; Create offer workflow - Step 1: Details; Draft journey; Create decision policy Workflow - Step 2: Add Decision Scopes.

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

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)

Web: In most cases, when a time limit exists, the user is given an option to turn off, adjust, or extend the time limit. Exception includes:

Some content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs on the following pages: Channel configurations: Creation flow for email channel; Create Journey.

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)

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)

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. Exception includes:

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: Create Journey; Content fragments: creation; Content creation in email designer; Create Campaign workflow-Properties tab; Email Designer - Personalization Editor; Channel configurations: Creation flow for email channel; Create audience - compose audience.

2.4.3 Focus Order (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.4.3 (Web)
• 10.2.4.3 (Non-web document)
• 11.2.4.3 (Open Functionality Software)
• 11.2.4.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Most components receive focus in a meaningful order. Exceptions include:

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 in the following component: Left hand navigation and following pages: Journey Properties flyout; Campaign report; Create decision policy Workflow - Step 2: Add Decision Scopes; Create Journey workflow-Exit Criteria; Email Designer - Personalization Editor; Create audience - build rule.

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 on the following pages: Campaign report; Journey Properties flyout; Create decision policy Workflow - Step 3: Add Fallback Offer.

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: Create offer workflow - Step 4: Review.

Keyboard focus is not confined within a modal, 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 page: Create offer workflow - Step 4: Review.

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 most links can be determined from the link text alone or from the link text and its programmatic context. Most components receive focus in a meaningful order. Exception includes:

The purpose of the link is not made clear by its text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where the link goes. This occurs on the following page: Channel configurations: Creation flow for email channel.

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: Campaign report; Email Designer - Personalization Editor.

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: Create Journey; Create decision policy Workflow - Step 3: Add Fallback Offer; Campaign report; Channel configurations: Creation flow for email channel; Content creation in email designer; Create offer workflow - Step 2: Add Constraints; Home page; Create decision policy Workflow - Step 2: Add Decision Scopes; Journey Properties flyout; Create offer workflow - Step 3: Add Representations.

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

3.1.1 Language of Page (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.1.1 (Web)
• 10.3.1.1 (Non-web document)
• 11.3.1.1.1 (Open Functionality Software)
• 11.3.1.1.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

3.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)

Web: In most cases, when a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user, or the user is informed about the change ahead of time. Exception includes:

When a user changes the setting of some user interface controls (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriented. This occurs on the following pages: Channel configurations: Creation flow for email channel; Create offer workflow - Step 2: Add Constraints; Home page.

3.2.6 Consistent Help (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

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:

A form field with an error is 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 the error occurred. This occurs on the following page: Create decision policy Workflow - Step 2: Add Decision Scopes.

Errors for some form inputs (such as text input fields, radio buttons, select dropdowns, or checkboxes) are 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 pages: Journey Properties flyout; Content fragments: creation; Create offer workflow - Step 1: Details; Create Campaign workflow-Properties tab.

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: Journey inventory page (Browse tab)-List View; Create audience - build rule-Audiences tab; Campaign report.

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: Create offer workflow - Step 1: Details; Journey Properties flyout.

Select or dropdown control missing a visible label so the purpose of the Select or dropdown control is not clear. This occurs on the following pages: Journey Properties flyout; Email Designer - Personalization Editor; Campaign report.

3.3.7 Redundant Entry (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

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:

Multiple form input elements do 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 determine the name of each element and may not understand its purpose or how to interact with it. This occurs on the following pages: Create Journey workflow-Search and Filter; Campaign report.

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 on the following pages: Campaign report; Channel configurations: Creation flow for email channel; Create Campaign workflow-Actions tab; Create decision policy Workflow - Step 2: Add Decision Scopes.

Multiple elements that appear and function like a slider 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 value or how to interact with it. This occurs on the following pages: Campaign report; Create Journey; Content creation in email designer.

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 on the following pages: Create audience - build rule-Audiences tab; Campaign report.

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: Home page; Campaign report; Create offer workflow - Step 3: Add Representations.

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 page: Create decision policy Workflow - Step 3: Add Fallback Offer.

Multiple elements have 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 each element or how to interact with it. This occurs on the following pages: Journey Properties flyout; Create Journey; Create Campaign workflow-Actions tab; Email Designer - Personalization Editor.

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 page: Channel configurations: Creation flow for email channel.

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 page: Create Campaign workflow-Properties 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 on the following pages: Campaign report; Create audience - build rule-Audiences tab; Create offer workflow - Step 1: Details; Create Journey; Create audience - build rule-Attributes tab; Channel configurations: Creation flow for email channel; Create decision policy Workflow - Step 2: Add Decision Scopes; Create audience - build rule-Events tab; Email Designer - Personalization Editor.

Multiple breadcrumb regions are missing one or more required attributes in their HTML code that provides the programmatic role, name, state, or another property of the region and its contents 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 current state or how to interact with each region and its contents. This occurs on the following pages: Create audience - build rule-Audiences tab; Create audience - build rule-Attributes tab.

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: Create audience - build rule-Audiences tab; Campaign report; Email Designer - Personalization Editor.

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: Channel configurations: Creation flow for email channel; Create Journey workflow-Exit Criteria.

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: Campaign report; Email Designer - Personalization Editor; Create Journey; Channel configurations: Creation flow for email channel; Draft journey.

When a button is pressed, its 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 button is pressed. This occurs on the following page: Campaign report.

When a control is disabled, its 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 control is disabled. This occurs on the following page: Create Journey.

An element's HTML code has syntax errors, 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: Home page.

The "application" role is incorrectly applied to an element or group of elements, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, structure, or content of the element(s) or how to interact with it. This occurs on the following page: Create audience - compose audience.

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: Create decision policy Workflow - Step 2: Add Decision Scopes; Email Designer - Personalization Editor; Campaign report.

Multiple elements are missing or have 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 each element and may not understand its purpose or content or how to interact with it. This occurs on the following pages: Create audience - build rule-Events tab; Create offer workflow - Step 1: Details.

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: Campaign report.

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 component: Left hand navigation and following pages: Create audience - build rule-Audiences tab; Create audience - build rule-Attributes tab; Create decision policy Workflow - Step 2: Add Decision Scopes.

[Accessibility] - State: Expand/collapse state of the element is missing or incorrect - Campaign report (Table of contents button). This occurs on the following pages: Campaign report; Create audience - build rule; Create decision policy Workflow - Step 4: Summary; Create decision policy Workflow - Step 2: Add Decision Scopes; Create audience - build rule-Events tab; Home page; Create audience - build rule-Audiences tab.

ARIA attributes does not contain valid values - Content creation in email designer (Content tab control). This occurs on the following page: Content creation in email designer.

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. Exceptions 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 on the following pages: Campaign report; Create audience - build rule; Home page; Create decision policy Workflow - Step 2: Add Decision Scopes; Create audience - build rule-Attributes tab; Create offer workflow - Step 2: Add Constraints; Content creation in email designer; Create Journey.

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: Left hand navigation and following pages: Campaign report; Create decision policy Workflow - Step 2: Add Decision Scopes; Home page.

The color contrast ratio between text placed over an image and that image is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following page: Campaign report.

The color contrast ratio between placeholder text in an input and the 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 on the following page: Journey Properties flyout.

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: Most content is readable and functional when browser zoom is set to 200% of its initial size. Exceptions 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 on the following pages: Create Journey; Create audience - build rule-Attributes tab; Create decision policy Workflow - Step 3: Add Fallback Offer; Create audience - compose audience; Content creation in email designer; Campaign report; Email Designer - Personalization Editor; Channel configurations: Creation flow for email channel; Resume Journey.

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 on the following pages: Journey inventory page (Browse tab)-List View; Resume Journey; Create audience - compose audience; Create offer workflow - Audiences panel; Email Designer - Personalization Editor; Campaign report.

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: On most pages, when content can be presented visually using only text, an image of text is not used to present that text. Exception includes:

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: Draft journey.

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 does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following pages: Content fragments: creation; Create Campaign workflow-Properties tab; Channel configurations: Creation flow for email channel; Create offer workflow - Step 3: Add Representations; Create offer workflow - Step 1: Details; Create Campaign workflow-Actions tab; Create decision policy Workflow - Step 4: Summary.

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 in the following component: Creation flow header and following pages: Create audience - build rule-Audiences tab; Create Journey; Content creation in email designer; Campaign report; Journey inventory page (Browse tab)-List View; Home page; Channel configurations: Creation flow for email channel; Create audience - build rule-Attributes tab; Create offer workflow - Audiences panel; Create Campaign workflow-Properties tab.

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 on the following pages: Campaign report; Content creation in email designer; Journey Properties flyout; Journey inventory page (Browse tab)-List View; Draft journey; Create decision policy Workflow - Step 3: Add Fallback Offer; Create offer workflow - Step 4: Review; Resume Journey; Home page; Create offer workflow - Audiences panel; Create Journey; Create audience - build rule; Create audience - compose audience; Create offer workflow - Step 2: Add Constraints; Orchestration; Create audience - build rule-Audiences tab; Email Designer - Personalization Editor; Create Journey workflow-Exit Criteria.

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 meaningful non-text content elements have sufficient contrast. Exceptions include:

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 on the following pages: Journey Properties flyout; Email Designer - Personalization Editor; Campaign report; Content creation in email designer; Create decision policy Workflow - Step 1: Details; Create decision policy Workflow - Step 2: Add Decision Scopes; Create decision policy Workflow - Step 3: Add Fallback Offer; Channel configurations: Creation flow for email channel; Create audience - build rule-Audiences tab; Create offer workflow - Step 1: Details; Create offer workflow - Audiences panel.

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: Campaign report; Create audience - build rule.

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 on the following pages: Journey Properties flyout; Campaign report.

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: Campaign report; Create audience - build rule.

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 component: Creation flow header and following pages: Campaign report; Create Journey; Home page; Create audience - build rule-Attributes tab; Content creation in email designer; Email Designer - Personalization Editor; Journey inventory page (Browse tab)-List View; Create audience - build rule-Audiences tab; Create Journey workflow-Exit Criteria.

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. Exception includes:

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: Campaign report; Create decision policy Workflow - Step 2: Add Decision Scopes.

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 cases, when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. Exceptions include:

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 on the following pages: Draft journey; Campaign report.

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 on the following pages: Campaign report; Draft journey.

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 for form and interactive controls are informative. 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: Email Designer - Personalization Editor; Campaign report; Create decision policy Workflow - Step 4: Summary; Create Campaign workflow-Actions tab; Create offer workflow - Step 1: Details; Journey Properties flyout; Create audience - compose audience; Create decision policy Workflow - Step 2: Add Decision Scopes; Channel configurations: Creation flow for email channel; Create decision policy Workflow - Step 3: Add Fallback Offer.

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 on the following pages: Email Designer - Personalization Editor; Create Journey; Campaign report; Create offer workflow - Step 3: Add Representations; Channel configurations: Creation flow for email channel; Create offer workflow - Step 2: Add Constraints; Content creation in email designer; Create decision policy Workflow - Step 2: Add Decision Scopes; Create audience - compose audience; Create audience - build rule; Create Journey workflow-Exit Criteria; Home page; Journey Properties flyout; Create decision policy Workflow - Step 4: Summary; Create audience - build rule-Audiences tab; Orchestration; Create offer workflow - Audiences panel.

2.4.7 Focus Visible (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.2.4.7 (Web)
• 10.2.4.7 (Non-web document)
• 11.2.4.7 (Open Functionality Software)
• 11.2.4.7 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software)
• 504.2 (Authoring Tool)
• 602.3 (Support Docs)

Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include:

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 on the following pages: Create Journey; Journey Properties flyout; Content creation in email designer; Orchestration; Campaign report; Draft journey; Create audience - build rule; Email Designer - Personalization Editor.

The visual focus indicator for multiple interactive elements (such as links, buttons, or form inputs) is not visible, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following pages: Create audience - build rule; Create decision policy Workflow - Step 3: Add Fallback Offer; Create decision policy Workflow - Step 1: Details; Create offer workflow - Step 3: Add Representations; Campaign report; Create offer workflow - Step 1: Details; Create decision policy Workflow - Step 2: Add Decision Scopes.

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. Exception includes:

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: Create audience - build rule.

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. Exception includes:

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 on the following pages: Content creation in email designer; Campaign report; Create Journey; Create audience - build rule-Events tab; Draft journey; Email Designer - Personalization Editor; Journey inventory page (Browse tab)-List View; Create audience - compose audience; Create offer workflow - Step 1: Details; Create audience - build rule-Attributes tab; Create audience - build rule-Audiences tab; Create decision policy Workflow - Step 2: Add Decision Scopes.

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 on the following pages: Create decision policy Workflow - Step 1: Details; Create audience - compose audience; Channel configurations: Creation flow for email channel.

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 on the following pages: Orchestration; Campaign report; Create offer workflow - Step 2: Add Constraints; Create audience - build rule-Audiences tab; Create offer workflow - Step 3: Add Representations; Journey Properties flyout.

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)

Web: On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. Exception includes:

A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following page: Email Designer - Personalization Editor.

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: When status messages do not receive focus, the product does not provide the update to assistive technology. Example includes:

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 component: Creation flow header and following pages: Create decision policy Workflow - Step 2: Add Decision Scopes; Create offer workflow - Step 1: Details; Create offer workflow - Step 3: Add Representations; Create audience - compose audience; Email Designer - Personalization Editor; Create Campaign workflow-Actions tab; Create Journey workflow-Exit Criteria; Journey inventory page (Browse tab)-List View; Home page; Create decision policy Workflow - Step 3: Add Fallback Offer; Journey Properties flyout; Create Journey workflow-Search and Filter; Content creation in email designer; Content fragments: creation; Orchestration; Channel configurations: Creation flow for email channel; Create audience - build rule; Create offer workflow - Step 4: Review; Create decision policy Workflow - Step 1: Details; Create audience - build rule-Audiences tab; Create Campaign workflow-Properties tab; Create audience - build rule-Events tab; Create offer workflow - Audiences panel; Create audience - build rule-Attributes tab; Campaign report.

Web: Most functionality is 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.2.1 Timing Adjustable

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.1.2 Language of Parts

As noted in 3.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 4.1.2 Name, Role, Value

Web: Most functionality is 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.2.1 Timing Adjustable

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.1.2 Language of Parts

As noted in 3.2.2 On Input

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 functionality is 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 without hearing. Exception includes:

As noted in 3.1.2 Language of Parts

Web: Most functionality is usable with limited hearing. Exception includes:

As noted in 3.1.2 Language of Parts

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.2.1 Timing Adjustable

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 functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. 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.2.1 Timing Adjustable

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.1.2 Language of Parts

As noted in 3.2.2 On Input

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: 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. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: 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. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: 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. Exception includes:

As noted in 1.3.1 Info and Relationships

Web: For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exception includes:

As noted in 4.1.2 Name, Role, Value

Web: 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

Web: 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. Exception includes:

As noted in 2.1.1 Keyboard

Web: On most pages, 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. Exception includes:

As noted in 2.4.7 Focus Visible

Web: In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exception includes:

As noted in 4.1.3 Status Messages

Web: Most functionality is 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.2.1 Timing Adjustable

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.1.2 Language of Parts

As noted in 3.2.2 On Input

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 functionality is usable with limited vision. Exceptions include:

As noted in 1.1.1 Non-text Content

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.2.1 Timing Adjustable

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.2.2 On Input

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 functionality is 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 without hearing. Exceptions include:

As noted in 1.1.1 Non-text Content

As noted in 2.2.1 Timing Adjustable

Web: Most functionality is usable with limited hearing. Exceptions include:

As noted in 2.2.1 Timing Adjustable

Web: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

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.2.2 On Input

As noted in 4.1.2 Name, Role, Value

Web: Most functionality is usable by people with limited reach. Exceptions include:

As noted in 2.5.3 Label in Name

Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions include:

As noted in 1.4.12 Text Spacing

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.2.1 Timing Adjustable

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.2.2 On Input

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.3 Status Messages