[
    {
        "role": "user",
        "content": "is%20the%20node%20editor%20in%20godot%20accessible%20when%20using%20a%20screen-reader%3F"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s what I found out about how accessible Godot\u2019s *node editor* is when using a screen reader \u2014 what works now, what doesn\u2019t, and what\u2019s in progress.\n\n---\n\n## \u2705 What *is* supported (as of Godot 4.5)\n\nWith the release of **Godot 4.5** (stable, released around mid-September 2025), significant strides were made to improve accessibility: ([heise.de](https://www.heise.de/en/news/Game-Engine-Godot-4-5-with-Screenreader-support-and-Stencil-Buffer-10651078.html?utm_source=openai))\n\n- Godot integrated a library called **AccessKit** to provide accessibility infrastructure for its UI toolkit. ([godotengine.org](https://godotengine.org/releases/4.5/index.html?utm_source=openai))  \n- This adds *experimental screen reader support* to many UI elements, particularly the *Control nodes*, and allows binding behavior of all types of Nodes. ([heise.de](https://www.heise.de/en/news/Game-Engine-Godot-4-5-with-Screenreader-support-and-Stencil-Buffer-10651078.html?utm_source=openai))  \n- Editor components such as the **Project Manager**, **Inspector**, and \"standard UI nodes\" have been made accessible to screen readers. ([godotengine.org](https://godotengine.org/releases/4.5/index.html?utm_source=openai))  \n- There is an editor setting called `interface/accessibility/accessibility_support`, which controls whether accessibility support is enabled automatically (if a screen reader is detected), always active, or fully disabled. ([docs.godotengine.org](https://docs.godotengine.org/en/stable/classes/class_editorsettings.html?utm_source=openai))  \n\nSo, certain core parts of the Godot editor *are* now readable by screen readers, and some configuration is available to tweak this behavior depending on what assistive tools you're using.\n\n---\n\n## \u26a0\ufe0f What *is not yet* fully accessible\n\nHowever, it\u2019s important to understand the limitations; the node editor is **not** yet fully screen-reader friendly:\n\n- Support is still **experimental**. Many parts of the editor are not yet accessible. ([godotengine.org](https://godotengine.org/releases/4.5/index.html?utm_source=openai))  \n- As of Godot 4.5, **only parts** of the editor interface are speaking friendly: the Project Manager, Inspector, and standard UI widgets. The deeper node tree / node editor features are *not* yet reliably accessible. ([godotengine.org](https://godotengine.org/releases/4.5/index.html?utm_source=openai))  \n- In prior versions (Godot 3.x and before), the editor was basically invisible to screen readers \u2014 menus, buttons, node trees would not be detected or announced. ([github.com](https://github.com/godotengine/godot/issues/58074?utm_source=openai))  \n- A plugin developed by community members (\u201cGodot Accessibility Plugin\u201d) adds some editor-speech and behavior, but it is not enough to allow full development work inside the editor if you can\u2019t see. ([github.com](https://github.com/lightsoutgames/godot-accessibility?utm_source=openai))  \n\n---\n\n## \ud83d\udd0d Node Editor Specifics\n\nWhen you talk about the **node editor**, you usually mean:\n\n- The *scene tree* (hierarchy of nodes)\n- The node selection, adding/removing child nodes, reordering them\n- Panel specific to nodes (e.g. properties, signals, script attachment)\n- Graph-type editors (visual shader editor, etc.)\n\nHere\u2019s what I found specifically for the node editor:\n\n- **Scene tree navigation**: only partially accessible. The node tree itself is a custom UI, so many nodes (tree items) may not be announced (or be very confusing) by screen readers. ([github.com](https://github.com/lightsoutgames/godot-accessibility?utm_source=openai))  \n- **Dialogs for adding nodes / selecting node types**: often non-accessible or very poorly labeled, so screen readers may not announce fields or buttons inside those dialogs. ([github.com](https://github.com/lightsoutgames/godot-accessibility?utm_source=openai))  \n- **Node properties / inspector**: This is one of the more accessible parts; screen readers can read labels in the inspector panel and some properties. But some custom controls may still be invisible or lack meaningful accessibility labels. ([heise.de](https://www.heise.de/en/news/Game-Engine-Godot-4-5-with-Screenreader-support-and-Stencil-Buffer-10651078.html?utm_source=openai))  \n\n---\n\n## \ud83d\udd2d What\u2019s being worked on & what to expect\n\n- Further development is ongoing. Godot 4.5 introduced many improvements, but also explicitly states that **accessibility for the editor is still not complete**. Future versions may fill in missing pieces. ([godotengine.org](https://godotengine.org/releases/4.5/index.html?utm_source=openai))  \n- Issues and pull requests are active around expanding screen reader compatibility (for example PR #76829 mentioned in forums). ([reddit.com](https://www.reddit.com/r/godot/comments/18iirlj/accessibility_in_godot_engine/?utm_source=openai))  \n- Plugins/extensions for accessibility are being built by the community (like \u201cgodot-accessibility\u201d) to add additional features, speech feedback, etc. These are helpful but aren\u2019t substitutes for built-in support yet. ([github.com](https://github.com/lightsoutgames/godot-accessibility?utm_source=openai))  \n\n---\n\n## \ud83e\uddee Bottom line\n\nAs of now (Godot 4.5):\n\n- Yes \u2014 *some* parts of the node editor are accessible via screen readers. You can interact with the Project Manager, the Inspector, some UI controls, and possibly navigate to some nodes in the scene tree in a limited way.\n- No \u2014 it\u2019s not yet possible to fully use the editor (build a whole scene, work in the node editor, visually place/arrange nodes) **only** via screen reader with confidence. Many essential workflows are still inaccessible or very awkward.\n- It\u2019s best used in combination with other tools (external text editor, command line, community plugins) if you rely entirely on screen reader support.\n\n---\n\nIf you like, I can help put together a checklist of what\u2019s currently usable in your version of Godot (based on your OS etc.), or help you find the best workflows or tools that make Godot more usable for screen-reader users. Would you want me to do that?"
    }
]