Is there a reason you decided to use a div and make it work like a button instead of just using a button element?
As I understand it, the first step in accessibility is using proper semantic HTML, since a great deal of this functionality is already built-in and handled by a11y tech, such as screen readers and Braille displays.
Yes there is, I'm glad you asked! Often at Fixt, we find ourselves in situations where a button simply wasn't the best tool for the job. This does bypass some of the incredible built in accessibility tools but many developers will make that trade-off, ignoring users with disabilities. This article was simply meant to bridge that gap with small changes that we can do, as developers.
Is there a reason you decided to use a div and make it work like a button instead of just using a button element?
As I understand it, the first step in accessibility is using proper semantic HTML, since a great deal of this functionality is already built-in and handled by a11y tech, such as screen readers and Braille displays.
Yes there is, I'm glad you asked! Often at Fixt, we find ourselves in situations where a
buttonsimply wasn't the best tool for the job. This does bypass some of the incredible built in accessibility tools but many developers will make that trade-off, ignoring users with disabilities. This article was simply meant to bridge that gap with small changes that we can do, as developers.I hope I explained that well enough! :)
Thanks for the explanation. I've been pushing hard against non-semantic HTML in my company, since it seems so much like reinventing the wheel.
You're right though, that at least you're bringing the idea to the front of people's minds, and that's a win all by itself.