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.
86 Comments - Last post 1 hour ago by Kaprime
55 Comments - Last post 1 hour ago by Chris76de
22 Comments - Last post 1 hour ago by Luckz
1,043 Comments - Last post 1 hour ago by sensualshakti
1,963 Comments - Last post 2 hours ago by Gamy7
36 Comments - Last post 2 hours ago by Gamy7
16 Comments - Last post 2 hours ago by m0r1arty
1,197 Comments - Last post 50 seconds ago by combatbeard
527 Comments - Last post 2 minutes ago by Patzl
2,235 Comments - Last post 27 minutes ago by GrinderPlague
28,522 Comments - Last post 30 minutes ago by TheSteveHarvey
149 Comments - Last post 34 minutes ago by brian14
16,897 Comments - Last post 51 minutes ago by softbearcas
466 Comments - Last post 1 hour ago by Noxco
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.