• Accessibility Statements

Accessibility Statement for Secure Sign

This is an accessibility statement from SSH Communications Security.

Measures to support accessibility

SSH Communications Security takes the following measures to ensure accessibility of Secure Sign:

  • Include accessibility as part of our mission statement.
  • Include accessibility throughout our internal policies.
  • Integrate accessibility into our procurement practices.
  • Assign clear accessibility goals and responsibilities.
  • Employ formal accessibility quality assurance methods.

Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. Secure Sign is partially conformant with WCAG 2.2 level AA.

Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

Compatibility with browsers and assistive technology

Secure Sign is designed to be compatible with the following assistive technologies:

  • Screen readers (e.g., NVDA, JAWS, VoiceOver, Orca)
  • Keyboard navigation tools

Secure Sign is not compatible with:

  • Outdated browsers (e.g., Internet Explorer)
  • Assistive technologies that do not support ARIA or HTML5 form elements

Technical specifications

Accessibility of Secure Sign relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Limitations and alternatives

Despite our best efforts to ensure accessibility of Secure Sign, there may be some limitations. Below is a description of known limitations and potential solutions. We are actively working to address these issues and improve accessibility.

Known limitations for Secure Sign:

  1. Printed PDF versions of web forms: Form fields, labels, and images in printed PDFs may be partly inaccessible to some screen readers or keyboard users. The PDF output becomes a static visual copy and might miss some accessibility tags or form controls. We are evaluating other PDF printing software solutions and improving the conversion process from form HTML to PDF to better preserve accessibility features.

Assessment approach

SSH Communications Security assessed the accessibility of Secure Sign by the following approaches:

  • Self-evaluation
  • External evaluation

Date

This statement was created on 20 November 2025 using the W3C Accessibility Statement Generator Tool.

Was this page helpful?