When you use HTML as intended you get a lot of accessibility for free, including information about the name, role and state of HTML elements. When the browser creates the DOM it also creates an accessibility tree. Léonie Watson
Dawid Masiejczyk
8mo
Indeed. I'm into the approach of building basic components on pure HTML. When using libraries, most often you'll meet some accessibility issues which you can't easily fix without modifying the library itself
Yes! This gets overlooked too often and is the key reason we see so many accessibility issues when teams reach for divs and spans instead of buttons, headings, and form labels. The browser will do the heavy lifting for you, but only if you let it. Usually the simplest fix is also the most accessible one.