aom
aom copied to clipboard
WICG
Accessibility Object Model
One of the major gaps in ARIA is that a custom control can't be manipulated via accessibility actions. For example, on almost all platforms, a native HTML slider can be...
- Finite vocabulary of a11y only events - target and bubble in a11y tree (not capture for now) - then fire fallback DOM event _if event propagation not stopped_ Need...
These properties seem extraordinarily out of place, and encroaching on the territory of CSS. What purpose do they serve? The spec gives no normative requirements for how UAs are supposed...
I think these should still be in the main DOM tree, not the accessibility tree. This reminds me of the old "intention events" proposal, which I cannot find. In general,...
The spec defines: ``` interface AccessibleInputEvent : Event { }; interface AccessibleSetValueEvent : AccessibleInputEvent { attribute DOMString value; }; ``` Firstly, it seems odd to just have `AccessibleInputEvent` as an...
Enabling "native" browser accessibility support has performance and memory implications. Simply setting or accessing the AOM should not do this. This needs to be clear in the spec.
Raising roleDescription (currently in future work) as an issue b/c "role description" is in ARIA 1.1 and implemented on Apple's iOS and macOS platforms. For example, in iWork (native), we...
The US vs British spelling thing is annoying. For an API like this, you could just treat the two as aliases, or have the single-'l' version throw if someone tries...
The spec has ``` js interface AccessibleSetValueEvent : Event { attribute DOMString value; }; ``` Event has a `detail` field that can be used for a similar purpose as well,...
This is similar-ish to Issue #4, which says that AT needs to be able to query focus, selection start & end, etc. in a canvas [or contenteditable] text editor. AT...
