Something I learned from playing with NVDA just now is that our YouTube video embedding isn't that accessible.
I suppose it's because we use an iframe, but I don't think NVDA tells me it's a "video" at any point.
It's probably because I'm still getting the hang of NVDA, but the first time I reached a video, I think it just read something like "ungrouped element" and moved on to the next paragraph.
When I went back later, I was able to move through all the links in the embedded video, including the play button. Not sure why I didn't get them the first time.
Another thing I noticed: with math content, sometimes it just reads the math, and sometimes it announces the math as an "application" before reading it. I couldn't figure out how NVDA decides whether or not to do this.
I also discovered that if I hit the space bar after tabbing to a math element, it opens the MathJax menu. If I hit escape to get out of the menu, the keyboard shortcuts for NVDA (arrows, h, d) stop working.
But I suspect that some of these are problems that an experienced user of screen readers would not have.