Scott O'Hara

adding aria-label to listitems is properly throwing a warning. doing this can result in either the content of the listitem being ignored, or the aria-label won't be exposed. either way,...

these attributes should be allowed on an element which allows the article role to be set, or the article element itself. so that does seem something that needs to be...

no, and the information that describes that example explains why. also they are not separate elements, the list item has been given the option role, and the list element (ul)...

validator hasn't been updated to properly check this element - https://github.com/validator/validator/issues/1569

Regarding what screen readers do with levels beyond 6, [here's a test file](https://scottaohara.github.io/tests/html-headings/6plus.html) I put together back in October. tldr; seems the levels are correctly exposed at the platform level,...

I do think that the examples should better call out gaps, or implications for mobile (re: #420). Per Patrick's comment, >rather than just relying on the very high-level generic "mobile...

@Jym77 per your requesting my review - i personally dont' agree that it makes sense to designate `` as inapplicable because it's hidden from the a11y tree with display none....

i had written a response, but with @tombrunet's comment, i see that would just be going off topic... so i'll refrain. if i understand your comment, Tom, are you saying...

>add background note that stuff out of the accessibility tree still need to respect this but won't cause user problem will "wont' cause user problem" be qualified in this note...

Note: this behavior does not happen if the content referenced by `aria-describedby` is not injected into the page. There is something odd going on with JAWS and Chrome specifically where...