Adobe Accessibility Conformance Report

International Edition

(Based on VPAT® Version 2.4)

Name of Product/Version:

Adobe Experience Platform

 

Report Date: 

April 2023

 

Product Description: 

Adobe Experience Platform is the most powerful, flexible, and open system on the market for building and managing complete solutions that drive customer experience. Experience Platform enables organizations to centralize and standardize customer data and content from any system and apply data science and machine learning to dramatically improve the design and delivery of rich, personalized experiences.

 

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:

Standard/Guideline

Included in Report

Web Content Accessibility Guidelines 2.0

Level A: Yes
Level AA: Yes
Level AAA: No

Web Content Accessibility Guidelines 2.1

Level A: Yes
Level AA: Yes
Level AAA: No

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018

Yes

EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, - V3.1.1 (2019-11) 

Yes

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.

Criteria

Conformance Level

Remarks and Explanations

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

Web: The product provides sufficient text alternatives for most instances of active and informative images. Exceptions include: 

  • Detailed alternative description is missing in 'Dashboards - Create dashboard 4', 'Global and Homepage - Dashboard (License Usage)', 'Global and Homepage - Modify dashboard button', 'License Usage - Overview', 'Dashboards - Create dashboard 3', 'Data management - Monitoring - Streaming end-to-end tab', 'Global and Homepage - Dashboard (Segment)' screen.
  • Text alternative is missing in 'Header', 'Customer - Identities - Create identity namespace button and modal', 'Data management - Queries - Credentials tab' screen.
  • [role='img'] elements do not have an alternative text in 'Customer - Segments - Browse Tab' screen.
  • Short text alternative is missing in 'Global and Homepage - Modify dashboard button', 'Global and Homepage - Dashboard (Segment)', 'Dashboards - Create dashboard 4', 'Data management - Monitoring - Streaming end-to-end tab', 'Dashboards - Create dashboard 3', 'License Usage - Overview', 'Global and Homepage - Dashboard (License Usage)' screen.
  • The decorative image is not hidden from screen readers in 'Global and Homepage – Homepage' screen.
  • Text alternative does not present same info as image in 'Global and Homepage - Homepage' screen.

Guideline 1.2 Time-based Media:

Provide alternatives for time-based media.

Criteria

Conformance Level

Remarks and Explanations

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)

Web: Supports (Not Applicable)

Web: The product does not contain prerecorded audio-only or video-only media.

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)

Web: Supports

Web: The product contains prerecorded synchronized media and open or closed captions are provided.

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)

Web: Supports (Not Applicable)

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

1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.4 (Web)
  • 10.1.2.4 (Non-web document)
  • 11.1.2.4 (Open Functionality Software)
  • 11.1.2.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs

Revised Section 508

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

Web: Supports (Not Applicable)

Web: The product does not contain live synchronized media.

1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.5 (Web)
  • 10.1.2.5 (Non-web document)
  • 11.1.2.5 (Open Functionality Software)
  • 11.1.2.5 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

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

Web: Supports (Not Applicable)

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

Guideline 1.3 Adaptable:

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Criteria

Conformance Level

Remarks and Explanations

1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

Web: Most of the visual structure and relationship information is provided through element semantics or object information or in text. Exceptions include:

  • Heading levels are out of order in 'Dashboards - Create dashboard 2', 'Data management - Queries - Credentials tab', 'Global and Homepage - Homepage', 'Data management - Monitoring - Dashboard tab' screens.
  • Visible label/form field are not associated in 'Customer - Identities - Identity Graph tab', 'Profiles - Browse Tab', 'Global and Homepage - Dashboard (License Usage)', 'Global and Homepage - Dashboard (Segment)', 'Dashboards - Create dashboard 3', 'Data Management - Places - Create POI', 'Data management - Monitoring - Dashboard tab', 'License Usage - Overview' screens.
  • Text should not be marked as a heading in 'Global and Homepage - Homepage', 'License Usage - Overview', 'Global and Homepage - Dashboard (License Usage)' screens.
  • Group of form controls not associated with group label in 'Global and Homepage - Modify dashboard button' screen.
  • Visual heading text is not marked as heading in 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Data management - Schemas - Create schema', 'Customer - Identities - Identity Graph tab', 'Data management - Schemas - Create data type', 'Profiles - Browse Tab' screen.
  • Form elements do not have labels in 'Privacy - Policies - Labels - Create Label modal' screen.
  • <ul> and <ol> must only directly contain <li>, <script> or <template> elements in 'Data Management - Places - Import POI 1' screen.
  • Content is not a list but is marked as such in 'Global and Homepage - widget library' screen.
  • The group label is not associated with its group of radio buttons in 'Customer - Identities - Create identity namespace button and modal', 'Global and Homepage - Dashboard (License Usage)' 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: Partially Supports

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

  • Screen reader focus is lost or misplaced due to user interaction or content update in 'Dashboards - Create dashboard 3' screen.

