Adobe Accessibility Conformance Report
International Edition

(Based on VPAT® Version 2.4)

Product Information

Name of Product/Version: Adobe Connect - Host (Web) meeting client version 12.2

Report Date: February 2023

Product Description: HTML-client for participating in online virtual classrooms, webinars, and meetings.

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.0 Level AAA.

WCAG 2.1 Report

This section 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: 

  • Text alternative is missing in "Manage breakout session - Host View", "Video - Host View" screens.
  • ARIA progress bar does not have an accessible name in the “Polls Section - Host View” screen.
  • Text alternative does not serve the same purpose as image in “Meeting Room Header” 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

Web: The product does not provide its own pre-recorded audio-only or video-only media.

Meeting participants may share audio-only/video-only files during the meeting and provide the necessary alternative.

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 supports open and closed captioning for its recorded meetings. Users can assign a dedicated participant to type closed captioning or use a third party closed captioning provider.

The product does not provide its own prerecorded media that would require captions. Meeting participants may share pre-recorded content during a meeting and provide the necessary captioning.

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

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

Meeting participants may share prerecorded video during the meeting and provide the necessary audio description, downloadable transcript or other 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

Web: The product supports closed captioning for its meetings.

Meeting hosts can assign a dedicated participant to type closed captioning or use a third party closed captioning provider.

 

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

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

Meeting participants can provide audio description for video content or provide a downloadable transcript.

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 visual structure and relationship information is provided through element semantics or object information or are available in text.

Exceptions include:

  • Text should not be marked as a heading in the “Start Camera - Host View” screen.
  • Visual heading text is not marked as heading in "Host & Presenter Only Area - Host View", "Meeting Room Header", "Place Participants on Hold Modal - Host View", "Preferences Modal - Host View", "Raised Hands Section - Host View", "Start Recording - Host View" screens.
  • Content is not a list but is marked as such in the “Raised Hands Section - Host View” screen.
  • Visual list is not marked up as a list in the “Files - Host View” screen.
  • Form field is not labeled in "Shared PDF Content - Host View", "Polls Section - Host View", "Manage breakout session - Host View", and "Files - Host View" screens.
  • Visible label/form fields are not associated in the “Place Participants on Hold Modal - Host View” 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: 

  • aria-hidden="true" is used incorrectly in "Manage breakout session - Host View", "Preferences Modal - Host View" screens.
  • Hidden content is readable with a screen reader in the “Start Camera - Host View” screen.
  • Informative (Interactive) content is not readable by a screen reader in "Shared PDF Content - Host View", "Polls Section - Host View", "Manage breakout session - Host View", "Files - Host View", "Meeting Room Header", and "Manage breakout session - Host View" 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)

Web: Supports

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

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

Exceptions include: 

  • Identify input purpose not accurate in “Login” screen.

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 info in the “Layout Panel - Host view” screen.
  • Link contrast is not at least 3:1 with surrounding text in the “Entry Page” 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

Exception includes:

  • Text content lacks 4.5:1 contrast ratio in “Login”, "Entry Page", "Files - Host View", "Host & Presenter Only Area - Host View", "Manage breakout session - Host View", "Meeting Room Header", "Shared PDF Content - Host View", "Start Camera - Host View", "Video - Host View" screens.
  • Placeholder text lacks a 4.5:1 contrast ratio in the “Login” 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: 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 the "Meeting Room Header", "Preferences Modal - Host View" screens. 

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:

  • Some page content does not reflow to fit horizontally when the page width is changed to 320 CSS pixels in multiple screens across the application.
  • Some part of the page content overlaps when the page width is changed to 320 CSS pixels in the "Keyboard Shortcuts Modal", "Meeting Room Header", "Place Participants on Hold Modal - Host View", "Preferences Modal - Host View", "Raised Hands Section - Host View", "Start Recording - Host View" 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: Partially Supports

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

Exceptions include:

  • Active user interface component lacks a 3 to 1 contrast ratio in "Chat Section - Host View", "Login", "Start Recording - Host View" screens.
  • An icon lacks 3 to 1 contrast ratio in "Entry Page", "Notes section - Host view", "Chat Section - Host View", "Poll Section - Host view", "Files Section - Host View", "Manage breakout session - Host View" screens.
  • Graphical objects lack a 3 to 1 contrast ratio in the “Layout Panel - Host view” screen.
  • State of an active component lacks 3 to 1 contrast ratio in "Keyboard Shortcuts Modal", "Preferences Modal - Host View", "Shared PowerPoint - Host view" 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: Supports

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

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 "Chat Section - Host View", "Host & Presenter Only Area - Host View", "Manage breakout session - Host View", "Q&A - Host View", "Shared PowerPoint - Host view", "Video - Host View" screens.
  • Device-dependent event handlers are used in "Manage breakout session - Host View", "Preferences Modal - Host View" screens.

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: Most product functionality can be operated without a keyboard trap. 

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

Web: The product provides a mechanism to bypass blocks of content that are repeated on most pages.

Exceptions include:

  • Frames are missing an accessible name in the “Shared PowerPoint - Host view” screen.

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 title of a page describes its 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:

  • Keyboard focus order is not logical in “Shared PowerPoint - Host view” screen.
  • Modal is closed, focus is not returned to trigger in “Keyboard Shortcuts Modal” 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: Supports

Web: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. 

 

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.

Exceptions include:

  • Buttons have the same name but different actions in "Files - Host View", "Manage breakout session - Host View", "Polls Section - Host View" screens.
  • Label does not convey the purpose of control in the “Login” screen.
  • Programmatic label does not convey the purpose of control in "Entry Page", "Meeting Room Header", "Shared PDF Content - Host View", "Shared PowerPoint - Host view", "Start Camera - Host View" 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: Partially Supports

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

Exceptions include:

  • Focus indicator is missing in the “Preferences Modal - Host View” 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: Most of the accessible names of the controls contain the text of their visible labels. 

Exceptions include:

  • Accessible name does not contain a visible label in the “Meeting Room Header” component.

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 “Login” 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:

  • Instructions are inaccurate or incomplete for assistive technology users in the “Layout Panel - Host view” 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) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

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

Web: Partially Supports

Web: In most product functions, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and IDs are unique. 

Exceptions include:

  • Certain ARIA roles are not contained by particular parents in "Manage breakout session - Host View", "Preferences Modal - Host View" screens.
  • Certain ARIA roles do not contain particular children in the “Manage breakout session - Host View” screen.
  • Duplicate IDs are present in "Entry Page", "Video - Host View", "Files - Host View", "Meeting Room Header", "Manage breakout session - Host View", "Shared PowerPoint - Host view", "Shared PDF Content - Host View", "Polls Section - Host View" 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: Does not support

Web: User interface components in most product functions provide programmatic name, role, and state information. However, some controls do not provide name, role, and state information to assistive technology. 

Exceptions include:

  • ‘Mute all attendees’ menu item checkbox disabled state is not conveyed in “Manage breakout session - Host View” screen.
  • Button disabled state is not conveyed in "Manage breakout session - Host View", "Shared PDF Content - Host View" screens.
  • Button does not have a name in "Raised Hands Section - Host View", "Video - Host View" screens.
  • Button does not have a role in "Layout Panel - Host view", "Polls Section - Host View", "Manage breakout session - Host View", "Files - Host View", "Q&A - Host View", "Shared PowerPoint - Host view" screens.
  • Button is missing both a role and a name in "Manage breakout session - Host View", "Preferences Modal - Host View", "Q&A - Host View" screens.
  • Button pressed state is not conveyed in "Layout Panel - Host view", "Shared PDF Content - Host View", "Shared PowerPoint - Host view", "Video - Host View" screens.
  • Main room sub menu elements are missing required roles and attributes in “Manage breakout session - Host View” screen.
  • State: Expand/collapse state of the element is missing or incorrect in "Meeting Room Header", "Notes Section - Host View", "Chat Section - Host View", "Q&A - Host View", "Shared PDF Content - Host View" screens.
  • State: Selected state of the element is missing or incorrect in "Meeting Room Header", "Preferences Modal - Host View", "Q&A - Host View", "Shared PDF Content - Host View", "Shared PowerPoint - Host view", "Start Camera - Host View" screens.
  • The element functions as if it has two roles in the “Polls Section - Host View” screen.
  • Application: role="application" is used inappropriately in multiple screens across the application.
  • Combo-box is missing appropriate roles and attributes in "Entry Page", "Shared PowerPoint - Host view" screens.
  • Elements do not use allowed ARIA attributes in "Entry Page", "Login", "Notes Section - Host View", "Q&A - Host View" screens.
  • Invalid ARIA role value is used in “Files - Host View” screen.
  • States/Properties: Invalid ARIA attribute is used in "Place Participants on Hold Modal - Host View", "Start Recording - Host View" screens.
  • Tab widget is missing appropriate roles and attributes in “Shared PowerPoint - Host view” screen.
  • Tooltip content is not accessible to screen readers in the “Preferences Modal - Host View” screen.
  • Tab widget is missing appropriate roles and attributes in “Shared PowerPoint - Host view” screen.
  • Tooltip content is not accessible to screen readers in the “Preferences Modal - Host View” 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: When status messages do not receive focus, the product does not provide the dynamic update to the assistive technology.

