• he him

night of the living bathroom

art tag is #dedusdraws


ewie
@ewie

I'm gonna be honest, I'm not a particularly huge fan of people doing fancy text like this:

Oooh look at this fancy text aren't I so fancy

Or some, like, homestuck typing quirk-ass text like this:

GC: Objection!!!

I think it's hard to read, it's hard to make sense of, and honestly I think it's also kinda annoying. But, I understand that for some people, it's how they want to (or need to) express themselves. And as someone who's a bit of a big fan of accessibility, I'd like to give people the choice to do what they want, but in a way that's not going to completely heck over people using screen readers.

So, I'd like introduce Accessible fancy text 🎉!!!

Below is a snippet you can use in your cohost posts (chosts) to make sure that if you use fancy text (which I wouldn't recommend using in general but still), it'll still be readable to screen readers. Below the fold is a writeup about it that goes into more detail.

The Snippet

<!-- use div, p, span, whatever works here -->
<div aria-describedby="user-content-id-name">
	<span aria-hidden="true"> <!-- Put your stuff here! --> </span>
	<span id="id-name" style="clip: rect(0 0 0 0); clip-path: inset(50%); height: 1px; overflow: hidden; position: absolute; white-space: nowrap; width: 1px;">Rewrite the stuff but in human-readable text</span>
</div>

It also works inline too!


ewie
@ewie

i’ve been seeing people use fancier text and stuff a lot more now that cohost is more popular so i’m gonna repost this as a reminder to make sure your stuff is accessible :)


dedusmulntxt
@dedusmulntxt

and since we're on cohost we can also just use css fonts instead of unicode


You must log in to comment.

in reply to @ewie's post:

all my snippet does is hide the text to a screen reader and offer substitute text for the screen reader to read. it is only ever applicable if the base text itself is not legible by screen readers. if you’re uncertain about whether or not you should use it, you can always activate the screen reader built in to your computer (or download a free one off the internet) and give it a listen yourself!

I don't mean this to be hostile, just curious (I want to be better able to test things going forward):

what fancy text and what screen reader? talkback and espeak read the unicode letter words just as their words at least on firefox (I checked by pasting the text elsewhere without your code blocks to make sure it wasn't just those)

edit: they still don't handle the block/circle text though, but they ignore it instead of spamming now

this post was made while i was still on twitter and i remained endlessly annoyed by the waves of discourse about people wanting to use the fancy unicode text in display names or posts and stuff. this is a beef i’ve had for a minimum of 4 years.

A meme meant to look like a sketchy ad. It reads, “Screen readers hate us! Learn how to ruin your disabled friends’ lives with this one weird trick! Find out how: click here.”

i really only re-shared it in response to a recent wave of posts because i didn’t want to spread negativity and preferred to share an old post that was helpful.

i tested it using only voiceover, which is the dominant screen reader on mobile (and is only moderately popular on desktop). i don’t have nvda or jaws on my computer, and didn’t want download any additional screen readers just for a cohost post. (sorry!) i have never of espeak, and according to usage data, its not used at all. talkback isn’t used very much, and given that i have heard that most people who need a screen reader will use ios solely for its accessibility features, it’s far more likely that talkback just hasn’t implemented the spec correctly and not that i am missing something. afaik, i am using these aria features mostly as intended, and these are the correct aria features for what i want.

hope that answers your questions!

yeah! no pressure, I just was wondering if you knew of a list or tested a few is all. This whole thing is a MESS, apparently i can't trust any single one since I'd just been testing things with TalkBack.

Windows Narrator fails the test too.