Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTML-AAM: should we have some general language for sub-doms? #141

Closed
cyns opened this issue Jan 12, 2016 · 1 comment
Closed

HTML-AAM: should we have some general language for sub-doms? #141

cyns opened this issue Jan 12, 2016 · 1 comment
Labels

Comments

@cyns
Copy link
Contributor

cyns commented Jan 12, 2016

Canvas has an author-supplied sub-dom, which also maps into the accessibility api tree
The audio and video elements can have a whole tree of children if @controls is present.
Should we add some general language to the document on how to handle these situations?

Here's what we have for UIA for canvas now. It seems inadequate.
Control Type: Image
NOTE: subdom elements will be mapped separately.

@jasonkiss
Copy link
Contributor

This issue was moved to w3c/html-aam#3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants