brunopulis / awesome-a11y

A curate list about A11Y

Awesome Accessibility

Para uma versão em português deste arquivo, veja README.pt-BR.

Image is an illustration by Heydon Pickering which you can see on Dribble.

A curated list of awesome accessibility tools, articles, and resources. Inspired by awesome-svg, awesome-webcomponents and awesome-flexbox.

Please read the contribution guidelines before contributing.

Table of Contents

• Accessibility Weekly
• Articles and Videos
• Blogs
• Books
• Certificates
• Companies and Organizations
• Conferences
• Courses
• Guides
• Jobs
• Laws
• Meetups
• Other Resources
• People to Follow in Web Accessibility
• Podcasts
• Talks
• Tools
• W3C Specification

Support me

awesome-a11y's Issues

Add podcast section

Add a new section to Podcasts

Accessibility Insights

Proposal

• Add Accessibility Insights from Microsoft

Demo

• Repository
• Reference

Checkpoints

• Confirm if this feature is already part of this living documentation
• If no, get a go ahead to create a Merge request

Organisation

I'm looking for a way to organize the list in a clearer and more concise way.
I thought of a separate folder structure with its specific subjects.

E.g

Talks

• Talk 1
• Talk 2

Helpful pattern page?

Hi Bruno,

Great page!

Would you find these a11y patterns I've created helpful? http://haltersweb.github.io/Accessibility/ (repository for these is at: https://github.com/haltersweb/Accessibility)

All the best,

Adina (@haltersweb)

Validate pull requests with Travis

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

Why legends ?

Hello,

Nice initiative ! thank you for your work.

But why do you use legend for level description ?

The legend is hard to memorize, and, for a screen reader user, the content of the icon's alt attribute is not really helpful (it describes the icon). I search through the code, but it seems i can't find alternative information about the level next to the icon, but maybe I just didn't see it.

Why don't you just put the text level instead of the icon and remove the legend ?

Consider adding Checka11y.css?

Is your feature request related to a problem? Please describe.
N/A

Describe the solution you'd like
I feel Checka11y.css has become a popular project with people learn accessibility and people looking for a cool project that highlights accessibility in a different way. It's also extremely popular during Hacktoberfest.

Describe alternatives you've considered
N/A

Additional context
Links:

• https://checka11y.jackdomleo.dev
• https://github.com/jackdomleo7/Checka11y.css
• https://github.com/jackdomleo7/Checka11y.css-browser-extension

Contributing with links about a11y

Contributing with links, articles, videos, talks and lot of stuff's about a11y.

Create: Frontend to project

People to follow resource

Hello, wanted to alert you of a project I have rolling that lots of folks have contributed to you could either point to or steal from! :)

https://github.com/joe-watkins/top-people-to-follow-in-web-accessibility

Better organisation

Better organize the list of resources, for example, a more organized index.

Organize: Awesome A11y

Tools Section

Add the Tools section to organize tools using in evaluation accessibility

Align tooling sections

The structure for the "assistive technology", "tools" and "validators" sections is not fully clear:

• tools lists all the screen readers, which assistive technology does this as well
• there is tools and validators, while the second has a "Tools" headline as well

Does it make sense to move everything to tools and use subheadlines for structuring?

Add README in brazilian portuguese

Add translate to brazillian portuguese.

Word Missing in Development Testing and Validators under Validators/tota11y

Currently it reads "simple validator using". Is the missing word "Javascript"?

Can't push my branch for PR

Hi there. I am trying to push some fixes and additions to the courses page, but when trying to push, I get access denied. :(

404 on google's accessibility guide

In Guides, Link to google's intro to web accessibility is a 404;

there's now https://developers.google.com/web/fundamentals/accessibility/
or https://www.udacity.com/course/web-accessibility--ud891# (developed in partnership with google) and not sure which you prefer to replace the previous link with.

A11y Project listing duplicated in companies.md

Remove second A11yProject listing.