At Sumsub, we pursue the goal of spreading a people-friendly digital future that is safe, accessible, and inclusive for all — our partners, their businesses, and the users they serve.

The Sumsub SDK supports WCAG 2.2 Level AA standards, making our verification a secure environment designed for users with diverse visual, auditory, motor, and cognitive abilities.

The following core features represent our current implementation of inclusive design:

• Screen reader and assistive technology support
• Navigation and interface Interaction
• Visual standards and display adaptability
• Cognitive ease and error handling

Screen reader and assistive technology support

The SDK is optimized for native screen readers, including VoiceOver (iOS/macOS) and TalkBack (Android). The key accessibility features include:

• Text alternatives: All non-text content, such as instructional icons and status graphics, includes descriptive alt text or ARIA labels to ensure full context for visually impaired users.
• Semantic labeling: Interactive elements and input fields are programmatically labeled. Required fields are specifically identified in the code, allowing assistive technologies to alert users before submission.
• Real-time announcements: Dynamic updates, such as successful document captures or processing states, are presented during verification to keep the user informed.

Verification and testing

To verify the implementation of these accessibility features on a mobile device, you can utilize the built-in screen reader tools.

Test the implementation on iOS (VoiceOver):

1. Navigate to Settings → Accessibility → VoiceOver.
2. Enable the VoiceOver toggle.
3. Use a single-finger swipe to move focus between SDK elements and a double-tap to activate them.

Test the implementation on Android (TalkBack):

1. Go to Settings → Accessibility → TalkBack.
2. Enable the TalkBack toggle.
3. Use left/right swipes to navigate and a double-tap to confirm actions.

By testing with these tools, you can experience how the Sumsub SDK communicates instructions (for example, Frame your document) and provides feedback through audio assistance.

Navigation and interface interaction

We keep the flow focused on users who rely on keyboards, switches, or have limited motor skills. All of these are provided through the following solutions:

• Keyboard navigation: All functional elements are accessible via a logical keyboard focus order.
• Target size & precision: In accordance with WCAG 2.2 standards, all interactive components (buttons, toggles, links) maintain a minimum target size of 24x24 pixels to ensure ease of interaction.
• Visible focus indicators: A clear, high-contrast focus ring is utilized to help users navigate the interface without a mouse or touch input.

Visual standards and display adaptability

The SDK’s visual design focuses on clarity and readability under various conditions. What helps ensure these visual standards:

• Color contrast: All text and essential UI components adhere to a minimum 4.5:1 contrast ratio, meeting standard requirements for users with low vision or color deficiencies.
• Text resizing: The interface supports system-level font scaling and browser zoom up to 200% without loss of functionality or overlapping content.
• Visual instructions: For complex tasks such as Liveness checks, we provide clear on-screen visual prompts that complement automated processes and audio cues.

Cognitive ease and error handling

Our workflows are designed to be predictable and easy to understand, reducing the cognitive load on the user. How this is achieved:

• Consistent component behavior: Navigation and UI patterns remain uniform throughout the verification journey.
• Accessible error correction: When an input error occurs, the SDK provides a specific text-based description of the issue and clear guidance on how to resolve it.
• Simplified authentication: In alignment with the latest WCAG 2.2 criteria, we prioritize straightforward verification methods and avoid complex cognitive load in the interface.

All aforementioned measures are fully aligned with the WCAG 2.2 AA level guidelines. If you have any questions or want to report any related difficulty, feel free to contact us at [email protected].