I don't have this issue, just checked, it both read, and is navigable if tabbed away from. I'm on version 1803 of windows 10. I do run NVDA snapshots, in particular, the Next branch, so this may be why, still, if you haven't updated to 2018.2, now might be the time. Also, if that doesn't help, go to settings and set the debug level to debug, then see if anything shows up that looks suspicious in the log having to do with not being able to read control states and shit, specifically , look for anything that shows iaccessible, MSAA, or UIA, I don't know which it would use because I'm fucked if I understand it, but yeah.
If there is shit in the log, create a Github issue and detail the issue with the log section relevant, but make sure you haven't typed any sensitive information, because when NVDA is on input / output or higher in debug mode, it collects key presses and shit, so remove that or just chop away the section relevant to the problem. I'd set it back to info too when I was done so its not making huge ass logs.
Facts with Tom MacDonald, Adam Calhoun, and Dax
End racism
End division
Become united