Skip to content

Accessibility

Accessibility refers to the design and creation of products, devices, services or environments that are usable by people with a wide range of abilities and disabilities. It aims to ensure that all users, including those with visual, auditory, motor, or cognitive impairments, can access and interact with digital and physical spaces effectively. Accessibility is essential for inclusivity, allowing everyone equal access to information, services, and opportunities.

WCAG 2.2 (Web Content Accessibility Guidelines 2.2) is a set of guidelines developed by the World Wide Web Consortium (W3C) to ensure that web content is accessible to all users, including those with disabilities. Products must comply with these guidelines by incorporating features such as text alternatives for non-text content, keyboard accessibility, and sufficient contrast to improve readability. Adherence to WCAG 2.2 helps businesses meet legal requirements and promotes a more inclusive digital environment​ (Kinsta, Accessibility Works)​.

Improving accessibility not only ensures legal compliance but also broadens the user base, enhancing the experience for up to 20% of the population who benefit from accessible websites and applications. This includes people with disabilities and those with situational limitations.

In Europe, a new accessibility directive mandates that companies comply with the WCAG 2.1 standards at levels A and AA by 2025. This ensures that digital products are perceivable, operable, understandable, and robust for people with disabilities. The European Accessibility Act (EAA) applies to a broad range of products and services including consumer electronics (like computers and smartphones), self-service terminals (e.g., ATMs), e-commerce services, electronic communications, banking services, and transport information systems.

Accessibility of our SDKs

The individual components within our SDKs are specifically designed and tested for accessibility.

By utilizing our SDKs, you are not just adopting a framework, but integrating a suite of accessible components ready to support your application's compliance with standards, securing an inclusive experience for your users.

However, the very nature of the verification process and the requirements of certain regulations, which require users to present both their document and their face in real time and which prevent them from receiving assistance due to the potential for coercion, mean that certain steps in the process are not 100% accessible to everyone.

Recommendations

The following guidelines ensures that the components provided by our SDK are integrated in a manner that maximizes usability and meets WCAG standards for all users:

Ensure adequate color contrast

Color contrast is vital for perceivability, especially for users with low vision or color blindness.

  • Clarity is key: Always maintain a clear difference between the text color (foreground) and the background color.
  • Don't mix hues: Avoid mixing light text on light backgrounds or dark text on dark backgrounds.
  • Contrast ratio: Is a numerical measurement that describes the difference in luminosity between a foreground color (the text) and a background color. The ratio can range from 1:1 (no contrast) up to 21:1 (maximum contrast). The WCAG AA minimum contrast ratio is typically 4.5:1 for normal text and 3:1 for large text.

Provide comprehensive Alt Text for images

All non-text content must have a text alternative so that it can be converted into other formats (like speech or Braille). Every 'img' element must contain an 'alt' attribute.

Use descriptive content. The alt text must clearly and concisely describe the purpose and content of the image.

Although it's possible to hide the heading via configuration, it's not optimal. Semantic structure is critical for screen reader users. If you visually hide or completely remove header elements (such as the title or subtitle in the capture view), the accessibility of the content will be compromised.

Commitment to continuous auditing and excellence

Our commitment extends far beyond initial design. We are dedicated to continuously auditing our products to ensure that our SDK components not only meet, but consistently exceed, the requirements of current standards like WCAG 2.1. This proactive and iterative auditing process allows us to rapidly adopt the highest accessibility standards available, ensuring that as global guidelines evolve (such as the transition to WCAG 2.2 and beyond), our SDKs remains the forefront of digital inclusion and compliance.

Every day, we continue to work and subject our products to audits and testing to become not only more accessible, but also more usable. This ongoing effort ensures that our solutions evolve hand in hand with users’ needs, offering an inclusive and intuitive experience for everyone.