The button role isn't enough for an accessible interface
Folks, let's think about how to improve our buttons for people who have to use a keyboard as a single way to interact with UI🤔
A lot of apps become more accessible for people who use screen readers. That's awesome! But something went wrong.. 😐😐😐
I became to face buttons that aren't buttons, i.e <button> isn't used and instead of it role="button" is used. Why is bad?
People have 0% chances to interact with UI. 🆘🆘🆘 They can’t use the interface at all 😩😩😩
The role doesn't affect interactivity of buttons. That's why people can't interact with these buttons using a keyboard.
So, please, check your buttons so that they are created using <button>. Please, give a chances people use your UI 🙏🙏🙏
✉️ Need help? Ask me any questions: firstname.lastname@example.org
❤ Thank you so much, my sponsors: Ben Rinehart, Sergio Kagiema, Jesse Willard, Tanya Ten, Konstantinos Kapenekakis, Spiridon Konofaos.
Folks, I'm a content creator with a passion for making more public content for the community. For that, I have to look for sponsors. They help me to stay afloat.
If you like what I do, please, support me on Patreon. As words of appreciation, I’ll give you access to my content earlier others directly to your inbox. Thank you 🙏