a11y (digital accessibility)

190 readers

1 users here now

#Introduction This community is dedicated to discussing topics around digital accessibility and disability rights. Please be respectful following the rules below.

#Guidelines No abusive, derogatory, or offensive posts or comments. No porn, gore, NSFW, or advertisements are allowed. Do not vendor spam accessibility products or events.

#Encourageent Please ask questions and share your experiences around digital accessibility and disability rights. Please be open to other views so we can engage in respectful dialogue.

#FYI I'm waiting to add an icon or badge until alt text can be added for them in Lemmy.

founded 1 year ago

MODERATORS

Thinker33

Strikethrough Accessibility (www.webaxe.org)

submitted 7 months ago by Thinker33 to c/a11y

1 comments fedilink hide all child comments

This article explores different ways of coding strikethrough and uses screen reading software to determine how accessible each method is. Hopefully, more screen reading software will support the scenario 1 method used in the future.

top 1 comments

sorted by: hot top controversial new old

[–] kellyaster 1 points 7 months ago

I also hope scenario 1 is adopted more widely. Native html is always ideal due to its inherent semantics without the need for hacks or additional workarounds, though users will have to demand their screen readers support it and devs will have to insist on using it if it's ever to become widespread.

They never should have deprecated as a strikethrough in the first place, but I digress. The tag makes the most sense because it is an HTML5 standard, and we should all push for semantic html usage and support.