1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

Web: Instructions that do not rely solely on sensory characteristics.

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

Web: Supports

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

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

Web: Supports (Not Applicable)

Web: The product does not contain input fields that collect information about the user.

Guideline 1.4 Distinguishable:

Make it easier for users to see and hear content including separating foreground from background.

Criteria

Conformance Level

Remarks and Explanations

1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

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

  • Color alone is used to convey information in 'Data management - Schemas - Create data type', ‘Data management - Schemas - Create schema’, 'Customer - Profiles - Create merge policy - Select Profile Dataset' screen.
  • Link contrast is not at least 3:1 with surrounding text in 'Data Management - Places - Create POI', 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Profiles - Browse Tab', 'Data management - Schemas - Create data type', ‘Data management - Schemas - Create schema’, screen.

 

1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.2 (Web)
  • 10.1.4.2 (Non-web document)
  • 11.1.4.2 (Open Functionality Software)
  • 11.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

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

Web: Supports (Not Applicable)

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

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

Web: Most text meets minimum contrast requirements. 

Exceptions include:

  • Text content lacks 4.5:1 contrast ratio in 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Header', 'Data management - Monitoring - Streaming end-to-end tab', 'Privacy - Policies - Labels - Create Label modal', 'Data management - Queries - Create query', 'Data management - Schemas - Create data type', 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Data management - Schemas - Create schema' screen.
  • Link or button text lacks 4.5:1 contrast ratio on hover or focus in 'Profiles - Browse Tab' screen.
  • Placeholder text lacks 4.5:1 contrast ratio in 'Sandbox - Create Sandbox modal', 'Privacy - Policies - Create Policy - Configure', 'Customer - Segments - Create segment', 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Customer - Profiles - Create merge policy - Configure', 'Header', 'Data management - Schemas - Create data type', ‘Data management - Schemas - Create schema’,  screen.
  • Elements do not have sufficient color contrast in 'Data management - Monitoring - Dashboard tab', 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Data Management - Places - Import POI 1', 'Global and Homepage - widget library', 'Header', 'Data Collection - DataStreams - New DataStream (Configure)', 'Dashboards - Create dashboard 3' screen.

1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.4 (Web)
  • 10.1.4.4 (Non-web document)
  • 11.1.4.4.1 (Open Functionality Software)
  • 11.1.4.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

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

Web: Partially Supports

Web: The product allows browser zoom to resize text up to 200 percent without loss of content or functionality. Exceptions include:

  • Content is lost at 200% zoom in 'Dashboards - Create dashboard 3', 'Privacy - Policies - Marketing actions - Create marketing action modal', 'Privacy - Policies - Labels - Create Label modal', 'Dashboards - Create dashboard 2', 'Customer - Segments - Create segment' 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)

Web: Supports

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

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

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 does not reflow to fit 320px width equivalent in 'Dashboards - Create dashboard 3', 'Customer - Segments - Create segment', 'Customer - Profiles - Create merge policy - Select Profile Dataset' screen.
  • Content overlaps other content at 320px width equivalent in 'Dashboards - Create dashboard 3', 'Data management - Schemas - Create schema', 'Customer - Segments - Create segment', 'Data management - Schemas - Create data type', 'Customer - Profiles - Create merge policy - Select Profile Dataset' screen.

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

