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.
25 Comments - Last post 10 minutes ago by thekenya
10 Comments - Last post 23 minutes ago by Seibitsu
26 Comments - Last post 1 hour ago by eda46
37 Comments - Last post 1 hour ago by FritoleXx
32 Comments - Last post 1 hour ago by lostsoul67
10 Comments - Last post 1 hour ago by lostsoul67
8 Comments - Last post 1 hour ago by aez76
89 Comments - Last post 6 minutes ago by DrTenma
58 Comments - Last post 6 minutes ago by DrTenma
2 Comments - Last post 10 minutes ago by Matwyn
2,029 Comments - Last post 23 minutes ago by Romaki96
18 Comments - Last post 43 minutes ago by wigglenose
718 Comments - Last post 53 minutes ago by Vampus
312 Comments - Last post 55 minutes ago by schmetti
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.