Adobe Experience Platform 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 application.

Exception includes:

Some images that act as a link or control do not have a text alternative, so people who are blind and/or use a screen reader will not understand the function performed by each image. This occurs on the following pages: Create dataset from schema - Step 1; Customer - Profiles - Overview.

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 pages: Customer - Profiles - Overview; License Usage - Details - Data visualization.

A complex image does not have a text alternative, 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: Dataset activity.

A decorative image is not hidden from screen readers, so people who are blind and/or use a screen reader will have to navigate through unnecessary and duplicative text. This occurs on the following pages: Home; Create Audience: Build Rule.

An informative image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information conveyed the image. This occurs on the following pages: Schemas - Deque Test Schema - Structure Tab; Administration - Permissions; Create a computed attribute; Schemas - Name and Review; Add field groups; Create query.

An image does not have a text alternative that contains essential text from the visual image, so people who are blind and/or use a screen reader will not understand the information available in the image. This occurs on the following page: Schemas - Overview.

An image does 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 page: Customer - Profiles - Overview.

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 structure and relationship information are not provided programmatically or in text.

Exceptions include:

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 pages: Create a computed attribute; Create Audience: Build Rule; Ai Assistant.

A heading level is 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: Use Case Playbook Overview; Ai Assistant; Schemas - Video Modal; AI Assistant: Discover Prompts Modal.

A layout table is incorrectly marked up as a data table, so people who are blind and/or use a screen reader will perceive the table as presenting relational data rather than simply positioning text on a page. This occurs on the following pages: Administration - Permissions; Dataset activity; Home; Administration - Sandboxes.

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 pages: Dataset activity; Use Case Playbook - Playbook Detail; Add field groups; Edit Widget.

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: Schemas - Deque Test Schema - Structure Tab; Schemas - Name and Review; Dataset activity; Home; Create Audience: Build Rule; Data Management - Places; Create dataset from schema - Step 1; Administration - Sandboxes; Profile: Computed attributes; Schemas - Create Schema.

Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Create a computed attribute; Home; Create Audience: Build Rule.

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: Data governance.

Content that does not visually function as a list is marked up as a list, so the structure of the page is misrepresented to and people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Experience Events.

A block of content has incorrect semantic markup, so its meaning, structure, or relationships is not conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Administration - Permissions; AI Assistant: Discover Prompts Modal.

A nested list is not marked up properly, so the structure of the list is not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Create a computed attribute; Create Audience: Build Rule.

A description list is not marked up properly, so the structure of the list is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Dataset activity.

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: Add field groups.

Multiple elements' programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content. This occurs on the following pages: Widget Library; Use Case Playbooks - Instance; Use Case Playbook - Playbook Detail.

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 pages: Home; Schemas - Create Schema.

An HTML list element contains content that is visually presented as a part of the list, but the content's HTML coding does not include it programmatically in that list, so the structure of the list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Experience Events.

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: Edit Widget.

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.

Exception includes:

Screen readers can read content outside the modal dialog, so people who are blind and/or use a screen reader may become disoriented or confused. This occurs on the following page: Home.

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: Dataset activity.

The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: Use Case Playbook - Playbook Detail.

The correct reading order of dynamically changing content is not programmatically determinable by screen readers, so people who are blind and/or use a screen reader may not be made aware of new or changed content that is dynamically added to a page. This occurs on the following pages: Compose Audience; Data governance.

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.

Exception includes:

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 on the following pages: Customer - Profiles - Overview; Dataset activity; Data Management - Places.

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 on the following pages: Data governance; Data Management - Places; Add field groups; Experience Events.

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(s): Schemas – Deque Test Schema - Structure Tab; Administration - Permissions; Use Case Playbook Overview; Widget Library; Data governance; Data Management - Places; Create dataset from schema - Step 1; Add field groups.

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:

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 pages: Use Case Playbook Overview; Schemas - Create Schema.

