Yes, better for screen reader support where the JavaScript executes, but not so good for any situations—screen reader or otherwise—where JavaScript is unavailable (a link would still work as link).
I wish I could handle both 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 role of “button” to a link—that makes sense! So if JavaScript replaces the links with buttons, I may be on my way to covering both scenarios. adactio.com/notes/17580
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