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.
318 Comments - Last post 1 hour ago by DarthLonginus
21 Comments - Last post 2 hours ago by Dayannah
3,223 Comments - Last post 3 hours ago by drbeckett
10 Comments - Last post 7 hours ago by fedeLaria
228 Comments - Last post 8 hours ago by Reidor
5 Comments - Last post 12 hours ago by RobbyRatpoison
150 Comments - Last post 12 hours ago by Magiriano
1,590 Comments - Last post 15 minutes ago by CheMan39
43 Comments - Last post 19 minutes ago by real6662
1,387 Comments - Last post 1 hour ago by Masafor
123 Comments - Last post 1 hour ago by someonequeer
32 Comments - Last post 1 hour ago by windkit
119 Comments - Last post 1 hour ago by KOHTYP
153 Comments - Last post 2 hours ago by ChuanC6
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.