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

Accessibility tree #166

Open
xfq opened this issue May 21, 2021 · 3 comments
Open

Accessibility tree #166

xfq opened this issue May 21, 2021 · 3 comments
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response.

Comments

@xfq
Copy link
Member

xfq commented May 21, 2021

From #162:

Is it possible to expose an accessibility tree for accessibility APIs to provide a representation that can be understood by assistive technologies (such as screen readers)? Can developers use JavaScript to modify the accessibility tree in a MiniApp?

@xfq xfq added the a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response. label May 21, 2021
@xfq
Copy link
Member Author

xfq commented May 21, 2021

@xfq
Copy link
Member Author

xfq commented May 21, 2021

Related discussions: https://www.w3.org/2021/05/20-MiniApp-minutes.html#t03

@zhangyongjing
Copy link
Contributor

We can for sure define a common set of a11y attributes for UI components based on the reference implementations as listed above. For this we need to start the UI component spec first (In CG?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y-tracker Group bringing to attention of a11y, or tracked by the a11y Group but not needing response.
Projects
None yet
Development

No branches or pull requests

2 participants