I spent a lot of time in DOS and still do all my Linux work in the terminal, but when you're working with other people, being a total outlier and refusing to interface with a GUI seems a silly move to me. there are some tasks, such as web browsing, editing audio, which I've just never found comfortable from a command line. Windows and mobile screen readers have evolved to work with a GUI, the WIMP terminology is almost WIMK nowadays because 99 times out of a hundred i can use the keyboard in place of the mouse, and of course on touchscreens the finger does that anyway.
Undoubtedly, when visual interfaces were new, screen access tech lagged behind and the CLI remained simpler. These days, to shut ourselves in the past would I think do more harm than good. I'm not against a CLI for tasks where they are used, I'd never want to administrate my servers or databases visually. But equally, there are things where a window works best.

i much prefer a text based environment over a graphical one, any day. although i am still just as fast as (if not faster than) any standard windows power user, i feel most comfortable at a command or terminal prompt. as a network administrator, it's so incredibly easy to issue commands on a windows command prompt or powershell instead of chasing down unlabeled buttons buried within menus. tending to linux servers via ssh or modifying sql databases is a breeze at a terminal screen because again, you're not chasing down buttons or sifting through rows and columns of irrelevant info. i can filter out what i don't want to read and have important information front and center with some clever search strings.

console cowboy for life

It might be just me, but I don't like CLI much. It needs too much writing and memorizing commands and flags. It's very accessible, but I think using a good, accessible GUI is faster, easier and more intuitive to use. For example, I'm learning to use git. There are so many commands and flags that I needed to put them in a text file so I wouldn't forget them later. If it was a GUI environment I would just open the menu and choose the appropriate option that is there.

I used to be a heavy text console user back when I had sight. At one point in my life when I felt like using Linux exclusively I only ran a graphical user interface because of the web browser, so I do have a lot of experience. However now that I'm blind I prefer the semantics of graphical user interfaces when they work properly with screen-readers. I don't shy away from text consoles and do use them a lot when I code, but everything else I do using graphical user interfaces and don't think I'm changing my mind any time soon.

A problem that nobody mentioned with text-based applications is that many of them use ncurses, which is a library designed to render basic user interface elements such as dialogs, buttons, text boxes, scrollable lists, and so on in text terminals, and that makes them quite annoying to navigate because it's just text without any semantics that the screen-reader can recognize, so I have to move the screen-reader cursor up and down the terminal to find the information I'm looking for, hope that highlighting something makes a change that can be picked up by the terminal and announced by the screen-reader, and hope that I didn't miss anything important. Vim, an editor that I used a lot back in the day, is one such application, and since I'm yet to find an accessible graphical user interface port, I had to stop using it completely.

Finally, I have a problem with long output in text consoles, because the screen-reader cursor positions itself at the text caret by default, which forces me to move the cursor up a lot to find the command prompt where I typed the command and begin reading from there. Rust's error messages and the output of manual pages are two examples where this annoys me. I do have a solution for this, which is piping the output of some commands to TextMate, but even this is not very comfortable since I have to redirect all stderr output to stdout in some cases while in other cases I have to pipe the output to `col` in order to remove terminal controls, and it also requires me to install `rmate` and all of its dependencies on any remote machine or even local container where I have to edit files. Apple's Terminal has commands that allow for quickly jumping from command prompt to command prompt, but unfortunately these commands do not cause the screen-reader's cursor to be moved so they are of no use to me.

Just like with graphical user interfaces, there's still a lot to be done when it comes to bringing comfort to blind users in text consoles. It's possible to use them, but it's not an experience that I enjoy.

Personally, I would disagree - having used GUI elements for as long as I can remember even having had no sight whatsoever, I can't understand the constant advocation for terminal usage as a daily driver unless you've been permanently locked into using it.

I could be, if you have a screen reader that reads the console properly. NVDA doesn't read it so well these days, especially in Windows terminal. ConHost.exe works well though, lol. But TDSR on Mac and ChromeOS work well though.

I think the guis have gotten pretty good. I think you should be versed at both. I am pretty new to the terminal and such. Come from more of a user IT end of things