Thread: The Reading Vent & Rant Thread
View Single Post
Old 02-09-2025, 12:33 PM   #3460
ownedbycats
Custom User Title
ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.
 
ownedbycats's Avatar
 
Posts: 11,109
Karma: 77213681
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
Quote:
Originally Posted by ownedbycats View Post
Does it behave different with screenreaders?
Yes: https://www.timdunklee.com/notes/use...-letters-a11y/

Quote:
During one of our remediation sessions, I noticed an interesting thing that happened. Our accessibility expert was navigating through items on the page, when he landed on a heading that was typed manually in all capital letters. The heading read “SEE HOW IT WORKS.” When he focused on this heading it read out the word “IT” as “I.T.” because it thought it was an acronym. As a test, we quickly updated the heading to be title cased and used CSS text transform to make the text simply be styled as all uppercase. The result was that the heading was properly read out. I’ve always felt odd about data being in all uppercase letters, but now I have a very good reason for it.
ownedbycats is offline   Reply With Quote