Exceptions include:

  • Status message not automatically announced in “Manage breakout session - Host View” screen.

Table 2: Success Criteria, Level AAA

Notes: Not Applicable
 

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, some images are missing text alternatives, ARIA progress bar is missing an accessible name, and for some images the text alternative does not serve the same purpose as image.
  • As noted in 1.3.1 Info and Relationships, Text should not be marked as a heading, Visual heading text is not marked as heading, Content is not a list but is marked as such, Visual list is not marked up as list, Form field is not labeled and Visible label/form field are not associated.
  • As noted in 1.3.2 Meaningful Sequence, aria-hidden="true" is used incorrectly, Hidden content is readable with a screen reader, Informative (Interactive) content is not readable by a screen reader.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and Programmatic label does not convey purpose of control.
  • As noted in 3.3.1 Error Identification, Form field with error not identified.
  • As noted in 3.3.2 Labels or Instructions, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers

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, Text alternative is missing, ARIA progress bar does not have an accessible name, and Text alternative does not serve the same purpose as image.
  • As noted in 1.3.1 Info and Relationships, Text should not be marked as a heading, Visual heading text is not marked as heading, Content is not a list but is marked as such, Visual list is not marked up as list, Form field is not labeled and Visible label/form field are not associated.
  • As noted in 1.3.2 Meaningful Sequence, aria-hidden="true" is used incorrectly, Hidden content is readable with a screen reader, Informative (Interactive) 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), Text content lacks 4.5:1 contrast ratio, and Placeholder text 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%.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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.1 Error Identification, Form field with error not identified.
  • As noted in 3.3.2 Labels or Instructions, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.

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 info, 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, and Placeholder text lacks 4.5:1 contrast ratio.As noted in 3.3.1 Error Identification, Form field with error not identified on login screen.
  • As noted in 3.3.1 Error Identification, Form field with error not identified.

 

302.4 Without Hearing

Web: Supports

Web: Supports  Web: The product is functional for users without hearing.

302.5 With Limited Hearing

Web: Supports

Web: Supports  Web: The product is functional for users without 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, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.

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, Device-dependent event handlers are used.
  •  
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA

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, aria-hidden="true" is used incorrectly, Hidden content is readable with a screen reader, Informative (Interactive) content is not readable by a screen reader.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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.1 Error Identification, Form field with error not identified.
  • As noted in 3.3.2 Labels or Instructions, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.

Chapter 4: Hardware

Notes: Not Applicable
 

Chapter 5: Software

Notes:

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

EN 301 549 Report

Notes:

Chapter 4: Functional Performance Statements (FPS)

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, some images are missing text alternatives, ARIA progress bar is missing an accessible name, and for some images the text alternative does not serve the same purpose as image.
  • As noted in 1.3.1 Info and Relationships, Text should not be marked as a heading, Visual heading text is not marked as heading, Content is not a list but is marked as such, Visual list is not marked up as list, Form field is not labeled and Visible label/form field are not associated.
  • As noted in 1.3.2 Meaningful Sequence, aria-hidden="true" is used incorrectly, Hidden content is readable with a screen reader, Informative (Interactive) content is not readable by a screen reader.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and Programmatic label does not convey purpose of control.
  • As noted in 3.3.1 Error Identification, Form field with error not identified.
  • As noted in 3.3.2 Labels or Instructions, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.
  • As noted in 4.1.3 Status Messages, Status messages are 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, some images are missing text alternatives, ARIA progress bar is missing an accessible name, and for some images the text alternative does not serve the same purpose as image.
  • As noted in 1.3.1 Info and Relationships, Text should not be marked as a heading, Visual heading text is not marked as heading, Content is not a list but is marked as such, Visual list is not marked up as list, Form field is not labeled and Visible label/form field are not associated.
  • As noted in 1.3.2 Meaningful Sequence, aria-hidden="true" is used incorrectly, Hidden content is readable with a screen reader, Informative (Interactive) 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), Text content lacks 4.5:1 contrast ratio, and Placeholder text 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%.
  • As noted in 1.4.10 Reflow, some page content does not reflow to fit horizontally when the page width is changed to 320 CSS pixels.
  • 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 ratio, and State of active component lacks 3 to 1 contrast ratio.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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.1 Error Identification, Form field with error not identified.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.
  • As noted in 4.1.3 Status Messages, Status messages are not automatically announced.

