It seems like those buttons are not actual html buttons, they are just elements styled to look like buttons. So changing them to buttons might fix it. This video has some insight: Just use button -- A11ycasts #05
This page has some more hints for web developers on how to design accessible pages:
https://medium.com/@matuzo/writing-javascript-with-accessibility-in-mind-a1f6a5f467b9
Looks like an alternative "fix" might be to set a tabindex on those elements.
Disclaimer: I do not use a screen reader
Comment has been collapsed.
9 Comments - Last post 12 minutes ago by looseangel
23 Comments - Last post 33 minutes ago by Mitsukuni
553 Comments - Last post 3 hours ago by Delisper
722 Comments - Last post 3 hours ago by ZPE
66 Comments - Last post 4 hours ago by ZPE
2,041 Comments - Last post 5 hours ago by Wok
15,351 Comments - Last post 8 hours ago by jahas10
796 Comments - Last post 37 minutes ago by SamuelTwister
17 Comments - Last post 1 hour ago by misterhaan
26,431 Comments - Last post 2 hours ago by Dominicanoed
725 Comments - Last post 3 hours ago by grom9663
248 Comments - Last post 3 hours ago by hbouma
10,865 Comments - Last post 3 hours ago by Axelflox
2,683 Comments - Last post 6 hours ago by Mhol1071
There's an issue with the "Enter Giveaway", "Remove Entry" and "Create Ticket"
buttons. They seem to be lacking a certain hint, informing the browser they are
clickable.
Whatever it is that's missing, it causes pentadactyl[1] (and I assume screen
readers and other accessibility software etc) to not know they are clickable.
This requires me to access and use a mouse for them.
Unfortunately I am unaware of the actual hint required in the
HTML/JS/CSS. Traditionally these would be <input type=button> or similar but
that's probably web 1.0 these days :P Does anyone know off hand what might be
missing?
[1] Pentadactyl - a browser plugin that allows for complete mouseless keyboard
navigation, similar to vimium, vimperator etc
Comment has been collapsed.