Name of Product/Version: Harmonize
Report Date: March 2022
Product Description: Online Discussion Platform
Contact Information: harmonize-support@42lines.net
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 |
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.
Additionally, we have enlisted WebAIM to review Harmonize and they have found Harmonize to be substantially conformant with WCAG 2.1 Level A & AA. Here’s a link to their report: https://webaim.org/services/certification/42lines
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)
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.1 |
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 (Level A) | Supports | Harmonize provides description fields on uploaded images and video and all posts and comments have the ability to include text inline with media |
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Supports | Harmonize provides users the ability to upload multiple media files and label accordingly as well as include additional textual information |
1.2.2 Captions (Prerecorded) (Level A) | Supports | Video uploads and recordings are both automatically captioned by Harmonize Users can add their own SRT files to videos as well |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Supports | Harmonize does not support uploading multiple versions of audio or video, although users are free to upload separate copies and/or audio description |
1.3.1 Info and Relationships (Level A) | Supports | Harmonize utilizes correct semantic markup and labels all elements in support of assistive technologies |
1.3.2 Meaningful Sequence (Level A) | Supports | All content in Harmonize is displayed in a meaningful order |
1.3.3 Sensory Characteristics (Level A) | Supports | Harmonize provides instructions in the UI that are not dependent on sensory characteristics |
1.4.1 Use of Color (Level A) | Supports | Harmonize UI is designed to not be solely dependent on color for use |
1.4.2 Audio Control (Level A) | Supports | All audio playback in Harmonize requires user input; no audio play automatically |
2.1.1 Keyboard (Level A) | Supports | All page functionality is available using a keyboard |
2.1.2 No Keyboard Trap (Level A) | Supports | Harmonize does not have any page elements that trap keyboard focus |
2.1.4 Character Key Shortcuts (Level A 2.1 only) | Supports | Harmonize does not have any letter-, number-, or symbol-only keyboard shortcuts |
2.2.1 Timing Adjustable (Level A) | Supports | Harmonize does not include time-sensitive content |
2.2.2 Pause, Stop, Hide (Level A) | Supports | Harmonize does not include moving, blinking or scrolling content |
2.3.1 Three Flashes or Below Threshold (Level A) | Supports | Harmonize does not utilize any flashing elements |
2.4.1 Bypass Blocks (Level A) | Supports | Harmonize UI utilizes ARIA labels to aid in quick navigation to content |
2.4.2 Page Titled (Level A) | Supports | Harmonize provides descriptive titles for all pages |
2.4.3 Focus Order (Level A) | Supports | All pages and forms utilize a consistent focus order |
2.4.4 Link Purpose (In Context) (Level A) | Supports | Harmonize provides links with clear meaning from their text and context in page |
2.5.1 Pointer Gestures (Level A 2.1 only) | Supports | Harmonize does not utilize any pointer gestures |
2.5.2 Pointer Cancellation (Level A 2.1 only) | Supports | Harmonize triggers click and tap actions on up events and supports pointer cancellation |
2.5.3 Label in Name (Level A 2.1 only) | Supports | All inputs in Harmonize include labels |
2.5.4 Motion Actuation (Level A 2.1 only) | Supports | Harmonize does not utilize motion-activated features |
3.1.1 Language of Page (Level A) | Supports | Harmonize marks its default language as English |
3.2.1 On Focus (Level A) | Supports | Harmonize does not have any components that change context on focus |
3.2.2 On Input (Level A) | Supports | Harmonize does not utilize UI that changes upon input |
3.3.1 Error Identification (Level A) | Supports | Harmonize labels input errors and provides instructions to the user |
3.3.2 Labels or Instructions (Level A) | Supports | All fields within Harmonize include labels |
4.1.1 Parsing (Level A) | Supports | Harmonize utilizes full and properly formatted tags |
4.1.2 Name, Role, Value (Level A) | Supports | Some UI elements in Harmonize require further additions and refinement to provide proper ARIA labeling |
Table 2: Success Criteria, Level AA
Notes:
Criteria | Conformance Level | Remarks and Explanations |
1.2.4 Captions (Live) (Level AA) | Supports | Harmonize does not include support for live video or audio |
1.2.5 Audio Description (Prerecorded) (Level AA) | Supports | Users could upload versions of a video that include audio description but we don’t offer an ability to switch between the two |
1.3.4 Orientation (Level AA 2.1 only) | Supports | Harmonize utilizes a responsive UI and is tested against portrait and landscape modes on small and large screens |
1.3.5 Identify Input Purpose (Level AA 2.1 only) | Supports | All input elements have associated text labels |
1.4.3 Contrast (Minimum) (Level AA) | Supports | Harmonize UI supports minimum or greater contrast ratios |
1.4.4 Resize text (Level AA) | Supports | Harmonize supports text resizing without loss of content |
1.4.5 Images of Text (Level AA) | Supports | Harmonize does not use images of text |
1.4.10 Reflow (Level AA 2.1 only) | Supports | Harmonize utilizes a responsive UI |
1.4.11 Non-text Contrast (Level AA 2.1 only) | Supports | All UI elements in Harmonize conform to minimum or greater contrast ratios |
1.4.12 Text Spacing (Level AA 2.1 only) | Supports | The Harmonize UI supports changes in text size and spacing without loss of readability |
1.4.13 Content on Hover or Focus (Level AA 2.1 only) | Supports | Harmonize utilizes title attributes only for tooltips |
2.4.5 Multiple Ways (Level AA) | Supports | Harmonize provides multiple paths to all main content and provides clear navigation to all pages |
2.4.6 Headings and Labels (Level AA) | Supports | All page regions and landmarks in Harmonize have proper identification |
2.4.7 Focus Visible (Level AA) | Supports | Harmonize highlights the currently focused item for all inputs |
3.1.2 Language of Parts (Level AA) | Supports | Harmonize only supports English at present and is identified using the HTML lang attribute |
3.2.3 Consistent Navigation (Level AA) | Supports | Harmonize utilizes consistent navigation across all pages |
3.2.4 Consistent Identification (Level AA) | Supports | Harmonize re-uses components across pages to ensure a consistent experience |
3.3.3 Error Suggestion (Level AA) | Supports | All form errors in Harmonize utilize links back to the field in error |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | In Harmonize, posts and comments can be previewed before publishing and edited or deleted after publishing and deletions trigger a confirmation modal before continuing |
4.1.3 Status Messages (Level AA 2.1 only) | Supports | Status messages in Harmonize can be programmatically determined and read by assistive technologies |