This 100%. There's the tree view and tools to make sure tags are there. Some tools to check that the site is keyboard navigable. But I still find I have to go t

This 100%. There's the tree view and tools to make sure tags are there. Some tools to check that the site is keyboard navigable. But I still find I have to go through with a janky screen reader plugin to make sure (the best I can) that the site really works for screen readers. The main problem is that as a sighted user, I'm used to scanning a site and discarding tons of superfluous information. If all that is read to someone it is tedious and very hard to navigate with. In many ways, the developer needs to think of an entirely new UX for a user on a screen reader. Hiding repeated elements is one of the biggest things to be done. Do the items for the screen reader have context is another. On a graphical page a button with the word "GO" might make complete sense. It makes a lot less sense when being read to a non-sighted user after listening to a bunch of other elements.