Web application accessibility

Name of Product/Version: Rocket.Chat / 4.54.0

Platform: Web Application

Report Date: March 27, 2025

Product Description: Rocket.Chat is a customizable open-source communications platform for organizations with high standards of data protection. It enables real-time conversations between colleagues, with other companies or with your customers, across devices on web, desktop or mobile. While our commitment is to ensure accessibility within the team collaboration product, we acknowledge that users may interact with third-party integrations, plugins, or content. These components are beyond our direct control, and their accessibility may vary.

Contact information: [email protected]

Website: Accessibility Statement

Applicable Standards/Guidelines

This report covers the degree of conformance with the following accessibility standards/guidelines:

Standard/Guideline

Included in report

Web Content Accessibility Guidelines 2.0

Level A: Accessibility program running

Level AA: Accessibility program running

Level AAA: No

Web Content Accessibility Guidelines 2.1

Level A: Accessibility program running

Level AA: Accessibility program running

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.

  • Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG 2.0 Level AAA.

For criteria marked “Supports,” substantial conformance with the criterion by the product or service has been determined through the Evaluation Testing, which includes a mix of external audit—conducted by an expert in the field—and self-assessment by the Rocket.Chat team.

In the tables below, for all criteria marked “Not Applicable,” the specific feature covered by that criterion is not part of the product. For example:

If pre-recorded audio-only or video-only content is not part of a product, then WCAG criterion 1.2.1 Audio-only and Video-only (Prerecorded) will be marked “Not Applicable.”

WCAG Criterion

Results

Remarks and explanations

1.1.1 Non-text content (A)

Does not support

No remarks

1.2.1 Audio-only and Video-only (Prerecorded) (A)

Not applicable

No remarks

1.2.2 Captions (Prerecorded) (A)

Not applicable

No remarks

1.2.3 Audio Description or Media Alternative (Prerecorded) (A)

Does not support

E.g., alt text once uploading files (same as planned on mobile).

1.2.4 Captions (Live) (AA)

Not applicable

No remarks

1.2.5 Audio Description (Prerecorded) (AA)

Not applicable

No remarks

1.3.1 Info and Relationships (A)

Does not support

Possibly compliant but worth a review

1.3.2 Meaningful Sequence (A)

Does not support

Possibly compliant but worth a review

1.3.3 Sensory Characteristics (A)

Supports

Worth a quick review on few specific items

1.3.4 Orientation (AA)

Supports

No remarks

1.3.5 Identify Input Purpose (AA)

Supports

No remarks

1.4.1 Use of Color (A)

Supports

No remarks

1.4.2 Audio Control (A)

Supports

No remarks

1.4.3 Contrast (Minimum) (AA)

Supports

Worth a review scanning the application with contrast ratio tool.

1.4.4 Resize text (AA)

Supports

No remarks

1.4.5 Images of Text (AA)

Supports

No remarks

1.4.10 Reflow (AA)

Supports

Chat is compliant, admin is challenging b/c of the permission table

1.4.11 Non-text Contrast (AA)

Supports

No remarks

1.4.12 Text Spacing (AA)

Does not support

Possibly compliant but worth a review

1.4.13 Content on Hover or Focus (AA)

Does not support

Possibly compliant but worth a review

2.1.1 Keyboard (A)

Does not support

Needs review after 7.0 launch

2.1.2 No Keyboard Trap (A)

Does not support

Design has already mapped majority of places missing the keyboard nav and also has set how the navigation order.

2.1.4 Character Key Shortcuts (A)

Supports

No remarks

2.2.1 Timing Adjustable (A)

Does not support

Toast messages should have a accessibility setting for timing adjustment

2.2.2 Pause, Stop, Hide (A)

Does not support

No remarks

2.3.1 Three Flashes or Below Threshold (A)

Does not support

Not prioritized

2.4.1 Bypass Blocks (A)

Supports

A MVP is in place, but a few opportunities may be found through the accessibility program

2.4.2 Page Titled (A)

Supports

No remarks

2.4.3 Focus Order (A)

Does not support

Needs review after 7.0 launch

2.4.4 Link Purpose (In Context) (A)

Supports

No remarks

2.4.5 Multiple Ways (AA)

Does not support

This criterion aligns with the goals of the User Productivity Tools (New Navigation) project.

2.4.6 Headings and Labels (AA)

Supports

No remarks

2.4.7 Focus Visible (AA)

Supports

No remarks

2.5.1 Pointer Gestures (A)

Does not support

Not prioritized

2.5.2 Pointer Cancellation (A)

Supports

No remarks

2.5.3 Label in Name (A)

Supports

No remarks

2.5.4 Motion Actuation (A)

Does not support

Not prioritized

3.1.1 Language of Page (A)

Supports

No remarks

3.1.2 Language of Parts (AA)

Does not support

Not prioritized

3.2.1 On Focus (A)

Supports

No remarks

3.2.2 On Input (A)

Supports

No remarks

3.2.3 Consistent Navigation (AA)

Supports

This criterion aligns with the goals of the User Productivity Tools (New Navigation) project.

3.2.4 Consistent Identification (AA)

Supports

No remarks

3.3.1 Error Identification (A)

Does not support

Needs to follow the same plan we have for the mobile accessibility program

3.3.2 Labels or Instructions (A)

Supports

No remarks

3.3.3 Error Suggestion (AA)

Does not support

Needs to follow the same plan we have for the mobile accessibility program

3.3.4 Error Prevention (Legal, Financial, Data) (AA)

Does not support

Not prioritized

4.1.1 Parsing (A)

Supports

No remarks

4.1.2 Name, Role, Value (A)

Does not support

No remarks

4.1.3 Status Messages (AA)

Does not support

Needs to follow the same plan we have for the mobile accessibility program

© 2025 Rocket.Chat Inc. All rights reserved. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The information contained in this document represents the current view of Rocket.Chat Inc. on the issues discussed as of the date of publication. Rocket.Chat cannot guarantee the accuracy of any information presented after the date of publication.

Rocket.Chat’s WCAG 2.1 conformance reports provide the information included in ITI’s “VPAT® 2.4Rev WCAG (March 2022)” template. “Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI). This document includes material copied from or derived from the Web Content Accessibility Guidelines (WCAG 2.1). Copyright © 2017-2018 W3C® (MIT, ERCIM, Keio, Beihang). This document is not the Web Content Accessibility Guidelines (WCAG) and should not be used as a substitute for it. Excerpts of WCAG are referenced solely for purposes of detailing Rocket.Chat’s conformance with the relevant provisions. A full and complete copy of the Guidelines is available from the W3C WAI.

Rocket.Chat regularly updates its websites and provides new information about the accessibility of products as that information becomes available.

Customization of the product voids this conformance statement from Rocket.Chat. Customers may make independent conformance statements if they have conducted due diligence to meet all relevant requirements for their customization.

This document is for informational purposes only. ROCKET.CHAT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.