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

Audit nteract behavior under screenreaders #852

Closed
captainsafia opened this issue Sep 29, 2016 · 4 comments
Closed

Audit nteract behavior under screenreaders #852

captainsafia opened this issue Sep 29, 2016 · 4 comments
Labels
feature: ui/ux hacktoberfest new-contributor-friendly outdated workflow: issue should stay closed stale workflow: stale issue

Comments

@captainsafia
Copy link
Member

A brief test of nteract's behavior when used with a screenreader exposes several bugs. It'd be great to have an accessibility specialist or a visually-impaired individual give the application an audit for its behavior on different screen-readers.

Furthermore, we should run our application through react-a11y to find other accessibility issues that might contribute to making nteract play nicer with screen readers.

@jdetle
Copy link
Member

jdetle commented Sep 29, 2016

Edited: I was talking with a family friend at edX and she was saying that they don't let any product into the edX platform doesn't comply with WCAG.

@captainsafia
Copy link
Member Author

I was talking with a family friend at edX and she was saying that they don't let any product through that doesn't comply with WCAG.

Product through for what?

@rgbkrk
Copy link
Member

rgbkrk commented Feb 6, 2017

@rgbkrk rgbkrk added this to the Release Candidate milestone Feb 7, 2017
@stale
Copy link

stale bot commented Apr 13, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale workflow: stale issue label Apr 13, 2018
@stale stale bot closed this as completed Apr 20, 2018
@lock lock bot added the outdated workflow: issue should stay closed label Jul 20, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature: ui/ux hacktoberfest new-contributor-friendly outdated workflow: issue should stay closed stale workflow: stale issue
Projects
None yet
Development

No branches or pull requests

3 participants