A secure handoff should be usable by everyone.

Our commitment

Accessibility is treated as a product requirement, not a collection of image labels.

We design for keyboard operation, visible focus, meaningful structure, sufficient contrast, zoom and reflow, reduced motion, clear labels and instructions, understandable errors, and assistive-technology announcements that do not expose secret content unnecessarily.

Current support

• Semantic headings, landmarks, labels, lists, tables, and navigation.
• A skip link and visible keyboard focus on public and core application surfaces.
• Layouts designed to reflow on small screens and at substantial browser zoom.
• Text alternatives for meaningful non-text content; decorative marks are hidden from assistive technology.
• Status and error messages exposed without using colour as the only signal.
• Motion removed when the operating system requests reduced motion.
• Secret values are not placed in automatic live announcements.

Known limitations

Slack, Microsoft Teams, Outlook, browser extensions, identity-provider pages, and operating-system dialogs include interfaces outside SecretBridge's direct control. Their keyboard, screen-reader, zoom, and contrast behaviour may vary by host and version.

The support form uses hCaptcha for abuse prevention. hCaptcha provides accessibility options, but its challenge is a third-party surface and may behave differently from the rest of SecretBridge. Use its accessibility options; if it remains a barrier, contact us through the support route in the Slack or Microsoft marketplace listing.

The operator onboarding surface and collaboration-platform embedded surfaces are tested as they change, but some combinations of host application and assistive technology may require additional remediation. Please report the exact platform, browser or app version, assistive technology, and task you were attempting.

Accessibility feedback

Contact the secure support form if an accessibility barrier prevents you from creating, receiving, or revealing a secret. Do not include secret plaintext, reveal links, access tokens, passwords, or private keys. We can arrange a safer channel if sensitive diagnostic evidence is necessary.

Include the page or platform, what you expected, what happened, and the assistive technology or input method you were using.