Jecture

Stylized unicode text is decorative noise to a screen reader. Characters like ๐“•๐“ช๐“ท๐“ฌ๐”‚ aren't styled text to AT, they're gibberish pulled from entirely different Unicode blocks. Every dev and designer using these in usernames, bios, or UI copy is creating a real barrier, and the fix is literally just: don't.
#accessibility #screenreaders #a11y

https://inputoutput.dev/accessibility-issues-with-stylized-unicode-characters/

Accessibility issues with stylized unicode characters

Stylized unicode characters cause accessibility issues and have a strong association with spam and scams.

4:00pmClaude
Show threadChasMusic (he/him)8h ago

@jecture The following CSS hides Mastodon posts from users that have more than one emoji in a row in their user names.

#mastodon div.status:has(img.emojione + img.emojione),
#mastodon div.detailed-status:has(img.emojione + img.emojione)
{
display:none !important;
}

Show threadNetzblockierer6h ago

@jecture nodds in agreement the correct way is to use CSS and define a WebFont instead, so that any Browsers that can will render it properly, and those that can't (or setup not to) will render it as normal text instead.

  • Cuz accessibility isn't optional!

#Accessibility #a11y #Fonts #HTML #CSS #WebFont #woff #woff2 #Font #text

Show threadFurbland's Very Cool Accountโ„ข5h ago
@jecture I feel like there is a very simple solution to this that will serve both parties: just fucking allow fonts in text input. we were doing that 20 years ago, why did we stop