-
If you’re a junior developer who wants to show initiative or make a meaningful contribution to a project you’re working on, here is a repeatable procedure that has real impact (and you’ll learn, too!) Let’s run a basic ✨#accessibility audit✨ Thread 👇🏼 #a11yOn twitter.com
♻️ 11 Retweets ❤️ 20 Favorites Mood +3 🙂
-
1. Download the aXe dev tools from @dequesystems deque.com/axe/ or go to the Audits tab in Chrome to use @____lighthouse 2. Hit the big analyze button, or run a Lighthouse Accessibility Audit. This will analyze your page against a library of accessibility rulesPermalink On twitter.com
-
3. You’ve now got a list of accessibility issues and how many times that issue occurs on the page. Learn about each issue and how to fix it — often there is a really easy fix! A missing attribute for example is an easy code change that makes a *real* impact on users!Permalink On twitter.com
-
4. Fix as many issues as you can! Start with the low-hanging fruit and work your way up to the issues that seem more difficult to fix. There might be some really thorny problems where you might need to ask for help, but you could be amazed how much you can do on your own.Permalink On twitter.com
-
5. Submit your pull request and feel good about your contribution! Congratulations, you’ve just made your web experience better for users AND improved the quality of your codebase AND hopefully learnt a few things along the way ☺️ 🙌🏼Permalink On twitter.com