Keyboard access
Navigation, forms, disclosures, dialogs, activation, file selection, and primary desktop workflows are intended to work without a pointer.
Accessibility
Access should not depend on how you use a computer.
CloakShift is committed to providing an accessible experience and aims to conform to WCAG 2.2 Level AA.
Current approach
Built for keyboard, screen, and assistive-technology use.
Accessibility is tested during development, but automated checks do not replace use with real assistive technology.
Visible and flexible
The website includes visible focus, responsive reflow, reduced-motion support, forced-colors support, and controls sized for reliable activation.
Clear status
Important errors, progress, completion, activation, and demo changes use labeled status regions where the current product supports them.
Known testing boundary
More manual testing remains.
Windows and macOS
Narrator and VoiceOver testing should cover installation, the secure composer, file selection, restored transcripts, settings, deletion, and error dialogs.
Browser changes
Supported AI sites, Chrome, and Edge can change independently. Accessibility testing must be repeated when their composer or extension behavior changes.
Third-party pages
AI services, browser stores, operating-system installers, and other third-party services have their own accessibility behavior.
Report a barrier
Tell us what blocked you.
Include the page or app edition, operating system, assistive technology, and the step that did not work. Do not send private files, vaults, API keys, access codes, or card information.