aom
aom copied to clipboard
WICG
Accessibility Object Model
## Phase 1 topics - Status of [ARIA reflection](https://github.com/w3c/aria/issues/691) discussion? - Options for [`Element` reflection](https://github.com/whatwg/html/issues/3515)? - `fooElements` or just `foo`? - if `fooElements`, what reflection is there between `fooElements` and...
@alice and others have mentioned the Custom Elements use case. Component creators want to define the default accessibility semantics yet still allow authors the ability to override the default semantics...
@alice asked that I list each ARIA attribute as an exercise to determine how it should (if it should) be conveyed on virtual AccessibleNodes. **Note 1:** This issue bears no...
https://wicg.github.io/aom/spec/phase2.html says: > Accessibility input events go through capture and bubble phases, just like DOM events. The only difference is that the capture and bubble phases happen entirely in the...
At least, it seems that's a 1:1 relationship that will never change.
Stage 4 of the proposal will allow for the "ability to walk the computed tree structure including virtual nodes" but has very little to say about how accessibility nodes can...
[`accessibleNode` IDL attribute](https://wicg.github.io/aom/spec/#dom-element-accessiblenode) on `Element` interface should have either `[SameObject]` or `[NewObject]` depending on which semantics is desirable (presumably `[SameObject]`).
The section [2.6 Validation](https://wicg.github.io/aom/spec/#validation) says the following: > Upon setting a property of AccessibleNode, no validation is done. The user-provided value is simply stored, converted to the appropriate type via...
The definition of [`AccessibleNode` interface](https://wicg.github.io/aom/spec/#accessiblenode) mentions "AccessibleNode properties" but this term is not defined anywhere. Perhaps it's referring to [IDL attributes](https://heycam.github.io/webidl/#dfn-attribute) of the `AccessibleNode` interface. This should be clarified.