Adobe Campaign-cloud-accessibility-conformance-report-may-2026 Accessibility Conformance Report

Criteria

Conformance Level

Remarks and Explanations

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: Partially Supports

Authored Content: Partially Supports

Web: Most visual structure and relationship information is provided through element semantics. Exceptions 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: Schema Definition; Schema Details; Email: Edit Content; Add Conditions; Campaign Settings; Acquisition.

One or more data cells are 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: Create Typology.

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: Home page; Open Email Designer; Email: Edit Properties; Email: Add Language; Email Delivery: Edit Content; Import HTML; Target Mapping Details; Schema Definition; Create Delivery Dashboard; Create Campaign; New Campaign; Campaign reports; Profile Details; Audience Details; Reports.

A set of radio buttons is not programmatically grouped, so the group label for the 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 page: Email: Edit Properties.

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: Profile Details.

Authored Content: Authors can provide appropriate semantics, object information and textual equivalents for most visual structure and relationship information. Exceptions include:

A block of text is marked up as a heading but is not a heading, 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 page: Email Delivery: Edit Content.

A group of form controls is not programmatically associated with their group label, so the purpose of individual controls in the group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following page: Import HTML.

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: Partially Supports

Authored Content: Supports

Web: The product presents most content in a meaningful sequence. Exceptions include:

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 pages: Email: Edit Content; Campaign logs; Campaign reports; Create Typology; Explorer; Targeting Dimension.

The screen reader announcement of static text does not match the visual text displayed, so the intended meaning of the text will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following page: Build Audience.

Authored Content: The product allows authors to present content in a meaningful sequence.

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)

Web: Supports

Authored Content: Supports

Web: Instructions do not rely solely on sensory characteristics.

Authored Content: Authors can ensure that content meets this criterion.

Criteria

Conformance Level

Remarks and Explanations

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: Partially Supports

Authored Content: Supports

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 a control, 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 page: Open Email Designer.

Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs in the following component: Search.

Authored Content: Authors can ensure that content meets this criterion.

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)

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain audio that plays automatically.

Authored Content: Authored content does not contain audio that plays automatically.

Criteria

Conformance Level

Remarks and Explanations

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: Partially Supports

Authored Content: Partially Supports

Web: Most product functionality can be operated through a keyboard interface. Exceptions 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 on the following pages: Email: Edit Content; Add Conditions.

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: Email: Edit Content.

An action cannot be performed when using a screen reader, so people who are blind and others who use a screen reader cannot perform this action. This occurs on the following page: Add Conditions.

Authored Content: Authors can ensure that content most content meets this criterion. Exceptions 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 on the following page: Email Delivery: Edit Content.

2.1.2 No Keyboard Trap (Level A)

Also applies to:

EN 301 549 Criteria

9.2.1.2 (Web)
10.2.1.2 (Non-web document)
11.2.1.2 (Open Functionality Software)
11.2.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

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

Web: Supports

Authored Content: Supports

Web: The product does not include keyboard traps.

Authored Content: Authored content does not include keyboard traps.

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

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not provide character key shortcuts.

Authored Content: Authored content does not provide character key shortcuts.

Criteria

Conformance Level

Remarks and Explanations

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: Partially Supports

Authored Content: Partially Supports

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:

Toast notifications automatically disappear after a fixed time period without user control, preventing users from reading or acting on the information at their own pace. This occurs on the following pages: Email: Edit Properties; Campaign Settings; Open Email Designer; Schema Definition; Create Campaign; Profile Details; Add Conditions; Build Audience.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

Toast notifications automatically disappear after a fixed time period without user control, preventing users from reading or acting on the information at their own pace. This occurs on the following page: Import HTML.

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)

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not include elements which move, blink, scroll, or auto-update.

Authored Content: Authors can ensure that content meets this criterion.

Criteria

Conformance Level

Remarks and Explanations

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)

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain flashing content.

Authored Content: Authors can ensure that content does not flash.

Criteria

Conformance Level

Remarks and Explanations

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

