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.
11 Comments - Last post 1 hour ago by Dunther
15 Comments - Last post 1 hour ago by UltimateArck
3 Comments - Last post 2 hours ago by Lugum
10 Comments - Last post 2 hours ago by DeliberateTaco
36 Comments - Last post 2 hours ago by Leon30670
3 Comments - Last post 3 hours ago by CasualGamerMe
297 Comments - Last post 3 hours ago by SerenaM
124 Comments - Last post 8 minutes ago by neomysto
8,622 Comments - Last post 13 minutes ago by steveywonder75
35 Comments - Last post 1 hour ago by Grogglz
1,566 Comments - Last post 1 hour ago by ExcelElmira
16,370 Comments - Last post 2 hours ago by MaxiBoi1357
147 Comments - Last post 2 hours ago by olehsamoilenko
4 Comments - Last post 2 hours ago by RePlayBe
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.