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
The current HTML code for librespeed is not accessible. The main button (or... the only button) is currently implemented as <div onclick=""></div>. Instead, it should be a <button> or <input type="button">. Why? Because it is not focusable by keyboard, and very likely not accessible for screen readers (I don't use one, I cannot say for sure).
Steps to reproduce
Open the page.
Press ↹ Tab to try to focus the button and start the speed test using only your keyboard.
Expected behaviour
It should work, it should be accessible.
What happens instead
The button is not a button, so it is not focusable, so it cannot be interacted purely by keyboard.
Other remarks
There might be other accessibility issues, but I haven't investigated them.
The text was updated successfully, but these errors were encountered:
I am aware of that: the examples are not accessible at all, it's not just the button.
If you have experience with screen readers and other accessibility technologies, it would be great to add a new, accessible example
Well, adding a tabindex seems to be a bad practice in this case, not only it can mess up the tabbing order (if using a value greater than zero), but it's not even a complete solution (would still be missing the ARIA attribute role="button"). It's much better and much simpler to just replace the <div> with <button>.
Description
The current HTML code for librespeed is not accessible. The main button (or... the only button) is currently implemented as
<div onclick=""></div>
. Instead, it should be a<button>
or<input type="button">
. Why? Because it is not focusable by keyboard, and very likely not accessible for screen readers (I don't use one, I cannot say for sure).Steps to reproduce
↹ Tab
to try to focus the button and start the speed test using only your keyboard.Expected behaviour
It should work, it should be accessible.
What happens instead
The button is not a button, so it is not focusable, so it cannot be interacted purely by keyboard.
Other remarks
There might be other accessibility issues, but I haven't investigated them.
The text was updated successfully, but these errors were encountered: