James Craig
James Craig
Also, for Axe-Core or other audit frameworks specifically, there is already the ability to get some or all of what you need in a test-only context by writing a wrapper...
Also to discuss these [WPT test results](https://wpt.fyi/results/svg-aam/role/roles.tentative.html?label=pr_head&max-count=1&pr=50555)...
and these remaining [interop-accessibility task issues](https://github.com/web-platform-tests/interop-accessibility/issues/?q=is%3Aissue%20state%3Aopen%20SVG)
@jcsteh wrote: > Would [the "ax node from element" getter] return an axId or an accessible node snapshot? That's an open question. Initially I thought either "ax node from element"...
Possibly need a way to register for outward notifications too… e.g. When a live region changes.
Spoke with @OrKoN today who mentioned a related use case for accessibility in webdriver... possibly https://github.com/w3c/webdriver-bidi/issues/443
TPAC-related updates summarized in https://github.com/WICG/aom/issues/197#issuecomment-1719393870
Most relevant from above linked notes: > Interesting point from @jgraham that most proposed features ("get axnode from el", "get axnode by id", "synthesize AT event") could be in both...
Actually we could even remove (3. Trigger/Synthesize Accessibility Event/Notification) from the MVP, but it seems achievable and useful, so I'm keeping it in the short list for now.
Potential error codes: code | name | description -- | -- | -- 404 | stale accessible node reference | A command failed because the reference accessible node is no...