[miki123211]

Actually GUIs or websites, if done right, can be way better than anything that is text based. They include much more semantic information that a screen reader can use. For example, on websites, we have special shortcut keys to i.e. jump to next heading, table, landmark etc. We can even navigate within tables. This makes using most web/electron/chromium apps pretty easy. Most blind people prefer traditional win32 guis, but I actually don't. Problems arise when semantic information isn't provided, as in a web developer making the text whatever color is fashionable now and adding an onClick instead of using <button>. I don't see how a text-based OS would be different from that.

[mwcampbell]

Can you expand on why you don't prefer traditional Win32 GUIs?

[miki123211]

Web UIs can be used with my screen reader's search functionality and quick navigation keys. For example, in Spotify, which uses a web UI, I can do ctrl+ins+f, type rock, press enter and I'm focused on the Rock playlist. Similarly, in Skype, I can search for "audio call" etc. Some elements can also be reached pretty quickly with navigation keys. I think it's much easier to screw up a win32 gui than a web app. The non-web paets of Itunes are a good example. They're accessible, but all objects need to be reached by pressing tab, and there's a lot of objects. There's no semantic structure and no way to provide one. A website-like document would work better in this case.