-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Blog series for Global Accessibility Awareness Day #628
Comments
@rajasegar Awesome! Do you want us to plug this initiative in Friday's Ember Times issue e.g. a call for writers, if you are looking for them? lmk |
@amyrlam Yes, definitely. That would be great to have more people pitching in for the posts. |
@rajasegar quick suggestion, if we agree upon this list, can we make it a TODO checklist? It is something that is followed in the Ember times PR. If someone opts to write on it, the same item can be assigned to individuals? |
@abhilashlr done |
I'd love to write about the a11y testing topic. |
👍 I went ahead and added @praskovia-root to testing above, hope that's ok! |
@MelSumner @rajasegar @abhilashlr and team: I meant to submit a PR but committed to the branch instead by accident. Let me know if you have any feedback! Will go out in tomorrow's issue. 9cb6cee |
This looks fine to me, I think the quicker we sent this out the better. I will wait for the feedback from the rest of the team. |
Hi @amyrlam, the content reads great 🏆 but a minor spelling mistake for |
I'll close this as the post is up! https://blog.emberjs.com/2020/05/21/global-accessibility-awareness-day.html |
This came out of a discussion in #st-a11y channel about doing an A11y blog post series for GAAD ( Global Accessibility Awareness Day) https://globalaccessibilityawarenessday.org/
The idea is to publish a blog post each day from May 1 - 21 with the following topics, one topic/day. This will open up a lot of ways for Ember developers to know more about A11y and inturn to create awareness about the subject. Willing to collaborate on any topic with other people.
@MelSumner wanted to check with the blog team so that the folks can respond with the topic they'd like to write about, hence creating an issue for the same here.
The text was updated successfully, but these errors were encountered: