Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.4)
Product Information
- Name of Product/Version: Adobe Analytics Analysis Workspace
- Product Description: Analysis Workspace is a flexible browser tool that allows you to quickly build analyses and share insights. Using the drag-and-drop interface, you can craft your analysis, add visualizations to bring data to life, curate a dataset, share and schedule projects with anyone in your organization.
- Date: October 2023
- Contact information: access@adobe.com
- Evaluation Methods Used: Product testing involved use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Level AA: Yes
Level AAA: No
Level AA: Yes
Level AAA: No
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.1 Level AAA.
WCAG 2.1 Report
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation.
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.1.1 (Web)
- 10.1.1.1 (Non-web document)
- 11.1.1.1.1 (Open Functionality Software)
- 11.1.1.1.2 (Closed Functionality Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: The product provides sufficient text alternatives for most instances of functional and informative images.
Exceptions include:
Functional image missing text alternative in ‘Segment builder - Blank and Populated’ screen.
Complex Images missing detailed alternative description in ‘Flow - Blank and Populated’, ‘Report Suite Selector’, ‘Trend Metrics from Visualize button’, ‘User Preferences Modal’ screens.
Complex Images detailed alternative description is not adequate in ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’ screens.
Complex Images missing short text alternative in ‘Attribution Panel - Populated’, ‘Contribution analysis of anomaly detection’, ‘Flow - Blank and Populated’ screens.
Complex Images short text alternative is not appropriate in ‘Combo chart - Blank and Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’ screens.
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.1 (Web)
- 10.1.2.1 (Non-web document)
- 11.1.2.1.1 (Open Functionality Software)
- 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.2 (Web)
- 10.1.2.2 (Non-web document)
- 11.1.2.2 (Open Functionality Software)
- 11.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.3 (Web)
- 10.1.2.3 (Non-web document)
- 11.1.2.3.1 (Open Functionality Software)
- 11.1.2.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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)
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.1 (Web)
- 10.1.3.1 (Non-web document)
- 11.1.3.1.1 (Open Functionality Software)
- 11.1.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Most visual structure and relationship information is not provided through element semantics or object information or are available in text.
Exceptions include:
The content visually appears to be a data table but is not marked up as a table in ‘Create new alert’, ‘Successful Alert Save’ screens.
Data table has missing or incomplete header cell markup in ‘Calendar’ screen.
The checkboxes group label is not associated with its checkboxes in ‘Flow - Blank and Populated’, ‘Share Workspace’, ‘User Preferences Modal’ screens.
Group of form controls not associated with group label in ‘Alert Builder, Blank’, ‘Combo chart - Blank and Populated’, ‘Share Workspace’, ‘Alert Builder, Populated’ screens.
The radio buttons group label is not associated with its radio buttons in ‘User Preferences Modal’ screen.
Control is not a heading but marked as a heading in ‘Left Rail Menu’, ‘Trend Metrics from dragging Visualization to main page’ screens.
Heading levels are out of order in ‘Attribution Panel - Blank’, ‘Home Page and Header / Share Navigation’, ‘User Preferences Modal’, ‘Venn Diagram - Blank’ screens.
Text should not be marked as a heading in ‘New Panel Set Up - Step 1’, ‘Segment details and edit options’, ‘Share Workspace’ screens.
Visual heading text is not marked as heading in ‘Annotation Builder - Blank’, ‘Annotation Builder - Populated’, ‘Left Rail Menu’ screens.
Visual list is not marked up as list in ‘Combo chart - Blank and Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Attribution Panel - Populated’ screens.
Form element does not have label in ‘User Preferences Modal’ screen.
Role="presentation" or "none" is used incorrectly in ‘Segment builder - Blank and Populated’ screen.
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:
aria-hidden="true" attribute is used incorrectly in ‘Combo chart - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’ screens.
Hidden content is readable with a screen reader in ‘Cohort Table - Blank and Populated’, ‘Curate Project data’ screens.
Informative (static) content is not readable by a screen reader in ‘Alert Builder, Blank’, ‘Home Page and Header / Share Navigation’, ‘Alert Builder, Populated’ screens.
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.3.4 Orientation (Level AA 2.1 only)
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 only)
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
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.1 (Web)
- 10.1.4.1 (Non-web document)
- 11.1.4.1 (Open Functionality Software)
- 11.1.4.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Most of the functions of the product do not convey information through color alone.
Exceptions include:
Color alone is used to convey information in ‘Annotation Builder - Blank’, ‘Attribution Panel - Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Flow - Blank and Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘Populated Panel’, ‘Segment Comparison - Populated’, ‘Trend Metrics from dragging Visualization to main page’, ‘Trend Metrics from Visualize button’, ‘User Preferences Modal’ screens.
Link contrast is not at least 3:1 with surrounding text in ‘Attribution Panel - Populated’, ‘Choose Panel Type’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Footer’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘Populated Panel’, ‘Trend Metrics from dragging Visualization to main page’, ‘Trend Metrics from Visualize button’ screens.
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)
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 of the text does not meet minimum contrast requirements.
Exceptions include:
Large text content lacks 3:1 contrast ratio in ‘Attribution Panel - Populated’, ‘Contribution analysis of anomaly detection’, ‘Segment Comparison - Populated’ screens.
Link or button text lacks 4.5:1 contrast ratio on hover or focus in ‘Left Rail Menu’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Attribution Panel - Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Combo chart - Blank and Populated’ screens.
Placeholder text lacks 4.5:1 contrast ratio in ‘Alert Builder, Blank’, ‘Create new alert’, ‘Create new annotation’, ‘Segment builder - Blank and Populated’, ‘Share Workspace’, ‘Successful Alert Save’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Attribution Panel - Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Combo chart - Blank and Populated’ screens.
Text content lacks 4.5:1 contrast ratio most of the screens in the application.
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 text can be resized using browser zoom, but content and functionality is lost in some product functions.
Exceptions include:
Some part of the page content is lost when the page is zoomed to 200% in ‘Alert Builder, Blank’, ‘Create new annotation’, ‘Home Page and Header / Share Navigation’, ‘New Panel Set Up - Step 2’, ‘Successful Alert Save’, ‘User Preferences Modal’, ‘Alert Builder, Populated’, ‘Create new alert’ screens.
Functionality and content are lost at 200% zoom in ‘Footer’ screen.
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 only)
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 content is presented without loss of information or functionality, and without requiring scrolling in two dimensions.
Exceptions include:
Content and functionality are lost at 320px width equivalent in ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’ screens.
Content does not reflow to fit horizontally within the viewpoint when the page is adjusted to an equivalent width of 320px in ‘Home Page and Header / Share Navigation’ screen.
Content overlaps other content at 320px width equivalent in ‘Alert Builder, Blank’, ‘Annotation Builder - Blank’, ‘Create new annotation’, ‘Curate Project data’, ‘Footer’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Segment builder - Blank and Populated’, ‘Segment details and edit options’, ‘Share Workspace’, ‘Successful Alert Save’, ‘User Preferences Modal’, ‘View Header’, ‘Alert Builder, Populated’, ‘Create new alert’ screens.
1.4.11 Non-text Contrast (Level AA 2.1 only)
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 meaningful non-text content does not meets sufficient color contrast requirements.
Exceptions include:
Active user interface component lacks 3 to 1 contrast ratio in ‘Key Metric Summary - Blank and Populated’, ‘Combo chart - Blank and Populated’, ‘Trend Metrics from Visualize button’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Attribution Panel - Populated’, ‘Segment Comparison - Blank’, ‘Segment Comparison - Populated’, ‘Alert Builder, Blank’, ‘Annotation Builder - Blank’, ‘Segment builder - Blank and Populated’, ‘Share Workspace’ screens.
An icon lacks 3 to 1 contrast ratio in ‘Attribution Panel - Populated’, ‘Cohort Table - Blank and Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘New Panel Set Up - Step 2’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Venn Diagram - Blank and Populated’ screens.
Graphical object lacks 3 to 1 contrast ratio in ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Fallout - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Report Suite Selector’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘User Preferences Modal’ screens.
State of active component lacks 3 to 1 contrast ratio in ‘Alert Builder, Blank’, ‘Annotation Builder - Blank’, ‘Attribution Panel - Blank’, ‘Calendar’, ‘Choose Panel Type’, ‘Cohort Table - Blank and Populated’, ‘Combo chart - Blank and Populated’, ‘Create new annotation’, ‘Flow - Blank and Populated’, ‘Home Page and Header / Share Navigation’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘Successful Alert Save’, ‘Venn Diagram - Blank and Populated’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Fallout - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Segment builder - Blank and Populated’, ‘Attribution Panel - Populated’, ‘Segment Comparison - Blank’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Alert Builder, Populated’ screens.
1.4.12 Text Spacing (Level AA 2.1 only)
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:
Text spacing content cut off for ‘Search components’ field most of the screens in the application.
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
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 of the product’s functionality, the additional content that is displayed on hover or focus is not dismissible, hoverable or persistent.
Exceptions include:
Additional content not dismissible in ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Flow - Blank and Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’ screens.
Hover content disappearing most of the screens in the application.
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.1 (Web)
- 10.2.1.1 (Non-web document)
- 11.2.1.1.1 (Open Functionality Software)
- 11.2.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Most product functionality cannot be operated through a keyboard interface.
Exceptions include:
Device-dependent event handlers are used in ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Fallout - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Home Page and Header / Share Navigation’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘Populated Panel’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Venn Diagram - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’ screens.
Function cannot be performed by keyboard alone in ‘Alert Builder, Blank’, ‘Anomaly detection’, ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Curate Project data’, ‘Fallout - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Left Rail Menu’, ‘Successful Alert Save’, ‘Trend Metrics from dragging Visualization to main page’, ‘Trend Metrics from Visualize button’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Alert Builder, Populated’ screens.
Link does not have an href value in ‘Footer’ screen.
Scrollable region does not have keyboard access in ‘Attribution Panel - Populated’ screen.
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 only)
Also applies to:
EN 301 549 Criteria
- 9.2.1.4 (Web)
- 10.2.1.4 (Non-web document)
- 11.2.1.4.1 (Open Functionality Software)
- 11.2.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.1 (Web)
- 10.2.2.1 (Non-web document)
- 11.2.2.1 (Open Functionality Software)
- 11.2.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: The product does not include functionality dependent on time limits.
Exceptions include:
Content visually appears and disappears with no ability to adjust timing in ‘Successful Segment Save’ screen.
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.2 (Web)
- 10.2.2.2 (Non-web document)
- 11.2.2.2 (Open Functionality Software)
- 11.2.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.3.1 (Web)
- 10.2.3.1 (Non-web document)
- 11.2.3.1 (Open Functionality Software)
- 11.2.3.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.1 (Web)
- 10.2.4.1 (Non-web document) – Does not apply
- 11.2.4.1 (Open Functionality Software) – Does not apply
- 11.2.4.1 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.2 (Web)
- 10.2.4.2 (Non-web document)
- 11.2.4.2 (Open Functionality Software) - Does not apply
- 11.2.4.2 (Closed Software) - Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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:
Hidden or empty element receives focus in ‘Attribution Panel - Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Populated Panel’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘User Preferences Modal’ screens.
Keyboard focus is lost or misplaced due to user interaction or content update in ‘View Header’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Combo chart - Blank and Populated’, ‘Trend Metrics from Visualize button’ screens.
Keyboard focus order is not logical in ‘Calendar’ screen.
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: Most of the links have a purpose that can be determined from the link text alone or from the programmatic context of the link.
Exceptions include:
Purpose of link is not clear in context in ‘Annotation Builder – Blank’, ‘Share Workspace’ screens.
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 not descriptive.
Exceptions include:
Buttons have same name but different actions, present most of the screens in the application.
Programmatic label does not convey purpose of control in ‘Alert Builder, Blank’, ‘Attribution Panel - Blank’, ‘Attribution Panel - Populated’, ‘Cohort Table - Blank and Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Flow - Blank and Populated’, ‘Home Page and Header / Share Navigation’, ‘Key Metric Summary - Blank and Populated’, ‘Populated Panel’, ‘Segment builder - Blank and Populated’, ‘Segment Comparison - Blank’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Venn Diagram - Blank and Populated’, ‘Alert Builder, Populated’ screens.
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 of the focusable elements have a visible keyboard focus indicator.
Exceptions include:
Focus indicator is missing in ‘Calendar’ screen.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures (Level A 2.1 only)
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 only)
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 only)
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: Most of the accessible names of the controls contain the text of their visible labels.
Exceptions include:
Accessible name does not contain visible label in ‘Attribution Panel - Blank’, ‘Attribution Panel - Populated’, ‘Cohort Table - Blank and Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Flow - Blank and Populated’, ‘Home Page and Header / Share Navigation’, ‘Key Metric Summary - Blank and Populated’, ‘Populated Panel’, ‘Segment builder - Blank and Populated’, ‘Segment Comparison - Blank’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Venn Diagram - Blank and Populated’ screens.
Accessible name missing in ‘Alert Builder, populated’, ‘Annotation Builder - Blank’, ‘Successful Alert Save’, ‘User Preferences Modal’, ‘Alert Builder, Blank’ screens.
2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.2.5.4 (Web)
- 10.2.5.4 (Non-web document)
- 11.2.5.4 (Open Functionality Software)
- 11.2.5.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Guideline 3.1 Readable:
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.1.1 (Web)
- 10.3.1.1 (Non-web document)
- 11.3.1.1.1 (Open Functionality Software)
- 11.3.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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)
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.1 (Web)
- 10.3.2.1 (Non-web document)
- 11.3.2.1 (Open Functionality Software)
- 11.3.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.2 (Web)
- 10.3.2.2 (Non-web document)
- 11.3.2.2 (Open Functionality Software)
- 11.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
3.2.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
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.1 (Web)
- 10.3.3.1 (Non-web document)
- 11.3.3.1.1 (Open Functionality Software)
- 11.3.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 of the input fields.
Exceptions include:
Label is not persistent in ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Attribution Panel - Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Combo chart - Blank and Populated’, ‘Segment builder - Blank and Populated’ screens.
Visible label missing in ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Attribution Panel - Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Combo chart - Blank and Populated’, ‘Segment builder - Blank and Populated’, ‘Alert Builder, Populated’, ‘Calendar’, ‘Home Page and Header / Share Navigation’, ‘Successful Alert Save’ screens.
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)
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria
- 9.4.1.1 (Web)
- 10.4.1.1 (Non-web document)
- 11.4.1.1.1 (Open Functionality Software)
- 11.4.1.1.2 (Closed Software)
- 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 elements have proper start and end tags. Elements are nested according to their specifications. Elements do not contain duplicate attributes or duplicate IDs.
Exceptions include:
Certain ARIA roles do not contain particular children in ‘Left Rail Menu’, ‘Trend Metrics from dragging Visualization to main page’, ‘Alert Builder, Blank’, ‘Alert Builder, populated’, ‘Choose Panel Type’, ‘Successful Alert Save’, ‘Report Suite Selector’ screens.
Certain ARIA roles are not contained by particular parents in ‘Calendar’, ‘Left Rail Menu’, ‘Trend Metrics from dragging Visualization to main page’, ‘Choose Panel Type’, ‘Curate Project data’ screens.
Interactive controls are nested in ‘Alert Builder, Blank’, ‘Alert Builder, Populated’, ‘Home Page and Header / Share Navigation’ screens.
id attribute values are not unique in ‘Choose Panel Type’ screen.
IDs used in ARIA and labels are not unique in ‘Alert Builder, Blank’, ‘Alert Builder, Populated’ screens.
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)
- 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 at most of the places do not provide programmatic name, role, state, or value information.
Exceptions include:
ARIA input fields do not have an accessible name in ‘Alert Builder, Blank’, ‘Alert Builder, Populated’, ‘Annotation Builder - Blank’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Attribution Panel - Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Combo chart - Blank and Populated’ screens.
ARIA toggle fields do not have an accessible name in ‘User Preferences Modal’, ‘Calendar’ screens.
Combo box is missing appropriate roles and/or attributes in ‘Alert Builder, Blank’, ‘Left Rail Menu’, ‘Report Suite Selector’, ‘User Preferences Modal’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Contribution analysis of anomaly detection’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Attribution Panel - Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘Combo chart - Blank and Populated’, ‘Alert Builder, Populated’ screens.
The unallowed ARIA attributes are used in ‘User Preferences Modal’, ‘Trend Metrics from Visualize button’, ‘Alert Builder, Blank’, ‘Alert Builder, Populated’, ‘Attribution Panel - Populated’, ‘Contribution analysis of anomaly detection’, ‘Create new alert’, ‘Create new annotation’, ‘Home Page and Header / Share Navigation’, ‘Populated Panel’, ‘Left Rail Menu’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Fallout - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Key Metric Summary - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Combo chart - Blank and Populated’ screens.
The element's role is missing or incorrect in ‘Left Rail Menu’, ‘Choose Panel Type’, ‘Create new annotation’, ‘View Header’ screens.
The element has missing or incorrect states or properties in ‘Share Workspace’ screen.
Tooltip content is not accessible to screen readers in ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Fallout - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Home Page and Header / Share Navigation’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’ screens.
Buttons do not have an accessible name in ‘User Preferences Modal’, ‘Alert Builder, Blank’, ‘Alert Builder, Populated’, ‘Attribution Panel - Populated’, ‘Create new alert’, ‘Create new annotation’, ‘Fallout - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Segment details and edit options’, ‘Successful Alert Save’, ‘Left Rail Menu’, ‘New Panel Set Up - Step 1’, ‘Trend Metrics from dragging Visualization to main page’ screens.
Button does not have a role in ‘Alert Builder, Blank’, ‘Anomaly detection’, ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Create new alert’, ‘Create new annotation’, ‘Curate Project data’, ‘Fallout - Blank and Populated’, ‘Key Metric Summary - Blank and Populated’, ‘New Panel Set Up - Step 1’, ‘Segment Comparison - Populated’, ‘Successful Alert Save’, ‘Trend Metrics from Visualize button’, ‘View Header’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’, ‘Alert Builder, Populated’ screens.
Button is missing both a role and a accessible name in ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Fallout - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Key Metric Summary - Blank and Populated’, ‘Left Rail Menu’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’, ‘New Panel Set Up - Step 1’, ‘New Panel Set Up - Step 2’, ‘Populated Panel’, ‘Venn Diagram - Blank and Populated’, ‘Cohort Table - Blank and Populated’, ‘Contribution analysis creation panel’, ‘Attribution Panel - Blank’, ‘Segment Comparison - Blank’ screens.
Button pressed state is not conveyed in ‘Attribution Panel - Populated’, ‘Combo chart - Blank and Populated’, ‘Segment Comparison - Populated’, ‘Trend Metrics from Visualize button’ screens.
Form elements do not have labels in ‘Alert Builder, Blank’, ‘Alert Builder, populated’, ‘Create new alert’, ‘Create new annotation’, ‘Create new annotation’ screens.
Expand/collapse state of the element is missing or incorrect in ‘Segment Comparison - Populated’, ‘Left Rail Menu’, ‘Alert Builder, Blank’, ‘Alert Builder, Populated’, ‘Attribution Panel - Blank’, ‘Attribution Panel - Populated’, ‘Calendar’, ‘Choose Panel Type’, ‘Cohort Table - Blank and Populated’, ‘Combo chart - Blank and Populated’, ‘Contribution analysis of anomaly detection’, ‘Create new alert’, ‘Create new annotation’, ‘Fallout - Blank and Populated’, ‘Flow - Blank and Populated’, ‘Home Page and Header / Share Navigation’, ‘Key Metric Summary - Blank and Populated’, ‘Populated Panel’, ‘Report Suite Selector’, ‘Segment builder - Blank and Populated’, ‘Segment Comparison - Blank’, ‘Successful Alert Save’, ‘Successful Alert Save’, ‘User Preferences Modal’, ‘Venn Diagram - Blank and Populated’, ‘View Header’ screens.
Selected state of the element is missing or incorrect in ‘Curate Project data’ screen.
Table sort state is missing in ‘Successful Alert Save’ screen.
4.1.3 Status Messages (Level AA 2.1 only)
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)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
When status messages do not receive focus, the product does not provide the update to assistive technology.
Exceptions include:
Status message is not automatically announced to screen readers most of the screens in the application.
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, Functional image missing text alternative, Complex Images missing detailed alternative description, Complex Images detailed alternative description is not adequate, Complex Images missing short text alternative, Complex Images short text alternative is not appropriate.
As noted in 1.3.1 Info and relationships, The content visually appears to be a data table but is not marked up as a table, data table has missing or incomplete header cell markup, the checkboxes group label is not associated with its checkboxes, group of form controls not associated with group label, the radio buttons group label is not associated with its radio buttons, control is not a heading but marked as a heading, heading levels are out of order, text should not be marked as a heading, visual heading text is not marked as heading, visual list is not marked up as list, Form element does not have label, Role="presentation" or "none" is used incorrectly.
As noted in 1.3.2 Meaningful sequence, aria-hidden="true" attribute is used incorrectly, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 1.4.1 Use of color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content, Functional image missing text alternative, Complex Images missing detailed alternative description, Complex Images detailed alternative description is not adequate, Complex Images missing short text alternative, Complex Images short text alternative is not appropriate.
As noted in 1.3.1 Info and relationships, The content visually appears to be a data table but is not marked up as a table, data table has missing or incomplete header cell markup, the checkboxes group label is not associated with its checkboxes, group of form controls not associated with group label, the radio buttons group label is not associated with its radio buttons, control is not a heading but marked as a heading, heading levels are out of order, text should not be marked as a heading, visual heading text is not marked as heading, visual list is not marked up as list, Form element does not have label, Role="presentation" or "none" is used incorrectly.
As noted in 1.3.2 Meaningful sequence, aria-hidden="true" attribute is used incorrectly, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 1.4.1 Use of color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.3 Contrast (Minimum), Large text content lacks 3:1 contrast ratio, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio, Text content lacks 4.5:1 contrast ratio.
As noted in 1.4.4 Resize text, some part of the page content is lost when the page is zoomed to 200%, Functionality and content are lost at 200% zoom.
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.3 Contrast (Minimum), Large text content lacks 3:1 contrast ratio, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio, Text content lacks 4.5:1 contrast ratio.
Web: Users with limited manipulation who use speech recognition or switch control software will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic labels do not convey purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
Web: Users with limited reach and strength will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic labels do not convey purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
Web: The product is functional for users 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. The product provides labeling for most controls. Exceptions include:
As noted in 1.3.2 Meaningful sequence, aria-hidden="true" attribute is used incorrectly, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes: Not Applicable
Chapter 6: Support Documentation and Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
EN 301 549 Report
Notes:
Chapter 4: Functional Performance Statements (FPS)
Notes:
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, Functional image missing text alternative, Complex Images missing detailed alternative description, Complex Images detailed alternative description is not adequate, Complex Images missing short text alternative, Complex Images short text alternative is not appropriate.
As noted in 1.3.1 Info and relationships, The content visually appears to be a data table but is not marked up as a table, data table has missing or incomplete header cell markup, the checkboxes group label is not associated with its checkboxes, group of form controls not associated with group label, the radio buttons group label is not associated with its radio buttons, control is not a heading but marked as a heading, heading levels are out of order, text should not be marked as a heading, visual heading text is not marked as heading, visual list is not marked up as list, Form element does not have label, Role="presentation" or "none" is used incorrectly.
As noted in 1.3.2 Meaningful sequence, aria-hidden="true" attribute is used incorrectly, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 1.4.1 Use of color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.13 Content on Hover or Focus, Additional content not dismissible, Hover content disappearing.
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
As noted in 4.1.3 Status Messages, Status messages are not automatically announced.
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content, Functional image missing text alternative, Complex Images missing detailed alternative description, Complex Images detailed alternative description is not adequate, Complex Images missing short text alternative, Complex Images short text alternative is not appropriate.
As noted in 1.3.1 Info and relationships, The content visually appears to be a data table but is not marked up as a table, data table has missing or incomplete header cell markup, the checkboxes group label is not associated with its checkboxes, group of form controls not associated with group label, the radio buttons group label is not associated with its radio buttons, control is not a heading but marked as a heading, heading levels are out of order, text should not be marked as a heading, visual heading text is not marked as heading, visual list is not marked up as list, Form element does not have label, Role="presentation" or "none" is used incorrectly.
As noted in 1.3.2 Meaningful sequence, aria-hidden="true" attribute is used incorrectly, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 1.4.1 Use of color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.10 Reflow, Content and functionality are lost at 320px width equivalent, Content does not reflow to fit horizontally within the viewpoint when the page is adjusted to an equivalent width of 320px, Content overlaps other content at 320px width equivalent.
As noted in 1.4.11 Non-text Contrast, Active user interface component lacks 3 to 1 contrast ratio, An icon lacks 3 to 1 contrast ratio, Graphical object lacks 3 to 1 contrast, State of active component lacks 3 to 1 contrast ratio.
As noted in 1.4.13 Content on Hover or Focus, Additional content not dismissible, Hover content disappearing.
As noted in 1.4.3 Contrast (Minimum), Large text content lacks 3:1 contrast ratio, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio, Text content lacks 4.5:1 contrast ratio.
As noted in 1.4.4 Resize text, some part of the page content is lost when the page is zoomed to 200%, Functionality and content are lost at 200% zoom.
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic labels do not convey the purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
As noted in 4.1.3 Status Messages, Status messages are not automatically announced.
Web: Most of the functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.3 Contrast (Minimum), Large text content lacks 3:1 contrast ratio, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio, Text content lacks 4.5:1 contrast ratio.
As noted in 1.4.11 Non-text Contrast, Active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio, Graphical object lacks 3 to 1 contrast, State of active component lacks 3 to 1 contrast ratio.
Web: Users with limited manipulation or strength who use speech recognition or switch control software will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 1.4.13 Content on Hover or Focus, Additional content not dismissible, Hover content disappearing.
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 2.5.3 Label in Name, Accessible name missing, Accessible name does not contain visible label.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
Web: Users with limited reach will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 1.4.13 Content on Hover or Focus, Additional content not dismissible, Hover content disappearing.
As noted in 2.1.1 Keyboard, Device-dependent event handlers are used, Function cannot be performed by keyboard, Link does not have an href value, Scrollable region does not have keyboard access.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 2.5.3 Label in Name, Accessible name missing, Accessible name does not contain visible label.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
Web: The product is functional for users 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. The product provides labeling for most controls. Exceptions include:
As noted in 1.3.2 Meaningful sequence, aria-hidden="true" attribute is used incorrectly, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 2.2.1 Timing adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, Keyboard focus order is not logical.
As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
As noted in 2.4.7 Focus Visible, Focus indicator is missing.
As noted in 3.3.2 Labels or Instructions, Label is not persistent, visible label missing.
As noted in 4.1.1 Parsing, Certain ARIA roles do not contain particular children, Certain ARIA roles are not contained by particular parents, Interactive controls are nested, id attribute values are not unique, IDs used in ARIA and labels are not unique.
As noted in 4.1.2 Name, Role, Value, ARIA input fields do not have an accessible name, ARIA toggle fields do not have an accessible name, Combo box is missing appropriate roles and/or attributes, the unallowed ARIA attributes are used, the element's role is missing or incorrect, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, buttons do not have an accessible name, button does not have a role, button is missing both a role and a accessible name, button pressed state is not conveyed, form elements do not have labels, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, table sort state is missing.
As noted in 4.1.3 Status Messages, Status messages are not automatically announced.
Chapter 5: Generic Requirements
Notes:
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: See WCAG 2.1 section
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes: Not Applicable
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)