Accessibility Statement For Confirm | Confirm

Firm Connections 2026 | Two half-day virtual events. One goal: shaping the future of workforce enablement. 

Secure your spot today

Our Approach to Accessibility

Confirm considers accessibility throughout all phases of our product development cycle, from research and design through development and QA. We believe that designing to benefit people with disabilities creates products that better serve all users.

We work hard to meet level AA of the WCAG 2.2 standards through a combination of research, implementation techniques, tools, and testing. Our goal is to continuously improve and enhance the experience for all users. We build accessibility standards into all the components of our design system to deliver an inclusive experience across products.

Conformance Status

While we are continuously working to improve the usability of our products, Confirm is currently partially conformant with WCAG 2.2 level AA standards. This means that some parts of the platform do not fully conform to the accessibility standards.

Recent Accessibility Focused Developments Completed 

Added for WCAG 2.2:

  • 2.4.11 Focus Not Obscured (AA): When the user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
  • 2.5.7 Dragging Movements (AA): All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
  • 2.5.8 Target Size (Minimum) (AA): The size of the target for pointer inputs is at least 24 by 24 CSS pixels
  • 3.2.6 Consistent Help (A): If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they occur in the same relative order to other page content, unless a change is initiated by the user.
  • 3.3.7 Redundant Entry (A): Information previously entered by or provided to the user that is required to be entered again in the same process is either: auto-populated, or available for the user to select. Except when: re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid.
  • 3.3.8 Accessible Authentication (Minimum) (AA): A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least an a) An Alternative authentication method or b) A mechanism which is available to assist the user in completing the cognitive function test or c) an object recognition test is to recognize objects. Or (d) Personal Content to identify non-text content the user provided to the website.

Technical Specifications

Learn:Go is designed to be compatible with modern browsers and assistive technologies. We recommend the following combinations for optimal user experience:

Accessibility on Learn:Go relies on the following technologies to deliver an optimal user experience:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

Assessment Process

Confirm’s dedicated Design/UX Team conducts continuous audits and reviews (latest 04/25) along with QA testing for each release.

Software used for Audit purposes

  • NVDA 
  • VoiceOver (MacOS and iOS)
  • Native magnifier (built into OS)
  • Voice Control for Mac or iOS (speech to text)
  • Native OS features (high contrast mode)
  • WAVE 
  • axe DevTools
  • Google Lighthouse (built into Chrome Dev Tools)
  • Color Contrast Analyzer
  • Tab Order Visualizer ( Chrome Dev Tools)
  • Accessibility Insights
  • Hemingway Editor
  • Mobile specific:
    • Accessibility Scanner (Android)
    • Xcode Accessibility Inspector (iOS)

User Feedback

We love to hear any accessibility-related feedback. If you have any trouble with Learn:Go, please get in touch with us through any of the following options:

Learn:Up (formerly WorkRamp)

Learn:Up considers accessibility throughout all phases of our product development cycle, from research and design through development and QA. We believe that designing to benefit people with disabilities creates products that better serve all users.

We work hard to meet level AA of the WCAG 2.2 standards through a combination of research, implementation techniques, tools, and testing. Our goal is to continuously improve and enhance the experience for all users. We build accessibility standards into all the components of our design system to deliver an inclusive experience across products.

Conformance Status

While we are continuously working to improve the usability of our products, Learn:Up is currently partially conformant with WCAG 2.2 level AA standards. This means that some parts of the platform do not fully conform to the accessibility standards.

Areas not fully conformant

  • Employee Learning Cloud:
  • Events – Calendar View only
  • Guides – Attach File component – this uses a third party service
  • Admin console

All pages and functionality not listed above should be assumed to be WCAG 2.2 AA compliant.

Recent Accessibility Focused Developments Completed 

  • SC 1.1.1: Non-text Content (Level A) – Create a text alternative for visual and auditory content
  • SC 1.3.1: Info and Relationships (Level A) – Use code to reinforce relationships and information conveyed through presentation, so users can adapt the presentation to suit their needs while preserving the original meaning.
  • SC 1.4.1: Use of Colour (Level A) – Use information in addition to colour, such as shape or text, to convey meaning
  • SC 1.4.3: Contrast (Minimum) (Level AA) – Ensure all text elements have sufficient colour contrast between the text in the foreground and background colour behind it.
  • SC 2.1.1: Keyboard (Level A) – Ensure pointer actions have a keyboard equivalent
  • SC 2.4.1: Bypass Blocks (Level A) – Provide mechanisms to skip repetitive content and ensure that blocks of content, such as frames, are properly titled so users can navigate directly to the main information.
  • SC 2.5.8: Target Size (Minimum) (Level AA) – Ensure interactive targets are large enough for users to activate easily.
  • SC 4.1.2: Name, Role, Value (Level A) – Give components correct names, roles, states, and values, so assistive technology understand all components

Technical Specifications

Learn:Up is designed to be compatible with modern browsers and assistive technologies. We recommend the following combinations for optimal user experience:

Accessibility on Learn:Up relies on the following technologies to deliver an optimal user experience:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

Assessment Process

Learn:Up’s dedicated Design/UX Team conducts continuous audits and reviews (latest 01/26) along with QA testing for each release.

Software used for Audit purposes

  • NVDA 
  • VoiceOver (MacOS and iOS)
  • Native magnifier (built into OS)
  • Voice Control for Mac or iOS (speech to text)
  • Native OS features (high contrast mode)
  • WAVE 
  • axe DevTools
  • Google Lighthouse (built into Chrome Dev Tools)
  • Colour Contrast Analyzer
  • Tab Order Visualizer ( Chrome Dev Tools)
  • Accessibility Insights
  • Hemingway Editor
  • Mobile specific:
  • Accessibility Scanner (Android)
  • Xcode Accessibility Inspector (iOS)

User Feedback

We love to hear any accessibility-related feedback. If you have any trouble with Learn:Up, please get in touch with us.