Web: Supports

Authored Content: Supports

Web: The product provides mechanism to bypass repeated blocks.

Authored Content: Authored content does not contain repeated blocks that would require a skip mechanism.

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: Partially Supports

Authored Content: Supports

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 Delivery; Email Delivery: Edit Content; Schema Details; Campaigns; Email: Edit Properties; Create Campaign; Create External Account; New Campaign; Email: Add Language; Target Mapping Details; Create Workflow; Build Audience; Email: Edit Content.

Authored Content: The product allows authors to customize the page title.

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: Partially Supports

Authored Content: Supports

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

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 on the following pages: Add Conditions; Campaigns; New Campaign; Campaign logs; Targeting Dimension; Create Typology; Targeting Dimension; Open Email Designer.

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: Header.

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: Create Typology; Campaign reports; Email: Edit Content; Explorer; Targeting Dimension.

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: Email: Add Language.

Authored Content: Authors can ensure that content meets this criterion

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: Partially Supports

Authored Content: Supports

Web: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. 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: Home page.

Authored Content: Authors can ensure that content meets this criterion

Criteria

Conformance Level

Remarks and Explanations

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

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not rely on multipoint or path-based gestures.

Authored Content: Authored content does not rely on multipoint or path-based gestures.

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

Web: Supports

Authored Content: Supports

Web: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click.

Authored Content: Authors can ensure that content meets this criterion.

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 (Open Functionality Software)
11.2.5.3 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Authored Content: Supports

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: Audit Details; Email: Edit Properties.

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 in the following component: Filter and following pages: Reports; Create External Account; Create Delivery Dashboard; Home page; Email: Edit Properties; Schema Details; Target Mapping Details; Add Conditions.

Authored Content: Authors can ensure that the accessible names of controls contain the text of their visible labels.

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

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not have functionality operated by device motion or user motion.

Authored Content: Authored content does not have functionality operated by device motion or user motion.

Criteria

Conformance Level

Remarks and Explanations

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)

Web: Supports

Authored Content: Supports

Web: The language is programmatically determinable within the product.

Authored Content: Authors can set the language of the page.

Criteria

Conformance Level

Remarks and Explanations

3.2.1 On Focus (Level A)

Also applies to:

EN 301 549 Criteria

9.3.2.1 (Web)
10.3.2.1 (Non-web document)
11.3.2.1 (Open Functionality Software)
11.3.2.1 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508

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

Web: Supports

Authored Content: Supports

Web: Components do not initiate a change of context when focused.

Authored Content: Authors can ensure that content meets this criterion.

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

Authored Content: Supports

Web: Changes of context do not occur automatically on user input.

Authored Content: Authors can ensure that content meets this criterion.

