From the beginning of my self-taught front-end developer journey, I was interested in how to create apps and websites with accessibility in mind. I used semantic HTML and used Lighthouse on every project and felt really good about how accessible my websites were.
Little did I know that this is just the tip of the iceberg and there is so much more to it. There are many great tools and guidelines you can use to check how accessible your website is and how you can improve it.
I would like to gain the knowledge in these guidelines as well as learn how to use the different testing tools.
How I want to structure my journey.
- I will write and publish this article (✅) and make it a series.
- I will write about accessibility in general to give the community an overview of a11y in web development.
- I will start updating my existing projects, analyzing them in an accessible way and updating them as needed, starting with my personal portfolio.
- I will make my personal brand (colors, font, ..) accessible.
- I will update my second project SOS Animals.
In the meantime
- I will write about a11y in terms of specific elements such as navigation bars, headers, buttons, etc. and save examples as gist files.
- I will write about a11y beyond components, more specific things like a11y in
<head>, keyboard usage, and more.
- I'm going to take the Google UX Design Certificate to learn about accessibility from a different perspective. Because a11y is not only developer's job, it concerns all of us.
My goal would be to be known for my accessibility skills and be responsible for a11y at work 😇
Thanks for your reading and time. I really appreciate it!
Top comments (2)
Looking forward to following this series! As a newer developer, learning the best accessibility practices is definitely on my to-improve list! Thank you!
That's great. I really want to spread the word about accessibility and I am always happy to hear someone's going this accessibility path as well!