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 #185

Open
shzeshzeshze opened this issue May 28, 2021 · 0 comments
Open

Accessibility #185

shzeshzeshze opened this issue May 28, 2021 · 0 comments

Comments

@shzeshzeshze
Copy link

I'm coming from the Daedalus repo and yesterday I posted an issue there concerning it's accessibility. After forking it and running mainnet locally I see most of the UI is based of react-polymorph.

What are the team's thoughts on adopting and implementing some sort of accessibility standard? As a recommendation I would suggest WCAG 2.1 at AA conformance level. This WCAG quick reference guide is a great way to find all the different success criterion, why each is important, and success and failure modes for each.

I have not had time to evaluate each component individually but one that stuck out in my mind were the Select components (in react-polymorph) that make up the ProfileSettings component (in Daedalus). All of the labels are hardcoded with aria-hidden="true" and role="presentation" when in fact they are quite important to screen reader users.

I really like both of these projects so far and would love to see improved accessibility so that the UI in the applications IOHK puts out provide an equivalent experience to the widest possible audiences.

Thanks for your time.

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

No branches or pull requests

1 participant