Accessibility
Accessible use is not optional.
Docgate handles high-stakes information. The service should work for people using screen readers, keyboards, zoom, and mobile devices without requiring a separate consent step or alternate flow.
What accessibility means here
Accessibility is built into the interface itself. Users should not need to tick a special checkbox to make Docgate usable with a keyboard, screen reader, zoom, or mobile browser.
What the product is designed to support
Docgate is being built toward clear heading structure, readable contrast, visible focus states, responsive layouts, labeled form controls, keyboard-usable dialogs, and mobile-first spacing that keeps the main action near the top.
What still needs ongoing testing
Large result pages, export flows, authentication dialogs, and future billing flows should continue to be tested against WCAG 2.2 AA expectations on mobile Safari, Chrome, keyboard navigation, and screen readers.
Current standard
The right target for this product is WCAG 2.2 AA-level quality across the public website, scan flow, result pages, dashboard, auth modals, and billing modals. That work should be verified continuously as the product changes.
Accessibility contact
If you run into an accessibility barrier, contact [email protected] so the issue can be reviewed and fixed.