Oh hey, totally blind Linux user here. Not professionally yet (hoping that will change soon) but I do use Linux servers. Currently, my workflow is to use the SSH client in the Windows version of Git to manage everything remotely, even VMs on the same host I'm working on. As someone else mentioned, there is a Linux graphical screen reader, Orca, but the quality is not great. It takes very little to cause it to go nuts and either freeze or behave unpredictably, it can be pretty laggy/unresponsive, and just feels really buggy in general. There are also really annoying issues with how it interacts with every GUI terminal emulator I've tried. There is a kernel-space console screen reader called speakup that I can use in a pinch and which works reasonably well, but it's old and I think rarely gets updated (there was an issue two years or so ago where reading by word would cause a kernel panic, so yeah, you get the idea) and I frankly hate to listen to ESpeak (the only practical voice synthesizer option) for long periods of time, like it physically gives me a headache. I apologize for all the negativity, but those are the reasons I use Windows as my desktop OS; NVDA is where it's at for screen readers. As concerns large amounts of text, I either do what you mentioned and output to a file and use grep, or sometimes pipe it to less so I can scroll by page that way, since regular console scrolling is just awkward for me; could be that I'm doing something wrong there. For cases where I need to watch output in realtime it gets trickier; I generally turn off the "caret moves review cursor" and sometimes "report dynamic content changes" settings off so I can keep focus on what I'm examining and not get interrupted by new lines, and speed up speech to the limit of what I can understand (or sometimes beyond, if I don't need to know precisely what I'm looking at) in order to try and keep up with it as best I can. Probably still don't have the flexibility I would with vision, but it works okay. I'm unsure what I might need to change when I work with Linux in a professional setting; ncurses-based applications where the screen reader needs to follow the highlight are a particularly annoying problem. Sorry for the wall of text and that I'm late seeing this, but I hope you found something in here interesting.

Either grep for specifics or import into something like sqlite and write sql queries to extract what you need. Those approaches have worked for me at least.

There’s a screen reader on linux called orka, I think that’s how you spell it, perhaps that can help you.

I’ve not used it enough to help you, sorry.

Looking to get into pen testing/sysadmin work and that's basically what I do. Terminal stuff is just much easier and faster than fucking with a GUI, especially when using a screenreader.

I have no idea what we are talking about, but I feel like the intentions are good. Are you saying you are looking into ways to make your work more accessible for people with visual impairments, or that you want to get involved with teaching people with visual impairments?