❯Accessibility

Mirafold should be usable by everyone who can use the terminal agents it re-skins — including people who navigate by keyboard alone and people who use a screen reader. This page states the standard we hold ourselves to, where we stand against it today, the limits we know about, and how to tell us when we have fallen short.

1.The standard we aim for

Our target is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the level referenced by most accessibility law, including the standard U.S. Department of Justice points to under the Americans with Disabilities Act. We treat AA as the bar for the Mirafold web application, not an aspiration.

2.Where we stand today

Mirafold is partially conformant with WCAG 2.1 AA: most of the product meets the standard, with the specific exceptions named in section 4. This assessment is our own — based on hands-on keyboard and screen-reader testing plus automated scanning — and has not yet been reviewed by an independent auditor. We would rather publish a claim we can point to line by line than a blanket “fully accessible” that a single test could contradict.

3.What we have done

The measures below are in the product today and are checked by our test suite so they do not quietly regress:

• Full keyboard operation. Every control is reachable and operable with the keyboard alone — no mouse required. Menus and dialogs trap focus while open and return it to wherever you were when they close, and Esc closes them.
• Screen-reader announcements for live output. When an agent is working, a screen reader hears the turn begin, each tool it runs, and the finished reply — announced once, at natural boundaries, rather than flooding you token by token. Permission prompts and errors interrupt, because they need your attention; the running transcript stays quiet so you can read it at your own pace.
• Real controls with real names. Buttons are buttons, links are links, and each is announced with a meaningful name and role — never a bare “button.”
• Colour contrast well past the requirement. WCAG AA asks for a 4.5:1 contrast ratio for normal text; every one of Mirafold's themes clears that by roughly double at its faintest text, and a test enforces the floor so new themes cannot fall below it.
• Respect for reduced-motion. If your system asks for reduced motion, Mirafold turns its animation off.
• A visible focus indicator and a correct page language, so assistive technology reads content in the right voice.

4.Known limitations

We would rather you hear these from us than discover them:

• Not independently audited. The conformance claim above is our own assessment, not a third-party certification.
• Testing coverage is uneven across tools. Our screen-reader testing has been most thorough with Orca on Chrome. Other combinations — NVDA, JAWS, VoiceOver — should work, as we rely on standard semantics rather than any one reader's quirks, but we have not exercised each of them end to end.
• The device-pairing QR code is visual. Connecting a phone shows a QR code to scan. Because a QR code cannot be made non-visual, the same pairing link is always presented next to it as focusable text with a copy button, so the feature does not depend on seeing the code.
• Newer surfaces are scanned, but not all hand-tested. Our last full keyboard-and-screen-reader audit was in July 2026. Everything built since is covered by the automated scan that runs on every change — the file explorer, mission control, the shell-command input bar, the pinned-widget dock and the enlarged file view were all brought into it on 30 July 2026, which immediately surfaced one real barrier: the enlarged file view scrolled but could not be reached by keyboard. That is fixed. Automated scanning catches only the machine-checkable share of WCAG issues, so those newer surfaces still owe the same hands-on review the rest of the product has had.
• Agent-generated interface elements. Mirafold lets the underlying agent render rich interface pieces. We make the container accessible and isolate that content, but where a specific element's wording or structure comes from the agent, its readability can depend in part on the agent and model you have connected.

Automated scanning, which we run on every change, catches only about a third of WCAG issues — the machine-checkable ones. The rest we check by hand and by ear, and that work is ongoing.

5.Tell us about a barrier

If any part of Mirafold blocks you, we want to know — a specific report is the fastest way to get it fixed. Email support@mirafold.com with what you were trying to do, the page or screen, and the assistive technology and browser you were using. We aim to reply within five business days, and if something is blocking you right now we will work with you to get you the information or result another way while we fix the underlying issue.

back to mirafold.com