Requesting detailed documentation regarding what causes NVDA to announce the word 'document'

[soehlerSF]

Is your feature request related to a problem? Please describe.

No problem in particular: we are a software-as-a-service that provides capabilities for customers to create their own lightning components. Sometimes customers will configure a component that, when tabbed to (or focused), NVDA will read out 'document'. We're unable to provide a reproduction of this, but we suspect that it has to do with the presence of the html element <article> in relation to other elements where focus is passing from one article to another. We're unable to reproduce this consistently.

Describe the solution you'd like

We're hoping NVDA can update their documentation to indicate under what specific circumstances 'document' is read aloud, with emphasis on what configuration causes this to occur and with what elements. The reason this is important is because customers are comparing this product with the functionality of MacVO (for OS and browser consistency in testing) and MacVO does not seem to announce document focus swaps like NVDA does, so a better understanding of what technically causes this announcement would be of great help.

Describe alternatives you've considered

n/a

Additional context

n/a

[LeonarddeR]

@soehlerSF Thanks for your question. Since it is strictly spoken not an issue with NVDA, I converted it to a discussion. The reason why I believe so is that NVDA in most situations just announces what it is told to do so by the Browser.
I'm pretty sure articles aren't announced as document per se.
I'm afraid we can't help you further if we don't have access to the particular component. Basically though, every document rendered in a browser is supposed to be a document. So for example, if you are in Firefox and tab from the browser controls into the page, NVDA will announce the page title followed by the word document. When you right click and inspect accessibility properties, you will notice that the root node of the accessibility tree is of type (or rather role) document.

[seanbudd]

Let's redirect conversation back to #18642 for now. Can you share there what the concern clients have with NVDA reading "document"? Screen readers vary in behaviour and users prefer a variety of different verbosity levels. The behaviour of NVDA evolves over time, and depends on a large amount of user configuration. It's not extremely feasible for us to maintain thorough public documentation of exactly everything NVDA does, particularly to this level. I think this behaviour can be toggled off by "report articles" if you wish to disable it.

In #18642, can you please let us know:

• if we are violating any specs with this behaviour
• what behaviour you expect
• some sample steps to reproduce
• what the concerns are with the behaviour from the steps