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

Emoji Accessibility #532

Closed
6 of 7 tasks
brianamarie opened this issue Jul 20, 2017 · 10 comments
Closed
6 of 7 tasks

Emoji Accessibility #532

brianamarie opened this issue Jul 20, 2017 · 10 comments
Assignees

Comments

@brianamarie
Copy link
Contributor

brianamarie commented Jul 20, 2017

Overview

TL;DR
Emojis aren't accessible out of the box. For example, people who have impaired vision and may be using screen readers won't interact with emojis consistently across the board. Let's make sure our content is accessible.

Extra Detail

Screenshots

I was curious about this, so I asked a developer who is blind, and very open about how developing isn't always accessible.

tweet from @brianamarie: zersiax  I have a question for you if you don't mind. How accessible are emojis in written content?

I found his responses very helpful.

tweet responses from zerisiax, telling how emojis are not accessible and aren't read how we might think they would be

Others chimed in with more information, too.

tweet response from DenMcH about using span tags even in Markdown

Next steps (Edited to reflect new path forward)

Fix the problem in each course:

cc @github/services-training for awareness, and anyone who may want to ✋

@brianamarie brianamarie self-assigned this Jul 20, 2017
@JasonEtco
Copy link
Contributor

I support this endeavor. I'll do some research as well, I know of another a11y expert who might have some thoughts (Rob Dodson)

@brianamarie
Copy link
Contributor Author

@zersiax for more insight/guidance on making our resources (found here) more accessible.

@brianamarie
Copy link
Contributor Author

Also pinging @denmch for same reasons - more insight/guidance on making our resources (found here) more accessible.

@crichID
Copy link
Contributor

crichID commented Jul 20, 2017

@brianamarie thank you for surfacing this concern and taking immediate action ❤️.

@JasonEtco
Copy link
Contributor

Interesting tweet thread (still developing): https://twitter.com/JasonEtco/status/888077256131616768

@brianamarie
Copy link
Contributor Author

Intro course in progress here, all review welcome

@brianamarie
Copy link
Contributor Author

Great resource @beardofedu found: http://webaim.org/techniques/screenreader/

@hectorsector
Copy link
Member

This Chrome extension seems really helpful in this endeavor, @brianamarie!

screen shot 2017-08-24 at 8 35 45 am

@brianamarie
Copy link
Contributor Author

@hectorsector This is an awesome resource, thank you!!!

@brianamarie
Copy link
Contributor Author

All of the main todos in this issue have been completed. As we continue to work on content, I think it's important we keep accessibility in mind, and use the great tools that we've found! 🎉

This issue was closed.
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

4 participants