Adobe Connect Windows Application - Host
Accessibility Conformance Report published by Adobe
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 32 criteria
- Supports
- 22
- Partially supports
- 3
- Does not support
- 0
- Not applicable
- 7
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 13
- Partially supports
- 3
- Does not support
- 1
- Not applicable
- 7
- Not evaluated
- 0
Source: View the original report published by Adobe.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (115)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | Software: The product provides sufficient text alternatives for instances of active and informative images. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Software: The product does not contain 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) | A | Not Applicable | Software: The product does not contain pre-recorded synchronized media. Meeting participants may share pre-recorded content during a meeting and provide the necessary captioning. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Software: The product does not contain pre-recorded 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.3.1 | Info and Relationships | A | Partially Supports | Software: Most visual structure and relationship information is provided through element semantics or object information or are available in text. Exceptions include: Some checkboxes are not programmatically grouped in Screen Sharing dialog. |
| 1.3.2 | Meaningful Sequence | A | Supports | Software: The product presents content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Supports | Software: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | Supports | Software: The product does not convey information through color alone. |
| 1.4.2 | Audio Control | A | Supports | Software: Audio content can be controlled by the user. |
| 2.1.1 | Keyboard | A | Partially Supports | Software: Most product functionality can be operated through alternative input methods or keyboard interface. Exceptions include: Some functions in the Screen Sharing Mini Control Panel are not keyboard accessible. |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Software: The product provides character key shortcuts. The single character key shortcut is active when the relevant user interface component is in focus. |
| 2.2.1 | Timing Adjustable | A | Supports | Software: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | Software: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Software: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.2 | Page Titled | A | Supports | Software: The title of the software describes its purpose. |
| 2.4.3 | Focus Order | A | Supports | Software: Components receive focus in a meaningful order. |
| 2.4.4 | Link Purpose (In Context) | A | 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.5.1 | Pointer Gestures | A | Supports | Software: All functionality that can be operated with a pointer can be operated with single-point actions. |
| 2.5.2 | Pointer Cancellation | A | Supports | Software: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click. |
| 2.5.3 | Label in Name | A | Supports | Software: Accessible names of controls contain the text of their visible labels. |
| 2.5.4 | Motion Actuation | A | Supports | Software: Functionality that can be triggered by device motion or user motion detected by a device can be disabled, and the functionality can be operated without using motion. |
| 3.1.1 | Language of Page | A | Supports | Software: The product relies on the features of the underlying operating system to set and indicate the language of the user interface. |
| 3.2.1 | On Focus | A | Supports | Software: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Software: Changes of context do not occur automatically on user input. |
| 3.2.6 | Consistent Help | A | Supports | Software: Applications that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order. |
| 3.3.1 | Error Identification | A | Supports | Software: Where input errors are automatically detected, items in error are identified and error messages are provided as text. |
| 3.3.2 | Labels or Instructions | A | Supports | Software: Labels are provided for input fields. |
| 3.3.7 | Redundant Entry | A | Supports | Software: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security. |
| 4.1.1 | Parsing | A | Not Applicable | Software: The product is not implemented using markup languages. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Software: User interface components in most product functions provide programmatic name, role, state, or value information. Exceptions include: The Screen Share Mini Control Panel is not compatible with assistive technologies. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Software: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Software: The product does not contain prerecorded video content that would require audio description. |
| 1.3.4 | Orientation | AA | Supports | Software: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Not Applicable | Software: The product’s technology does not have support for programmatic identification of input purpose. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Software: Most text meets minimum contrast requirements. Exceptions include: Some text has insufficient color contrast in the Start sharing dialog |
| 1.4.4 | Resize text | AA | 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 | AA | Supports | Software: The product uses text instead of images of text, except for branding elements that are considered essential. |
| 1.4.10 | Reflow | AA | Does Not Support | Software: At 320 CSS pixels, most product functions lose content or functionality or require two-dimensional scrolling. Examples include: Some content or functionality becomes unavailable at 320 CSS pixels in the Room Menu. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Software: The product has meaningful non-text content elements, such as most meaningful graphics and user interface components, with sufficient contrast. Exceptions include: The volume slider track has insufficient color contrast on the room entry screen. A focus indicator has insufficient color contrast in the login screen. |
| 1.4.12 | Text Spacing | AA | Not Applicable | Software: The product is not implemented using markup languages. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Software: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion. |
| 2.4.5 | Multiple Ways | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Software: Most headings and labels for form and interactive controls are informative. Exceptions include: Some controls on the application home screen have duplicate or unclear programmatic labels. |
| 2.4.7 | Focus Visible | AA | Supports | Software: The keyboard focus indicator is visible by default. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | Software: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. |
| 2.5.7 | Dragging Movements | AA | Supports | Software: All functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | Software: The size of the target for each clickable control is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. |
| 3.1.2 | Language of Parts | AA | Supports | Software: Changes of language for passages or phrases can be programmatically determined. |
| 3.2.3 | Consistent Navigation | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 3.2.4 | Consistent Identification | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 3.3.3 | Error Suggestion | AA | Supports | Software: Where input errors are automatically detected, suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Software: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Software: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the website. |
| 4.1.3 | Status Messages | AA | Supports | Software: Status messages are programmatically determined and conveyed to assistive technology without requiring focus changes. |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.3.1 | Object Information | - | Partially Supports | The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.2 | Modification of Object Information | - | Partially Supports | For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.3 | Row, Column, and Headers | - | Supports | When a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. |
| 502.3.4 | Values | - | Partially Supports | For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.5 | Modification of Values | - | Partially Supports | For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include: As noted in 4.1.2 Name, Role, Value |
| 502.3.6 | Label Relationships | - | Partially Supports | For most elements that act as a label for another element and elements that are labelled by another element, the labelling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include: As noted in 1.3.1 Info and Relationships As noted in 4.1.2 Name, Role, Value |
| 502.3.7 | Hierarchical Relationships | - | Supports | When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. |
| 502.3.8 | Text | - | Partially Supports | Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions include: As noted in 1.3.1 Info and Relationships |
| 502.3.9 | Modification of Text | - | Supports | When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology. |
| 502.3.10 | List of Actions | - | Supports | When one or more actions may be performed on an element, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. |
| 502.3.11 | Actions on Objects | - | Partially Supports | For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include: As noted in 2.1.1 Keyboard |
| 502.3.12 | Focus Cursor | - | Supports | On all pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. |
| 502.3.13 | Modification of Focus Cursor | - | Supports | When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology. |
| 502.3.14 | Event Notification | - | Partially Supports | Status messages relevant to user interactions are available to, and presented by, assistive technology. |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not display video. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not provide pre-recorded media that requires audio description. |
| 504.2.1 | Preservation of Information Provided for Accessibility | - | Not Applicable | The product is not an authoring tool. |
| 504.2.2 | PDF Export | - | Not Applicable | The product is not an authoring tool. |
| 4.2.1 | Usage without vision | - | Partially Supports | Software: Most functions of the product are usable without vision. Exceptions include: As noted in 1.3.1 Info and Relationships As noted in 2.1.1 Keyboard As noted in 2.4.6 Headings and Labels As noted in 4.1.2 Name, Role, Value |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: Most functions of the product are usable with limited vision. Exceptions include: As noted in 1.4.3 Contrast (Minimum) As noted in 1.4.10 Reflow As noted in 1.4.11 Non-text Contrast As noted in 2.1.1 Keyboard As noted in 2.4.6 Headings and Labels As noted in 4.1.2 Name, Role, Value |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Software: Most functions of the product are usable without perception of color. Exceptions include: As noted in 1.4.3 Contrast (Minimum) As noted in 1.4.11 Non-Text Contrast |
| 4.2.4 | Usage without hearing | - | Supports | Software: All functions of the product are usable without hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Software: All functions of the product are usable with limited hearing. |
| 4.2.6 | Usage with no or limited vocal capability | - | Supports | Software: The product is functional for users without speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Software: Most functions of the product are usable with limited manipulation and strength does not require fine motor control or simultaneous manual operations. Exceptions include: As noted in 2.1.1 Keyboard As noted in 2.4.6 Headings and Labels As noted in 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Supports | Software All functions of the product are usable by people with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Software: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Software: Most functions of the product are usable 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 or accessibility features of the platform. The product provides [descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include: As noted in 2.4.6 Headings and Labels |
| 4.2.11 | Privacy | - | Supports | Software: The product maintains user privacy when accessibility features are used · When text is masked visually, the private information is not announced in a screen reader. The product gives screen reader users sufficient opportunity to use their own private listening devices when reading personal data. |
| 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.7 | Access without speech | - | Not Applicable | The product does not have closed functionality. |
| 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 | - | 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.6.1 | Tactile or auditory status | - | Not Applicable | Tactile or auditory status is not included in the product. |
| 5.6.2 | Visual status | - | Not Applicable | Visual status of controls isn’t discernible in the product |
| 6.2.3 | Interoperability | - | Not Applicable | Software: The product does not provide Real-Time Text (RTT) functionality or an RTT display. Therefore, the requirement for Interoperability does not apply. |
| 6.2.4 | RTT responsiveness | - | Not Applicable | Software: The product does not provide Real-Time Text (RTT) functionality or an RTT display. Therefore, the requirement for RTT responsiveness does not apply. |
| 6.5.2 | Resolution | - | Supports | Software: The product provides two-way video communication with adequate resolution to support effective visual communication, including the perception of facial features and sign language communication where video is used. |
| 6.5.3 | Frame rate | - | Supports | Software: The product provides video communication with a frame rate adequate for effective visual interaction and the interpretation of visual communication cues, including sign language communication. |
| 6.5.4 | Synchronization between audio and video | - | Supports | Software: Audio and video streams are synchronized during video communication sessions, allowing users to effectively perceive and interpret visual and auditory communication cues. |
| 6.5.5 | Visual indicator of audio with video | - | Supports | Software: The product provides visual indicators of audio activity during video communication, allowing users to identify when participants are speaking. |
| 6.5.6 | Speaker identification with video (sign language) communication | - | Supports | Software: Participants in video communication sessions can be identified through visual participant information and speaker indicators, enabling users to determine who is communicating. |
| 7.1.1 | Captioning playback | - | Supports | The product displays closed captions. |
| 7.1.2 | Captioning synchronization | - | Supports | When the product displays captions, synchronization is preserved between the captions and the corresponding audio |
| 7.1.3 | Preservation of captioning | - | 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 | - | Supports | When the product displays captions for video that has synchronized audio, the display characteristics (such as color, font, or size) of the caption text can be modified by the user so people with low vision or color blindness can adapt the caption text to meet their needs. |
| 7.1.5 | Spoken subtitles | - | Does Not Support | The product does not support spoken subtitles. |
| 7.2.1 | Audio description playback | - | Supports | The product provides audio tracks option for users to select and play audio description tracks |
| 7.2.2 | Audio description synchronization | - | Supports | The product does have a mechanism to play audio description. |
| 7.2.3 | Preservation of audio description | - | Supports | Audio description can be provided in a manner that is synchronized with the video content. |
| 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.8.2 | Accessible content creation | - | Not Applicable | The product is not an authoring tool. |
| 11.8.3 | Preservation of accessibility information in transformations | - | Not Applicable | The product is not an authoring tool. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product is not an authoring tool. |
| 11.8.5 | Templates | - | Not Applicable | The product is not an authoring tool. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated Not stated. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.