Zoho WorkDrive Accessibility Conformance Report WCAG Edition

Product Information

Name of the productZoho WorkDrive
Report DateJune 12, 2025
Contact Informationsupport@zohoworkdrive.com

Product Description

Zoho WorkDrive is a cloud file storage and content collaboration platform that helps hybrid teams, small businesses, and large enterprises work together efficiently.

Notes

  • We are actively working towards achieving WCAG 2.0, 2.1, 2.2 A & AA levels compliance to ensure enhanced accessibility and inclusivity for all users.
  • The accessibility options available in Zoho WorkDrive for end users are detailed in this document, indicating the current conformance level.
  • WCAG level AAA is not supported and hence the table has been removed in this report.

Evaluation Methods Used

  • The assessment was conducted using a combination of manual and automated testing.
  • We used manual evaluation methods, involving direct testing by the developer.
  • Automated testing was conducted using a combination of industry standard and custom-written static analysis tools.

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/GuidelineIncluded in Report
Web Content Accessibility Guidelines 2.0 Level A (Yes)
Level AA (Yes)
Level AAA (No)
Web Content Accessibility Guidelines 2.1 Level A (Yes)
Level AA (Yes)
Level AAA (No)
Web Content Accessibility Guidelines 2.2 Level A (Yes)
Level AA (Yes)
Level AAA (No)

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.

WCAG 2.x Report

Table 1: Success Criteria, Level A

CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text Content (Level A)Supports
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Partially SupportsWe currently support on-demand transcription for audio files and video files with voice-over. Transcription for video files without sound is not supported at the moment.
1.2.2 Captions (Prerecorded) (Level A)Does Not SupportWe currently do not support captions for video content.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Partially SupportsCurrently, our transcripts capture only spoken content and omit visual descriptions, resulting in limited support for complete media alternatives.
1.3.1 Info and Relationships (Level A)Partially Supports
  • <i> tags are currently used for styling SVG icons; semantic alternatives are being evaluated.
  • Some headings are not programmatically recognized by assistive technologies due to missing semantic roles.
  • While most UI elements have appropriate labels, a few input fields rely on ARIA attributes without visible labels.
  • Visual indicators for mandatory fields (like asterisks or color) are inconsistently applied across the UI.
  • Radio buttons and checkboxes are grouped using the name attribute, but <fieldset> and <legend> are yet to be implemented for proper semantic grouping.
  • Certain input components are not yet structured as accessible groups and need improvement.
1.3.2 Meaningful Sequence (Level A)Supports
1.3.3 Sensory Characteristics (Level A)Supports
1.4.1 Use of Color (Level A)Supports
1.4.2 Audio Control (Level A)Supports
2.1.1 Keyboard (Level A)Supports
2.1.2 No Keyboard Trap (Level A)Supports
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)Does Not Support
2.2.1 Timing Adjustable (Level A)Does Not Support
2.2.2 Pause, Stop, Hide (Level A)Supports
2.3.1 Three Flashes or Below Threshold (Level A)Supports
2.4.1 Bypass Blocks (Level A)Supports
2.4.2 Page Titled (Level A)Supports
2.4.3 Focus Order (Level A)Supports
2.4.4 Link Purpose (In Context) (Level A)Supports
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)Supports
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)Supports
2.5.3 Label in Name (Level A 2.1 and 2.2)Partially SupportsLabel and programmatic name alignment issues observed: All labels are currently visible, unique, and descriptive. However, some programmatic names do not begin with the visible label text, and aria-label support is limited.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)Not Applicable
3.1.1 Language of Page (Level A)Supports
3.2.1 On Focus (Level A)Supports
3.2.2 On Input (Level A)Partially Supports
  • In the Move, Copy, and Picker dialogs, folders are created when focus moves out of the input field without a clear "Create" button. This may confuse keyboard or screen reader users.
  • For watermark and comment inputs, an alert is shown when closing the preview, warning that unsaved changes will be lost.
3.2.6 Consistent Help (Level A 2.2 only)Supports
3.3.1 Error Identification (Level A)Partially SupportsIn some forms, the submit button gets disabled without showing an error message. We're working on enhancing this by displaying a clear error message to guide users.
3.3.2 Labels or Instructions (Level A)Partially Supports
  • Some inputs may lack visible labels, but accessible names are still provided programmatically.
  • A few labels are not fully descriptive, which may affect clarity.
  • To improve usability, provide clear instructions at the start of forms and use aria-describedby to associate inline help text with relevant inputs.
3.3.7 Redundant Entry (Level A 2.2 only)Supports
4.1.1 Parsing (Level A)Partially SupportsIn areas like the left navigation, visually styled lists are not always coded using proper semantic HTML tags (<ul>, <ol>, <li>). This can cause issues for screen readers, which rely on correct markup to announce list structures accurately.
4.1.2 Name, Role, Value (Level A)Supports