aom
aom copied to clipboard
WICG
Accessibility Object Model
https://a11y-api.github.io/a11y-api/spec/ 06 September 2016 Just a few simple typos: - Accessiblity - AccessibileNode - a AccessibleNodeList ( an ) - an relationship ( x 2 ) - happend - labeledBy...
E.g. it seems strange that you allow negative column count, or that column counts > 2^32 wrap back to -2^32. See also https://w3ctag.github.io/design-principles/#numeric-types
These are both Map like structures, so they should perhaps be defined as: ``` JS interface AccessibleNode : EventTarget { attribute DOMString role; readonly attribute AccessibilityMap attributes; readonly attribute AccessibilityMap...
Can we please nave these things differently? It's quite confusing, particularly as all DOM nodes are by definition accessible.
In relation to: ``` JS partial interface AccessibleNode { attribute typename attributeName; }; ``` The spec says: > Setting the attribute must invoke setAttribute() with the first argument being the...
This is really excellent and very well explained. I think it will address the pain points currently experienced. Adding imperative programmatic access opens the AT API up nicely. I did...
It seems plausible to me that they exist, but I can't think of any... This informs a number of the existing design choices, e.g. how certain properties only work when...
> In particular, setting an AccessibleNode's labelledBy or describedBy attributes will have no effect on its accessible name or description. Set the label and description attributes directly if you want...
``` js var axVirtualButton = new AccessibleNode("button"); axVirtualButton.label = "Enable Audio Descriptions"; axVirtualButton.offsetWidth = 224; axVirtualButton.offsetHeight = 72; ``` could become ``` js var axVirtualButton = new AccessibleNode("button", { label:...
This might be related to #21 and #22. But both of them store the value in the source, which seems like it would cause collisions.