James Craig

@minorninth wrote: > …in Phase 4 we'll add a separate async mechanism to explore the computed tree (which would include text nodes). Okay.

Defined in ARIA https://www.w3.org/TR/wai-aria/complete#aria-autocomplete

It's not clear to me how this would work with possible inward-pointing references (e.g. aria-activedescendant) in addition to the outward-pointing references like aria-labelledby.

> that can works exactly as described above, where the internal element receiving the focus is auto-wired as the active descendant There are a number of IDREFS-valued ARIA attributes that...

Changing a static element (heading, cell, etc.) to an editable node (textfield, etc). The ideal way would be to use a new node, but many web authors just add a...

If I may, I think Domenic (@domenic) is asking for use cases to _reassign_ an element's role once it's already been explicitly set. Dominic (@minorninth) is responding with use cases...

But my interpretation may be incorrect.

@domenic wrote: > But in discussions with @slightlyoff, he was unsure on the value of reassigning an element's role, and noted that if this was not allowed, a very different...

@domenic wrote: > For the indirect variant: any Esc keypress events on iPhones automatically indicate to the site an AT user, since Esc keypresses are otherwise impossible there This could...

[Web Platform Design Principle 2.9](https://w3ctag.github.io/design-principles/#do-not-expose-use-of-assistive-tech) states, “Don’t reveal assistive technologies are being used.” Because of this, AOM direction has been to avoid any distinguishing event difference between AT uses and...