3.2.6 Consistent Help (Level A 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 – Does not apply

Web: Supports

Authored Content: Supports

Web: The product contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.

Authored Content: Authors can ensure that content meets this criterion.

Criteria

Conformance Level

Remarks and Explanations

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: Partially Supports

Authored Content: Supports (Not Applicable)

Web: Most input errors are identified and described to the users in text. Exception includes:

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: Profile Details.

Authored Content: Authored content does not contain user input controls which would require error identification.

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: Partially Supports

Authored Content: Partially Supports

Web: Labels are provided for most input fields. Exceptions include:

The label for a form field is missing, so the field's purpose is not clear. This occurs on the following page: Create Typology.

A select or dropdown control is missing a visible label, so the information or selection expected before interacting with the control cannot be understood. This occurs on the following page: Email: Edit Properties.

Authored Content: Authors can ensure that most content meets this criterion. Exception includes:

A select or dropdown control is missing a visible label, so the information or selection expected before interacting with the control cannot be understood. This occurs on the following page: Email Delivery: Edit Content.

3.3.7 Redundant Entry (Level A 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 – Does not apply

Web: Supports

Authored Content: Supports

Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.

Authored Content: Authors can ensure that content meets this criterion.

Criteria

Conformance Level

Remarks and Explanations

4.1.1 Parsing (Level A)

Also applies to:

EN 301 549 Criteria

9.4.1.1 (Web)
10.4.1.1 (Non-web document)
11.4.1.1.1 (Open Functionality Software)
11.4.1.1.2 (Closed Software) - 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: Does not apply

Authored Content: Does not apply

Web: This criterion was removed from WCAG 2.2.

Authored Content: This criterion was removed from WCAG 2.2.

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: Partially Supports

Authored Content: Partially Supports

Web: User interface components in some product functions do not provide programmatic name, role, state, or value information. Examples include:

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 pages: Targeting Dimension; Schema Preview; Schema Definition; Edit code; Email: Add Language; Campaign Settings; Create Audience; Select Attribute.

The content of a tooltip 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 page: Add Conditions.

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: Create Delivery Dashboard; Reports.

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: Audit Details; Explorer; Email: Edit Properties.

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: Add Conditions; Open Email Designer.

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: Add Conditions; Profile Details; Schema Definition; Email: Add Language; Build Audience.

An element 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 page: Email: Edit Content.

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: Create Delivery Dashboard.

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 on the following pages: Select Attribute; Add Conditions; Edit Code.

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 component: Header and following pages: Reports; Build Audience; Add Conditions.

Authored Content: Authors can ensure that most content meets this criterion. Exception includes:

A button does not have a programmatic role, so its 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 page: Email Delivery: Edit Content.

Criteria

Conformance Level

Remarks and Explanations

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)

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain live synchronized media.

Authored Content: Authored content does not contain live synchronized media.

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)

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain prerecorded video content that would require audio description.

Authored Content: Authored content does not contain video content that would require audio description.

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

Web: Supports

Authored Content: Supports

Web: Content does not restrict its view and operation to a single display orientation.

Authored Content: Authors can ensure that content does not restrict its view and operation to a single display orientation.

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 (Open Functionality Software)
11.1.3.5 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Authored Content: Supports

Web: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Example includes:

No programmatic purpose is provided for an input element (like a text input field), so browsers or assistive technology are not able to automatically suggest information to fill in the input. This occurs on the following page: Profile Details.

Authored Content: Authors can ensure that content meets this criterion.

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: Partially Supports

Authored Content: Supports

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: Add Conditions; Edit Code.

The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of the control. This occurs in the following component: Left Navigation.

Authored Content: Authors can ensure that content meets this criterion.

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: Partially Supports

Authored Content: Supports

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 in the following component: Filter and following pages: History Report; Schema Definition; Create Audience; Email: Add Language; Add Conditions; New Campaign.

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: Home page; Schema Preview; Build Audience.

Authored Content: Using browser zoom, text can be resized up to 200 percent without loss of content or functionality

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

Authored Content: Supports

Web: The product uses text instead of images of text, except for branding elements that are considered essential.

Authored Content: Authors can ensure that content meets this criterion.

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.1 (Open Functionality Software)
11.1.4.10.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: Does Not Support

Authored Content: Partially Supports

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: Audience Details; Reports; Target Mapping Details; Create External Account; Campaign Settings; Email: Edit Properties; Audit Details; Profile Details; Predefined Filters Details.

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 components: Header; Filter and following pages: Add Conditions; Create External Account; Open Email Designer; Email: Edit Content; Schema Details; Target Mapping Details.

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: Email: Edit Properties; New Campaign; Add Conditions; Campaigns; Home page; Create Delivery Dashboard; Schema Preview; History Report; Schema Definition; Create Audience; Create Workflow; Build Audience; Explorer; Email: Add Language; Campaign logs; Create Delivery.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

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 page: Email Delivery: Edit Content.

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 page: Email Delivery: Edit Content.

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: Partially Supports

Authored Content: Partially Supports

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: Add Conditions; Email: Edit Properties; Create External Account; Build Audience.

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: New Campaign; Email: Edit Properties; Email: Edit Content; Email: Add Language; Target Mapping Details; Edit code; Create Delivery; Dashboard' Email Delivery: Edit Content; Campaigns; Build Audience; Create Campaign; New Campaign; Campaign Settings; Campaign reports' Add Conditions' Audience Details' Home Page' Create Workflow.

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 component: Date Picker and following pages: Create Delivery Dashboard; Create Typology; Home page; Select Attribute; Reports; Edit Code.

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 on the following pages: Add Conditions; Build Audience.

Authored Content: Authors can ensure that most content meets this criterion. Exception includes:

An icon (or part of the icon required to understand its content) does 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 icon. This occurs on the following page: Email Delivery: Edit Content.

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

Authored Content: Supports

Web: The product supports the required text style properties without loss of content or functionality.

Authored Content: Authors can ensure that content meets this criterion.

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: Partially Supports

Authored Content: Supports

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 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: Select Attribute; Schema Preview; Create Typology.

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: Select Attribute; Schema Definition; Schema Preview; Create Typology; Edit Code; Add Conditions.

Authored Content: Authors can ensure that content meets this criterion.

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

Web: Supports

Authored Content: Supports

Web: Users can locate web pages in the product through multiple ways.

Authored Content: Authors can ensure that content meets this criterion.

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: Partially Supports

Authored Content: Partially Supports

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: Add Conditions; Schema Preview; Target Mapping Details; Select Attribute; Select campaign template; Select folder; Select group or operator; Campaign Settings.

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: Search and following pages: Edit Code; Select Attribute; Home page; Schema Definition; Reports; Email: Edit Properties; Email: Add Language; Add Conditions; Create Delivery; Create Delivery Dashboard; Campaign Settings; Target Mapping Details; Create Campaign; Create Workflow.

Authored Content: Authors can ensure that most content meets this criterion. Exceptions include:

A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following page: Email Delivery: Edit Content.

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: Partially Supports

Authored Content: Partially Supports

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: Campaign reports; Add Conditions; Home page; Open Email Designer.

The visual focus indicator for an interactive element (such as a link, button, or form input) is not visible, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs in the following component: Filter.

Authored Content: Authors can ensure that most content meets this criterion.

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 page: Email Delivery: Edit Content.

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

Authored Content: Supports

Web: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

Authored Content: Authors can ensure that content meets this criterion.

2.5.7 Dragging Movements (Level AA 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 – Does not apply

Web: Partially Supports

Authored Content: Partially Supports

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: Email: Edit Content; Home page; Build Audience; Create topology; Create Delivery Dashboard; Explorer; Campaigns; New Campaign; Campaign logs; Campaign reports; Targeting Dimension; Reports.

Authored Content: Authors can ensure that most content meets this criterion.

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 page: Email Delivery: Edit Content.

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: Partially Supports

Authored Content: Supports

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

A target's hit area does 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 page: Profile Details.

Authored Content: Authors can ensure that content meets this criterion.

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

Authored Content: Supports

Web: Changes of language for passages or phrases can be programmatically determined.

Authored Content: Authors can set the language for individual phrases within content.

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

Web: Supports

Authored Content: Supports

Web: When navigational mechanisms are repeated in the product they occur in a consistent relative order.

Authored Content: Authors can ensure that content meets this criterion.

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

Web: Supports

Authored Content: Supports

Web: Components with the same functionality are identified consistently.

Authored Content: Authors can ensure that components with the same functionality are identified consistently in a set of pages.

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)

Web: Supports

Authored Content: Supports (Not Applicable)

Web: Where input errors are automatically detected, suggestions for correction are provided to the user.

Authored Content: Authored content does not detect input errors that are displayed to users.

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)

Web: Supports

Authored Content: Supports (Not Applicable)

Web: The product does not process legal commitments or financial transactions. When editing files, changes to user-controllable data are reversible or can be confirmed before finalizing.

Authored Content: Authored content does not contain legal or financial data and does not modify user-controllable data.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria - Does not apply

Revised Section 508 – Does not apply

Web: Supports

Authored Content: Supports

Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the website.

