You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no ARIA support for button in the prebuilt UI.
I embedded the prebuilt UI on my Wordpress website successfully. It works fine, but it turns out it is not very accessible.
I was testing the chat room with my friend who is blind. He uses a screen reader. He could connect, we could communicate, but he could not find the buttons.
The reason is that button tags have neither labels nor "title" attributes. So there is no ariaLabel set, no text reader has no idea what is the name of the button that has the focus. For a blind person all buttons are the same: with no names.
There is an easy way to fix it, but using correctly ARIA attributes. There is no disadvantage, no changes for user interface, everything is just more accessible.
I realize that not many people need accessibility for UI, but since the modifications are not complicated or time consuming, I thought you guys could help. Thanks!
The text was updated successfully, but these errors were encountered:
Hey @UnprofessionalMartin,
Thanks for you suggestion 👍, we realized that ARIA support is needed in this SDK
We will surely add this in our future prebuilt releases
We are also planning for PR criteria, so that other developers also can contribute into our SDK
There is no ARIA support for button in the prebuilt UI.
I embedded the prebuilt UI on my Wordpress website successfully. It works fine, but it turns out it is not very accessible.
I was testing the chat room with my friend who is blind. He uses a screen reader. He could connect, we could communicate, but he could not find the buttons.
The reason is that button tags have neither labels nor "title" attributes. So there is no ariaLabel set, no text reader has no idea what is the name of the button that has the focus. For a blind person all buttons are the same: with no names.
There is an easy way to fix it, but using correctly ARIA attributes. There is no disadvantage, no changes for user interface, everything is just more accessible.
I realize that not many people need accessibility for UI, but since the modifications are not complicated or time consuming, I thought you guys could help. Thanks!
The text was updated successfully, but these errors were encountered: