aom
aom copied to clipboard
WICG
Accessibility Object Model
I've been playing around with AOM (great job, by the way!) and thought it would be cool if I could automate some `getComputedAccessibleNode` checks with [Puppeteer](https://github.com/GoogleChrome/puppeteer). I was expecting that...
Hello, May I use this image and maybe the one with the bee and/or the checkbox on some slides I am making to train our developers in an understanding of...
As mentioned in the accessibility tree breakout session at TPAC today, (filing as an issue as requested by @alice ) I think there's a use case for information flowing from...
There are certain situations where the `lang` attribute is not honoured by screen readers e.g. alt text of an `img` which has a `lang` attribute. Is it possible for AOM...
https://github.com/w3c/webcomponents/issues/758 raises some doubts about using `ShadowRoot` to encapsulate semantics for web components. I've written up two versions of some spec changes to try and formalise some of the ideas...
[W3C Accessibility Object Model, Phase 3 Unofficial Draft 17 July 2018](https://wicg.github.io/aom/spec/virtual-accessibility-nodes.html) has a broken link to the Explainer URI in the Abstract.
Is there any reason why virtual AccessibleNode would need to be ever recreated during Node (or ShadowNode) lifecycle? If not, then IDL should reflect that by [SameObject] keyword https://heycam.github.io/webidl/#SameObject.
Re-opening this - frustratingly there is no "undo" for a merge, just a git revert. See #118 for earlier discussion. @cookiecrook @minorninth let's discuss more here.
## Validation options Note: these are by no means mutually exclusive, and we may want a combination of several. 1. **No validation** ```js el.accessibleNode.role = "banana"; el.accessibleNode.role; // "banana" ```...
As discussed, we would like to propose that we have a common pattern for all non-tree relationships (possibly including `htmlFor`): ```js el.htmlFor = 'id-for-my-input'; el.htmlForElement = myInput; // overrides htmlFor...