Voluntary Product Accessibility Template

Name of Product/Version: Harmonize

Report Date: April 2025

Product Description: Online Discussion Platform

Contact Information: support@harmonizelearning.com

Notes

Revision	Date
V1.0 – Original Document	May 2020
V1.1 – Updated to note auto-captioning of video	August 2020
V1.2 – Updated to note ARIA improvements	November 2020
V1.3 – Updated to note various improvements	January 2021
V1.4 – Updated to note various improvements	March 2021
V1.5 – Updated to note certification by WebAIM and ARIA improvements	March 2022
V1.6 – Updated to VPAT 2.5 and WCAG 2.2	April 2025

Note: 2026 plans for additional accessibility features added in Nov 2025, will be revised to a v1.7 when those features go live.

Evaluation Methods Used

Testing was performed primarily using WAVE and the WAVE toolbar extension for Chrome. Additional testing utilized keyboard navigation of the site and the NVDA screen reader on Chrome using the Windows 10 operating system.

Accessibility is a design requirement of every new feature in Harmonize, and every release goes through accessibility testing utilizing the above testing methods to ensure conformance is maintained.

Additionally, we have enlisted WebAIM to review Harmonize and they have found Harmonize to be substantially conformant with WCAG 2.1 Level A & AA.

Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)

What to do if you find an issue

We consider accessibility a journey, not just from a legal compliance perspective but from a usability perspective. So if you find something in Harmonize that seems harder to use than it should, please email it to support@harmonizelearning.com as we prioritize accessibility related issues as if they were bugs and do our best to address them quickly.

Applicable Standards/Guidelines

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

Standard/Guidelines

Included in Report

Web Content Accessibility Guidelines 2.2

Level A

Level AA

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 be used only in WCAG 2.0 Level AAA.

WCAG 2.x Report

Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: Success Criteria, Level A

Notes:

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content	Supports	Harmonize provides description fields on uploaded images and video and all posts and comments have the ability to include text inline with media. Starting in 2026, Harmonize will offer the option to prefill alt text using AI so instructors and students have a good 1st step to edit.
1.2.1 Audio-only and Video-only (Prerecorded)	Supports	Harmonize provides users the ability to upload multiple media files and label accordingly as well as include additional textual information. Starting in 2026, we’re going to allow creation and editing of captions and audio descriptions as well as permitting AI to prefill both for instructors and students to edit.
1.2.2 Captions (Prerecorded)	Supports	Video uploads and recordings are both automatically captioned by Harmonize. Users can add their own SRT files to videos as well. Starting in 2026, and in-app caption editor will be available.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Supports	Harmonize does not support uploading multiple versions of audio or video, although users are free to upload separate copies and/or audio description. Starting in 2026, users can create extended audio descriptions with a built-in editor or they can even have AI prefill an extended audio description for them to edit.
1.3.1 Info and Relationships	Supports	Harmonize utilizes correct semantic markup and labels all elements in support of assistive technologies
1.3.2 Meaningful Sequence	Supports	All content in Harmonize is displayed in a meaningful order
1.3.3 Sensory Characteristics	Supports	Harmonize provides instructions in the UI that are not dependent on sensory characteristics
1.4.1 Use of Color	Supports	Harmonize UI is designed to not be solely dependent on color for use
1.4.2 Audio Control	Supports	All audio playback in Harmonize requires user input; no audio play automatically
2.1.1 Keyboard	Supports	All page functionality is available using a keyboard
2.1.2 No Keyboard Trap	Supports	Harmonize does not have any page elements that trap keyboard focus
2.1.4 Character Key Shortcuts	Supports	Harmonize does not have any letter-, number-, or symbol-only keyboard shortcuts
2.2.1 Timing Adjustable	Supports	Harmonize does not include time-sensitive content
2.2.2 Pause, Stop, Hide	Supports	Harmonize does not include moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold	Supports	Harmonize does not utilize any flashing elements
2.4.1 Bypass Blocks	Supports	Harmonize UI utilizes ARIA labels to aid in quick navigation to content
2.4.2 Page Titled	Supports	Harmonize provides descriptive titles for all pages
2.4.3 Focus Order	Supports	All pages and forms utilize a consistent focus order
2.4.4 Link Purpose (In Context)	Supports	Harmonize provides links with clear meaning from their text and context in page. Additionally, when users provide links, we request a preview from the target site to display to make them more accessible.
2.5.1 Pointer Gestures	Supports	Harmonize does not utilize any pointer gestures
2.5.2 Pointer Cancellation	Supports	Harmonize triggers click and tap actions on up events and supports pointer cancellation
2.5.3 Label in Name	Supports	All inputs in Harmonize include labels
2.5.4 Motion Actuation	Supports	Harmonize does not utilize motion-activated features
3.1.1 Language of Page	Supports	Harmonize marks its default language as English
3.2.1 On Focus	Supports	Harmonize does not have any components that change context on focus
3.2.2 On Input	Supports	Harmonize does not utilize UI that changes upon input
3.2.6 Consistent Help	Supports	Harmonize offers a consistent help content regardless of page orientation or zoom level
3.3.1 Error Identification	Supports	Harmonize labels input errors and provides instructions to the user
3.3.2 Labels or Instructions	Supports	All fields within Harmonize include labels
3.3.7 Redundant Entry	Supports	Harmonize reuses already-entered information wherever possible.
4.1.2 Name, Role, Value	Supports	Some UI elements in Harmonize require further additions and refinement to provide proper ARIA labeling

Table 2: Success Criteria, Level AA