Web: Most meaningful non-text content elements have sufficient contrast requirements. Exceptions include:

  • State of active component lacks 3 to 1 contrast ratio in 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Data management - Schemas - Create schema' screen.
  • Active user interface component lacks 3 to 1 contrast ratio in 'Data management - Schemas - Create schema' screen.
  • Graphical object lacks 3 to 1 contrast ratio in 'Dashboards - Create dashboard 3' screen.

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

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

  • Text spacing content overlaps in 'Customer - Profiles - Create merge policy - Select Profile Dataset' screen.

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

Web: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion. 

Guideline 2.1 Keyboard Accessible:

Make all functionality available from a keyboard.

Criteria

Conformance Level

Remarks and Explanations

2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

Web: Most product functionality can be operated through a keyboard interface. Exceptions include:

  • Function cannot be performed by keyboard alone in 'Sandbox - Create Sandbox modal', 'Global and Homepage - Modify dashboard button', 'Data management - Monitoring - Dashboard tab', 'Dashboards - Create dashboard 4', 'Dashboards - Create dashboard 3', 'Data Management - Places - Create POI', 'Customer - Segments - Create segment', 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Global and Homepage - widget library' screen.
  • Scrollable region does not have keyboard access in 'Customer - Segments - Browse Tab', 'Data management - Monitoring - Dashboard tab', 'License Usage - Overview', 'Privacy - Policies - Browse tab', 'Data management - Schemas - Browse tab', 'Data management - Datasets - Browse tab', 'Data management - Datasets - Create dataset', 'Customer - Identities - Browse tab' screen.
  • Drag and drop feature is not keyboard accessible in 'Dashboards - Create dashboard 4', 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Global and Homepage - Modify dashboard button' screen.
  • Device-dependent event handlers are used in 'Global and Homepage - Dashboard (Segment)', 'Data management - Monitoring - Streaming end-to-end tab', 'Dashboards - Create dashboard 3', 'Global and Homepage - Dashboard (License Usage)', 'Global and Homepage - Modify dashboard button', 'License Usage - Overview' 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)

Web: Supports

Web: The product does not include keyboard traps.

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

Web: Supports (Not Applicable)

Web: The product does not provide character key shortcuts.

Guideline 2.2 Enough Time:

Provide users enough time to read and use content.

Criteria

Conformance Level

Remarks and Explanations

2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports (Not Applicable)

Web: The product does not include time limits.

2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.2.2 (Web)
  • 10.2.2.2 (Non-web document)
  • 11.2.2.2 (Open Functionality Software)
  • 11.2.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

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

Web: Supports (Not Applicable)

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

Guideline 2.3 Seizures:

Do not design content in a way that is known to cause seizures. 

Criteria

Conformance Level

Remarks and Explanations

2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.3.1 (Web)
  • 10.2.3.1 (Non-web document)
  • 11.2.3.1 (Open Functionality Software)
  • 11.2.3.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

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

Web: Supports (Not Applicable)

Web: The product does not contain flashing content. 

Guideline 2.4 Navigable:

Provide ways to help users navigate, find content, and determine where they are. 

Criteria

Conformance Level

Remarks and Explanations

2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

Web: The product provides a skip link, which allows users to bypass repeated blocks.

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

Web: The titles of pages describe their purpose.

2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

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

  • Hidden or empty element receives focus in 'Data Management - Places - Create POI', 'Privacy - Data Hygiene - Create Data Hygiene Request 2' screen.
  • Keyboard focus is lost or misplaced due to user interaction or content update in 'Dashboards - Create dashboard 3', 'Privacy - Data Hygiene - Create Data Hygiene Request 2' screen.
  • Modal is closed, focus is not returned to trigger in 'Sandbox - Create Sandbox modal' screen.
  • Keyboard focus order is not logical in 'Header' 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: Partially Supports

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 'Data management - Schemas - Create data type', ‘Data management - Schemas - Create schema’, screen.

2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

Web: Users can locate web pages in the product through the menu and options in the main section.

 2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

