1.1.1 Non-text Content (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.1.1 (Web)
• 10.1.1.1 (Non-web document)
• 11.1.1.1.1 (Open Functionality Software)
• 11.1.1.1.2 (Closed Functionality Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

Web: The product provides sufficient text alternatives for most instances of non-text content.

Exceptions include:

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 pages: Blank and populated fallout visualization; Data view - Configure.

The long description for a complex image does not adequately convey the information presented by the image, so people who are blind and/or use a screen reader will not be able to understand the information available in the image. This occurs on the following pages: Contribution analysis of anomaly detection; Anomaly detection.

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 pages: Blank and populated Combo chart; Blank and populated flow visualization; Blank and populated Key Metric Summary viz; Constructed segment comparison; Content Analytics - Reporting UI; Guided Analysis - Trends; Open the options under Guided Analysis; Populated attribution panel; Trend metrics from visualize button.

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 pages: Connections - View connection; New panel set up Step 1; Open the options under Guided Analysis; Content Analytics - Reporting UI.

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: Does Not Support

Electronic Docs: Does Not Support

Web: Some structure and relationship information are provided through element semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text. Examples include:

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: Content Analytics - Onboarding UI.

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: Content Analytics - Reporting UI; Connections - View connection; Open the options under Guided Analysis; Content Analytics - Onboarding UI; Data view - Settings; Guided Analysis - Trends; Blank and populated Venn diagram; Blank and populated cohort table; Guided Analysis - Active growth; Blank attribution panel; Guided Analysis - Conversion trends; Guided Analysis - Net Growth; Guided Analysis - Funnel.

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: Connections - Create new connection; Blank and populated Key Metric Summary viz.

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: Open the options under Guided Analysis; Content Analytics - Onboarding UI; Data view - Configure; Data view - Components; Content Analytics - Configuration’s list.

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 pages: Open the options under Guided Analysis; Data view - Configure.

Content that is visually presented as a single table is marked up as more than one table element, so the table's structure and data relationships will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Content Analytics - Reporting UI; Populated attribution panel; Contribution analysis of anomaly detection; Constructed segment comparison.

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: Data view - Landing Page.

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 pages: Content Analytics - Reporting UI; Blank and populated Key Metric Summary viz; Blank and populated flow visualization; Blank and populated cohort table; Blank and populated Combo chart.

Some sets of radio buttons are not programmatically grouped, so the group label for each set of radio buttons will not be conveyed to people who are blind and/or use a screen reader and they will not understand the purpose of the individual radio buttons. This occurs on the following pages: Content Analytics - Reporting UI; Content Analytics - Onboarding UI; Blank and populated Key Metric Summary viz.

An element's programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content. This occurs on the following pages: Connections - Create new connection; Connections - View connection; Connections - Create new connection - Add datasets; Data view - Components; Connections - Landing page; Data view - Landing Page.

Electronic Docs: Some structure and relationship information are provided through element semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text. Exceptions include:

PDF document is not a tagged PDF, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the structure and relationship of the PDF content. This occurs on the following page: PDF.

1.3.2 Meaningful Sequence (Level A)

Also applies to:

EN 301 549 Criteria

• 9.1.3.2 (Web)
• 10.1.3.2 (Non-web document)
• 11.1.3.2.1 (Open Functionality Software)
• 11.1.3.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

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

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: Curate project data.

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 page: new panel set up Step 1.

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

Screen reader focus is lost or misplaced due to user interaction or content update, making navigation difficult or impossible for people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Blank and populated Venn diagram.

The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: Content Analytics - Reporting UI; Constructed segment comparison.

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

Electronic Docs: Partially 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 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: Content Analytics - Reporting UI; Connections - View connection; Populated attribution panel.

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 page: new panel set up Step 1.

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 pages: Connections - View connection; Content Analytics - Reporting UI; Data view - Components; Left rail menu; Populated attribution panel; Add conditions to a cohort table.

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

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 page: PDF.

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 cannot be operated through a keyboard interface. Examples include:

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: new panel set up Step 1; Anomaly detection; Blank and populated Venn diagram.

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 most of the pages in the website (Eg: combo box options info and expand icons, panel drag and drop)

An in-page link cannot be activated using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this link. This occurs on the following page: Footer.

2.1.2 No Keyboard Trap (Level A)

Also applies to:

EN 301 549 Criteria

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

Revised Section 508

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

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.2.1.4 (Web)
• 10.2.1.4 (Non-web document)
• 11.2.1.4.1 (Open Functionality Software)
• 11.2.1.4.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

2.2.1 Timing Adjustable (Level A)

Also applies to:

EN 301 549 Criteria

• 9.2.2.1 (Web)
• 10.2.2.1 (Non-web document)
• 11.2.2.1 (Open Functionality Software)
• 11.2.2.1 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

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

Some content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs on the following pages: Data view - Settings; Data view - Landing Page.

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: On most pages where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. Exceptions include:

The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following page: new panel set up Step 2.

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

Page TITLE element does not identify purpose of page. This occurs on the following pages: Connections - Create new connection; Content Analytics - Onboarding UI; Create/Edit Configuration.

2.4.3 Focus Order (Level A)

Also applies to:

EN 301 549 Criteria

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

Revised Section 508

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

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

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: Content Analytics - Reporting UI; Connections - View connection; Populated attribution panel; New panel set up Step 1; Content Analytics - Onboarding UI; Contribution analysis of anomaly detection; Blank segment comparison; Blank and populated cohort table; Select Data View; Constructed segment comparison; Connections - Landing page.

Keyboard focus does not follow the visual focus order, or it does not move to the intended target, 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: Export pdf.

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: Connections - Create new connection - Add datasets; Data view - Settings; Blank and populated Venn diagram; Blank and populated cohort table; Connections - Landing page; New panel set up Step 2.

The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the following pages: Content Analytics - Reporting UI; New panel set up Step 1; Constructed segment comparison.

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: Connections - Create new connection - Add datasets.

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

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: Open the options under Guided Analysis.

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: Content Analytics - Reporting UI; Connections - View connection; Blank and populated fallout visualization; Content Analytics - Onboarding UI; Blank and populated Key Metric Summary viz; Blank and populated Venn diagram; Blank and populated flow visualization; Blank segment comparison; Blank and populated cohort table; Blank and populated Combo chart; Connections - Landing page; Blank attribution panel.

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: Open the options under Guided Analysis; Populated attribution panel; Contribution analysis of anomaly detection; Blank and populated cohort table; Constructed segment comparison; Blank attribution panel.

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)

Web: Supports

Electronic Docs: Partially Supports

Web: The language is programmatically determinable within the product.

Electronic Docs: The language is programmatically determinable within the document. Exceptions include:

No language is programmatically assigned to the PDF document, so screen readers may mispronounce content. This occurs on the following page: PDF.

3.2.1 On Focus (Level A)

Also applies to:

EN 301 549 Criteria

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

Revised Section 508

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

3.2.2 On Input (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.2.2 (Web)
• 10.3.2.2 (Non-web document)
• 11.3.2.2 (Open Functionality Software)
• 11.3.2.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

3.2.6 Consistent Help (Level A 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

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:

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: Connections - Create new connection; Data view - Settings; Data view - Configure.

3.3.2 Labels or Instructions (Level A)

Also applies to:

EN 301 549 Criteria

• 9.3.3.2 (Web)
• 10.3.3.2 (Non-web document)
• 11.3.3.2 (Open Functionality Software)
• 11.3.3.2 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

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

The label of an element is not persistent (always visible on the page) so the element's purpose may be difficult to discover. This occurs on the following page: Blank and populated fallout visualization.

The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: new panel set up Step 1; Select Data View; Connections - Landing page; Data view - Landing Page; Content Analytics - Configuration’s list.

Some visible Instructions for a form input field are not available for people who use assistive technology. This occurs on the following page: Data view - Components.

Select or dropdown control missing a visible label so the select or dropdown control purpose is not clear. This occurs on the following pages: Content Analytics - Reporting UI; Connections - View connection; Populated attribution panel; Blank and populated fallout visualization; New panel set up Step 1; Data view - Settings; Add conditions to a cohort table; Blank and populated Venn diagram.

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

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 most of the pages in the website (Eg: combo box options info and expand icons)

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 most of the web pages in the website (Eg: Add visualizations to Panel container)

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: Content Analytics - Reporting UI; Populated attribution panel.

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 pages: Content Analytics - Reporting UI; Populated attribution panel; Contribution analysis of anomaly detection; Anomaly detection; Blank and populated Combo chart; Constructed segment comparison.

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: Left rail menu.

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: Connections - Create new connection; Header navigation.

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: new panel set up Step 1; Data view - Settings; Blank and populated Key Metric Summary viz; Blank and populated Venn diagram; Data view - Components; Blank and populated Combo chart.

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 most of the pages in the website (Eg: combo box options)

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: Content Analytics - Reporting UI; Populated attribution panel; Trend metrics from visualize button; New panel set up Step 1; Contribution analysis of anomaly detection; Anomaly detection; Guided Analysis - Trends; Blank and populated Venn diagram; Blank and populated flow visualization; Blank and populated Combo chart; Constructed segment comparison; Blank attribution panel.

A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following pages: new panel set up Step 1.

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: Content Analytics - Reporting UI; Open the options under Guided Analysis; Populated attribution panel; Contribution analysis of anomaly detection; Blank and populated cohort table; Constructed segment comparison; Blank attribution panel.

A custom user interface component is not compatible with assistive technologies, so people who use assistive technology will not be able to interact with it. This occurs on the following page: Left rail menu.

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: Left rail menu.

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 pages: Content Analytics - Reporting UI; New panel set up Step 1.

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: Connections - View connection; Select Data View; Connections - Landing page; Data view - Landing Page; Content Analytics - Configuration’s list; Open the options under Guided Analysis

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: Connections - View connection; Connections - Create new connection - Add datasets; Data view - Components; Blank and populated cohort table; Constructed segment comparison.

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: Data view - Components.

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

Electronic Docs: Partially Supports

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: Blank and populated fallout visualization; Blank and populated flow visualization; Blank attribution panel.

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: Content Analytics - Reporting UI; Open the options under Guided Analysis; Populated attribution panel; Blank and populated fallout visualization; Trend metrics from visualize button; New panel set up Step 1; Contribution analysis of anomaly detection; Anomaly detection; Blank and populated Key Metric Summary viz; Blank and populated Venn diagram; Blank and populated flow visualization; Blank and populated cohort table; Blank and populated Combo chart; Constructed segment comparison; Guided Analysis - Active growth; Blank attribution panel; Header navigation.

The color contrast ratio between large text and its background is less than 3:1, so people who are colorblind or have low vision may have difficulty reading the text. Large text is text over 18 points (24 pixels) or 14 points (19 pixels) if bold. This occurs on the following pages: Populated attribution panel; Contribution analysis of anomaly detection; Constructed segment comparison.

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: Content Analytics - Reporting UI; Blank and populated fallout visualization; New panel set up Step 1; Blank and populated Key Metric Summary viz; Blank and populated Venn diagram; Blank and populated flow visualization; Blank and populated cohort table; Blank attribution panel; Export pdf.

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

Electronic Docs: Most text meets minimum contrast requirements. Exceptions include:

The color contrast ratio between large text and its background is less than 3:1, so people who are colorblind or have low vision may have difficulty reading the text. Large text is text over 18 points (24 pixels) or 14 points (19 pixels) if bold. This occurs on the following page: PDF.

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: Connections - Create new connection; Connections - View connection; Connections - Create new connection - Add datasets; Populated attribution panel; Blank and populated fallout visualization; Select Data View; Connections - Landing page; Left rail menu.

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: Data view - Settings; Data view - Components; Data view - Landing Page.

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]. 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: Connections - View connection; Open the options under Guided Analysis; New panel set up Step 1; Select Data View.

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: Connections - Create new connection; Content Analytics - Reporting UI; Connections - View connection; Connections - Create new connection - Add datasets; Populated attribution panel; Blank and populated fallout visualization; Trend metrics from visualize button; New panel set up Step 1; Content Analytics - Onboarding UI; Contribution analysis of anomaly detection; Data view - Settings; Anomaly detection; Blank and populated Key Metric Summary viz; Guided Analysis - Trends; Data view - Configure; Blank and populated Venn diagram; Blank and populated flow visualization; Blank segment comparison; Data view - Components; Blank and populated cohort table; Blank and populated Combo chart; Curate project data; Constructed segment comparison; Guided Analysis - Active growth; Connections - Landing page; Blank attribution panel; Data view - Landing Page; Guided Analysis - Conversion trends; Guided Analysis - Net Growth; Left rail menu; Contribution analysis creation panel (after selecting Analyze); Guided Analysis - Funnel; Add or remove components; Content Analytics - Configurations list; Blank and populated Key Metric Summary viz; Add conditions to a cohort table.

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: Connections - View connection; Blank and populated fallout visualization; Blank and populated flow visualization; New panel set up Step 2; Header navigation; Content Analytics - Configuration’s list.

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.11 (Web)
• 10.1.4.11 (Non-web document)
• 11.1.4.11 (Open Functionality Software)
• 11.1.4.11 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Most, if not all, boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content do not have a 3:1 color contrast ratio with adjacent color(s) or their background. Examples include:

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 most of the pages in the website (Eg: panel drag and drop border)

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 on the following pages: Connections - Create new connection; Content Analytics - Reporting UI; Populated attribution panel; Trend metrics from visualize button; Content Analytics - Onboarding UI; Contribution analysis of anomaly detection; Anomaly detection; Blank and populated Key Metric Summary viz; Data view - Configure; Blank and populated Venn diagram; Blank and populated cohort table; Constructed segment comparison; Guided Analysis - Active growth; Guided Analysis - Net Growth.

The indicator for the state of an interactive element (like a checkbox or radio button) 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 state of the interactive element. This occurs on the following pages: Open the options under Guided Analysis; Populated attribution panel; Blank and populated Key Metric Summary viz; Blank and populated Venn diagram; Blank and populated cohort table; Constructed segment comparison; Left rail menu.

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 pages: Content Analytics - Reporting UI; Populated attribution panel; Trend metrics from visualize button; New panel set up Step 1; Contribution analysis of anomaly detection; Anomaly detection; Blank and populated Key Metric Summary viz; Guided Analysis - Trends; Blank and populated Venn diagram; Blank and populated flow visualization; Constructed segment comparison; Guided Analysis - Conversion trends; Guided Analysis - Net Growth.

The focus indicator of an interactive element (like a 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 when the interactive element is receiving focus. This occurs on most of the web pages in the website (Eg: Add Visualizations to Panel button)

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

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.1.4.13 (Web)
• 10.1.4.13 (Non-web document)
• 11.1.4.13 (Open Functionality Software)
• 11.1.4.13 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include:

Content that appears on mouse hover 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: Content Analytics - Reporting UI; Populated attribution panel; Trend metrics from visualize button; Contribution analysis of anomaly detection; Anomaly detection; Guided Analysis - Trends; Blank and populated flow visualization; Blank and populated Combo chart; Constructed segment comparison; Guided Analysis - Active growth; Guided Analysis - Conversion trends; Guided Analysis - Net Growth.

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: Content Analytics - Reporting UI; Populated attribution panel; Blank and populated fallout visualization; Trend metrics from visualize button; New panel set up Step 1; Contribution analysis of anomaly detection; Anomaly detection; Blank and populated Key Metric Summary viz; Guided Analysis - Trends; Blank and populated Venn diagram; Blank and populated flow visualization; Blank and populated cohort table; Blank and populated Combo chart; Constructed segment comparison; Guided Analysis - Active growth; New panel set up Step 2; Guided Analysis - Conversion trends; Guided Analysis - Net Growth; Table visualize button; Contribution analysis creation panel (after selecting Analyze); Guided Analysis - Funnel; Populated segment comparison

2.4.5 Multiple Ways (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.2.4.5 (Web)
• 10.2.4.5 (Non-web document) – Does not apply
• 11.2.4.5 (Open Functionality Software) – Does not apply
• 11.2.4.5 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

2.4.6 Headings and Labels (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.2.4.6 (Web)
• 10.2.4.6 (Non-web document)
• 11.2.4.6 (Open Functionality Software)
• 11.2.4.6 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

Web: Most headings and labels for form and interactive controls are informative. Exceptions include:

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: Content Analytics - Reporting UI; Open the options under Guided Analysis; Blank and populated fallout visualization; New panel set up Step 1; Content Analytics - Onboarding UI; Blank and populated Key Metric Summary viz; Blank and populated Venn diagram; Blank and populated flow visualization; Blank segment comparison; Blank and populated cohort table; Blank and populated Combo chart; Blank attribution panel; Data view - Landing Page.

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: Content Analytics - Reporting UI; Connections - Create new connection - Add datasets; Open the options under Guided Analysis; Populated attribution panel; Blank and populated fallout visualization; New panel set up Step 1; Data view - Settings; Blank and populated Key Metric Summary viz; Blank and populated Venn diagram; Blank and populated flow visualization; Blank segment comparison; Data view - Components; Blank and populated cohort table; Blank and populated Combo chart; Constructed segment comparison; Blank attribution panel; Table visualize button; Populated segment comparison; Create/Edit Configuration.

2.4.7 Focus Visible (Level AA)

Also applies to:

EN 301 549 Criteria

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

Revised Section 508

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

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

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: Populated attribution panel; Blank and populated fallout visualization; Data view - Components.

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include:

A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following pages: Content Analytics - Reporting UI; Populated attribution panel; Constructed segment comparison.

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, if not all, functionality that uses a dragging movement cannot be achieved by a single pointer without dragging, excepting functions for which dragging is essential or the functionality is determined by the user agent and not modified by the author. Examples include:

Some functionality relies on a dragging movement with no single-pointer, single touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture on most of the web pages in the audit.

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, if not all, clickable controls is not at least 24 by 24 CSS pixels, and the target size is not determined by the user agent; there is not a different control with equivalent functionality; the target is not in line with text; the presentation of the target is not essential to the function or otherwise exempted under the rule; and each control is not spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Examples include:

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 most of the web pages combo box options (help and dropdown icons)

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

A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following page: Content Analytics - Configuration’s list.

3.2.3 Consistent Navigation (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.2.3 (Web)
• 10.3.2.3 (Non-web document) – Does not apply
• 11.3.2.3 (Open Functionality Software) – Does not apply
• 11.3.2.3 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

3.2.4 Consistent Identification (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.2.4 (Web)
• 10.3.2.4 (Non-web document) – Does not apply
• 11.3.2.4 (Open Functionality Software) – Does not apply
• 11.3.2.4 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

• 501 (Web)(Software) – Does not apply to non-web software
• 504.2 (Authoring Tool)
• 602.3 (Support Docs) – Does not apply to non-web docs

3.3.3 Error Suggestion (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.3.3 (Web)
• 10.3.3.3 (Non-web document)
• 11.3.3.3 (Open Functionality Software)
• 11.3.3.3 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

Also applies to:

EN 301 549 Criteria

• 9.3.3.4 (Web)
• 10.3.3.4 (Non-web document)
• 11.3.3.4 (Open Functionality Software)
• 11.3.3.4 (Closed Software)
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508

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

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

EN 301 549 Criteria – Does not apply

Revised Section 508 – Does not apply

4.1.3 Status Messages (Level AA 2.1 and 2.2)

Also applies to:

EN 301 549 Criteria

• 9.4.1.3 (Web)
• 10.4.1.3 (Non-web document)
• 11.4.1.3 (Open Functionality Software)
• 11.4.1.3 (Closed Software) – Does not apply
• 11.8.2 (Authoring Tool)
• 12.1.2 (Product Docs)
• 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include:

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 on the following pages: Content Analytics - Reporting UI; Connections - View connection; Open the options under Guided Analysis; Populated attribution panel; Blank and populated fallout visualization; New panel set up Step 1; Data view - Settings; Blank and populated Key Metric Summary viz; Data view - Configure; Blank and populated Venn diagram; Blank and populated flow visualization; Data view - Components; Blank and populated cohort table; Select Data View; Blank and populated Combo chart; Connections - Landing page; Blank attribution panel; Data view - Landing Page; Table visualize button; Content Analytics - Configurations list; Connections - Create new connection - Add datasets.

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.1.1 Language of Page

As noted in 3.1.2 Language of Parts

As noted in 3.3.1 Error Identification

As noted in 4.1.2 Name, Role, Value

Web: Most functions of the product are usable With Limited Vision. Exceptions include:

As noted in 1.1.1 Non-Text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (minimum)

As noted in 1.4.4 Resize Text

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.1.1 Language of Page

As noted in 3.1.2 Language of Parts

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Web: Most functions of the product are usable without perception of color. Exceptions include:

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (minimum)

As noted in 3.3.1 Error Identification

Web: Most functionality is usable without hearing. Exceptions include:

As noted in 3.1.1 Language of Page

As noted in 3.1.2 Language of Parts

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

As noted in 3.1.1 Language of Page

As noted in 3.1.2 Language of Parts

Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:

As noted in 2.1.1 Keyboard

As noted in 2.2.1 Timing Adjustable

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 4.1.2 Name, Role, Value

Web: Most 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.2.2 Pause, Stop, Hide

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 3.1.1 Language of Page

As noted in 3.1.2 Language of Parts

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

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

As noted in 4.1.2 Name, Role, Value

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

As noted in 4.1.2 Name, Role, Value

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

As noted in 1.3.1 Info and Relationships

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

As noted in 4.1.2 Name, Role, Value

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

As noted in 4.1.2 Name, Role, Value

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

As noted in 1.3.1 Info and Relationships

As noted in 4.1.2 Name, Role, Value

When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 1.3.1 Info and Relationships

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

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

As noted in 2.1.1 Keyboard Navigation

The position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:

As noted in 2.4.7 Focus Visible

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

As noted in 4.1.3 Status Messages

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.1.1 Language of Page

As noted in 3.1.2 Language of Parts

As noted in 3.3.1 Error Identification

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages

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

As noted in 1.1.1 Non-Text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.3 Contrast (minimum)

As noted in 1.4.4 Resize Text

As noted in 1.4.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.1.1 Language of Page

As noted in 3.1.2 Language of Parts

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

Web: Most functions of the product are usable without perception of color. Exceptions include:

• As noted in 1.4.1 Use of Color
• As noted in 1.4.3 Contrast (minimum)
• As noted in 1.4.11 Non-Text Contrast
• As noted in 3.3.1 Error Identification

Web: Most functionality is usable without hearing. Exceptions include:

As noted in 3.1.1 Language of Page

As noted in 3.1.2 Language of Parts

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

As noted in 3.1.1 Language of Page

As noted in 3.1.2 Language of Parts

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

As noted in 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 2.5.3 Label in Name

As noted in 4.1.2 Name, Role, Value

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

As noted in 1.4.13 Content on Hover or Focus

As noted in 2.5.3 Label in Name

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

As noted in 1.1.1 Non-Text Content

As noted in 1.3.1 Info and Relationships

As noted in 1.3.2 Meaningful Sequence

As noted in 1.4.1 Use of Color

As noted in 1.4.10 Reflow

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.2.2 Pause, Stop, Hide

As noted in 2.4.2 Page Titled

As noted in 2.4.3 Focus Order

As noted in 2.4.4 Link Purpose (in context)

As noted in 2.4.6 Headings and Labels

As noted in 2.4.7 Focus Visible

As noted in 2.5.3 Label in Name

As noted in 3.1.1 Language of Page

As noted in 3.1.2 Language of Parts

As noted in 3.3.1 Error Identification

As noted in 3.3.2 Labels or Instructions

As noted in 4.1.2 Name, Role, Value

As noted in 4.1.3 Status Messages