Reminder for those who may not be aware that those "fancy/custom text" things using special unicode characters that bypass ASCII fonts to make your name look cool or fancy or whatever ruin accessibility, like hard.

They break screen readers hard, since most, if not all, don't know how to handle them properly and end up pronouncing something like "Special character S" or whatever. They're also significantly harder to read than a user's chosen font, or the default fonts on any reasonable operating system or website, especially for neurodivergent and in particular dyslexic people.

Please stop using them, and maybe nudge your friends to stop using them.

Boosts appreciated for awareness

#Accessibility #FancyFonts #Neurodivergent #Boostswelcome

@fizzyizzy05 @0x4d6165 hm i wonder if you could implement a "simple" version of your name thats not using special characters and then a "fancy" version too, and then just show the simple one to screen readers, you could even have a toggle for it .. maybe hmm :?

this way you can still have this way of expressing yourself, and everything else still works .. maybe ..

@Li @fizzyizzy05 @0x4d6165 Hmm, maybe a browser setting to only "display" ascii characters + overwrite fonts / text styling with a user chosen one if desired. Although that doesn't fix any text that is embedded in an image or something but for text as text that might work.
But then it also makes sense to just make text accessible when possible -TS
@SphereSystem2 @fizzyizzy05 @0x4d6165 really you want to something to normalize unicode symbols that look alike so like 🅰️ => A and stuff .. i think iconv can do something like that .. but i mean this breaks if your not from english speaking culture still since ascii is very english centric
@Li @fizzyizzy05 @0x4d6165 Yes, that's true you need to also allow for other alphabets which ascii doesn't at least well. Hmm, maybe what you need is a sybol set between unicode and ascii, something that includes all the alphabets and nothing else, although that does mean trying to get people to agree to a third character set standard which oof.
@SphereSystem2 @fizzyizzy05 @0x4d6165 the issue is unicode is for script from every language, things like æ and ß etc have actual meanings but also "look like" ae and B .. you need to know purpose of why their used not what is used ..
@Li @fizzyizzy05 @0x4d6165 Yes, that certainly doesn't help at all. Hmm, guess you would need a language tag included to filter for characters outside that language, but then that needs to easily be changed and runs into issues even then for anyone multilingual potentially, in our experience when people share multiple languages the language can switch mid sentence, let alone between them making any language tagging difficult.
@SphereSystem2 @fizzyizzy05 @0x4d6165 i think doing it automatically just wont work and what you need is something like alt text for text, tbh but anyways
@Li @fizzyizzy05 @0x4d6165 You are probably correct on that, although given that people don't always use alt text already it is probably still mostly a social issue to be solved socially as much as a tech solution feels easier in some ways, sometimes there isn't one or if there is it's absurdly complex actually.
@SphereSystem2 @fizzyizzy05 @0x4d6165 i think its partly a social issue, partly a technical one, screen readers not handling it properly feels like a technical problem, and things like an "alt text for unicode weirdness" seems like a possible solution to that, but then the social problem is that you'd have to get people to do that, maybe it'd get less pushback than just 'dont do this at all' though .. i suspect it would, as peoples names are like .. well yknow? .. but erh
@Li Yes, it's possible that making some technical changes could help with the social issue, but it almost certainly can't be the entire solution, making it easier to make sure text is accessible helps but it's probably practically impossible to ensure it is purely technically so some social soloutioning is likely necessary as well.