Web: Most headings and labels are descriptive in the product. Exceptions include:

  • Programmatic label does not convey purpose of control in 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Data management - Schemas - Create schema' screen.
  • Buttons have same name but different actions in 'Dashboards - Create dashboard 3' screen.
  • Label does not convey purpose of control in 'Customer - Profiles - Create merge policy - Select Profile Dataset' screen.

 

2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

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

  • Focus indicator is not visible in 'Header' screen.

Guideline 2.5 Input Modalities:

Make it easier for users to operate functionality through various inputs beyond keyboard. 

Criteria

Conformance Level

Remarks and Explanations

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

Web: Supports (Not Applicable)

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

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

Web: Supports

Web: Product functions that use a single pointer are completed when the user releases the pointer.

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

Web: The accessible names of controls contain the text of their visible labels. Exceptions include:

  • Accessible name does not contain visible label in 'Dashboards - Create dashboard 3' screen.

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

Web: Supports (Not Applicable)

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

Guideline 3.1 Readable:

Make text content readable and understandable. 

Criteria

Conformance Level

Remarks and Explanations

3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

Web: The language is programmatically determinable within the product.

3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports (Not Applicable)

Web: Content is only presented in one language at a time.

Guideline 3.2 Predictable:

Make Web pages appear and operate in predictable ways. 

Criteria

Conformance Level

Remarks and Explanations

3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

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

3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

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

3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

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

3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

Web: Components with the same functionality are identified consistently.

Guideline 3.3 Input Assistance:

Help users avoid and correct mistakes. 

Criteria

Conformance Level

Remarks and Explanations

3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.1 (Web)
  • 10.3.3.1 (Non-web document)
  • 11.3.3.1.1 (Open Functionality Software)
  • 11.3.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

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

Web: Partially Supports

Web: Most input errors are identified and described to the users in text. Exceptions include:

  • Form field with error not identified in 'Customer - Segments - Create segment', 'Privacy - Data Hygiene - Create Data Hygiene Request 1' screen.
  • Input error is not described in text in 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Customer - Segments - Create segment' screen.

 

 

3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

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

  • Visible label missing in 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Privacy - Policies - Create Policy - Configure' screen.
  • Label is not persistent in 'Customer - Segments - Create segment' screen.

3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports

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

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports (Not Applicable)

Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data.

Guideline 4.1 Compatible:

Maximize compatibility with current and future user agents, including assistive technologies. 

Criteria

Conformance Level

Remarks and Explanations

4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria

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

Web: In most of the product functions, elements have complete 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 must contain particular children in 'Data management - Schemas - Create data type', 'Customer - Segments - Create segment', 'Global and Homepage - Homepage', 'Data management - Datasets - Browse tab', 'Global and Homepage - widget library', 'Data management - Schemas - Create schema', 'Customer - Profiles - Union schema tab', 'Data management - Monitoring - Batch end-to-end tab' screen.
  • Certain ARIA roles are not contained by particular parents in 'Data Collection - Tags - New Property', 'Customer - Profiles - Create merge policy - Review', 'Global and Homepage - Dashboard (Customer: Segments)', 'Global and Homepage - Homepage', 'Data Collection - Event Forwarding - New Property' screen.
  • IDs of active elements are not unique in 'Data Collection - Assurance - Create New Session 1', 'Data Collection - Assurance - Create New Session 2' screen.
  • id attribute value are not unique in 'Customer - Segments - Create segment', 'Global and Homepage - widget library', 'Connections - Sources - Catalog', 'Dashboards - Create dashboard 3' screen.
  • Interactive controls must not be nested in 'Customer - Segments - Create segment', 'Data management - Schemas - Create your first schema - Video tutorial modal' screen.
  • IDs used in ARIA and labels are not unique in 'Global and Homepage - Inventory (table) component and configuration button' screen.

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

