Scott O'Hara

seems to me the validator should be calling both out then. Using JAWS and Edge/Chrome, for example, I can only find a single image on the page, and it's announced...

this does seem to be a quirk with how these are checked. since the nested table, which has the td elements with roles, is a role=presentation itself, this 'should' be...

yup, my apologies for not being more clear in that initial issue. rather wish people just wouldn't do this though. oh well...

yes, the 3 allowed values is what this should check for, and are what should be allowed here. if `aria-pressed` is undefined, e.g., `aria-pressed=""` or an invalid value, then ARIA...

similar to the other `dialog role=dialog` the rule would need to be modified slightly to ignore the redundant role that's applied to it, and just surface the warning instead.

not exactly. a `div` is not allowed a child/descendant of a `button` _element_ (the need for this requirement can be debated, but that's out of scope here) a `div` is...

>Well, at least JAWS and VoiceOver will treat role=button same as , which is the whole point of that role after all. they announce the role the same. They don't...

>Imo wherever role="button" is used one should be able to use its semantic equivalent `` instead and same rules should apply. Am I getting this wrong? Yes. Again, the no...

no. that's not what i've been saying. If you read the ARIA in HTML spec, you'd see that there are many rules for use of ARIA with HTML that **are**...

What value is consistency if the validation error isn’t actually an error?