At Paris F2F: Discussed this further (the computed accessibility node concept). There is a strong parallel to the problems we've seen in Style computation and read-back problems that have long been a sore spot for performance. In this respect, my idea to read the `role` value and have it imply a computation is probably not a good idea. We're assuming that the computation of a single a11y node in the tree involves potentially global (document-wide) searches to resolve things like element ids to element instances (for certain ARIA properties), etc., so this model of having an operation that returns a promise seems right. So, cudos on your approach. We do have some feedback on the approach to do the read-back, especially around locality, e.g., the requested a11y node should be more directly requested from the node of interest:
```js
banana.getA11yNode().then((n) => { console.log(n.role); });
```
--
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-434646622
Received on Wednesday, 31 October 2018 11:06:24 UTC