So I am definitely doing this!
Published
Hey there,
I don’t like public commitments—but here I am, doing this publicly.
Web accessibility has always been an integral part of me being a frontend developer, I generally don't like the idea of limiting people and knowing that something I build might be inaccessible due to my ignorance just doesn’t sit right with me.
But I've come to understand that accessibility goes beyond just writing accessible code and I keep realizing how much I don’t know—so I've decided to do something about it.
My Goal
I want to master web accessibility and gain the confidence to call myself a WAS (Web Accessibility Specialist)
My Plan
- Spend at least 2 hours daily learning about accessibility
- Follow the IAAP WAS Body of Knowledge (BoK) (Oct 2024 update) for structured learning
- Understand the W3C accessibility resources
- Get comfortable with AT (Assistive Technologies)
- Understand the European Accessibility (EN 301 549)
- Run accessibility audits to better understand WCAG 2.2
- Update this blog with insights, tutorials, and takeaways
- Prepare for and take the IAAP WAS certification exam
- Become a WAS
Join Me on This Path
You can follow along as I update this blog with insights, learnings, and challenges. Maybe you’ll learn something new—or maybe you’ll just enjoy the journey with me!
You could also check out my past articles on dev.to (opens in a new tab). where I’ve written about specific web accessibility topics.
This idea was inspired by Amy Carney’s 100 Days of A11y
Let’s go!