All tools are public Github repositories primary written in HTML and/or JavaScript
| Repo | Type | Purpose | Dependencies |
|---|---|---|---|
| GoogleChrome/accessibility-developer-tools-extension | browser addon | code audit | Closure Compiler |
| ainspector/ainspector.github.io | browser addon | code audit | - |
| yargalot/grunt-accessibility | CLI | code audit | Node/Grunt |
| nature/pa11y | CLI | code audit | Node/PhantonJS |
| addyosmani/a11y | CLI | code audit | Node/PhantomJS |
| dequelabs/axe-core | in-page function | code audit | - |
| GoogleChrome/accessibility-developer-tools | local Node service | code audit | Node |
| rackt/react-a11y | React Component | code audit | React |
| squizlabs/HTML_CodeSniffer | stand-alone page | code audit | - |
| haltersweb/Accessibility | stand-alone page | code library | - |
| prettydiff/colorContrast | stand-alone page | color contrast | - |
| jxnblk/colorable | stand-alone page | color contrast | - |
| LeaVerou/contrast-ratio | stand-alone page | color contrast | - |
| RAMP-PCAR/RAMP-PCAR | framework | framework | Node/Grunt |
| a11yproject/a11yproject.com | stand-alone page | informational | Ruby |
| wesbos/keycodes | stand-alone page | keyboard keycodes | - |
| zone/zwag | stand-alone page | reference WCAG | Node |
| dylanb/dylanb.github.io | stand-alone page | reference ARIA | - |
| melmo/melmo.github.io | stand-alone page | reference landmarks | - |
| nature/pa11y-dashboard | stand-alone page | reporting | Node/PhantomJS |
| Khan/tota11y | in-page function | semantic analysis | JQuery |
| prettydiff/semanticText | in-page function | semantic analysis | - |
| howlowck/Akbar | bookmarklet | vision simulation | - |
| adobe-accessibility/Accessible-Mega-Menu | web component | web component | JQuery |
| A11yance/a11y-core | local Node service | ? | Node/Grunt |
My purpose in making such a list is that I want to be aware of what things are being evaluated so that I can get an idea of what things aren't being evaluated. Accessibility is hard, and since many commercial sites don't produce high quality HTML accessibility is much harder than it should be. Making accessibility easier to implement and understand is absolutely important. Good tools help with this.
Sometimes the biggest problem with accessibility is that we know what to check for (most of the time), but we don't always know what grading aspects we are missing. Examples include color contrast problems over gradient backgrounds and improper use of the title attribute. Sometimes we also don't realize how the dynamic interactions we introduce with JavaScript alienate segments of our audience.
Accessibility advocates typically suggest having at least 3 accessibility tools frequently used, because they each are better in different particular areas. An awareness of the tools available benefits everybody whether or not you intend to make accessibility tools. Please submit pull requests with additional tools.