A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following pages: Create a computed attribute; Widget Library; Customer - Profiles - Overview; Dataset activity; Data governance; Create Audience: Build Rule; Data Management - Places; Create dataset from schema - Step 1; License Usage - Details - Data visualization; Add field groups; View Profile Detail; Experience Events; Schemas - Video Modal; Edit Widget; Create query.

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: Create query.

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)

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: Administration - Permissions; Create a computed attribute; License Usage - Details - Data visualization; Edit Widget; Create query.

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.

Exception includes:

Keyboard focus or touch screen swiping goes to an element that is 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 a computed attribute; Data Management - Places.

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 pages: Home; View Profile Detail; Publish a computed attribute modal; Edit governance labels modal.

Keyboard focus is not moved to a modal when the modal opens, so people who use the keyboard to navigate content (including screen reader users) may not be able to use the modal and in some cases may not know it is present on the page. This occurs on the following page: Administration - Sandboxes - Unable to import package modal.

The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the following page: Data governance.

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 pages: View Profile Detail; Administration - Sandboxes - Unable to import package modal.

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.

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 pages: Home; Use Case Playbooks - Instance.

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:

The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Administration - Permissions; Use Case Playbook Overview; Widget Library; Customer - Profiles - Overview; Home; Use Case Playbooks - Instance; Add field groups; Schemas - Overview; Schemas - Create Schema.

An interactive element (such as a link, button, or form input) does not have an accessible name because its visible label is not programmatically associated with the element, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Compose Audience; Create Audience: Build Rule; Data Management - Places; Create Audience button and modal; Create query.

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)

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.

Exceptions include:

