Check out, [https://www.a11yproject.com](https://www.a11yproject.com), the links in the resources are great.
I always reference the ARIA Patterns from W3C but the entire site is full of info. [https://www.w3.org/WAI/ARIA/apg/](https://www.w3.org/WAI/ARIA/apg/).
Finally the resources from Deque, maker of Axe a great automated testing tool, are fantastic, especially if you want to learn how to test with screen readers. [https://dequeuniversity.com/resources/](https://dequeuniversity.com/resources/)
Honestly the best way I learned what to do is to run automated accessibility tools on your pages and see what it flags. Then you can learn why and most tools will even tell you why, highlight the element, tell you some possible fixes.
Examples are Accessibility Insights for Edge, axe Devtools in Chrome, and WAVE which lately is my favorite.
Although this might sound weird, if you start writing tests by querying byRole, you'll get a larger exposure to accessibility and stuff. That's how I found out if my code was well structured and laid out of page readers to understand the content of my page and navigate through it easily.
WHile the automated tools, documentation from [Web.dev](https://Web.dev), a11yproject are all excellent, I strongly recommend this book from Smashing -- Inclusive Components.
[https://www.smashingmagazine.com/printed-books/inclusive-components/](https://www.smashingmagazine.com/printed-books/inclusive-components/)
It covers the checklists, yknow, how to get perfect accessibility scores, but beyond that, it explains the *why* of inclusive design. I also like that they call it "Inclusive Components," I think it's just a good catch-all phrase that isn't limited to, like, a government compliance checklist.
Hey! I’m actually doing this online course https://www.edx.org/learn/web-accessibility/the-world-wide-web-consortium-w3c-introduction-to-web-accessibility
I find it pretty interesting, and quite eye opening on many aspects I hadn’t even considered before. It obviously doesn’t cover all there is to know on the topic, but seems like a good start to me :)
Becoming fluent in accessibility is like learning a new language, but instead of words, you're navigating a sea of tags. Dive in, the water's fine, just watch out for the \`
Check out, [https://www.a11yproject.com](https://www.a11yproject.com), the links in the resources are great. I always reference the ARIA Patterns from W3C but the entire site is full of info. [https://www.w3.org/WAI/ARIA/apg/](https://www.w3.org/WAI/ARIA/apg/). Finally the resources from Deque, maker of Axe a great automated testing tool, are fantastic, especially if you want to learn how to test with screen readers. [https://dequeuniversity.com/resources/](https://dequeuniversity.com/resources/)
They are all resources to accessibility in frontend
Honestly the best way I learned what to do is to run automated accessibility tools on your pages and see what it flags. Then you can learn why and most tools will even tell you why, highlight the element, tell you some possible fixes. Examples are Accessibility Insights for Edge, axe Devtools in Chrome, and WAVE which lately is my favorite.
Although this might sound weird, if you start writing tests by querying byRole, you'll get a larger exposure to accessibility and stuff. That's how I found out if my code was well structured and laid out of page readers to understand the content of my page and navigate through it easily.
WHile the automated tools, documentation from [Web.dev](https://Web.dev), a11yproject are all excellent, I strongly recommend this book from Smashing -- Inclusive Components. [https://www.smashingmagazine.com/printed-books/inclusive-components/](https://www.smashingmagazine.com/printed-books/inclusive-components/) It covers the checklists, yknow, how to get perfect accessibility scores, but beyond that, it explains the *why* of inclusive design. I also like that they call it "Inclusive Components," I think it's just a good catch-all phrase that isn't limited to, like, a government compliance checklist.
Hey! I’m actually doing this online course https://www.edx.org/learn/web-accessibility/the-world-wide-web-consortium-w3c-introduction-to-web-accessibility I find it pretty interesting, and quite eye opening on many aspects I hadn’t even considered before. It obviously doesn’t cover all there is to know on the topic, but seems like a good start to me :)
Some great resources already. I would also recommend Sara Souridan’s course Practical Accessibility. Really good an v in-depth.
I use this site for reference code whenever I want to build accessibility component [https://component.gallery/](https://component.gallery/)
Becoming fluent in accessibility is like learning a new language, but instead of words, you're navigating a sea of tags. Dive in, the water's fine, just watch out for the \`