Re: [w3ctag/design-reviews] Review Accessibility Object Model (#134)

OK, coming back to this review! TPAC was a great chance to sync up, so thanks for your time there! Some point-by-point follow-ups on your last comments:

> After recent discussions, we also plan to surface InputEvents for the AT actions which would cause keyboard events to fire: https://gist.github.com/alice/570307ab24765de14837be1da49e1f98 ("Option 1" in that write-up.)

I participated in the discussion. Outcomes to surface as `input` events' [`inputType`](https://w3c.github.io/input-events/#events-inputevents) sounds great.

> The shape of the Custom Element API is being discussed in w3c/webcomponents#758 and I think will be discussed more at TPAC.

Yep, that was a spirited discussion. I'm hopeful that the `ElementInternals` will end-up with the right usage pattern, but that does sound like the right home for this stuff.

> Accessibility tree nodes have position attributes which are useful for multiple reasons:
> * drawing outlines for sighted users to keep track of where AT focus is
> * supporting "touch exploration" modes
>
> I'm not sure what you mean by "legacy" - what would the non-legacy version be?

I had this question answered when we chatted in-person. My understanding: if there will be a virtual a11y node, it must act as proxy for all the relevant state that would otherwise be on a regular Element. "Legacy" was just my way of grouping all pre-existing CSS-OM APIs. I hope we can help with the use-cases, but wondering if many of them can be addressed by the so-called "searchable invisible DOM" (which needs a better name BTW). Seems as if the virtual a11y node and related standarization of the a11y tree is still a way off, so not going to worry too much about it right now.

> ```js
> console.log(banana.role);            // empty string - no ARIA role is set
> ```

Ah, this is not what I expected. I thought the role IDL attribute might work more like input's `type` content attribute and IDL attribute (e.g., how the IDL attribute always returns the "computed" value). For custom-elements much of this might be made more sensical with the ElementInternals, but for other elements, I'd like to have the IDL attributes reflect/compute as much as possible--however I understand that might be much more complicated for certain types and there's an argument for consistency. But for role, I would really like to see that return a computed value!


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/134#issuecomment-434384545