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.
610 Comments - Last post 11 minutes ago by Berion83
44 Comments - Last post 45 minutes ago by xeos23
17,321 Comments - Last post 51 minutes ago by Carenard
232 Comments - Last post 5 hours ago by Reidor
12 Comments - Last post 6 hours ago by KjaerBeto
47,462 Comments - Last post 7 hours ago by pizzahut
3,257 Comments - Last post 8 hours ago by MeguminShiro
163 Comments - Last post 1 minute ago by Ch1cWolf
109 Comments - Last post 4 minutes ago by Donners
89 Comments - Last post 8 minutes ago by Donners
1,728 Comments - Last post 40 minutes ago by Beauregarde
281 Comments - Last post 1 hour ago by Fallador
10 Comments - Last post 1 hour ago by SaPOWrra
1,142 Comments - Last post 2 hours ago by mourinhos86
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.