Not quite, because now you have to add Space bar support, you are telling non-sighted SR users there is no context menu when there is, and depending on styling or expectation a voice user may have to do a double-step to choose it. Replacing with a <button> is better.
October 30th, 2020
role of “button” to the link, would that deal with the expectation issue?
(That would still allow the link to be a fallback for non-JS scenarios.)
You can handle both scenarios, but it involves maybe swapping elements and testing with site users. Ideal solutions may vary between sites because of different audience technology profile, skill level, expectation, etc. So less a technical issue than a testing issue.
Ah, right, I see now that you said replacing with an actual
button is better than adding a
Yeah, I could have been more clear. I will blame Twitter character limits.
No, no, that was totally down to me reading in haste. adactio.com/notes/17581