Ben Ramsey on Nostr: #WebAccessibility question: I have my name in an `h1` heading, and my browser's ...
#WebAccessibility question: I have my name in an `h1` heading, and my browser's (Safari) text-to-speech reads it fine. However, when I add `text-transform: uppercase;` as a style to the heading, text-to-speech now reads out “B-E-N Ramsey.” It spells out “Ben” but not “Ramsey.” Anyone know why?
If I switch to Edge, it spells out the full name, “B-E-N R-A-M-S-E-Y.”
Those who work with screen readers, is this how they work? Do they always spell out words in all-caps?
Published at
2023-09-16 04:40:25Event JSON
{
"id": "c651867cd9bd2d32a807f09b8454300425476a8333a6dfc81cd2084e01398b1a",
"pubkey": "e653eb60b2db5edf906d354c2825bf00a80dfab1b1766cd97805155e8fcc0db3",
"created_at": 1694839225,
"kind": 1,
"tags": [
[
"t",
"webaccessibility"
],
[
"proxy",
"https://phpc.social/users/ramsey/statuses/111072983455307380",
"activitypub"
]
],
"content": "#WebAccessibility question: I have my name in an `h1` heading, and my browser's (Safari) text-to-speech reads it fine. However, when I add `text-transform: uppercase;` as a style to the heading, text-to-speech now reads out “B-E-N Ramsey.” It spells out “Ben” but not “Ramsey.” Anyone know why?\n\nIf I switch to Edge, it spells out the full name, “B-E-N R-A-M-S-E-Y.”\n\nThose who work with screen readers, is this how they work? Do they always spell out words in all-caps?",
"sig": "ccff7cccb0616038630a055080467c4368a7f54841d1314095106c0873322208a53a37ed9463c0d5766d8a4a4b0eb3c3a3e13490e28b5a3ec33cbb597660823b"
}
