Presently authors need to employ visually hidden content to programmatically convey what the element visually represents with its default UA CSS strike-through.

Just for the sake of clarity, authors could also use role="deletion" rather than visually hidden content.

Thank you for the clarifying comment @jcsteh. Yes, my comment was meant to allude to practices that have been promoted prior to that role’s wider implementation, and the fact that there is a “semantic” difference between the html del and s elements. I have a minor companion Pr to edit the aria spec so that the deletion role definition covers both use cases for the different html elements.

I'm going to merge this since it's been picked up by @spectranaut for implementation in chromium, and Firefox has marked the bug as an enhancement.