I see your point, but nesting has to be expressible somehow with ascii. I suspect this is better addressed by an IDE or a customized screen reader.
BTW, I find the parens in Lisp to be hopeless even as a sighted person, and even spending considerable effort trying to format it to make it clear. It's one reason why I customized my text editor with a "matching paren" command, which is a life saver. (It also matches braces and square brackets, even #if/#ifdef/#ifndef/#else/#elif/#endif.)
Your comical bumbling with basic code editing is difficult to grasp.
Auto-indentation and parenthesis matching has been a standard feature of any decent programming editor for decades.
Vim matches parentheses and C #ifdef out-of-the box, and indents Lisp. It did all that very well in the year 2000 when I started in Lisp.
A parenhesis matching command (the % key) has been in Vi since the 1970's, and the same is true of the Lisp mode (:set lisp) that handles the bulk of the indentation semantics. When you load a .lisp file, Vim turns on Lisp mode. That ancient invention is what does the indentation.
Nobody spends "considerable effort" formatting Lisp. Not even buffoons like me who use a Vi derivative, and who are ridiculed by Emacs users.
Oh I know I didn't invent paren matching, though I did add it to my editor in the 80's. I can claim invention of #if matching, though, as I implemented that in the 80's, too. Don't know of any prior art on that.
Vim was vi at the time :-) and didn't have a Lisp mode at the time that I was aware of, and I haven't messed with Lisp since the 80's.
And yes, I still find Lisp difficult to read, regardless of how its formatted. Infix reads much better for me.
BTW, I find the parens in Lisp to be hopeless even as a sighted person, and even spending considerable effort trying to format it to make it clear. It's one reason why I customized my text editor with a "matching paren" command, which is a life saver. (It also matches braces and square brackets, even #if/#ifdef/#ifndef/#else/#elif/#endif.)