[
    {
        "role": "user",
        "content": "is%20the%20Obsidian%20application%20for%20Windows%20accessible%20for%20screen%20reader%20users%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s what I found out about Obsidian\u2019s accessibility for screen reader users on Windows. The short answer: **it\u2019s partially accessible**, but with significant limitations and known accessibility regressions in recent versions. I\u2019ll break it down in detail so you can see where things work, where they don\u2019t, and what users have reported.\n\n---\n\n## \u2705 What works, or worked\n\n- Users have reported that earlier versions of Obsidian were *somewhat usable* with screen readers like **NVDA** on Windows. ([reddit.com](https://www.reddit.com/r/ObsidianMD/comments/mtclgg?utm_source=openai))  \n- Basic elements like menus and the UI panels are partially exposed: you can navigate to note titles, select files, and use certain commands. ([forum.obsidian.md](https://forum.obsidian.md/t/accessibility-obsidian-with-screen-readers/19669?utm_source=openai))  \n- Some users noted that **if you select all text** (Ctrl + A), the text *can* be read\u2014so text is present and accessible in some contexts. ([forum.obsidian.md](https://forum.obsidian.md/t/accessibility-obsidian-with-screen-readers/19669?utm_source=openai))  \n\n---\n\n## \ud83d\udeab Major limitations & regressions\n\nWhile some things work, there are *significant and fairly recent regressions* that have made core functionality unusable for screen reader users:\n\n- **After version 1.7.0** (which moved Obsidian to Electron 30), users report that screen readers like NVDA and Windows Narrator can no longer read *the content of notes*\u2014in both edit mode and preview mode. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n- Even when using special flags (like `--force-renderer-accessibility`), the content of notes is not exposed to the accessibility tree. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n- Pieces of the UI also suffer: the *Quick Switcher* (Ctrl+O) and *Command Palette* (Ctrl+P) sometimes fail to announce selection changes; external links may be read as the URL rather than the link text. These are usability-affecting bugs. ([forum.obsidian.md](https://forum.obsidian.md/t/accessibility-wrong-or-no-text-provided-to-jaws-screen-reader-in-links-quick-switcher-command-palette/84377?utm_source=openai))  \n- Themes and third-party plugins are likely further complicating accessibility; they can interfere with focus, contrast, and how elements are exposed to assistive tech. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n\n---\n\n## \ud83d\udd27 Reasons behind the issues\n\n- Obsidian is built with **Electron**, which governs how rendering works under the hood. Some version updates (such as your move to Electron 30) have changed how content is exposed to screen readers, leading to these regressions. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n- The editor component in Obsidian uses **CodeMirror 5**, which various users have called out as having architectural limitations for screen reader support. It doesn\u2019t always expose cursor movement or typed text in a way that many screen readers can announce. ([forum.obsidian.md](https://forum.obsidian.md/t/accessibility-obsidian-with-screen-readers/19669?utm_source=openai))  \n\n---\n\n## \u26a0\ufe0f Current status (as of early to mid 2025 into 2026)\n\n- As noted above, version 1.7.0 (c. mid-2025) introduced major accessibility regressions. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n- There are ongoing bug reports and feature-request threads in Obsidian\u2019s forums from screen reader users asking for fixes. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n- It doesn\u2019t appear these fundamental issues have yet been fully resolved; users report continuing broken behavior in current versions. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n\n---\n\n## \ud83d\udee0 Workarounds & what might help\n\nWhile these problems persist, here are some strategies that help partially:\n\n- Use older versions (pre-1.7.0 / before the Electron 30 update) if possible, where editing content with screen readers was more functional.  \n- Limit or disable custom themes and plugins that may interfere with interface structure, contrast, or focus behavior. Plain default UI tends to expose more correctly.  \n- Raise issues in Obsidian\u2019s forum or GitHub for bugs: most progress in fixes has come from user reports. Awareness seems central.  \n- Explore whether community plugins designed with a11y in mind might help patch the gaps.  \n\n---\n\n## \ud83d\udea8 Bottom line\n\nObsidian on Windows is **not fully accessible** for screen reader users right now. If you depend on a screen reader (especially as a blind user), core tasks like reading or editing notes may be severely impaired or unusable in the latest versions. Unless substantial improvements have been made very recently, there's a risk using Obsidian will leave you with incomplete access.  \n\nIf you\u2019d like, I can check whether a more recent version (after mid-2025) has restored accessibility for note content or has fixed these specific bugs. Would you prefer that?"
    },
    {
        "role": "user",
        "content": "yes"
    },
    {
        "role": "assistant",
        "content": "I searched recent sources and here\u2019s what current information indicates (as of mid-2025 through early 2026) about whether Obsidian on Windows has regained or improved screen reader accessibility\u2014especially for reading/editing note content. Unfortunately, there are *no confirmed fixes* for the biggest regression (loss of content access), and many issues remain unaddressed. Below is a detailed breakdown.\n\n---\n\n## \ud83d\udd75\ufe0f What recent reports and changelogs say\n\n**Issue since version 1.7.0:**  \nA user reported that after Obsidian was updated to version 1.7.0 (which moved the underlying platform to Electron 30), **no screen reader** (including NVDA or Windows Narrator) could read *note contents*\u2014neither in edit nor preview mode. Even launching the app with command-line accessibility flags did not restore access. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))\n\n**Current version when reporting:**  \nAt the time of that issue report (July 2025), Obsidian was already at version 1.8.10 (using Electron 34), and the report confirms that **the problem persists** in those newer versions. ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))\n\n---\n\n## \ud83d\udea7 Other outstanding accessibility issues\n\nEven outside of the main content reading issue, several other accessibility bugs continue to be reported:\n\n- Problems with the **Quick Switcher** (Ctrl+O) and **Command Palette** (Ctrl+P) where screen readers do *not* announce which command or file is selected. ([forum.obsidian.md](https://forum.obsidian.md/t/accessibility-wrong-or-no-text-provided-to-jaws-screen-reader-in-links-quick-switcher-command-palette/84377?utm_source=openai))  \n- External links sometimes being read by screen readers as raw URLs rather than link texts. ([forum.obsidian.md](https://forum.obsidian.md/t/accessibility-wrong-or-no-text-provided-to-jaws-screen-reader-in-links-quick-switcher-command-palette/84377?utm_source=openai))  \n- Buttons or controls in sidebars lacking accessible labels, which makes them non-navigable by screen readers. ([forum.obsidian.md](https://forum.obsidian.md/t/accessibility-obsidian-with-screen-readers/19669?page=2&utm_source=openai))  \n\n---\n\n## \u2139\ufe0f What about recent releases & changelogs?\n\n- The Obsidian **1.11 playback (desktop)** version, released on *January 12, 2026*, lists various improvements (e.g. new fonts, API changes, settings icon updates) and moves to Electron v39.2.6. However, it does *not* mention any fixes specifically addressing the screen reader accessibility regression in note content. ([obsidian.md](https://obsidian.md/changelog/2026-01-12-desktop-v1.11.4/?utm_source=openai))  \n- There have been no announcements found in Obsidian\u2019s official changelogs that state: \u201cFixed screen reader reading of note text in edit/preview mode\u201d or similar.  \n\n---\n\n## \u2705 So what is *currently* accessible\n\nBased on what users have reported:\n\n- Some menu items and UI elements are still reachable and announced by screen readers, especially when using keyboard navigation for certain non-note content (e.g. vault file names, settings menus). ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n- Selecting all text in a note (Ctrl+A) sometimes allows screen readers to announce the text, which indicates that the text *is* present in the application (but not correctly exposed to accessibility APIs for incremental navigation/movement). ([forum.obsidian.md](https://forum.obsidian.md/t/screen-reader-accessibility-issues-in-recent-versions-of-obsidian/103245?utm_source=openai))  \n\n---\n\n## \u26a0\ufe0f Summary & status as of May 2026\n\n- As of Obsidian 1.8+ (through at least version 1.11), *the major regression* in screen reader access to *note contents* **has not yet been restored**.  \n- Other accessibility issues remain, including with commands, links, and navigation.  \n- There is strong user interest and ongoing discussion in forums, but no firmly confirmed fix yet.  \n\n---\n\nIf you want, I can try digging in to see if there is a **pre-release**, **beta**, or hidden branch where this is fixed, or check in plugin or experimental flags that might help restore content reading. Would you prefer that?"
    }
]