𝓓𝓲𝓭 𝔂𝓸𝓾 𝓴𝓷𝓸𝔀 𝓽𝓱𝓪𝓽 𝓽𝓱𝓲𝓼 𝓲𝓼 𝓪 𝓣𝓸𝓸𝓽! 𝓯𝓮𝓪𝓽𝓾𝓻𝓮?
𝕊𝕖𝕝𝕖𝕔𝕥 𝕤𝕠𝕞𝕖 𝕥𝕖𝕩𝕥, 𝕒𝕟𝕕 𝕡𝕣𝕖𝕤𝕤 𝔽𝕠𝕟𝕥 𝕚𝕟 𝕥𝕙𝕖 𝕡𝕠𝕡𝕦𝕡 𝕞𝕖𝕟𝕦.
𝕴𝖙 𝖎𝖘 𝖛𝖊𝖗𝖞 𝖆𝖓𝖓𝖔𝖞𝖎𝖓𝖌.
@tootapp 𝖆 𝖈𝖚𝖗𝖘𝖊 𝖇𝖊 𝖚𝖕𝖔𝖓 𝖞𝖔𝖚 for this 𝓵𝓸𝓿𝓮𝓵𝔂 𝓯𝓮𝓪𝓽𝓾𝓻𝓮
@tootapp It's kind of not friendly to people using screenreaders tbh
@zigg It's not really friendly to anyone.
(Although screenreaders should in theory be able to parse it through Unicode tables, but I don't know how much they bother.)
@tootapp yeah, that kinda hurts to look at
@tootapp If you do this again can you add a CW on it? because this really hurts my eyes :(
@maloki The most horrible thing is, due to the way it is implemented, it works in the CW field too.
@tootapp Maybe you should reconsider that?
@zichy It is definitely not a feature meant to be used regularly, and it's hidden for that reason.
Although it would probably be a good idea to report it as a bug for the screen reader, as people do use funny Unicode tricks like these quite regularly.
@tootapp is the text still good for accessibility and screen readers?
@tootapp Is it accessible?
@tootapp I immediately looked for a new TestFlight build, then realized something. 𝙸 𝚍𝚒𝚍𝚗’𝚝 𝚗𝚎𝚎𝚍 𝚘𝚗𝚎. But, I would not be opposed to receiving one anyway… 🤞🏻
@jamie Me too... But I just spent a lot of time implementing loading timelines in both directions, only to realise it doesn't actually work with Mastodon. Luckily Gargron is looking into fixing it, but I need to wait and see until it lands so I can version gate the feature. Working on more stuff while waiting.
@tootapp in addition to the accessibility problem people are mentioning, these weird font posts also cause Amaroq to hang for a few seconds every time I scroll past one for some reason. It’s a super pain!
@tootapp this is 𝖗𝖎𝖉𝖎𝖈𝖚𝖑𝖔𝖚𝖘!
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!