Practical Accessibility is a self-paced video course designed to demystify web accessibility and equip you with the knowledge you need to confidently create more accessible websites and web applications today.
Accessibility can be straight-up difficult and intimidating. How do you get started? Where do you start? How do you know if what you've built is accessible? How do you find and fix accessibility issues when they come up?
I know how hard it is to find answers, and how easy it is to make mistakes—mistakes that have a direct, tangible impact on your users' ability to use your websites and applications. I know how overwhelming and sometimes frustrating accessibility can feel at first.
But I promise you, accessibility isn't always as hard as it seems, especially if you know where and when to start. And my goal with this course is to demystify it and make it friendlier and more approachable.
Practical Accessibility is the culmination and distillation of years of my experience in learning, developing, and teaching about web accessibility. It is a structured curriculum aimed to equip you with the foundational, evergreen knowledge you need to gain a deep understanding of accessibility.
Armed with this knowledge, you will be able to anticipate places where you may create barriers to access for people and avoid them in your work, as well as fix or remove existing barriers in your current projects. And you don't need any prior experience in accessibility to get started!
If you're a design engineer, front-end designer, a jаvascript engineer, or a back-end developer looking to gain a deep understanding of accessibility, then this course is for you.
In this course, you will find answers to questions like
What is the thought process for building accessible components from scratch?
Do I need jаvascript to make this accessible?
Why is semantic HTML so important? And how do I know which HTML element to choose?
What is the accessibility tree? and what does it tell me about the accessibility of my components?
What is ARIA? and when do I reach for ARIA versus native HTML?
How do I navigate the different ARIA and WCAG documents?
How does CSS affect accessibility?
Why are accessible names such a big deal? And which technique should I prioritize when providing names to my components?
What are the best practices for creating and validating forms? And why is native HTML5 form validation not enough?
How do I announce content updates to my users?
.and many, many more.
Homepage:

https://practical-accessibility.today/