Authored Content: Authors can ensure that content meets this criterion.

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) - Does not apply
11.4.1.3 (Open Functionality Software) - Does not apply
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: Partially Supports

Authored Content: Partially Supports

Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exception 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 components: Header; Search and following pages: Open Email Designer; Create Typology; Email: Edit Properties; Explorer; Create External Account; Reports; Predefined Filters Details; Create Workflow; Create Delivery Dashboard; Add Conditions; Select Attribute; Create Campaign; Schema Preview; Edit Code; Campaign Settings; Campaign reports; Email: Edit Content.

Authored Content: Authors can ensure that most content meets this criterion. 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 on the following page: Email Delivery: Edit Content.

Criteria

Conformance Level

Remarks and Explanations

302.1 Without Vision

Web: Partially Supports

Authored Content: Partially Supports

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.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.3.1 Error Identification

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content in which most functions can be used without vision. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

As noted in 2.4.6 Headings and Labels

As noted in 4.1.2 Name, Role, Value

302.2 With Limited Vision

Web: Partially Supports

Authored Content: Partially Supports

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 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.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content in which most functions can be used with limited vision. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

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

302.3 Without Perception of Color

Web: Partially Supports

Authored Content: Supports

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

Authored Content: Authors can create content in which functions can be used with limited vision.

302.4 Without Hearing

Web: Supports

Authored Content: Supports

Web: The product is functional for users without hearing.

Authored Content: Authors can create content which is functional for users without hearing.

302.5 With Limited Hearing

Web: Supports

Authored Content: Supports

Web: The product is functional for users with limited hearing.

Authored Content: Authors can create content which is functional for users with limited hearing.

302.6 Without Speech

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not require the use of speech.

Authored Content: Authors can create content which is functional for users without speech.

302.7 With Limited Manipulation

Web: Partially Supports

Authored Content: Partially Supports

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

Authored Content: Authors can create content which is functional with limited manipulation. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

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

302.8 With Limited Reach and Strength

Web: Supports

Authored Content: Supports

Web: The product is functional with limited reach and strength.

Authored Content: Authors can create content which is functional with limited reach and strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Partially Supports

Authored Content: Partially Supports

Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:

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

Authored Content: Authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:

As noted in 1.3.1 Info and Relationships

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

Criteria

Conformance Level

Remarks and Explanations

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.2 section

See information in WCAG 2.2 section

502 Interoperability with Assistive Technology

Heading cell – no response required

502.2.1 User Control of Accessibility Features

Not Applicable

The product is not platform software, so this requirement does not apply.

502.2.2 No Disruption of Accessibility Features

Not Applicable

The product does not disrupt platform accessibility features.

502.3 Accessibility Services

Heading cell – no response required

502.3.1 Object Information

Partially Supports

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

502.3.2 Modification of Object Information

Partially Supports

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

502.3.3 Rows, Column, and Headers

Partially Supports

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

502.3.4 Values

Partially Supports

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. Exceptions include:

As noted in 4.1.2 Name, Role, Value

502.3.5 Modification of Values

Partially Supports

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. Exceptions include:

As noted in 4.1.2 Name, Role, Value

502.3.6 Label Relationships

Partially Supports

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

502.3.7 Hierarchical Relationships

Partially Supports

For most 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

502.3.8 Text

Supports

All text, text attributes (such as whether text is static or editable), and text boundaries (such as text that receives visual focus) are programmatically determinable, so they can be perceived and conveyed by assistive technology.

502.3.9 Modification of Text

Supports

When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology.

502.3.10 List of Actions

Partially Supports

For most of the elements on which one or more actions may be performed, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

502.3.11 Actions on Objects

Partially Supports

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

502.3.12 Focus Cursor

Partially Supports

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. Exceptions include:

As noted in 2.4.7 Focus Visible

502.3.13 Modification of Focus Cursor

Supports

When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.

502.3.14 Event Notification

Partially Supports

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

502.4 Platform Accessibility Features

Not Applicable

The product is not platform software, so this requirement does not apply.

503 Applications

