I don't need text to speech, but when I'm writing code with deep nesting one of my practices is to leave a comment at the end of each block relaying the block I'm exiting. For example:

void myFunction()
{
while(globalBool)
{
if(globalFlag)
{
anotherFunction();
} // end if(globalFlag)

else sleep(1000);
} // end while(globalBool)
} // end myFunction

This might be more convoluted in SQL than in C style languages, but it could be a style that could help.

Wow! It looks like a lot of blind coders are here.

I use the NVDA beeps bit as well for Python but also make use of the spoken indent level sometimes. It’ll announce “4 space” or “12 space” and so on. There’s also a few VS Code extension called Indentnav that lets you jump to blocks of indentation, jump to the parent or child blocks, and move only within the same block. Think there’s an NVDA add-on that’s needed to make it work properly though. When I’m back at work tomorrow I can get the specifics if you’re interested.

Some editors have the ability to match pairs of parens, brackets, braces, and quotes. In TextMate 2 on MacOS, for example, pressing Control+Up/Down (requires disabling the global functionality assigned to these shortcut keys) inside a pair of parens, brackets, braces, or quotes will jump to the enclosing opening or closing character respectively, reading the line on which the cursor landed in the process. Visual Studio Code, which as I understand it works well with screen-readers on Windows, can do that as well.

You can have it speak as well as beep, which helps a lot. If you don't want this to happen whilst you're doing other things, you can make a configuration profile for your text editor of choice. Beyond that, it's just a matter of getting used to it. I'm not aware of a more efficient solution.

Apart from what others have said, I think modifying the query's structure can help. I've found over the years that following specific rules really helps me keep track of things. For instance, every where condition, every join, and every group or order by is on its own line. Subselects have the opening parenthesis on the line where they start, then all their code indented on subsequent lines. For instance:

```
select column1, column2, s1.column4
from table1
join table2 on table2.ptID = table1.id
join (
select someColumn as column4, id
from table3
) sub on sub.id = table1.id
where table1.id in (1, 3, 7)
order by table1.id
```

I sure hope that example makes sense. It's early, and I'm writing this on my phone. It should give you an idea of the way I structure things, at least. Of course, you don't have to use my rules. My point is that making rules which make sense to you, and which you always follow, can really help to clear up what a query is doing.

I'm not blind, but I am a developer. I wonder if this $1 idea has ever been produced commercially. The link is a .pdf, I hope it's readable.

Apart from that, I would say that keeping proper track of nesting is annoying whether you can see or not, and relying on indentation to guide you can bite you in the butt, because in many languages the whitespace is irrelevant. So, generally speaking I add comments to at least the closing of a nested block.

Braille. Always braille.