The Accessibility Project is an open source project committed to making web accessibility easier for frontend designers and developers to understand and adopt into a daily workflow. The project started in mid-January 2013 in response to a general feeling among developers that core accessibility concepts, features and code examples are overly difficult to extract.
The project has three core tenets. It aims to be digestible (offering short, easy to understand pieces of content), up-to-date (in line with the latest standards) and forgiving (because people make mistakes, and web accessibility is tricky).
At the time of writing, 102 people have contributed to The Accessibility Project and it has become an invaluable resource for any developer looking to make their sites more accessible to all.
Post Body
Accessibility can be a complex and difficult topic. The Accessibility Project understands this and wants to help make it easier to implement on the web. Our goal is to accomplish this with three principles in mind:
Digestible. We strive to feature short, digestible pieces of content.
Up-to-date. The project is hosted on GitHub so information can be current with the latest standards.
Forgiving. People make mistakes, so we seek to be encouraging.
Accessibility is important Why
Blind and visually impaired make up 285,000,000 people according to the World Health Organization (June 2012) with 39,000,000 categorized as legally blind and the remaining 246,000,000 visually impaired. Deaf and hearing impaired make up 275,000,000 (2004) in the moderate-to-profound hearing impairment category.
To put these in perspective, the population of the United States of America is 315,000,000 (January 2013).
Disabilities can also be conditional. A broken arm, a loud restaurant, harsh glare, not speaking the local language all are examples where someone may benefit from accessible practices.
Another motivation is discoverability. You can find more relevant resources, and with greater precision. Using the term “accessibility” to search, you will find many irrelevant resources using that word in various other contexts. You may also miss resources in languages other than English. Many accessibility specialists from around the world use “a11y” as an international technical term when speaking about their work.
Resources of this site
Newsletters
Accessibility Weekly
Axess Lab Newsletter
Skip Links - A monthly newsletter curated by the HackerYou Web Accessibility Club
The WebAIM Newsletter
Development Tools
AccessLint - A GitHub App that finds accessibility issues in your pull requests.
Accessibility Testing API - By Tenon.io
Pa11y - Automated accessibility testing
Quail JS Testing Plugin - A jQuery plugin for checking content against accessibility guidelines
Sass a11y - A Compass plugin
Sublime WAI-ARIA - WAI-ARIA Roles, States and Properties auto-completion for Sublime Text
ally.js - Helps JavaScript applications become more accessible
axe-core - Accessibility engine for automated Web UI testing
eslint-plugin-jsx-a11y - Static AST checker for a11y rules on JSX elements
PDFs
AcceDe PDF Project
Adobe: Create and verify PDF accessibility, Acrobat Pro
WebAIM: PDF Accessibility
HTML Related
A collection of accessible, modern front-end components - By Frend
Bootstrap accessibility plugin - By PayPal
HTML5 Accessibility - By Steve Faulkner
Periodic Table of ARIA roles - By dylanb
Using ARIA - By W3C
WAI-ARIA Authoring Practices - By W3C
WAI-ARIA Specification - By W3C
Web Accessibility Tutorials - By W3C
Courses
Accessibility courses, and more - List curated by Mike Gifford
Start Building Accessible Web Applications Today - By egghead.io
Web Accessibility by Google - Developing with Empathy - By udacity.com
Resources
https://a11yproject.com
Leave The Accessibility Project The A11Y Project to:
We have not curated any of ranatalha's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
