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: Authorization Screen and Google Docs Interface #31

Closed
csonnek opened this issue Mar 10, 2017 · 3 comments
Closed

Accessibility: Authorization Screen and Google Docs Interface #31

csonnek opened this issue Mar 10, 2017 · 3 comments

Comments

@csonnek
Copy link
Member

csonnek commented Mar 10, 2017

Moving here from our internal blog.

Had a user contact us (who is blind) in 3098158-t who is having trouble authorizing their Jetpack site because it’s not apparent that there’s a drop down:

authorize_wordpress_com_for_google_docs

While we’re visually prompted that it is a drop down, to her it’s not apparent as the down arrow isn’t accessible via keyboard. Even walking her through the steps in great detail using only my keyboard, she’s not able to select her Jetpack site since it’s not the first site in her list.

Additionally, in the list of sites in Google docs – there’s no way to remove a site once it’s been added unless you use a mouse hover:

accessible

Testing for screen reader devices would be the first step in relieving these pain points for visually impaired users.

@johngodley
Copy link
Member

While we’re visually prompted that it is a drop down, to her it’s not apparent as the down arrow isn’t accessible via keyboard. Even walking her through the steps in great detail using only my keyboard, she’s not able to select her Jetpack site since it’s not the first site in her list.

Just noting that this problem isn't caused by this plugin itself, but is part of the general WordPress.com / Jetpack authentication process. It definitely needs improving, and is worth bringing up elsewhere.

@johngodley
Copy link
Member

For the second part I think a link (with confirmation) would help.

Another problem with the X appearing on hover is encountered if the site name is long:

hover

@georgeh
Copy link
Contributor

georgeh commented Apr 12, 2017

The accessibility of the "remove site" button has been fixed, and the drop-down is something that is going to need to be addressed by the API team. We should be good here

@georgeh georgeh closed this as completed Apr 12, 2017
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

3 participants