Adobe Accessibility Conformance Report
International Edition
(Based on VPAT® Version 2.4)
Product Information
Name of Product/Version: Adobe Connect – (Mac OS) Version 2022.10.42
Report Date: February 2023
Product Description: Application 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 |
|---|---|
|
Level A: Yes |
|
|
Level A (Yes) Level AA (Yes) Level AAA (No) |
|
|
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.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)
Revised Section 508
|
Software: Partially Supports |
Software: The product provides sufficient text alternatives for most instances of active and informative images. 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
|
Software: Supports |
Software: 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)
Revised Section 508
|
Software: Supports |
Software: 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)
Revised Section 508
|
Software: Supports |
Software: 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)
Revised Section 508
|
Software: Supports |
Software: 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)
Revised Section 508
|
Software: Supports |
Software: 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)
Revised Section 508
|
Software: Partially Supports |
Software: Visual structure and relationship information is provided through object information or in text. |
|
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Software: Partially Supports |
Software: Visual structure and relationship information is provided through object information or in text. Exception includes:
|
|
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Software: Supports |
Software: Instructions do not rely solely on sensory characteristics. |
|
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports |
Software: 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 |
Software: Supports (Not Applicable) |
Software: The product does not contain input fields that collect information about the user. |
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
1.4.1 Use of Color (Level A)
Revised Section 508
|
Software: Supports |
Software: All functions of the product do not convey information through color alone. |
|
1.4.2 Audio Control (Level A)
Revised Section 508
|
Software: Supports (Not Applicable) |
Software: The product does not contain audio that plays automatically. |
|
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Software: Does not Support |
Software: Most text meets minimum contrast requirements. Exception includes:
|
|
1.4.4 Resize text (Level AA)
Revised Section 508
|
Software: Partially Supports |
Software: The product allows operating system display scaling to resize text up to 200 percent without loss of content or functionality. |
|
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Software: Supports |
Software: 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)
Revised Section 508 – Does not apply |
Software: Supports |
Software: At the required width of 320 CSS pixels, All content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. |
|
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports |
Software: Most meaningful non-text content elements have sufficient contrast requirements. Exceptions include:
|
|
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports (Not Applicable) |
Software: All functions of the product support 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 |
Software: Supports |
Software: 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
|
Software: Partially Supports |
Software: Most product functionality can be operated through a keyboard interface. Exceptions include:
|
|
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Software: Supports |
Software: The product does not include keyboard traps. |
|
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports (Not Applicable) |
Software: 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
|
Software: Supports (Not Applicable) |
Software: The product does not include time limits. |
|
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Software: Supports (Not Applicable) |
Software: 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
|
Software: Supports (Not Applicable) |
Software: 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
|
Software: Supports (Not Applicable) |
Software: This criterion does not apply to non-web software. |
|
2.4.2 Page Titled (Level A)
Revised Section 508
|
Software: Supports |
Software: The titles of pages describe their purpose. |
|
2.4.3 Focus Order (Level A)
Revised Section 508
|
Software: Supports |
Software: Components receive focus in a meaningful order. |
|
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Software: Supports |
Software: 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
|
Software: Supports (Not Applicable) |
Software: This criterion does not apply to non-web software. |
|
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Software: Does not Support |
Software: Some labels are descriptive. Exceptions include:
|
|
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Software: Supports |
Software: All focusable elements have a visible keyboard focus indicator. |
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 |
Software: Supports (Not Applicable) |
Software: 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 |
Software: Supports |
Software: 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 |
Software: Supports |
Software: The accessible names of controls contain the text of their visible labels. |
|
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports (Not Applicable) |
Software: 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
|
Software: Supports |
Software: The language is programmatically determinable within the product. |
|
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Software: Supports (Not Applicable) |
Software: 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
|
Software: Supports |
Software: Components do not initiate a change of context when focused. |
|
3.2.2 On Input (Level A)
Revised Section 508
|
Software: Supports |
Software: Changes of context do not occur automatically on user input. |
|
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Software: Supports (Not Applicable) |
Software: This criterion does not apply to non-web software. |
|
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Software: Supports (Not Applicable) |
Software: This criterion does not apply to non-web software. |
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
|
Software: Supports |
Software: All input errors are identified and described to the users in text. |
|
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Software: Supports |
Software: Labels are provided for input fields. |
|
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Software: Supports |
Software: Where input errors are automatically detected, suggestions for correction are provided to the user. |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Software: Supports (Not Applicable) |
Software: 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)
Revised Section 508
|
Software: Supports (Not Applicable) |
Software: The product is not implemented using markup languages. |
|
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Software: Does Not Support |
Software: User interface components in some product functions provide programmatic name, role, and/or state information. Exceptions include:
|
|
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports |
Software: When status messages do not receive focus, in most cases the product does provide the dynamic and automatic update to the assistive technology. Exception includes:
|
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 |
Software: Partially Supports |
Software: Most functions of the product are usable without vision. Exceptions include:
|
|
302.2 With Limited Vision |
Software: Partially Supports |
Software: Most functions of the product are usable with limited vision. Exceptions include:
|
|
302.3 Without Perception of Color |
Software: Partially Supports |
Software: Most functions of the product are usable without perception of color. Exceptions include:
|
|
302.4 Without Hearing |
Software: Supports |
Software: The product is functional for users without hearing. |
|
302.5 With Limited Hearing |
Software: Supports |
Software: The product is functional for users without hearing. |
|
302.6 Without Speech |
Software: Supports (Not Applicable) |
Software: The product does not require the use of speech. |
|
302.7 With Limited Manipulation |
Software: Partially Supports |
Software: Users with limited manipulation who use speech recognition or switch control software will not have difficulty navigating to most controls. Exceptions include:
|
|
302.8 With Limited Reach and Strength |
Software: Partially Supports |
Software: Users with limited reach and strength will not have difficulty navigating most of the controls. Exceptions include:
|
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Partially Supports |
Software: The product is mostly 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:
|
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
501.1 Scope – Incorporation of WCAG 2.0 AA The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines. EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0. |
See WCAG 2.x section |
See information in WCAG 2.x section |
|
Heading cell – no response required |
Heading cell – no response required |
|
|
502.2.1 User Control of Accessibility Features Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features. |
Not Applicable |
The product is not platform software. |
|
502.2.2 No Disruption of Accessibility Features Software shall not disrupt platform features that are defined in the platform documentation as accessibility features. |
Supports |
The product does not disrupt platform accessibility features. |
|
502.3 Accessibility Services Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services. |
Heading cell – no response required |
Heading cell – no response required |
|
502.3.1 Object Information The object role, state(s), properties, boundary, name, and description shall be programmatically determinable. |
Does Not Support |
As noted in 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value, most objects in the product do not expose name, role, or state and descriptive labels to assistive technology. |
|
502.3.2 Modification of Object Information States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology. |
Does Not Support |
The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions are noted in 4.1.2 Name, Role, Value. |
|
502.3.3 Row, Column, and Headers If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable. |
Not Applicable |
The product does not use data tables. |
|
502.3.4 Values Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable. |
Supports |
The product exposes the values of input controls to assistive technology. |
|
502.3.5 Modification of Values Values that can be set by the user shall be capable of being set programmatically, including through assistive technology. |
Supports |
The product allows assistive technology to modify the values of input controls. |
|
502.3.6 Label Relationships Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable. |
Supports |
The product UI exposes label relationships to assistive technologies. |
|
502.3.7 Hierarchical Relationships Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable. |
Does Not Support |
The product does not expose hierarchical relationships to assistive technology, as noted in 4.1.2 Name, Role, Value. |
|
502.3.8 Text The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable. |
Partially Supports |
Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions are noted in 1.3.2 Meaningful Sequence. |
|
502.3.9 Modification of Text Text that can be set by the user shall be capable of being set programmatically, including through assistive technology. |
Supports |
The product allows users to modify the text of input controls. |
|
502.3.10 List of Actions A list of all actions that can be executed on an object shall be programmatically determinable. |
Does Not Support |
Most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology as noted in 4.1.2 Name, Role, Value. |
|
502.3.11 Actions on Objects Applications shall allow assistive technology to programmatically execute available actions on objects. |
Does Not Support |
As noted in 2.1.1 Keyboard, the product does not allow assistive technology to perform most actions on objects. |
|
502.3.12 Focus Cursor Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components. |
Supports |
The product exposes focus, text insertion point, and text selection to assistive technology. |
|
502.3.13 Modification of Focus Cursor Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology. |
Supports |
The product allows assistive technology to move focus and modify text selection ranges. |
|
502.3.14 Event Notification Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology. |
Does Not Support |
The product does not notify assistive technology of most user interaction events as noted in 4.1.2 Name, Role, Value. |
|
502.4 Platform Accessibility Features Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) listed below: A. Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes; B. Section 9.3.4 Provide adjustment of delay before key acceptance; C. Section 9.3.5 Provide adjustment of same-key double-strike acceptance; D. Section 10.6.7 Allow users to choose visual alternative for audio output; E. Section 10.6.8 Synchronize audio equivalents for visual events; F. Section 10.6.9 Provide speech output services; and G . Section 10.7.1 Display any captions provided. |
Not Applicable |
The product is not platform software |
|
|
Heading cell – no response required |
Heading cell – no response required |
|
503.2 User Preferences Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor. EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2. |
Supports |
|
|
503.3 Alternative User Interfaces Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services. |
Not Applicable |
The product does not provide an alternative user interface that functions as assistive technology. |
|
503.4 User Controls for Captions and Audio Description Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4. |
Heading cell – no response required |
Heading cell – no response required |
|
503.4.1 Caption Controls Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection. |
Partially Supports |
The product provides user controls for captions for prerecorded meeting but not for shared media. |
|
503.4.2 Audio Description Controls Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection. |
Partially Supports |
The product provides user controls for audio description for prerecorded meeting but not for shared media. |
|
504.1 General Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format. |
Heading cell – no response required |
Heading cell – no response required |
|
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility. EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code. |
Not Applicable |
The product is not an authoring tool. |
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format. |
Not Applicable |
The product does not convert content. |
|
504.2.2 PDF Export Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1). |
Not Applicable |
The product does not export PDF files. |
|
504.3 Prompts Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for supported features and, as applicable, to file formats supported by the authoring tool. |
Not Applicable |
The product is not an authoring tool. |
|
504.4 Templates Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool. |
Not Applicable |
The product is not an authoring tool. |
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)
Notes:
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
4.2.1 Usage without vision |
Software: Partially Supports |
Software: Most functions of the product are usable without vision. Exceptions include:
|
|
4.2.2 Usage with limited vision |
Software: Partially Supports |
Software: Most functions of the product are usable with limited vision. Exceptions include:
|
|
4.2.3 Usage without perception of color |
Software: Partially Supports |
Software: Most functions of the product are usable without perception of color. Exceptions include:
|
|
4.2.4 Usage without hearing |
Software: Supports |
Software: The product is functional for users without hearing. |
|
4.2.5 Usage with limited hearing |
Software: Supports |
Software: The product is functional for users without hearing. |
|
4.2.6 Usage with no or limited vocal capability |
Software: Supports (Not Applicable) |
Software: The product does not require the use of speech. |
|
4.2.7 Usage with limited manipulation or strength |
Software: Partially Supports |
Software: Users with limited manipulation or strength who use speech recognition or switch control software will have difficulty navigating to controls. Examples include:
|
|
4.2.8 Usage with limited reach |
Software: Partially Supports |
Software: Users with limited reach will not have difficulty navigating to most of the controls. Exceptions include:
|
|
4.2.9 Minimize photosensitive seizure triggers |
Software: Supports (Not Applicable) |
Software: The product does not contain flashing content or media. |
|
4.2.10 Usage with limited cognition, language or learning |
Software: Partially Supports |
Software: 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:
|
|
4.2.11 Privacy |
Software: Supports (Not Applicable) |
Software: 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. As noted in 4.1.2 Name, Role, Value, most operable elements provide an accessible name. |
|
5.6 Locking or toggle controls |
|
|
|
5.6.1 Tactile or auditory status |
Not Applicable |
Tactile or auditory status is not included in the product. |
|
5.6.2 Visual status |
Supports |
Visual status of controls is discernible in the product. |
|
5.7 Key repeat |
Not Applicable |
Key repeat functionality is not found in the product. |
|
5.8 Double-strike key acceptance |
Not Applicable |
Double -strike key acceptance is not found in the product. |
|
5.9 Simultaneous user actions |
Not Applicable |
The product does not require simultaneous user actions to achieve any functionality. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
|
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 video. |
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.1 section)
Notes: Not Applicable
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
11.0 General (informative) |
Heading cell – no response required |
Heading cell – no response required |
|
11.5 Interoperability with assistive technology |
Heading cell – no response required |
Heading cell – no response required |
|
11.5.1 Closed functionality Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.5.2 to clause 11.5.2.17. |
Heading cell – no response required |
Heading cell – no response required |
|
11.5.2 Accessibility services |
Heading cell – no response required |
Heading cell – no response required |
|
11.5.2.1 Platform accessibility service support for software that provides a user interface Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology. Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste. |
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.2 Platform accessibility service support for assistive technologies |
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.3 Use of accessibility services Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology. Note: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2. It is best practice to develop software using toolkits that automatically implement the underlying platform accessibility services. |
Not Applicable |
The product is not platform software. |
|
11.5.2.4 Assistive technology Where the ICT is assistive technology it shall use the documented platform accessibility services. Note 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2. Note 2: Assistive technology can also use other documented accessibility services. |
Not Applicable |
This product is not assistive technology. |
|
11.5.2.5 Object information Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies. |
Does Not Support |
As noted in 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value, most objects in the product do not expose name, role, or state and descriptive labels to assistive technology. |
|
11.5.2.6 Row, column, and headers Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies. |
Not Applicable |
The product does not use data tables. |
|
11.5.2.7 Values Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies. |
Supports |
The product exposes the values of input controls to assistive technology. |
|
11.5.2.8 Label relationships Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies. |
Supports |
The product UI exposes label relationships to assistive technologies. |
|
11.5.2.9 Parent-child relationships Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies. |
Does Not Support |
The product does not expose hierarchical relationships to assistive technology, as noted in 4.1.2 Name, Role, Value. |
|
11.5.2.10 Text Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies. |
Partially Supports |
Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions are noted in 1.3.2 Meaningful Sequence. |
|
11.5.2.11 List of available actions Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies. |
Does Not Support |
Most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology as noted in 4.1.2 Name, Role, Value. |
|
11.5.2.12 Execution of available actions Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies. Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces. Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform. |
Does Not Support |
As noted in 2.1.1 Keyboard, the product does not allow assistive technology to perform most actions on objects. |
|
11.5.2.13 Tracking of focus and selection attributes Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies. |
Supports |
The product exposes focus, text insertion point, and text selection to assistive technology. |
|
11.5.2.14 Modification of focus and selection attributes Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items. Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces. Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform. |
Supports |
The product allows assistive technology to move focus and modify text selection ranges. |
|
11.5.2.15 Change notification Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13. |
Does Not Support |
The product does not notify assistive technology of most user interaction events as noted in 4.1.2 Name, Role, Value and in 4.1.3 Status Messages. |
|
11.5.2.16 Modifications of states and properties Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items. Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces. Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform. |
Partially Supports |
The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions are noted in 2.1.1 Keyboard. |
|
11.5.2.17 Modifications of values and text Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology. Note 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces. Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform. |
Supports |
The product allows assistive technology to modify the text and values of input controls. |
|
11.6 Documented accessibility usage |
Heading cell – no response required |
Heading cell – no response required |
|
11.6.1 User control of accessibility features Where software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users. |
Not Applicable |
The product is not platform software. |
|
11.6.2 No disruption of accessibility features Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software. |
Supports |
The product does not disrupt platform accessibility features. |
|
11.7 User preferences Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms. |
Supports |
The product adapts to platform settings. |
|
11.8 Authoring tools |
Heading cell – no response required |
Heading cell – no response required |
|
11.8.1 Content technology |
Heading cell – no response required |
Heading cell – no response required |
|
11.8.2 Accessible content creation (if not authoring tool, enter “not applicable”) Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable. Note: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool. |
See WCAG 2.x section |
See information in WCAG 2.x section |
|
11.8.3 Preservation of accessibility information in transformations If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output. Note 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages). Note 2: Re-coding transformations are transformations in which the technology used to encode the content is changed. |
Not Applicable |
This product is not an authoring tool. |
|
11.8.4 Repair assistance If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s). |
Not Applicable |
This product is not an authoring tool. |
|
11.8.5 Templates When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (Non-web documents) as applicable shall be available and identified as such. |
Not Applicable |
This 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.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable