Accessibility statement
VERIDU commits to WCAG 2.2 AA across core customer surfaces and verification workflows.
Audit in progress with [FIRM] · Engagement date: [DATE]. Independent accessibility verification target: Q3 2026.
Current posture
VERIDU UI and documentation surfaces are designed for keyboard accessibility, semantic structure, contrast consistency, and readable interaction copy. We continuously test production pages and fix accessibility regressions as part of release QA.
Known limitation
Some verification flows that rely on tremor-derived drawing input may not be ideal for all motor profiles. Where this limitation affects a user, VERIDU provides alternate verification pathways through non-drawing interaction and enterprise-assisted policy routing.
Documented alternative paths: /accessibility/alternatives.html.
Accessibility feedback
Report barriers directly below. Reports route to accessibility@veridu.id and are triaged under VERIDU accessibility SLA.
You can also email accessibility@veridu.id directly with browser/device and assistive technology context.