We have a framework to listen to actions whether they’re triggered by a click or a touchscreen or a keyboard. We add an HTML attribute data-action=“recommend”, and the system automatically attaches handlers. But this API was so successful that engineers starting slapping data-action on anything, even random <span> tags. Screenreaders don’t know about data-action, and won’t know that this is clickable.
Five Goofy Things Medium Did That Break Accessibility
Nick Santos

I totally agree, there’s really no excuse for not adhering to this advice BUT if it’s absolutely positively unavoidable, do you think `role=”button”` will suffice in terms of providing an accessible experience?