Accessibility: It's more than the tech
When we think about accessibility most of us think about screen readers but there's a lot more. The automated and manual techniques are a starting point. After you make all the changes suggested by the tools you still have to make decisions about your content. This is the beginning of my learning accessibility. Will report back along the learning path :-). ## Links and Resources - Accessibility - [ARIA, Accessibility APIs and coding like you give a damn! – Léonie Watson](https://www.youtube.com/watch?v=qdB8SRhqvFc) - [Leonie Watson: Using ARIA to solve everyday accessibility problems](https://www.youtube.com/watch?v=gQADBOsjBTM) - ARIA - [Using ARIA](https://w3c.github.io/using-aria/) - Best Practices - [WAI-ARIA Authoring Practices 1.1](https://www.w3.org/TR/wai-aria-practices-1.1/) - [MIND Patterns: Accessibility Patterns for the Web](https://ebay.gitbooks.io/mindpatterns/) - Voice Over - [Voice Over Getting Started Guide](https://help.apple.com/voiceover/info/guide/10.12/) - [Voice Over Commands](http://lab.dotjay.com/notes/voiceover-commands/) - aXe and aXe Coconut - [Test the leading edge of accessibility with aXe Coconut and aXe-core 3.0-alpha](https://www.deque.com/blog/test-leading-edge-accessibility-aXe-coconut-aXe-core-3-0/) - Browser Extensions - [aXe Chrome Extension (Stable)](https://chrome.google.com/webstore/detail/aXe/lhdoppojpmngadmnindnejefpokejbdd) - [aXe Coconut Chrome Extension](https://chrome.google.com/webstore/detail/aXe-coconut/iobddmbdndbbbfjopjdgadphaoihpojp) - [Firefox Devtools Integration](https://github.com/dequelabs/aXe-firefox-devtools) - Chrome specific - [How To Do an Accessibility Review](https://developers.google.com/web/fundamentals/accessibility/how-to-review) - [The new way to test accessibility with Chrome DevTools - A11ycasts #23](https://www.youtube.com/watch?v=b0Q5Zp_yKaU)