Aaron Leventhal

> I'm wondering if author-supplied markup is the best way to solve this synonym problem. Making the voice access feature a bit smarter, so that it either knows common synonyms...

For the discussion. Search engines currently handle synonyms and there are synonym libraries available, such as https://www.npmjs.com/package/synonyms Apologies to those working on this, but I'm concerned that it won't get...

Actually, Chrome divides things into a few cases. We should look at codifying it. See AXObject::SupportsNameFromContents() here, I think it's reasonably easy to understand even if you don't know C++:...

Matt, why do we need the focusable rule? Would it not be enough for the source to be visible, and the target to be visible & clickable? To activate the...

The default tabindex for a textfield is 0. That makes it both focusable and tabbable The tabindex=-1 overrides this and makes it not tabbable, but it's still focusable via both...

Chrome's current rule of propagating disabled to focusable descendants is a nice clean, easy-to-implement rule that works. I don't see the gain in propagating disabled to unfocusable descendants. This issue...

I believe `` should just be the inverse of aria-labelledby. It should work the same way. If the root is hidden, the name is still computed for the related control.

Hi Jamal! Having the value attribute filled with the URL is a legacy windows MSAA thing, we do that in the downstream windows layer, similar to how the MSAA value...

Similar to what James Teh mentioned, I don't believe this requires anything on the Chrome side. Chrome implements aria-errormessage and aria-invalid via the CORE-AAM spec, e.g. relations IA2_RELATION_ERROR and IA2_RELATION_ERROR_FOR.

+1 This would have an easy adoption path for existing content. And it falls back to the current behavior, which is great too.