Heading cell – no response required

503.2 User Preferences

Not Applicable

Not applicable to web.

503.3 Alternative User Interfaces

Not Applicable

The product does not provide an alternative user interface that functions as assistive technology.

503.4 User Controls for Captions and Audio Description

Heading cell – no response required

503.4.1 Caption Controls

Not Applicable

The product does not display video.

503.4.2 Audio Description Controls

Not Applicable

The product does not provide prerecorded media that requires audio description.

504 Authoring Tools

Heading cell – no response required

504.2 Content Creation or Editing

See WCAG 2.2 section

The product enables authors to create HTML content, such as emails. Content can be imported from other tools or created using built-in authoring functions which support the creation of accessible content by providing fields for Alt Text and Heading structures. See details for individual criteria in the WCAG 2.2 section

504.2.1 Preservation of Information Provided for Accessibility

Not Applicable

The product does not convert content.

504.2.2 PDF Export

Not Applicable

The product does not export PDF files

504.3 Prompts

Does Not Support

When an author inserts an image into an HTML email or landing page, the product prompts for image alt text. However, most functions in the product do not prompt authors to create accessible content.

504.4 Templates

Partially Supports

Templates in the product enable authors to create email content. None of the available templates support the creation of content that conforms to WCAG 2.0 Levels A and AA. Exceptions include:

As noted in 2.4.3 Focus Order

As noted in 2.4.7 Focus Visible

As noted in 4.1.2 Name, Role, Value

Criteria

Conformance Level

Remarks and Explanations

4.2.1 Usage without vision

Web: Partially Supports

Authored Content: Partially Supports

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.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.3.1 Error Identification

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

Authored Content: Authors can create content in which most functions can be used without vision. Exceptions include:

As noted in 1.3.1 Info and Relationships

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

As noted in 2.4.6 Headings and Labels

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

4.2.2 Usage with limited vision

Web: Partially Supports

Authored Content: Partially Supports

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

As noted in 1.1.1 Non-text Content

As noted in 1.3.5 Identify Input Purpose

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.10 Reflow

As noted in 1.4.11 Non-text Contrast

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.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Authored Content: Authors can create content in which most functions can be used with limited vision. Exceptions include:

As noted in 1.4.10 Reflow

As noted in 1.4.11 Non-text Contrast

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

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

4.2.3 Usage without perception of colour

Web: Partially Supports

Authored Content: Partially Supports

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

Authored Content: Authors can create content which is functional for users without perception of color. Exceptions include:

As noted in 1.4.11 Non-Text Contrast

4.2.4 Usage without hearing

Web: Supports

Authored Content: Supports

Web: The product is functional for users without hearing.

Authored Content: Authors can create content which is functional for users without hearing.

4.2.5 Usage with limited hearing

Web: Supports

Authored Content: Supports

Web: The product is functional for users with limited hearing.

Authored Content: Authors can create content which is functional for users with limited hearing.

4.2.6 Usage with no or limited vocal capability

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not require the use of speech.

Authored Content: Authors can create content which is functional for users without speech.

4.2.7 Usage with limited manipulation or strength

Web: Partially Supports

Authored Content: Partially Supports

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

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 4.1.2 Name, Role, Value

Authored Content: Authors can create content which is functional with limited manipulation and strength. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

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

4.2.8 Usage with limited reach

Web: Partially Supports

Authored Content: Supports

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

As noted in 2.5.3 Label in Name

Authored Content: Authors can create content which is functional with limited reach.

4.2.9 Minimize photosensitive seizure triggers

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not contain flashing content.

Authored Content: The product does not contain flashing content.

4.2.10 Usage with limited cognition, language or learning

Web: Partially Supports

Authored Content: Partially Supports

Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:

As noted in 1.3.5 Identify Input Purpose

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.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.3 Status Messages

Authored Content: Authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:

As noted in 2.2.1 Timing Adjustable

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.3 Status Messages

4.2.11 Privacy

Web: Supports (Not Applicable)

Authored Content: Supports (Not Applicable)