• When a user changes the setting of a user interface control (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: Schemas - Deque Test Schema - Structure Tab; Dataset activity; Add field groups.

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: Schemas - Name and Review.

An error for a form input (such as a text input field, radio button, select dropdown, or checkbox) is not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following pages: Administration - Permissions; Create a computed attribute.

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.

Exception includes:

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

Select or dropdown control missing a visible label, so the select or dropdown control purpose is not clear This occurs on the following pages: Create a computed attribute; License Usage - Details - Data visualization.

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.1 Parsing (Level A)

Applies to:

WCAG 2.0 and 2.1 – Always answer ‘Supports’

WCAG 2.2 (obsolete and removed) - Does not apply

EN 301 549 Criteria

• 9.4.1.1 (Web)
• 10.4.1.1 (Non-web document)
• 11.4.1.1.1 (Open Functionality Software)
• 11.4.1.1.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

4.1.2 Name, Role, Value (Level A)

Also applies to:

EN 301 549 Criteria

• 9.4.1.2 (Web)
• 10.4.1.2 (Non-web document)
• 11.4.1.2.1 (Open Functionality Software)
• 11.4.1.2.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

Web: User interface components in most product functions do not provide programmatic [name, role, state, or value] information.

Exceptions include:

An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following pages: Administration - Permissions; Data Management – Places; Data governance.

Appropriate index count is not exposed. This occurs on the following pages: Customer - Profiles - Overview.

An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Create query.

A form input element does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of the element and may not understand its purpose or how to interact with it. This occurs on the following page: Create query.

An element that appears and functions like a combobox does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Add field groups.

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: Home; Use Case Playbook - Playbook Detail; Ai Assistant; Add field groups; Schemas - Video Modal; Create Audience button and modal; Schemas - Create Schema.

An element does not have an attribute in its 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 a computed attribute; Dataset activity; Create Audience: Build Rule; Data Management - Places; Use Case Playbook - Playbook Detail; License Usage - Details - Data visualization.

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 pages: Edit Widget; Schemas - Create Schema.

An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Compose Audience.

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 pages: Customer - Profiles - Overview; Create Audience: Build Rule; License Usage - Details - Data visualization; Add field groups; Schemas - Video Modal.

An element that appears and functions like a tree view widget that presents a hierarchical list does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand name, purpose, structure, or content of the list or how to interact with it. This occurs on the following pages: Schemas - Name and Review; Create Audience: Build Rule; Schemas - Deque Test Schema - Structure Tab; Create a computed attribute.

The HTML code for a link or button is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of the element. This occurs on the following page(s): Create dataset from schema - Step 1; Administration - Sandboxes; Profile: Computed attributes; Create query.

A button does not have a programmatic name, so its 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: Data governance; Data Management - Places; Dataset activity; Data Management – Places.

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 pages: Administration - Permissions; Use Case Playbook Overview; Dataset activity; Data governance; Data Management - Places; Use Case Playbook - Playbook Detail; Create dataset from schema - Step 1; Add field groups; Experience Events; Profile: Computed attributes.

A button does not have a programmatic role and name, so its 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: Use Case Playbook Overview; Customer - Profiles - Overview; Data Management - Places; License Usage - Details - Data visualization; Add field groups; Create query.

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: Schemas – Deque Test Schema - Structure Tab.

A form field does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the form field or what input it requires. This occurs on the following pages: Compose Audience; Create Audience: Build Rule; Data Management - Places; Create Audience button and modal; Create query.

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: Create Audience button and modal; Schemas - Video Modal.

The programmatic state of an element that reveals or hides 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 the element or the state will be misrepresented. This occurs on the following pages: Administration - Permissions; Home; Ai Assistant; Add field groups; AI Assistant: Discover Prompts Modal.

For an element that allows 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 the element, the options available, and whether the element or an option is currently checked. This occurs on the following page: Data Management - Places.

An element that is focusable or contains one or more focusable elements is programmatically hidden, so people who use the keyboard to navigate as well as people who are blind and/or use a screen reader or other assistive technology will not be able to perceive or interact with the element. This occurs on the following pages: Compose Audience; License Usage - Details - Data visualization.

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 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 pages: Administration - Permissions; Create query.

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: Schemas – Deque Test Schema - Structure Tab; Data governance; Create Audience: Build Rule.

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 on the following pages: Data governance; Home.

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 a computed attribute; Data governance; Home; Use Case Playbooks - Instance; Use Case Playbook - Playbook Detail; Add field groups; Experience Events; Profile: Computed attributes; Schemas - Create Schema; Edit governance labels modal.

Functionality is lost when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to this functionality. This occurs on the following page: Create a computed attribute.

1.4.5 Images of Text (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.1.4.5 (Web)
• 10.1.4.5 (Non-web document)
• 11.1.4.5.1 (Open Functionality Software)
• 11.1.4.5.2 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

1.4.10 Reflow (Level AA 2.1 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].

Exceptions 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 page: Use Case Playbook - Playbook Detail.

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: Schemas – Deque Test Schema - Structure Tab; Compose Audience; Use Case Playbook Overview; Create a computed attribute; Data governance; Home; Create Audience: Build Rule; Data Management - Places; Use Case Playbooks - Instance; Create dataset from schema - Step 1; Ai Assistant; Schemas - Overview; Profile: Computed attributes; Publish a computed attribute modal; Create query; Schemas - Create Schema; Edit governance labels modal.

When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following pages: Customer - Profiles - Overview; Create Audience: Build Rule; Experience Events; Profile: Computed attributes; Edit Widget.

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 of the boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content does not have a 3:1 color contrast ratio with adjacent color(s) or their background.

Exceptions include:

The visual boundary of an interactive element (like a radio button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the boundaries of the interactive element. This occurs on the following pages: Schemas - Deque Test Schema - Structure Tab; Compose Audience; Administration - Permissions; Create a computed attribute; Customer - Profiles - Overview; Dataset activity; Data governance; Home; Data Management - Places; Ai Assistant; Add field groups; View Profile Detail; Schemas - Video Modal; Create query; Create dataset from schema - Step 2.

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 understand the information presented by the icon. This occurs across all web pages.

An image or graphic (like a chart) or part of the image/graphic 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 understand the information presented by the image/graphic. This occurs on the following page: Home.

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.12 (Web)
• 10.1.4.12 (Non-web document)
• 11.1.4.12 (Open Functionality Software)
• 11.1.4.12 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Most functions of the product support the required text style properties without loss of content or functionality

Exceptions include:

When text spacing is adjusted to help people with vision, reading and cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: View Profile Detail; Schemas - Create Schema.

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: When additional content appears on hover, becomes hidden when the mouse pointer moves over it.

Exception includes:

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: Customer - Profiles - Overview; License Usage - Details - Data visualization; Schemas - Video Modal.

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: Customer - Profiles - Overview; License Usage - Details - Data visualization; Schemas - Video Modal."

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 of the headings and labels are descriptive.

Exception includes:

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 pages: Schemas – Deque Test Schema - Structure Tab; Compose Audience; Use Case Playbook Overview; Widget Library; Customer - Profiles - Overview; Dataset activity; Data governance; Data Management - Places; Use Case Playbook - Playbook Detail; Add field groups; View Profile Detail; Schemas - Create Schema.

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: Use Case Playbook Overview; Create a computed attribute; Customer - Profiles - Overview; Dataset activity; Create dataset from schema - Step 1; Add field groups; View Profile Detail; AI Assistant: Discover Prompts Modal.

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.

Exception includes:

An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following pages: Create a computed attribute; Schemas - Name and Review; Home; Data Management - Places; Create dataset from schema - Step 1; Schemas - Video Modal.

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 on the following page: Data Management - Places.

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 pages: Create a computed attribute; Home; View Profile Detail; Schemas - Video Modal; Publish a computed attribute modal; Edit governance labels modal.

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 on the following pages: Create a computed attribute; Customer - Profiles - Overview; View Profile Detail; Edit Widget; Create query.

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 inline 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 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: Compose Audience; Dataset activity; Data governance; Schemas - Overview.

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 pages: Home; Add field groups.

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.

Exception includes:

A status message is 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 message or they may not hear it in a timely fashion. This occurs across all web pages.

Web: Most functions of the product are not usable without vision.

Exception includes:

1.1.1 Non-Text Content

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.4.1 Use of Color

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

3.1.2 Language of Parts

3.2.2 On Input

3.3.1 Error Identification

4.1.2 Name, Role, Value

Web: Most functions of the product are not usable with limited vision.

Exception includes:

1.1.1 Non-Text Content

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.4.1 Use of Color

1.4.3 Contrast (minimum)

1.4.4 Resize Text

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

2.4.7 Focus Visible

3.1.2 Language of Parts

3.2.2 On Input

3.3.1 Error Identification

3.3.2 Labels or Instructions

4.1.2 Name, Role, Value

Web: Most functionality is usable without perception of color.

Exception includes:

1.4.1 Use of Color

1.4.3 Contrast (minimum)

Web: Most, if not all, functionality is not usable with limited manipulation and/or requires fine motor control or simultaneous manual operations. Exception includes:

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

2.4.7 Focus Visible

4.1.2 Name, Role, Value

Web: Most, if not all, functionality is not 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.

Exception includes:

1.1.1 Non-Text Content

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.4.1 Use of Color

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

2.4.7 Focus Visible

3.1.2 Language of Parts

3.2.2 On Input

3.3.1 Error Identification

3.3.2 Labels or Instructions

4.1.2 Name, Role, Value

The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology.

Exception includes:

4.1.2 Name, Role, Value

For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology.

Exception includes:

4.1.2 Name, Role, Value

In most instances when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology.

Exception includes:

1.3.1 Info and Relationships

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

Exception includes:

4.1.2 Name, Role, Value

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

Exception includes:

4.1.2 Name, Role, Value

For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology.

Exception includes:

1.3.1 Info and Relationships

4.1.2 Name, Role, Value

For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology.

Exception includes:

1.3.1 Info and Relationships

4.1.2 Name, Role, Value

All the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology.

Exception includes:

1.3.2 Meaningful Sequence

Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology.

Exception includes:

4.1.2 Name, Role, Value.

For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology.

Exception includes:

2.1.1 Keyboard Navigation

The product exposes focus location, text insertion point, and object selection state for most user interface components.

Exception includes:

2.4.7 Focus Visible.

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

Exception includes:

4.1.3 Status Messages

The product does not provide user controls for audio descriptions.

Exceptions include:

A multimedia (video and audio) file does not have an audio description track. This occurs on the following page: Schemas - Video Modal.

Web: Most functions of the product are not usable without vision.

Exception includes:

1.1. 1 Non-Text Content

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.4.1 Use of Color

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

3.1.2 Language of Parts

3.2.2 On Input

3.3.1 Error Identification

4.1.2 Name, Role, Value

4.1.3 Status Messages

Web: Most functions of the product are not usable with limited vision.

Exception includes:

1.1.1Non-Text Content

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.4.1 Use of Color

1.4.3 Contrast (minimum)

1.4.4 Resize Text

1.4.10 Reflow

1.4.11 Non-Text Contrast

1.4.12 Text Spacing

1.4.13 Content on Hover or Focus

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

2.4.7 Focus Visible

3.1.2 Language of Parts

3.2.2 On Input

3.3.1 Error Identification

3.3.2 Labels or Instructions

4.1.2 Name, Role, Value

Web: Most functionality is usable without perception of color.

Exceptions are noted in:

1.4.1 Use of Color

1.4.3 Contrast (minimum)

1.4.11 Non-Text Contrast

Web: Most, if not all, functionality is not usable by people with limited manipulation and/or requires manipulation, simultaneous action, or hand strength.

Exception includes:

1.4.13 Content on Hover or Focus

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

2.4.7 Focus Visible

2.5.3 Label in Name

4.1.2 Name, Role, Value

Web: All functionality is usable by people with limited reach.

Exception includes:

1.4.13 Content on Hover or Focus

2.5.3 Label in Name

Web: Most, if not all, functionality is not 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.

Exception includes:

1.1.1 Non-Text Content

1.3.1 Info and Relationships

1.3.2 Meaningful Sequence

1.4.1 Use of Color

1.4.10 Reflow

1.4.12 Text Spacing

1.4.13 Content on Hover or Focus

2.1.1 Keyboard

2.4.2 Page Titled

2.4.3 Focus Order

2.4.4 Link Purpose (in context)

2.4.6 Headings and Labels

2.4.7 Focus Visible

2.5.3 Label in Name

3.1.2 Language of Parts

3.2.2 On Input

3.3.1 Error Identification

3.3.2 Labels or Instructions

4.1.2 Name, Role, Value

4.1.3 Status Messages

The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision.

Exception includes:

4.1.2 Name, Role, Value.

When the product displays captions for video that has synchronized audio, the display characteristics (such as color, font, or size) of caption text cannot be modified by the user

Exception includes:

A multimedia player does not provide a way for the user to modify the appearance of captions to their individual needs, so people who are deaf, have limited hearing, and others who rely on captions to understand the content may not have access to the information. This occurs on the following page: Schemas - Video Modal.

When the product displays captions for video that has synchronized audio, most, if not all, captions cannot be announced as spoken output.

Exception includes:

A multimedia player that provides access to subtitles does not provide an option for the subtitles to be read aloud, so people who are blind or low vision may not be able to hear the dialog in a language they can understand. This occurs on the following page: Schemas - Video Modal

The product does not allow the user to play audio description if it is available for video that has synchronized audio.

Exceptions include:

A multimedia player cannot play an audio description track, so people who are blind or have low vision are not able to access the information in the video portion of the multimedia described in the audio track. This occurs on the following page: Schemas - Video Modal.

The product does not provide user audio descriptions. Exception includes:

A multimedia player does not provide a control to activate the audio description track. This occurs on the following page: Schemas - Video Modal.