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

Triage existing components for a11y best practices #342

Closed
bitpshr opened this issue Oct 31, 2017 · 1 comment
Closed

Triage existing components for a11y best practices #342

bitpshr opened this issue Oct 31, 2017 · 1 comment

Comments

@bitpshr
Copy link
Member

bitpshr commented Oct 31, 2017

Enhancement

We've been doing a good enough job at preserving good a11y practices (thanks largely to @smhigley.) We can do better though. Some components, like AccordionPane and TitlePane, don't support arrow key navigation. We should use this (large) issue to go through each component and add a11y as necessary, especially since this is a pillar of Dojo 2 widgets.

Package Version: latest

@bitpshr bitpshr mentioned this issue Oct 31, 2017
3 tasks
@kitsonk kitsonk added this to the beta.5 milestone Nov 6, 2017
@morrinene morrinene added rc and removed beta5 labels Nov 20, 2017
@kitsonk kitsonk modified the milestones: beta.5, rc.1 Dec 11, 2017
@smhigley smhigley added the Epic label Jan 17, 2018
@bryanforbes bryanforbes mentioned this issue Jan 17, 2018
3 tasks
@dylans dylans modified the milestones: rc.1, rc.2 Mar 1, 2018
@agubler agubler removed the rc label Mar 9, 2018
@dylans dylans removed this from the rc.2 milestone Mar 20, 2018
@tomdye
Copy link
Member

tomdye commented Nov 22, 2018

Looks like this has been done as all related tasks are completed

@tomdye tomdye closed this as completed Nov 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants