On Tue, 11 Jun 2019, derek riemer wrote:
Does this actually use the dom, or does it use NVDA's view of the accessibility tree? DOM nodes are not always able to be mapped onto the accessibilityAlthough for this add-on's purposes, they probably shouldn't exist either.
The whole point of the add-on is to tell a developer what things look like in as much detail as possible, right?
So invisible DOM elements are irrelevant to that task. What other examples might there be, of times the DOM is out of sync with the tree?