Web: User interface components in most product functions provide programmatic name, role, and/or state information. Exceptions include:

  • Expand/collapse state of the element is missing or incorrect in 'Data management - Monitoring - Dashboard tab', 'Privacy - Data Hygiene - Create Data Hygiene Request 2', 'License Usage - Overview', 'Global and Homepage - widget library', 'Sandbox - Create Sandbox modal', 'Global and Homepage - Dashboard (Segment)', 'Global and Homepage - Modify dashboard button', 'Data management - Schemas - Create your first schema - Video tutorial modal', 'Dashboards - Create dashboard 3', 'Header', 'Data Management - Places - Create POI', 'Customer - Segments - Create segment', 'Global and Homepage - Dashboard (License Usage)', 'Customer - Identities - Identity Graph tab' screen.
  • Selected state of the element is missing or incorrect in 'Privacy - Data Hygiene - Create Data Hygiene Request 2' screen.
  • Button pressed state is not conveyed in 'Data Management - Places - Create POI', 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Data management - Schemas - Create schema' screen.
  • Button does not have a name in 'Data Management - Places - Create POI', 'Privacy - Data Hygiene - Create Data Hygiene Request 1', 'Global and Homepage - Dashboard (License Usage)', 'Global and Homepage - Dashboard (Segment)' screen.
  • Buttons do not have discernible text in 'Customer - Segments - Browse Tab', 'Data management - Schemas - Create schema', 'Data Management - Places - Create POI', 'Data management - Monitoring - Dashboard tab', 'Data Collection - Assurance - Create New Session 3', 'Customer - Segments - Create segment', 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Customer - Profiles - Create merge policy - Select Experience Event Dataset', 'Dashboards - Create dashboard 3' screen.
  • Elements must only use allowed ARIA attributes in 'Global and Homepage - Modify dashboard button', 'Data Management - Places - Create POI', 'Data management - Monitoring - Dashboard tab', 'Global and Homepage - Dashboard (Segment)', 'Customer - Segments - Create segment', 'License Usage - Overview', 'Privacy - Policies - Labels - Create Label modal', 'Customer - Identities - Identity Graph tab', 'Data management - Datasets - Browse tab', 'Customer - Profiles - Union schema tab', 'Sandbox - Create Sandbox modal', 'Data management - Monitoring - Batch end-to-end tab', 'Dashboards - Create dashboard 3' screen.
  • Tooltip content is not accessible to screen readers in 'Customer - Segments - Create segment', 'Global and Homepage - Modify dashboard button', 'License Usage - Overview', 'Dashboards - Create dashboard 2', 'Global and Homepage - Dashboard (Segment)', 'Data management - Monitoring - Streaming end-to-end tab', 'Dashboards - Create dashboard 3', 'Global and Homepage - Dashboard (License Usage)' screen.
  • The element has missing or incorrect states or properties in 'Header' screen.
  • Treeview is missing appropriate roles and/or attributes in 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Data management - Schemas - Create schema', 'Data management - Schemas - Create data type'.
  • Elements are using unallowed ARIA attributes in 'Customer - Profiles - Create merge policy - Configure' screen.
  • ARIA progressbar nodes do not have an accessible name in 'Customer - Profiles - Create merge policy - Review' screen.
  • Button does not have a role in 'Privacy - Data Hygiene - Create Data Hygiene Request 2', 'Customer - Identities - Identity Graph tab'.
  • Combobox is missing appropriate roles and/or attributes in 'Privacy - Data Hygiene - Create Data Hygiene Request 1' screen.
  • ARIA hidden element must not be focusable or contain focusable elements in 'Data Collection - DataStreams - New DataStream (Configure)', 'Dashboards - Create dashboard 3' screen.
  • The element's role is missing or incorrect in 'Header' screen.
  • Tab widget is missing appropriate roles and/or attributes in 'Data management - Monitoring - Dashboard tab' screen.
  • Button is missing both a role and a name in 'Data Management - Places - Create POI' 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

Web: Partially Supports

Web: In most of the screens of the product, when status messages do not receive focus, the product provides the updates to the assistive technology. Exceptions include:

  • Status message not automatically announced in 'Customer - Profiles - Create merge policy - Select Profile Dataset', 'Customer - Segments - Create segment', 'Dashboards - Create dashboard 3', 'Data management - Schemas - Create data type' screen.

 

Revised Section 508 Report

Notes:
 

Chapter 3: Functional Performance Criteria (FPC)

Notes: 

Criteria

Conformance Level

