Overview
This document outlines the new success criteria introduced in WCAG 2.2. These additions build upon WCAG 2.1 and aim to enhance accessibility for users with low vision, cognitive impairments, and those using touch-based or mobile interfaces.
We are actively working toward conformance with WCAG 2.2, though not all new criteria are fully met yet. Improvements are ongoing as part of our commitment to accessible design.
Level A
Criteria | Conformance Level | Remarks and Explanations |
3.2.6 Consistent Help | - Web: Supports | - Web: A self-help option is provided, offering both general and context-aware help directly within the software. |
3.3.7 Redundant Entry | - Web: Supports | - Web: Information is auto-populated or made available for the user to select or copy when needed. |
Level AA
Criteria | Conformance Level | Remarks and Explanations |
2.4.11 Focus Not Obscured (Minimum) | - Web: Supports | - Web: Keyboard-focused components remain visible and are not fully obscured by author-created content. |
2.5.7 Dragging Movements | - Web: Supports | - Web: All functionality that uses a dragging movement can also be performed using a single pointer action. |
2.5.8 Target Size (Minimum) | - Web: Supports | - Web: Pointer targets meet or exceed the minimum size of 24 by 24 CSS pixels unless exceptions apply. |
3.3.8 Accessible Authentication (Minimum) | - Web: Supports | - Web: Authentication uses username and password, with input fields that support pasting to ensure compatibility with browser and third-party password managers. |
Level AAA
Criteria | Conformance Level | Remarks and Explanations |
2.4.12 Focus Not Obscured (Enhanced) | - Web: Partially Supports | - Web: Interface components that receive keyboard focus are generally visible. Some edge cases may still exist, so this remains a work in progress. |
2.4.13 Focus Appearance | - Web: Partially Supports | - Web: Text elements are underlined when focused, and icon or text-based buttons use a 4px box-shadow and high-contrast background. Some edge cases may still exist, so this remains a work in progress. |
3.3.9 Accessible Authentication (Enhanced) | - Web: Partially Supports | - Web: SSO is supported in specific contexts. However, alternatives to username and password are not yet widely available, so further improvements are planned. |