JAWS-test

> Additionally, there is no way to read through the labels character by character with most screen readers if you apply aria-hidden. If this is an important argument, it should...

> Consider that example with JAWS. If you use aria-hidden, then you will only hear the label if you have smart nav on, or if you tab into the field,...

> It is discouraged. One of the cardinal rules of naming is to prefer visible content for accessible names. Unfortunately I did not find this statement in the mentioned documents

> Not sure how you are testing this snippet of code With JAWS 2019.1907.42 and Chrome 76.0.3809.100. I have tested it both in this form (thanks to tag omission almost...

> These are opposite situations. I don't understand it at all. From the point of view of a blind screen reader user, hidden and aria-hidden is the same. However, I...

Regardless of whether it is recommended or not, I would still find an explanation of hidden nodes useful. For which elements are they output? * aria-labelledby * aria-describedby * label...

Please use: https://github.com/w3c/accname/issues/57#issuecomment-529048546

Sure, I'm happy to do that. Since I don't speak English and only translate with google translator, someone would have to revise the wording afterwards.

@mcking65 > Do you agree that these are the changes we need to make? Yes, I agree. > I think most of your confusion comes from reading the AccName spec...

What do you mean by "both screenreaders" - there are more than two. I can confirm the problem for NVDA. This is clearly a bug of NVDA and should be...