Remarks and Explanations

302.1 Without Vision

Web: Partially Supports

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

  • As noted in 1.1.1 Non-text Content, Detailed alternative description is missing, Text alternative is missing, [role='img'] elements do not have an alternative text, Short text alternative is missing, the decorative image is not hidden from screen readers, Text alternative does not present same info as image.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, Visible label/form field are not associated, Text should not be marked as a heading, Group of form controls not associated with group label, Visual heading text is not marked as heading, Form elements do not have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Content is not a list but is marked as such, The group label is not associated with its group of radio buttons 
  • As noted in 1.3.2 Meaningful Sequence, Screen reader focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Scrollable region does not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 3.3.1 Error Identification, Form field with error not identified, Input error is not described in text.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.

302.2 With Limited Vision

Web: Partially Supports

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

  • As noted in 1.1.1 Non-text Content, Detailed alternative description is missing, Text alternative is missing, [role='img'] elements do not have an alternative text, Short text alternative is missing, the decorative image is not hidden from screen readers, Text alternative does not present same info as image.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, Visible label/form field are not associated, Text should not be marked as a heading, Group of form controls not associated with group label, Visual heading text is not marked as heading, Form elements do not have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Content is not a list but is marked as such, The group label is not associated with its group of radio buttons 
  • As noted in 1.3.2 Meaningful Sequence, Screen reader focus is lost or misplaced due to user interaction or content update.
  • As noted in 1.4.1 Use of Color, Color alone is used to convey information, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5: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, Elements do not have sufficient color contrast.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Scrollable region does not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 3.3.1 Error Identification, Form field with error not identified, Input error is not described in text.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.

302.3 Without Perception of Color

Web: Partially Supports

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

  • As noted in 1.4.1 Use of Color, Color alone is used to convey information, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5: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, Elements do not have sufficient color contrast.

302.4 Without Hearing

Web: Supports

Web: All functions of the product are usable without hearing.

302.5 With Limited Hearing

Web: Supports

Web: All functions of the product are usable with limited hearing.

302.6 Without Speech

Web: Supports (Not Applicable)

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

302.7 With Limited Manipulation

Web: Partially Supports

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, Function cannot be performed by keyboard alone, Scrollable region does not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.

302.8 With Limited Reach and Strength

Web: Partially Supports

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, Function cannot be performed by keyboard alone, Scrollable region does not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Partially Supports

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, Screen reader focus is lost or misplaced due to user interaction or content update.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 3.3.1 Error Identification, Form field with error not identified, Input error is not described in text.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.

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: 

Criteria

Conformance Level

Remarks and Explanations

4.2.1 Usage without vision

Web: Partially Supports

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

  • As noted in 1.1.1 Non-text Content, Detailed alternative description is missing, Text alternative is missing, [role='img'] elements do not have an alternative text, Short text alternative is missing, the decorative image is not hidden from screen readers, Text alternative does not present same info as image.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, Visible label/form field are not associated, Text should not be marked as a heading, Group of form controls not associated with group label, Visual heading text is not marked as heading, Form elements do not have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Content is not a list but is marked as such, The group label is not associated with its group of radio buttons.
  • As noted in 1.3.2 Meaningful Sequence, Screen reader focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Scrollable region does not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 3.3.1 Error Identification, Form field with error not identified, Input error is not described in text.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.
  • As noted in 4.1.3 Status Messages, Status message not automatically announced.

4.2.2 Usage with limited vision

