[
    {
        "role": "user",
        "content": "is%20the%20jaws%20or%20nvda%20screen%20reader%20known%20to%20work%20with%20wine%20(windows%20emulation%20under%20linux)%3F"
    },
    {
        "role": "assistant",
        "content": "I searched through user reports, issue trackers, and Wine/NVDA community discussions to check whether JAWS or NVDA screen readers work under Wine (the Windows compatibility layer on Linux). Here\u2019s a breakdown of what the evidence suggests, plus potential alternatives if they don\u2019t.\n\n---\n\n## \ud83d\udd0d What I found about NVDA under Wine\n\n### Bug reports & community threads\n\n- There is a longstanding open issue (\u201cWine support #11027\u201d) in the official NVDA GitHub issue tracker. It states that **NVDA currently doesn\u2019t work under Wine**, mainly because Wine does **not fully support necessary accessibility APIs** like Microsoft Active Accessibility (MSAA), UI Automation, IAccessible2, and focus hooks, all required by NVDA to \u201csee\u201d what\u2019s happening in the UI under Windows. ([github.com](https://github.com/nvaccess/nvda/issues/11027?utm_source=openai))\n\n- In a thread from mid-2024 on the NVDA mailing list / groups.io, a user reported trying to run an older version of NVDA (2017.2 installer) under Ubuntu 22.04 using Wine. They encountered errors even at install time. ([nvda.groups.io](https://nvda.groups.io/g/chat/topic/nvda_on_linux_using_wine/106480013?utm_source=openai))\n\n### What NVDA\u2019s docs say / imply\n\n- NVDA supports several **Windows accessibility APIs** (UI Automation, Microsoft Active Accessibility, IAccessible2, etc.). These are generally not implemented completely in Wine. That suggests NVDA needs those to function reliably. ([en.wikipedia.org](https://en.wikipedia.org/wiki/NonVisual_Desktop_Access?utm_source=openai))\n\n---\n\n## \ud83d\udee0 What about JAWS?\n\n- I didn\u2019t find any credible reports or evidence that JAWS (Job Access With Speech) runs successfully or reliably under Wine. Its architecture is proprietary, and relies heavily on Windows-specific drivers or system integrations that Wine does not duplicate. \n- Some mentions in \u201ccompatibility\u201d lists hint at JAWS under Windows, and list Orca, NVDA, etc. under Linux / alternatives. But nothing demonstrates JAWS working via Wine. ([spot.pcc.edu](https://spot.pcc.edu/~mgoodman/DL/screen_reader_compatibility.php?utm_source=openai))\n\n---\n\n## \ud83d\udeab Summary: Do they work?\n\nBased on current evidence:\n\n- **NVDA under Wine**: Not supported. People trying to install or run NVDA under Wine generally get errors, and core requirements like accessibility APIs aren\u2019t satisfied in Wine.  \n- **JAWS under Wine**: No solid evidence of working. Given how proprietary it is, it would be more difficult to make work than NVDA.\n\n---\n\n## \u2705 What are your alternatives?\n\nIf you're on Linux and need screen reading for Windows apps, here are some paths:\n\n1. **Use Linux-native screen readers**  \n   - *Orca*: built-in for GNOME desktop; works with native Linux apps and some cross-platform ones. ([en.wikipedia.org](https://en.wikipedia.org/wiki/Orca_%28assistive_technology%29?utm_source=openai))  \n   - Others: Linux distributions may offer \u201cSpeakup\u201d, \u201cMagnus\u201d etc. depending on what UI you use.  \n\n2. **Virtual machine**  \n   - Instead of Wine, run a Windows VM. NVDA and JAWS will work more reliably there because you're in a full Windows environment where all expected APIs, drivers, etc. are present.\n\n3. **Dual boot or remote access**  \n   - If you have access to a Windows machine, remote in, or dual-boot so you can use the real thing.\n\n4. **Accessibility APIs and mapping efforts**  \n   - For some apps that implement IAccessible or UI Automation, there are efforts to bridge Linux\u2019s AT-SPI or other accessibility layers to make things usable. But these are often app by app, not full coverage.\n\n---\n\nIf you like, I can dig into any recent patches or experimental builds (in Wine staging or similar) to see if anything has changed **in 2025 or 2026**. Would you prefer I do that?"
    }
]