Adobe Accessibility Conformance Report
(Based on VPAT® Version 2.4)
Product Information
Name of Product/Version: Adobe Connect Web Meeting Client Version 11.2
Product Description: HTML-client for participating in online virtual classrooms, webinars, and meetings.
Date: March 2021
Contact information: access@adobe.com
Notes: The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
Evaluation Methods Used: Testing Adobe Connect involved extensive use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well exclusive 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 |
Level A: Yes |
|
Level A: Yes |
|
Yes |
|
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.x 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.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 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)
Revised Section 508
|
Web: Partially Supports |
Web: The product provides sufficient text alternatives for most instances of non-text content, such as images and image buttons. Exceptions include:
|
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)
Revised Section 508
|
Web: Supports |
Web: The product does not provide its own prerecorded audio-only or video-only media. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: The product does not provide its own prerecorded media that require captions. Hosts can provide open or closed captions in prerecorded video clips. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not contain prerecorded video content that would require audio description or a media alternative. Hosts can provide a downloadable transcript for a shared prerecorded video clip. |
1.2.4 Captions (Live) (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product contains audio content of the live meetings and the product allows users to enter real-time closed captions or to connect to a professional captioning service. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product does not contain prerecorded video content that would require audio description or a media alternative. Attendees can provide user-selectable audio descriptions 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)
Revised Section 508
|
Web: Partially Supports |
Web: Some structure and relationship information, such as some labels for form fields, is provided through element semantics. However, most structure and relationship information is not provided programmatically or in text, such as:
|
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Web: Supports |
Web: The product presents content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Web: Supports |
Web: Instructions do not rely solely on sensory characteristics. |
1.3.4 Orientation (Level AA 2.1 only)
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)
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. Examples include:
|
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)
Revised Section 508
|
Web: Partially Supports |
Web: Most functions of the product do not convey information through color alone. Exceptions include:
|
1.4.2 Audio Control (Level A)
Revised Section 508
|
Web: Supports |
Web: The product allows participants to mute meeting room audio. |
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most text meets minimum contrast requirements. Exceptions include:
|
1.4.4 Resize text (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product allows browser zoom to resize text up to 200 percent without loss of content or functionality. |
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product uses text instead of images of text. |
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Does Not Support |
Web: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. Loss of information or functionality occurs and content which does not require two-dimensional layout for meaning relies on scrolling in two dimensions. Examples include:
|
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Partially Supports |
Web: Most meaningful non-text content elements, such as buttons in the top navigation area, have sufficient contrast. Exceptions include:
|
1.4.12 Text Spacing (Level AA 2.1 only)
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)
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)
Revised Section 508
|
Web: Partially Supports |
Web: Most product functionality can be operated through a keyboard interface. Exceptions include:
|
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not include keyboard traps for most of its content. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
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)
Revised Section 508
|
Web: Supports |
Web: The product does not include time limits. |
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Web: Supports |
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)
Revised Section 508
|
Web: Supports |
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)
Revised Section 508
|
Web: Supports |
Web: The product is a single-page web application that does not contain repeated content and therefore, does not require a mechanism to bypass repeated content. The product also includes keyboard mechanisms to move to different areas of the application quickly. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Web: Supports |
Web: The titles of pages describe their purpose. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Web: Supports |
Web: Components receive focus in a meaningful order. |
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
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)
Revised Section 508
|
Web: Supports |
Web: This criterion does not apply as the product is a single-page application. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most headings and labels are descriptive. Exception includes:
|
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Web: Supports |
Web: The keyboard focus indicator is visible by default. |
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)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product does not rely on multipoint or path-based gestures. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
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)
Revised Section 508 – Does not apply |
Web: Partially Supports |
Web: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include:
|
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
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)
Revised Section 508
|
Web: Supports |
Web: The language is programmatically determinable within the product. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Web: Supports |
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)
Revised Section 508
|
Web: Supports |
Web: Components do not initiate a change of context when focused. |
3.2.2 On Input (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Changes of context do not occur automatically on user input, with the following exception:
|
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product does not contain a navigational mechanism that is repeated on multiple web pages. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product is a single-page web application. It does not contain functional components that appear repeatedly within a set of web pages. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A)
Revised Section 508
|
Web: Supports |
Web: Where input errors are automatically detected, such as an incorrect username and password combination, items in error are identified and error messages are provided as text. |
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Web: Supports |
Web: Labels are provided for input fields. |
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Web: Supports |
Web: Where input errors are automatically detected, such as an incorrect username and password combination, suggestions for correction, are provided to the user. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product does not process legal commitments. Where user-controllable data is modified, user input is checked for input errors and the user is provided an opportunity to correct them. |
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)
Revised Section 508
|
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 any IDs are unique. Exceptions include:
|
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Most form controls have proper name and role information. However, user interface components in some product functions do not provide programmatic name, role, state, or value information. Examples include:
|
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Partially Supports |
Web: In most cases, when a status message does not receive focus, the product provides the update to assistive technology as a live region. Exceptions include:
|
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
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:
|
302.2 With Limited Vision |
Web: Partially Supports |
Web: Most functions of the product are usable with limited vision. Exceptions include:
|
302.3 Without Perception of Color |
Web: Partially Supports |
Web: Most functions of the product are usable without perception of color. Exceptions include:
|
302.4 Without Hearing |
Web: Supports |
Web: The product is functional for users without hearing. |
302.5 With Limited Hearing |
Web: Supports |
Web: The product is functional for users with limited hearing. |
302.6 Without Speech |
Web: Supports |
Software: The product is functional without speech. |
302.7 With Limited Manipulation |
Web: Partially Supports |
Web: Most functions of the product are usable with limited manipulation or strength. Exceptions include:
|
302.8 With Limited Reach and Strength |
Web: Supports |
Web: The product is functional with limited reach. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Web: Supports |
Web: The product is functional for users with limited language, cognitive, and learning abilities. |
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: 4.2 Functional Performance Statements (FPS)
Notes: According to C.4 Functional Performance, this section is informative only.
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:
|
4.2.2 Usage with limited vision |
Web: Partially Supports |
Web: Most functions of the product are usable with limited vision. Exceptions include:
|
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:
|
4.2.4 Usage without hearing |
Web: Partially Supports |
Web: The product is functional for users without hearing for the most part. Exceptions include:
|
4.2.5 Usage with limited hearing |
Web: Partially Supports |
Web: The product is functional for users with limited hearing for the most part. Exceptions include:
|
4.2.6 Usage without vocal capability |
Web: Supports |
Web: The product does not require the use of speech. |
4.2.7 Usage with limited manipulation or strength |
Web: Partially Supports |
Web: Most functions of the product are usable with limited manipulation or strength. Exceptions include:
|
4.2.8 Usage with limited reach |
Web: Supports |
Web: The product is functional with limited reach. |
4.2.9 Minimize photosensitive seizure triggers |
Web: Supports |
Web: The product does not contain flashing content. |
4.2.10 Usage with limited cognition, language or learning |
Web: Supports |
Web: The product is functional for users with limited language, cognitive, and learning abilities. |
4.2.11 Privacy |
Web: Supports |
Web: The product maintains user privacy when accessibility features are used. Examples include:
|
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed Functionality |
Not Applicable |
5.1.2.2-5.1.7 are not applicable for this product, which has no closed functionality. |
5.2 Activation of accessibility features |
Not Applicable |
The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features. |
5.3 Biometrics |
Not Applicable |
The product does not use biological characteristics for user identification or for control of the product. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
The product does not convert content. |
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 include:
|
5.6.1 Tactile or auditory status |
Not Applicable |
The product does not have locking or toggle controls. |
5.6.2 Visual status |
Not Applicable |
The product does not have locking or toggle controls. |
5.7 Key repeat |
Not Applicable |
The product relies on platform software to turn off or adjust key repeat. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not provide a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
The product relies on platform software features, such as Sticky Keys, to ensure simultaneous user actions are not required. |
Chapter 6: ICT with Two-Way Voice Communication
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
6.1 Audio bandwidth for speech |
Supports |
The product is able to encode and decode two-way voice communication in a frequency range with an upper limit of at least 7000 Hz. |
6.2.1.1 RTT communication |
Partially Supports |
The product supports text chat, transmitting characters after the Send button is activated. However, the product does not provide real-time text (RTT) functionality, such as TTY or RFC 4103. |
6.2.1.2 Concurrent voice and text |
Not Applicable |
While the product supports concurrent text chat and two-way voice communication, the product does not provide real-time text (RTT) functionality, such as TTY or RFC 4103. |
6.2.2.1 Visually distinguishable display |
Not Applicable |
The product does not provide RTT functionality, such as TTY or RFC 4103. |
6.2.2.2 Programmatically determinable send and receive direction |
Not Applicable |
The product does not provide RTT functionality, such as TTY or RFC 4103. |
6.2.2.3 Speaker identification |
Not Applicable |
The product does not provide RTT functionality, such as TTY or RFC 4103. |
6.2.2.4 Visual indicator of Audio with RTT |
Not Applicable |
The product does not provide RTT functionality, such as TTY or RFC 4103. |
6.2.3 Interoperability |
Not Applicable |
The product does not provide RTT functionality, such as TTY or RFC 4103. |
6.2.4 Real-time text responsiveness |
Not Applicable |
The product does not provide RTT functionality, such as TTY or RFC 4103. |
6.3 Caller ID |
Not Applicable |
The product does not provide caller identification or similar telecommunications functions. |
6.4 Alternatives to voice-based services |
Not Applicable |
The product does not provide voice mail, auto-attendant, or interactive voice response functions. |
6.5.2 Resolution |
Supports |
The product allows presentation of video pods with resolution of QCIF (176 by 144), full CIF (352 by 288), or higher. |
6.5.3 Frame rate |
Supports |
When users communicate through a typical broadband network, the video communication frame rate is at least 12 frames per second. |
6.5.4 Synchronization between audio and video |
Does Not Support |
When users communicate through a typical broadband network, the time difference between speech and video is greater than 100 milliseconds. |
6.5.5 Visual indicator of audio with video |
Supports |
When users speak, there is a visual indicator of audio activity. |
6.5.6 Speaker identification with video (sign language) communication |
Does Not Support |
The product does not allow speaker identification for realtime signing and sign language users. |
Chapter 7: ICT with Video Capabilities
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
7.1.1 Captioning playback |
Partially Supports |
The product allows users to enter closed captions for live meetings, but the shared videos do not display closed captions. |
7.1.2 Captioning synchronization |
Supports |
The product preserves synchronization when displaying captions. |
7.1.3 Preservation of captioning |
Supports |
The product preserves most captions in transmission and conversion, such as live captions in a meeting and captions in an exported recording. |
7.1.4 Captions characteristics |
Partially Supports |
The product does not provide a way for the user to adapt the displayed characteristics of captions for prerecorded video. |
7.1.5 Spoken subtitles |
Does Not Support |
The product does not provide spoken subtitles. |
7.2.1 Audio description playback |
Supports |
The product does allow audio description tracks. |
7.2.2 Audio description synchronization |
Supports |
Audio description can be provided in a manner that is synchronized with the video content. |
7.2.3 Preservation of audio description |
Supports |
The product does preserve audio description tracks when prerecorded video clips are transmitted in a meeting. |
7.3 User controls for captions and audio description |
Supports |
The product does provide user controls for captions and audio description. |
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: See WCAG 2.x section
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.1.1.1 through 11.4.1.3 |
See WCAG 2.x section |
See information in WCAG 2.x section |
11.5.2.3 Use of accessibility services |
See 11.5.2.5 through 11.5.2.17. |
See information in 11.5.2.5 through 11.5.2.17 |
11.5.2.4 Assistive technology |
Not Applicable |
Not applicable to web |
11.5.2.5 Object information |
Not Applicable |
Not applicable to web |
11.5.2.6 Row, column, and headers |
Not Applicable |
Not applicable to web |
11.5.2.7 Values |
Not Applicable |
Not applicable to web |
11.5.2.8 Label relationships |
Not Applicable |
Not applicable to web |
11.5.2.9 Parent-child relationships |
Not Applicable |
Not applicable to web |
11.5.2.10 Text |
Not Applicable |
Not applicable to web |
11.5.2.11 List of available actions |
Not Applicable |
Not applicable to web |
11.5.2.12 Execution of available actions |
Not Applicable |
Not applicable to web |
11.5.2.13 Tracking of focus and selection attributes |
Not Applicable |
Not applicable to web |
11.5.2.14 Modification of focus and selection attributes |
Not Applicable |
Not applicable to web |
11.5.2.15 Change notification |
Not Applicable |
Not applicable to web |
11.5.2.16 Modifications of states and properties |
Not Applicable |
Not applicable to web |
11.5.2.17 Modifications of values and text |
Not Applicable |
Not applicable to web |
11.6.1 User control of accessibility features |
Not Applicable |
The product is not platform software. |
11.6.2 No disruption of accessibility features |
Supports |
The product does not disrupt platform accessibility features. |
11.7 User preferences |
Not Applicable |
Web pages are isolated from their underlying platform. |
11.8 Authoring tools |
Not Applicable |
The product is not an authoring tool. |
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)