Web: Partially Supports

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

  • As noted in 1.1.1 Non-text Content, Detailed alternative description is missing, Text alternative is missing, [role='img'] elements do not have an alternative text, Short text alternative is missing, the decorative image is not hidden from screen readers, Text alternative does not present same info as image.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, Visible label/form field are not associated, Text should not be marked as a heading, Group of form controls not associated with group label, Visual heading text is not marked as heading, Form elements do not have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Content is not a list but is marked as such, The group label is not associated with its group of radio buttons 
  • As noted in 1.3.2 Meaningful Sequence, Screen reader focus is lost or misplaced due to user interaction or content update.
  • As noted in 1.4.1 Use of Color, Color alone is used to convey information, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.10 Reflow, Content does not reflow to fit 320px width equivalent, Content overlaps other content at 320px width equivalent.
  • As noted in 1.4.11 Non-text Contrast, State of active component lacks 3 to 1 contrast ratio, Active user interface component lacks 3 to 1 contrast ratio, Graphical object lacks 3 to 1 contrast ratio.
  • As noted in 1.4.12 Text Spacing, Text spacing content overlaps.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5: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, Elements do not have sufficient color contrast.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Scrollable region does not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 3.3.1 Error Identification, Form field with error not identified, Input error is not described in text.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.
  • As noted in 4.1.3 Status Messages, Status message not automatically announced.

4.2.3 Usage without perception of colour

Web: Partially Supports

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

  • As noted in 1.4.1 Use of Color, Color alone is used to convey information, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.11 Non-text Contrast, State of active component lacks 3 to 1 contrast ratio, Active user interface component lacks 3 to 1 contrast ratio, Graphical object lacks 3 to 1 contrast ratio.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5: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, Elements do not have sufficient color contrast.

4.2.4 Usage without hearing

Web: Supports

Web: All functions of the product are usable without hearing.

4.2.5 Usage with limited hearing

Web: Supports

Web: All functions of the product are usable with limited hearing.

4.2.6 Usage without vocal capability

Web: Supports (Not Applicable)

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

4.2.7 Usage with limited manipulation or strength

Web: Partially Supports

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 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Scrollable region does not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 2.5.3 Label in Name, Accessible name does not contain visible label.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.

4.2.8 Usage with limited reach

Web: Partially Supports

Web: Users with limited reach will not have difficulty navigating to most of the controls. Exceptions include:

  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Scrollable region do not have keyboard access, Drag and drop feature is not keyboard accessible, Device-dependent event handlers are used.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 2.5.3 Label in Name, Accessible name does not contain visible label.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.

4.2.9 Minimize photosensitive seizure triggers

Web: Supports (Not Applicable)

Web: The product does not contain flashing content or media.

4.2.10 Usage with limited cognition, language or learning

Web: Partially Supports

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, Screen reader focus is lost or misplaced due to user interaction or content update.
  • As noted in 1.4.12 Text Spacing, Text spacing content overlaps.
  • 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, Modal is closed, focus is not returned to trigger, Keyboard focus order is not logical.
  • As noted in 2.4.4 Link Purpose, Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions, Label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the focus indicator is not visible.
  • As noted in 3.3.1 Error Identification, Form field with error not identified, Input error is not described in text.
  • As noted in 3.3.2 Labels or Instructions, Visible label missing, Label is not persistent.
  • As noted in 4.1.1 Parsing, Certain ARIA roles must contain particular children, Certain ARIA roles are not contained by particular parents, IDs of active elements are not unique, id attribute value is not unique, Interactive controls must not be nested, IDs used in ARIA and labels are not unique.
  • As noted in 4.1.2 Name, Role, Value, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, Button pressed state is not conveyed, Button does not have a name, Buttons do not have discernible text, Elements must only use allowed ARIA attributes, Tooltip content is not accessible to screen readers, The element has missing or incorrect states or properties, Elements are using unallowed ARIA attributes, ARIA progressbar nodes do not have an accessible name, Button does not have a role, Combobox is missing appropriate roles and/or attributes, ARIA hidden element must not be focusable or contain focusable elements, The element's role is missing or incorrect, Tab widget is missing appropriate roles and/or attributes, Button is missing both a role and a name.
  • As noted in 4.1.3 Status Messages, Status message not automatically announced.

4.2.11 Privacy

Web: Supports (Not Applicable)

Web: The product does not provide any privacy features.

Chapter 5: Generic Requirements

Notes:

Criteria

Conformance Level

Remarks and Explanations

5.1 Closed functionality

5.1.2 General

5.1.2.1 Closed functionality

See 5.2 through 13

See information in 5.2 through 13

5.1.2.2 Assistive technology

See 5.1.3 through 5.1.6

See information in 5.1.3 through 5.1.6

5.1.3 Non-visual access

5.1.3.1 Audio output of visual information

Not Applicable

The product does not have closed functionality.

5.1.3.2 Auditory output delivery including speech

Not Applicable

The product does not have closed functionality.

5.1.3.3 Auditory output correlation

Not Applicable

The product does not have closed functionality.

5.1.3.4 Speech output user control

Not Applicable

The product does not have closed functionality.

5.1.3.5 Speech output automatic interruption

Not Applicable

The product does not have closed functionality.

5.1.3.6 Speech output for non-text content

Not Applicable

The product does not have closed functionality.

5.1.3.7 Speech output for video information

Not Applicable

The product does not have closed functionality.

5.1.3.8 Masked entry

Not Applicable

The product does not have closed functionality.

5.1.3.9 Private access to personal data

Not Applicable

The product does not have closed functionality.

5.1.3.10 Non-interfering audio output

Not Applicable

The product does not have closed functionality.

5.1.3.11 Private listening volume

Not Applicable

The product does not have closed functionality.

5.1.3.12 Speaker volume

Not Applicable

The product does not have closed functionality.

5.1.3.13 Volume reset

Not Applicable

The product does not have closed functionality.

5.1.3.14 Spoken languages

Not Applicable

The product does not have closed functionality.

5.1.3.15 Non-visual error identification

Not Applicable

The product does not have closed functionality.

5.1.3.16 Receipts, tickets, and transactional outputs

Not Applicable

The product does not have closed functionality.

5.1.4 Functionality closed to text enlargement

Not Applicable

The product does not have closed functionality.

5.1.5 Visual output for auditory information

Not Applicable

The product does not have closed functionality.

5.1.6 Operation without keyboard interface

5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

See information in 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus

Not Applicable

The product does not have closed functionality.

5.2 Activation of accessibility features

Supports

The product does not have specific documented accessibility features.

5.3 Biometrics

Not Applicable

Biometrics is not included in the product.

5.4 Preservation of accessibility information during conversion

Not Applicable

The product does not convert content.

5.5 Operable parts

5.5.1 Means of operation

Not Applicable

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

5.5.2 Operable parts discernibility

Partially Supports

The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions are noted in 1.3.1 Info and Relationships, 2.4.6 Headings and Labels and 4.1.2 Name, Role, Value.

5.6 Locking or toggle controls

5.6.1 Tactile or auditory status

Not Applicable

Tactile or auditory status is not included in the product.

5.6.2 Visual status

Supports

Visual status of controls is discernible in the product.

5.7 Key repeat

Not Applicable

Key repeat functionality is not found in the product.

5.8 Double-strike key acceptance

Not Applicable

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

5.9 Simultaneous user actions

Not Applicable

The product does not require simultaneous user actions to achieve any functionality.

Chapter 6: ICT with Two-Way Voice Communication

Notes: Not Applicable

 

Chapter 7: ICT with Video Capabilities

Notes: Video is present on Data management - Schemas - Create your first schema - Video tutorial modal screen.

 

Criteria

Conformance Level

Remarks and Explanations

7.1.1 Captioning playback

Supports

The video player has a CC (closed captions) button that will add closed captions to the video display.

7.1.2 Captioning synchronization

Supports

The video player supports synchronized captions.

7.1.3 Preservation of captioning

Not Applicable

The product does not transmit, convert, or record video with synchronized audio.

7.1.4 Captions characteristics

Does Not Support

The video player has the ability to show closed captions, however the appearance of those closed captions cannot be modified by the user.

7.1.5 Spoken subtitles

Does Not Support

The video player supports language subtitles, however it does not have a function to speak those subtitles out loud.

7.2.1 Audio description playback

Does Not Support

The video player does not have an AD (audio description) button that will play an audio description track (when an audio description track is provided by the video content provider).

7.2.2 Audio description synchronization

Not Applicable

The product does not have a mechanism to play audio description.

7.2.3 Preservation of audio description

Not Applicable

The product does not transmit, convert, or record video.

7.3 User controls for captions and audio description

Partially Supports

The product provides a closed caption control but no audio description control.

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 on the Adobe Accessibility Compliance website.

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)