One nit to pick; Electron is just HTML/CSS/JS and accessibility can be as good or bad as any other website. As for the rest, I'm frustrated because you're part

One nit to pick; Electron is just HTML/CSS/JS and accessibility can be as good or bad as any other website. As for the rest, I'm frustrated because you're partially right but also kinda defeatist and that makes me sad. I went checking and found a long history of discussion about accessibility in Godot's GUI toolkit (because the Godot editor is built in the Godot engine). It's an active topic, spanning multiple tickets over years. Their stance has evolved dramatically over time, but they appear to be putting real effort into improving the situation. Here's what I think is the current tracking ticket: https://github.com/godotengine/godot-proposals/issues/983 https://github.com/godotengine/godot-proposals/issues/983 Accessibility isn't a feature of Godot...yet, but it's obviously something that's important for mainstream adoption of serious software, especially non-audio-visual experience software. And it's obvious that people in the community care and are both asking for it and working on it. If anything we need to keep doing this and revisiting it over and again and keep improving it, testing it, giving feedback, contributing. Because for as many applications that wouldn't benefit from this approach, there are as many that would. Maybe what the community needs is a real-world application which would benefit from these accessibility features to help drive adoption and development.