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.
47,118 Comments - Last post 3 minutes ago by Fewithor
60 Comments - Last post 22 minutes ago by Gamy7
1,230 Comments - Last post 1 hour ago by Draconiano
56 Comments - Last post 1 hour ago by Mantve
16,338 Comments - Last post 1 hour ago by Peiperissimus
119 Comments - Last post 1 hour ago by Axelflox
1,866 Comments - Last post 2 hours ago by rongey420
89 Comments - Last post 5 minutes ago by Fluffster
10 Comments - Last post 20 minutes ago by Mhol1071
3,375 Comments - Last post 25 minutes ago by Mhol1071
2,733 Comments - Last post 25 minutes ago by Fluffster
56 Comments - Last post 30 minutes ago by FoxMulder
875 Comments - Last post 32 minutes ago by Chris76de
75 Comments - Last post 48 minutes ago by HowDareYou
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.