Onfido logo home page
Watch a demo
Get in touch
Arrow back Back to guides

Input-capture SDKs accessibility statement

Introduction

Building inclusive products is important to us at Onfido, so we've been working hard to get our input-capture SDKs in shape.

Our accessibility statement outlines the progress with our input-capture SDKs (Android, iOS and Web).

What are we doing?

To help create a positive experience for anyone who uses our input-capture SDKs, we've based our accessibility work on the Web Content Accessibility Guidelines WCAG (WCAG) 2.1. These guidelines explain how to make digital products more user-friendly for everyone, and address specific accessibility needs for different user groups. Each guideline falls into one of three levels of conformance: A (lowest), AA or AAA (highest). We’ve chosen levels A and AA as our current target for the Onfido input-capture SDKs.

How are we doing?

We're working hard to achieve our goal of levels A and AA accessibility, but we recognize that there are still areas that need improving.

Here’s a list of relevant guidelines that we’ve passed and what we’re doing about the ones we’ve failed:

Perceivable

1.1 Text Alternatives

1.1.1 Non-text Content - A

1.2 Time-based Media

1.2.1 Audio-only and Video-only (Prerecorded) - A

1.2.2 Captions (Prerecorded) - A

  • Not applicable

1.2.3 Audio Description or Media Alternative (Prerecorded) - A

  • Not applicable

1.2.4 Captions (Live) - AA

  • Not applicable

1.2.5 Audio Description (Prerecorded) - AA

  • Not applicable

1.3 Adaptable

1.3.1 Info and Relationships - A

1.3.2 Meaningful Sequence - A

1.3.3 Sensory Characteristics - A

  • Fail. We’re working on improving our camera capture experience to make it accessible, by removing the need to see the shapes and visual locations of components.

1.3.4 Orientation - AA

  • Fail (only applies to Android and iOS SDKs). Our product is currently optimized for face captures in portrait mode so we’ve deprioritized work on landscape mode for now. However, it’s something we intend to explore in the future.

1.3.5 Identify Input Purpose - AA

1.4 Distinguishable

1.4.1 Use of Color - A

1.4.2 Audio Control - A

1.4.3 Contrast (Minimum) - AA

1.4.4 Resize text - AA

1.4.5 Images of Text - AA

1.4.10 Reflow - AA

1.4.11 Non-text Contrast - AA

  • Fail (only applies to Web SDK). We’re working on improving our buttons' focus states to make them more accessible.

1.4.12 Text Spacing - AA

1.4.13 Content on Hover or Focus - AA

Operable

2.1 Keyboard Accessible

2.1.1 Keyboard - A

2.1.2 No Keyboard Trap - A

2.1.4 Character Key Shortcuts - A

  • Not applicable

2.2 Enough Time

2.2.1 Timing Adjustable - A

  • Fail. Our security requirements necessitate a time constraint for the face video recording.

2.2.2 Pause, Stop, Hide - A

2.3 Seizures and Physical Reaction

2.3.1 Three Flashes or Below Threshold - A

2.4 Navigable

2.4.1 Bypass Blocks - A

  • Not applicable

2.4.2 Page Titled - A

  • Not applicable

2.4.3 Focus Order - A

2.4.5 Multiple Ways - AA

  • Not applicable

2.4.6 Headings and Labels - AA

2.4.7 Focus Visible - AA

2.5 Input Modalities

2.5.1 Pointer Gestures - A

  • Not applicable

2.5.2 Pointer Cancellation - A

2.5.3 Label in Name - A

2.5.4 Motion Actuation - A

  • Not applicable

Understandable

3.1 Readable

3.1.2 Language of Page - A

3.1.3 Language of Parts - AA

  • Not applicable

3.2 Predictable

3.2.1 On Focus - A

3.2.2 On Input - A

3.2.3 Consistent Navigation - AA

3.2.4 Consistent Identification - AA

3.3 Input Assistance

3.3.1 Error Identification - A

3.3.2 Labels or Instructions - A

  • Fail (only applies to Web SDK). We’re working on improving edge cases error messages.

3.3.3 Error Suggestion - AA

Robust

4.1 Compatible

4.1.1 Parsing - A

4.1.2 Name, Role, Value - A

  • Fail (only applies to Web SDK). We’ve applied a fix to improve speech-to-text input. We need to test this fix before considering this guideline passed.

4.1.3 Status Messages - AA