Adobe Connect - Mobile Application version 4.2 - Android
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 — 31 criteria
- Supports
- 12
- Partially supports
- 9
- Does not support
- 2
- Not applicable
- 8
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 11
- Partially supports
- 4
- Does not support
- 1
- Not applicable
- 8
- 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 (106)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Does Not Support | Software: The product does not provide sufficient text alternatives for most. Exceptions include: Some images are missing text alternatives in Surveys, Resources, Share, Q&A Pod and Join a Meeting via Link screen. |
| 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. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Software: The product contains audio content, and closed captions are provided. |
| 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. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Software: Some structure and relationship information are provided through element semantics or object information or in text. However, most structure and relationship information are not provided programmatically or in text. Exceptions include: Some visual headings and structural relationships are not programmatically identified in Surveys, Quizzes, Q&A, and Chat Pods. |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Software: The product presents most content in a meaningful sequence. Exceptions include: Screen reader focus is lost or misplaced in Chat. Some informative static content is not announced by screen readers in Join a Meeting via Link, Menu Options, Chat Pod, and Share Pod. |
| 1.3.3 | Sensory Characteristics | A | Supports | Software: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | Partially Supports | Software: Most functions of the product do not convey information through color alone. Exception include: Color alone is used to convey the state of some controls in Q&A Pod. |
| 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 a keyboard interface. Exceptions include: Some actions cannot be performed using screen readers or switch controls in Meeting Controls, Menu Options, and Join a Meeting via Link screens and Chat, and Share Pods. |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | Software: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Supports | Software: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Software: Moving, blinking, scrolling, and auto-updating information can be paused, stopped or hidden by the user. |
| 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 | Not Applicable | Software: This success criterion technically doesn't apply to native mobile applications. |
| 2.4.3 | Focus Order | A | Supports | Software: Components receive focus in a meaningful order. |
| 2.4.4 | Link Purpose (In Context) | A | Not Applicable | Software: The product does not contain links. |
| 2.5.1 | Pointer Gestures | A | Partially Supports | Software: Most functionality that can be operated with a pointer can be operated with single-point actions. Exceptions include: Some functionality relies on path-based or multipoint gestures in Chat and Share Pods. |
| 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 | Partially Supports | Software: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include: Some interactive elements have missing or incorrect accessible names that do not match their visible labels in Chat and Survey Pods, and Menu Options, the Top Navigation bar, and Join a Meeting via Link screen. |
| 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 | Not Applicable | Software: This success criterion technically doesn't apply to native mobile applications. |
| 3.2.1 | On Focus | A | Supports | Software: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Partially Supports | Software: In most cases, when a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user, or the user is informed about the change ahead of time. Exceptions include: Changing the setting of some user interface controls causes an unexpected change of context in Menu Options. |
| 3.2.6 | Consistent Help | A | Supports | Software: On web pages 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 | Partially Supports | Software: Most input errors are identified and described to the users in text. Exceptions include: Error messages are not programmatically associated with the corresponding form fields in Surveys. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Software: Labels are provided for most input fields. Exceptions include: Some form field instructions are not programmatically associated with their corresponding fields in Chat. |
| 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.2 | Name, Role, Value | A | Does Not Support | Software: User interface components in most product functions do not provide programmatic [name, role, state, or value] information. Exceptions include: Some controls have missing or incorrect programmatic names in Meeting Controls, Q&A, Breakout rooms, Chat, Surveys, Menu Options, and Join a Meeting via Link. Some elements have missing or incorrect programmatic roles in Meeting Controls, Menu Options, Join a Meeting via Link, Chat, Surveys, Quizzes, and Share Pod. Some controls have missing or incorrect programmatic states or values in the Top Navigation bar, Surveys, Quizzes, Q&A, and Join a |
| 1.2.4 | Captions (Live) | AA | Supports | Software: The product contains audio content in a live meeting synchronised media, and closed captions are provided. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Software: The product does not contain pre-recorded video content that would require audio description. |
| 1.3.4 | Orientation | AA | Partially Supports | Software: The orientation of most of the content is not locked to either landscape or portrait unless a specific orientation is essential for the functionality. Exceptions include: Content does not support both portrait and landscape orientations in Join a Meeting via Link. |
| 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 Polls, Surveys, Chat, and Quizzes. |
| 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 | Not Applicable | Software: This success criterion technically doesn't apply to native mobile applications. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Software: Most meaningful non-text content elements have sufficient contrast. Exceptions include: Some interactive controls have insufficient non-text contrast, including control boundaries and state indicators, in Chat, Join a Meeting via Link, Menu Options, the Top Navigation bar, and Q&A. Some graphics and icons have insufficient non-text contrast in Meeting Controls, Q&A, and Menu Options. |
| 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 | Not Applicable | Software: The product does not contain elements triggered by hover or focus. |
| 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 have missing, ambiguous, or duplicate programmatic labels that do not clearly identify their purpose in the Top Navigation bar, Chat, Surveys, Join a Meeting via Link, and Menu Options. |
| 2.4.7 | Focus Visible | AA | Not Applicable | Software: This success criterion technically doesn't apply to native mobile applications. |
| 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: Clickable controls meet the minimum target size and spacing requirements. |
| 3.1.2 | Language of Parts | AA | Not Applicable | Software: Content is only presented in one language at a time. |
| 3.2.3 | Consistent Navigation | AA | Supports | Software: Navigation patterns that are repeated on web pages are presented in the same relative order each time they appear and do not change order when navigating through the site. |
| 3.2.4 | Consistent Identification | AA | Supports | Software: Labels, names, and/or text alternatives for content that have the same functionality across multiple web pages are consistently identified. |
| 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. [When editing files,] changes to user-controllable data are reversible or can be confirmed before finalizing. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Software: Authentication does not rely on cognitive function tests, or an accessible alternative is provided. |
| 4.1.3 | Status Messages | AA | Does Not Support | Software: Most, if not all, status messages cannot be programmatically determined and presented by assistive technologies without receiving focus. Examples include: Some status messages are not programmatically announced in Chat, Join a Meeting via Link, Menu Options, Polls, Q&A, Surveys. |
| 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 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 | 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 | In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include: As noted in 4.1.3 Status Messages |
| 503.4.1 | Caption Controls | - | Supports | The product provides user controls for closed captions. |
| 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 in Format Conversion | - | 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.1.1 Non-text Content As noted in 1.3.1 Info and Relationships As noted in 1.3.2 Meaningful Sequence As noted in 1.4.1 Use of Color As noted in 2.1.1 Keyboard As noted in 2.4.6 Headings and Labels As noted in 3.2.2 On Input As noted in 3.3.1 Error Identification As noted in 4.1.2 Name, Role, Value As noted in 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: Most functionality is usable with limited vision. Exceptions include: As noted in 1.1.1 Non-text Content As noted in 1.4.1 Use of Color As noted in 1.4.3 Contrast (Minimum) 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 3.2.2 On Input As noted in 3.3.1 Error Identification As noted in 3.3.2 Labels or Instructions 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.1 Use of Color As noted in 1.4.3 Contrast (Minimum) As noted in 1.4.11 Non-Text Contrast As noted in 3.3.1 Error Identification |
| 4.2.4 | Usage without hearing | - | Supports | Software: All functionality is usable without hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Software: All functionality is usable with limited hearing. |
| 4.2.6 | Usage with no or limited vocal capability | - | Supports | Software: All functionality is usable without speech or other vocal output. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Software: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include: As noted in 1.3.4 Orientation As noted in 2.1.1 Keyboard As noted in 2.4.6 Headings and Labels As noted in 2.5.1 Pointer Gestures As noted in 2.5.3 Label in Name As noted in 3.2.2 On Input As noted in 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Software: Most functionality is usable by people with limited reach. Exceptions include: As noted in 1.3.4 Orientation As noted in 2.5.1 Pointer Gestures As noted in 2.5.3 Label in Name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | 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 users. Exceptions include: As noted in 2.4.6 Headings and Labels As noted in 2.5.1 Pointer Gestures As noted in 3.2.2 On Input As noted in 3.3.1 Error Identification As noted in 3.3.2 Labels or Instructions As |
| 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. |
| 11.6.1 | User control of accessibility features | - | Not Applicable | The product is not platform software. |
| 11.6.2 | No disruption of accessibility features | - | Not Applicable | The product is not platform software. |
| 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.