Web: The product does not ask for or display legal, financial, or personal data.

Authored Content: Authored content does not ask for or display legal, financial, or personal data.

Criteria

Conformance Level

Remarks and Explanations

5.1 Closed functionality

Heading cell – no response required

5.1.2 General

Heading cell – no response required

5.1.2.1 Closed functionality

See 5.2 through 13

See information in 5.2 through 13

5.1.2.2 Assistive technology

See 5.1.3 through 5.1.6

See information in 5.1.3 through 5.1.6

5.1.3 Non-visual access

Heading cell – no response required

5.1.3.1 Audio output of visual information

Not Applicable

The product does not have closed functionality.

5.1.3.2 Auditory output delivery including speech

Not Applicable

The product does not have closed functionality.

5.1.3.3 Auditory output correlation

Not Applicable

The product does not have closed functionality.

5.1.3.4 Speech output user control

Not Applicable

The product does not have closed functionality.

5.1.3.5 Speech output automatic interruption

Not Applicable

The product does not have closed functionality.

5.1.3.6 Speech output for non-text content

Not Applicable

The product does not have closed functionality.

5.1.3.7 Speech output for video information

Not Applicable

The product does not have closed functionality.

5.1.3.8 Masked entry

Not Applicable

The product does not have closed functionality.

5.1.3.9 Private access to personal data

Not Applicable

The product does not have closed functionality.

5.1.3.10 Non-interfering audio output

Not Applicable

The product does not have closed functionality.

5.1.3.11 Private listening volume

Not Applicable

The product does not have closed functionality.

5.1.3.12 Speaker volume

Not Applicable

The product does not have closed functionality.

5.1.3.13 Volume reset

Not Applicable

The product does not have closed functionality.

5.1.3.14 Spoken languages

Not Applicable

The product does not have closed functionality.

5.1.3.15 Non-visual error identification

Not Applicable

The product does not have closed functionality.

5.1.3.16 Receipts, tickets, and transactional outputs

Not Applicable

The product does not have closed functionality.

5.1.4 Functionality closed to text enlargement

Not Applicable

The product does not have closed functionality.

5.1.5 Visual output for auditory information

Not Applicable

The product does not have closed functionality.

5.1.6 Operation without keyboard interface

Heading cell – no response required

5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

See information in 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus

Not Applicable

The product does not have closed functionality.

5.1.7 Access without speech

Not Applicable

The product does not have closed functionality.

5.2 Activation of accessibility features

Not Applicable

The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features.

5.3 Biometrics

Not Applicable

The product does not use biometric forms of user identification or control. All functionality is accessible through standard input methods (keyboard, mouse, UI).

5.4 Preservation of accessibility information during conversion

Not Applicable

The product does not convert content.

5.5 Operable parts

Heading cell – no response required

5.5.1 Means of operation

Not Applicable

The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate.

5.5.2 Operable parts discernibility

Not Applicable

The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate.

5.6 Locking or toggle controls

Heading cell – no response required

5.6.1 Tactile or auditory status

Not Applicable

Tactile or auditory status is not included in the product.

5.6.2 Visual status

Not Applicable

Visual status of controls isn’t discernible in the product

5.7 Key repeat

Not Applicable

Key repeat functionality is not found in the product.

5.8 Double-strike key acceptance

Not Applicable

Double -strike key acceptance is not found in the product.

5.9 Simultaneous user actions

Not Applicable

The product does not require simultaneous user actions for core functionality. All actions triggered by key combinations are also available via the graphical user interface using mouse or sequential keyboard navigation.

11.0 General (informative)

Heading cell – no response required

11.1.1.1 through 11.4.1.3

See WCAG 2.2 section

See information in WCAG 2.2 section

11.5 Interoperability with assistive technology

Heading cell – no response required

11.5.1 Closed functionality

Heading cell – no response required

11.5.2 Accessibility services

Heading cell – no response required

11.5.2.1 Platform accessibility service support for software that provides a user interface

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.2 Platform accessibility service support for assistive technologies

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.3 Use of accessibility services

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.4 Assistive technology

Not Applicable

The product is not assistive technology.

11.5.2.5 Object information

Partially Supports

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

11.5.2.6 Row, column, and headers

Partially Supports

The row and column of most data table cells, including headers of the row and column where present, can be programmatically determined so that they can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

11.5.2.7 Values

Partially supports

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. Exceptions include:

As noted in 4.1.2 Name, Role, Value

11.5.2.8 Label relationships

Partially Supports

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

11.5.2.9 Parent-child relationships

Partially Supports

For most 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

11.5.2.10 Text

Supports

The product exposes text content and text values to assistive technology.

11.5.2.11 List of available actions

Partially Supports

For most of the elements on which one or more actions may be performed, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 4.1.2 Name, Role, Value

11.5.2.12 Execution of available actions

Partially Supports

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

11.5.2.13 Tracking of focus and selection attributes

Partially Supports

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. Exceptions include:

As noted in 2.4.7 Focus Visible

11.5.2.14 Modification of focus and selection attributes

Supports

When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology.

11.5.2.15 Change notification

Partially Supports

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.a Status Messages

11.5.2.16 Modifications of states and properties

Partially Supports

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

11.5.2.17 Modifications of values and text

Partially Supports

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

11.6 Documented accessibility usage

Heading cell – no response required

11.6.1 User control of accessibility features

Not Applicable

The product is not platform software, so this requirement does not apply.

11.6.2 No disruption of accessibility features

Not Applicable

The product does not disrupt platform accessibility features.

11.7 User preferences

Not Applicable

The product is not platform software, so this requirement does not apply.

11.8 Authoring tools

Heading cell – no response required

11.8.1 Content technology

Heading cell – no response required

11.8.2 Accessible content creation

See WCAG 2.2 section

The product enables authors to create HTML content, such as emails. Content can be imported from other tools or created using built-in authoring functions which support the creation of accessible content by providing fields for Alt Text and Heading structures. See details for individual criteria in the WCAG 2.2 section.

11.8.3 Preservation of accessibility information in transformations

Not Applicable

The product does not convert content.

11.8.4 Repair assistance

Not Applicable

Accessibility checking functionality is not provided within the authoring tool, so this requirement does not apply.

11.8.5 Templates

Partially Supports

Templates in the product enable authors to create email content. None of the available templates support the creation of content that conforms to WCAG 2.1 Levels A and AA. Exceptions include:

As noted in 2.4.3 Focus Order

As noted in 2.4.7 Focus Visible

As noted in 4.1.2 Name, Role, Value

Adobe Accessibility Conformance Report International Edition

Product Information

Applicable Standards/Guidelines

Terms

WCAG 2.2 Report

Table 1: Success Criteria, Level A

Guideline 1.1 Text Alternatives:

Guideline 1.2 Time-based Media:

Guideline 1.3 Adaptable:

Guideline 1.4 Distinguishable:

Guideline 2.1 Keyboard Accessible:

Guideline 2.2 Enough Time:

Guideline 2.3 Seizures:

Guideline 2.4 Navigable:

Guideline 2.5 Input Modalities:

Guideline 3.1 Readable:

Guideline 3.2 Predictable:

Guideline 3.3 Input Assistance:

Guideline 4.1 Compatible:

Table 2: Success Criteria, Level AA

Table 3: Success Criteria, Level AAA

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Chapter 4: Hardware

Chapter 5: Software

Chapter 6: Support Documentation and Services

EN 301 549 Report

Chapter 4: Functional Performance Statements (FPS)

Chapter 5: Generic Requirements

Chapter 6: ICT with Two-Way Voice Communication

Chapter 7: ICT with Video Capabilities

Chapter 8: Hardware

Chapter 9: Web (see WCAG 2.2 section)

Chapter 10: Non-web Documents

Chapter 11: Software

Chapter 12: Documentation and Support Services

Chapter 13: ICT Providing Relay or Emergency Service Access