Zendesk SDK (Android)
Accessibility Conformance Report published by Zendesk
Partial extraction. We read 16 of 31 Level A and 13 of 24 Level AA criteria from this document (53% coverage). The remainder are missing from our extraction, not necessarily from Zendesk's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
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 — 16 criteria
- Supports
- 13
- Partially supports
- 3
- Does not support
- 0
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 13 criteria
- Supports
- 11
- Partially supports
- 2
- Does not support
- 0
- Not applicable
- 0
- Not evaluated
- 0
Source: View the original report published by Zendesk.
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 (51)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Android: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Android: The product does not contain any prerecorded video media that requires audio descriptions or a media alternative. |
| 1.3.2 | Meaningful Sequence | A | Supports | Android: The product ensures that a correct reading order can be programmatically determined for content whose presentation sequence affects its meaning. |
| 1.4.1 | Use of Color | A | Supports | Android: The product does not use color as the only visual means of conveying information, indicating an action, or prompting a response. |
| 2.1.1 | Keyboard | A | Supports | Android: The product ensures that interactive content and functionality is accessible and operable using a keyboard or keyboard emulator. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Android: The product does not use character key shortcuts. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Android: The product does not contain content that moves, blinks, scrolls, or auto-updates. |
| 2.4.1 | Bypass Blocks | A | Supports | Android: The product does not contain blocks of content repeated across multiple pages that require a bypass mechanism. |
| 2.4.3 | Focus Order | A | Partially Supports | Android: In most instances, screens of the product can be navigated sequentially with a focus order that matches the logical reading order. Exceptions include: • There is content with an illogical focus order, such as “1 of 1” text being announced before the input field. |
| 2.5.1 | Pointer Gestures | A | Supports | Android: The product does not require multipoint or path-based gestures for operation. |
| 2.5.3 | Label in Name | A | Supports | Android: The product ensures that when interface components have visual labels that include text, the provided accessible name contains the visually presented text. |
| 3.1.1 | Language of Page | A | Supports | Android: The product ensures that the default human language used on each screen can be programmatically determined. |
| 3.2.2 | On Input | A | Supports | Android: The product ensures that interactive components do not initiate a change in context when the component setting is changed unless followed by an explicit user action such as activation of a button or link. |
| 3.3.1 | Error Identification | A | Partially Supports | Android: In most instances, where the product automatically detects input errors, the item or field in error is identified and the error is described to the user in text. Exceptions include: • Error messages are not announced with the associated input fields when they receive focus. |
| 3.3.7 | Redundant Entry | A | Supports | Android: The product does not request redundant user-entered information in multi-step processes. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Android: In most instances, the product contains user interface components whose name, role, state, and value can be programmatically determined. Exceptions include: • There is missing role information for uploaded attachments. • A decorative image is exposed to assistive technology users. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Android: The product does not contain any prerecorded synchronized media (video with audio) that requires audio descriptions. |
| 1.3.5 | Identify Input Purpose | AA | Supports | Android: The product ensures that the purpose of input fields that request information about the user, such as name or email, can be programmatically determined. |
| 1.4.4 | Resize text | AA | Supports | Android: The product allows text to be resized without assistive technology up to 200 percent without loss of content or functionality. |
| 1.4.10 | Reflow | AA | Supports | Android: The product allows for resizing of content to a minimum width of 320 CSS pixels or vertical height of 256 CSS pixels without loss of content or functionality, and without requiring scrolling in two dimensions. |
| 1.4.12 | Text Spacing | AA | Supports | Android: The product supports user changes in text style properties, such as line height or text spacing, without loss of content or functionality. |
| 2.4.5 | Multiple Ways | AA | Supports | Android: Screens of the product are accessed via a process flow and do not otherwise require multiple methods of access. |
| 2.4.7 | Focus Visible | AA | Supports | Android: The product provides a visible indication of keyboard focus for elements on each screen. |
| 2.5.7 | Dragging Movements | AA | Supports | Android: The product does not use dragging movements for interactive functionality. |
| 2.5.8 | Target Size (Minimum) | AA | Partially Supports | Android: The size of the target meets the |
| 3.1.2 | Language of Parts | AA | Supports | Android: Screens of the product present content in a single language. |
| 3.2.4 | Consistent Identification | AA | Supports | Android: The product ensures that components with the same functionality are identified consistently across screens of the product. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Android: The product does not cause financial transactions or legal commitments to occur. User- controllable data is checked before submission and can be reversed or revised after submission. |
| 4.1.3 | Status Messages | AA | Partially Supports | Android: In most instances, the product provides status messages that can be presented to assistive technologies without receiving focus. Exceptions include: • There are dynamic status updates that are visually available but are not announced to assistive technology users. • When a new message is received, there is no status announced made to assistive technology users. |
| 4.2.1 | Usage without vision | - | Partially Supports | Partially Supports |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Where the product provides visual modes of operation, it mostly provides features that enable users to make better use of their limited vision as disclosed in: • 1.1.1 Non-text Content • 2.4.3 Focus Order • 3.3.1 Error Identification • 4.1.2 Name, Role, Value • 4.1.3 Status Messages |
| 4.2.3 | Usage without perception of colour | - | Supports | Where the product provides visual |
| 4.2.4 | Usage without hearing | - | Supports | Where the product provides auditory modes of operation, it allows at least one mode of operation that does not require hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Supports |
| 4.2.6 | Usage with no or limited vocal capability | - | Supports | Where the product requires vocal input from users, functions of the product do not require users to generate vocal output. |
| 4.2.7 | Usage with limited manipulation or strength | - | Supports | Where the product requires manual |
| 4.2.8 | Usage with limited reach | - | Supports | All functions of the product can be used with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | The product does not contain flashing |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | The product mostly allows for functionality that provides features and/or presentation that makes it simpler and easier to understand, operate and use except as disclosed in: • 2.4.3 Focus Order • 3.3.1 Error Identification • 4.1.3 Status Messages |
| 4.2.11 | Privacy | - | Supports | The product maintains user privacy |
| 5.1.4 | Functionality closed to text enlargement | - | Not Applicable | The product does not have any closed functionality. |
| 5.1.5 | Visual output for auditory information | - | Not Applicable | The product does not have any closed |
| 5.1.7 | Access without speech | - | Not Applicable | Not Applicable |
| 5.5.1 | Means of operation | - | Not Applicable | The product does not have operable parts. |
| 5.5.2 | Operable parts discernibility | - | Not Applicable | The product does not have operable |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | The product does not have locking or |
| 5.6.2 | Visual status | - | Not Applicable | The product does not have locking or toggle controls. |
| 11.6.1 | User control of accessibility features | - | Not Applicable | The product does not provide platform accessibility features. |
| 11.6.2 | No disruption of accessibility features | - | Not Applicable | The product does not have |
| 11.8.3 | Preservation of accessibility information in transformations | - | 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.