4.2.3 Usage 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 info, 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, and Placeholder text 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 ratio, and State of active component lacks 3 to 1 contrast ratio.
  • As noted in 3.3.1 Error Identification, Form field with error not identified.

4.2.4 Usage without hearing

Web: Supports

Web: Supports  Web: The product is functional for users without hearing.

4.2.5 Usage with limited hearing

Web: Supports

Web: Supports  Web: The product is functional for users without hearing.

4.2.6 Usage with no or limited 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 1.3.5 Identify Input Purpose, Identify input purpose not accurate.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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 does not contain visible labels.
  • As noted in 3.3.2 Labels or Instructions, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.

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 1.3.5 Identify Input Purpose, Identify input purpose not accurate.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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 does not contain visible labels.
  • As noted in 3.3.2 Labels or Instructions, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.

 

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, aria-hidden="true" is used incorrectly, Hidden content is readable with a screen reader, Informative (Interactive) content is not readable by a screen reader.
  • As noted in 1.3.5 Identify Input Purpose, Identify input purpose not accurate.
  • As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Device-dependent event handlers are used.
  • As noted in 2.4.1 Bypass Blocks, Frames are missing an accessible name.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Focus is not returned to trigger when a modal is closed.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Label does not convey purpose of control, and 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.1 Error Identification, Form field with error not identified.
  • As noted in 3.3.2 Labels or Instructions, Instructions are inaccurate or incomplete for assistive technology users.
  • As noted in 4.1.1 Parsing, Certain ARIA roles are not contained by particular parents, Certain ARIA roles do not contain particular children, and Duplicate IDs are present.
  • As noted in 4.1.2 Name, Role, Value, Checkbox disabled state is not conveyed, Button disabled state is not conveyed, Button is missing both a role and a name, Button pressed state is not conveyed, sub-menu elements are missing required roles and attributes, Expand/collapse state of the element is missing or incorrect, Selected state of the element is missing or incorrect, element functions as if it has two roles, role="application" is used inappropriately, Combo-box is missing appropriate roles and attributes, Elements do not use allowed ARIA attributes, Invalid ARIA role value is used, Invalid ARIA attribute is used, Tab widget is missing appropriate roles and attributes, and Tooltip content is not accessible to screen readers.
  • As noted in 4.1.3 Status Messages, Status messages are 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

Not Applicable

The product does not have accessibility features requiring activation.

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

Chapter 7: ICT with Video Capabilities

Notes: 

Criteria

Conformance Level

Remarks and Explanations

7.1 Caption processing technology

Heading cell – no response required

Heading cell – no response required

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

Note: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Supports

The product allows users to enter closed captions for live meetings, and the shared videos can display captions.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.

Supports

When the product displays captions, synchronization is preserved between the captions and the corresponding audio.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

Supports

The product preserves captions in transmission and conversion, such as live captions in a meeting and captions in an exported recording. 

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

       Note 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

      Note 2: Subtitles that are bitmap images are examples of unmodifiable characters.

Supports

The product supports adapting the displayed characteristics of captions.

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

      NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end users device.

      NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

      NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

      NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

Does Not Support

The product does not support spoken subtitles.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

Note 1: In such cases, the video content can include the audio description as one of the available audio tracks.

Note 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

Supports

The product provides audio tracks option for users to select and play audio description tracks.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

Supports

Audio description can be provided in a manner that is synchronized with the video content.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Supports

The product preserves available audio description data.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

Note 1: Primary media controls are the set of controls that the user most commonly uses to control media.

Note 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

Note 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Partially Supports

The product provides user controls for captions and audio descriptions for prerecorded meeting but not for shared media.

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