Skip to content

Accessibility

Accessibility is the practice of designing and integrating products so people with a wide range of visual, auditory, motor, and cognitive needs can complete the verification flow with as little friction as possible.

For native applications, teams commonly use the same core principles referenced in WCAG 2.2 AA for contrast, text alternatives, understandable copy, and predictable interaction.

Accessibility of XpressID Android

XpressID Android includes accessibility-related hooks in the current configuration model:

  • texts.common.logoAltText
  • texts.common.closeButtonAltText
  • texts.processResult.*.mediaAltText
  • texts.document[].instructions.*.desktopMediaAltText
  • texts.document[].instructions.*.mobileMediaAltText
  • texts.document[].review.mediaAltText
  • equivalent media alt text fields in selfie and video flows

The SDK also applies accessibility labels in native views such as loading, selectors, and configurable result media.

At the same time, identity verification has intrinsic limits: some steps require the user to show a real document and their face in real time without third-party intervention. Because of that, not every stage can be made equally accessible for every profile.

Recommendations

Keep meaningful text on screen

Avoid removing titles and subtitles unless there is a strong product reason. Instruction headings help screen-reader users and reduce ambiguity for everyone else.

Maintain adequate contrast

When overriding colors in styles, validate:

  • text against its background
  • button labels against button fills
  • feedback and status colors against surrounding surfaces

Do not rely on color alone to communicate success, warning, or failure.

Keep alt text synchronized with visible content

If you localize or rewrite texts, also update the related alternative text fields. logoAltText, closeButtonAltText, and media alt texts should describe purpose, not just appearance.

Good examples:

  • Company logo
  • Close verification flow
  • Illustration showing how to center the document inside the frame

Prefer clear and short copy

Instructional text should describe the expected action directly:

  • Show the front of your document
  • Center your face inside the frame
  • Turn your head to the left

Audit customized assets

If you replace bundled illustrations or result media:

  • keep them instructional rather than decorative
  • ensure they do not carry the only critical instruction
  • pair them with text so the flow remains understandable without the image

Continuous validation

Accessibility should be rechecked every time you customize:

  • colors and typography
  • texts and localization
  • media assets
  • visibility of headings, close actions, and result screens

The safest release process is to validate the customized flow on a physical iPhone with VoiceOver, Dynamic Type expectations, and real production copy.