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.
106 Comments - Last post 10 minutes ago by WastedYears
221 Comments - Last post 39 minutes ago by reigifts
8,615 Comments - Last post 1 hour ago by PaganFears
128 Comments - Last post 1 hour ago by possom2009
185 Comments - Last post 1 hour ago by devotee
1 Comments - Last post 1 hour ago by reigifts
49 Comments - Last post 1 hour ago by FranckCastle
243 Comments - Last post 44 seconds ago by aez76
124 Comments - Last post 6 minutes ago by Talien
111 Comments - Last post 16 minutes ago by MayoSlice
29 Comments - Last post 28 minutes ago by reigifts
46 Comments - Last post 41 minutes ago by XiaoLong
87 Comments - Last post 53 minutes ago by Rattyk
39 Comments - Last post 53 minutes ago by reigifts
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.