I'm addressing this thread to developers, mainly because I use my MacBook for work, and that means I have to read a lot of code with the browser, and have to deal with websites like Github, Gitlab and StackOverflow, which means a lot of code blocks.
For the past two years, I've mostly used VoiceOver and Safari, but I've been trying out Google Chrome and ChromeVox recently. I'm finding that neither of them seem to be as easy to work with as the flat system that Windows screen readers provide, but I wonder if you have figured a way of making this easier. I'll explain what I mean.
VoiceOver, in Safari, seems to be jumping from object to object. That means if you have a block of code where line endings are important and you need to look at the code character by character, the behavior is not predictable. Sometimes using the arrow keys work, and sometimes they don't.
When using Chrome and ChromeVox, you have to keep switching between the granularity levels, which is too much work. The flat keymap also has a lot of commands using control, but on the Mac I've found the best combination of ChromeVox keys to be the default Command+Ctrl, which makes those keys stop working.
Another issue is Google Docs: the level of accessibility varies a lot based on what you're using, and none of them seem to be 100% usable when collaborating with sighted people.
Any ideas welcome!