Accessibility Statement
Private Identity LLC — effective October 27, 2026 · next review October 2027 · privateid.com/accessibility
Private Identity is committed to making its products and its website accessible to people with disabilities. This statement covers the Ultrapass® identity verification and authentication flows that run inside our customers’ applications and websites (document capture, selfie and liveness capture, re-authentication, consent and result screens), the Ultrapass administration and support portals used by our customers’ staff, and privateid.com.
Conformance target and current status
Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the W3C, and with the related requirements of Section 508 of the Rehabilitation Act and EN 301 549 where they apply to our customers.
- Web verification flows. The Ultrapass web verification flows have been assessed by an independent accessibility assessor, documented in an Accessibility Conformance Report (VPAT® 2.5, WCAG 2.2 Level AA, November 2025). The report is available to customers and prospective customers on request.
- Native iOS and Android SDK screens. The native screens are built to the same standard and are tested with VoiceOver and TalkBack before each release; a companion screen-reader test program for the native SDK is in execution, and its results will be published as a further Accessibility Conformance Report.
- privateid.com and the customer portals are reviewed against the same criteria on each release.
Assistive technologies and features supported
The Ultrapass flows are designed to work with screen readers (V oiceOver, TalkBack, NVDA, JAWS), keyboard-only and switch navigation, operating-system text scaling up to 200%, high-contrast and dark modes, and reduced-motion settings. Capture steps give spoken and visual guidance (move closer, reduce glare, hold the document flat), accept a capture only when it will verify so that retries are rare, and impose no time limit that cannot be extended. Where a customer cannot complete a camera-based step, the customer’s organization can offer an assisted or alternative verification path through its own channels; our products are built so that the alternative path is available in the same session.
What we do to maintain accessibility
Accessibility requirements are part of our design system and software development lifecycle; every release is checked with automated tooling, manual expert review and assistive-technology testing; accessibility defects are tracked with the same priority scheme as security defects — a barrier that prevents a person using assistive technology from completing verification is treated as a high-priority defect with a workaround or fix targeted within one business day for customers under contract, and other conformance defects are fixed in the next scheduled release; product, design and engineering staff receive accessibility training; and this statement is reviewed at least annually.
Feedback and contact
If you encounter an accessibility barrier in an Ultrapass flow, in one of our portals or on privateid.com, please tell us: email accessibility@privateid.com with the product or page, the step, your device and assistive technology, and what happened. We acknowledge reports within two business days and keep you informed until the issue is resolved. If the barrier is inside a bank’s or another organization’s application, you may also contact that organization directly; it will route the report to us.