Expected paths
| App | Expected path | Lens markers | Status |
|---|---|---|---|
| Apple NotesNative (AppKit)Native text view; the direct Accessibility path is expected. | Accessibility (read and replace) | likely | Not checked |
| SafariWeb/WebKitWeb pages: reading usually works, replacing only in editable fields. | Accessibility (read and replace) | partial | Not checked |
| Google ChromeChromiumChromium builds its Accessibility tree on request; AYVI sets AXManualAccessibility for this. | Clipboard with consent | partial | Not checked |
| MailNative (AppKit)The compose window is a native text view; received messages are web content. | Accessibility (read and replace) | likely | Not checked |
| TextEditNative (AppKit)Reference app for the self-test flow (NSTextView). | Accessibility (read and replace) | likely | Not checked |
| XcodeNative (AppKit)The source editor is native; line bounds and replacing still need checking. | Accessibility (read and replace) | partial | Not checked |
| Visual Studio CodeElectronElectron app; selection and range are often incomplete. The Services menu or clipboard with consent are the fallbacks. | Clipboard with consent | unlikely | Not checked |
| IntelliJ IDEAJava (Swing)Java UI with its own Accessibility bridge; direct access is uncertain. | Clipboard with consent | unlikely | Not checked |
| TerminalNative (AppKit)Output is not an editable field; explain through the Services menu or text recognition, no replacing. | Services menu (read-only) | unlikely | Not checked |
| iTermNative (AppKit)Like Terminal: read-only, no replacing expected. | Services menu (read-only) | unlikely | Not checked |
All entries are expectations derived from the app type. No entry is a test result while its status reads “Not checked”.
What the paths mean
- Accessibility: AYVI reads and, after a diff, replaces the selection directly.
- Clipboard with consent: only after a visible, separately confirmed action; the previous clipboard content is restored where possible.
- Text recognition: a screen region you drag, recognized locally; read-only.
- Services menu: select text, then app menu → Services → “Explain with AYVI”; read-only, no clipboard.
Read-only content and Windows
For text an app reports as not changeable (such as web pages), AYVI offers only explain, summarize, translate and similar analyses; there is no replacing. PDFs are not systematically checked; the Services menu entry “Explain with AYVI” is the intended path. A Windows version is in progress (alpha) and is available only as an unsigned test build for known testers.
Check your own app
In the AYVI menu choose “Check active app compatibility”. The report contains capabilities only – permission, role, readable, range, bounds, writable, Chromium/Electron – never content. A status changes from “Not checked” only after a real manual test recorded in the manual test matrix.