alexseanchai: Katsuki Yuuri wearing a blue jacket and his glasses and holding a poodle, in front of the asexual pride flag with a rainbow heart inset. (Default)
[personal profile] alexseanchai
So one of my AO3 readers is a screenreader user, and she tells me her laptop does not play nice with emoji. (Her phone does, but that's not the point.) One of my Dreamwidth readers tells me that of these six emoji, 😸πŸ₯πŸ₯—πŸš°πŸ€’πŸ¦—, on her Windows 7 computer she sees two; the other four show up as the "Windows cannot identify this character" box. And at the size the emoji are displaying for me, I can't visually identify any of them. I know what five of them are without pasting them into Google, but that's because I know what I was doing last night when I was working on this fic; before googling, I cannot remember which cat face I used.

[Left to right: grinning cat with smiling eyes, croissant, green salad, potable water, face with thermometer, cricket. If I did not already know that was a cricket, I would wonder why there is an emoji of a queasy chicken.]

AO3 Work Skins/Tutorials series has, under the iOS text mockups one, a workaround for AO3 being uncooperative with emojis. Vintage 2016. As of November 2018, AO3 and emojis get along fine. HTML and I also get along fine, provided I can get to w3schools; CSS and I do not, and what we're relying on in those tutorials (and also in Repository) to get the visual effect of the iOS text messaging or whatever, without sacrificing accessibility for readers of downloaded fic copies et cetera, is AO3 work skins with CSS. Now, this workaround has image descriptions in for emoji (using the title attribute), so presumably there is a way to make the emoji accessible for all concerned, though the workaround is no longer necessary in order to make the emoji appear at all without eating everything later in the fic.

(I absolutely did not notice in October 2018 that only the first scene of the last part of something I posted that August was up on AO3. Nope. Certainly not.)

...So how do I do this?

(I'm linking this post in this comment thread, so anything we work out here is also there for the benefit of any other people turning to that AO3 tutorial for emoji help. So you know.)

ETA: Having been reminded by an article on image alt text best practices that the title attribute is approximately useless to users of either screenreaders or touchscreens, it follows that the above-mentioned workaround for emoji on pre–November 2018 AO3 was never useful for screenreader users at all—or touchscreen users, whom it hadn't occurred to me to worry about. (They type wryly, on their tablet's touchscreen keyboard.) So I'm suddenly a lot less sure my question has an answer. Also, using a span tag with a title attribute to handle transliteration and translation of hanzi, like I'm doing here with 敏塐, clearly isn't going to work either! Which expands the scope of my original question somewhat... (I'm copying that HTML into a comment below.)

With the emoji, the workaround [personal profile] stellar_dust and [personal profile] sylvaine suggest of images with alt text should indeed work. I'm still looking for a way to treat emoji as, essentially, text, because they're Unicode and that makes them essentially text, right? The hanzi, though, those are text, there is no question of it. I seriously do not want to screenshot the hanzi in order to embed an image with alt text if there is any way to avoid that while keeping the transliteration and translation attached to these bits of text!

(...the Mandarin transliteration, anyway, as found on Wiktionary. But this isn't where to ask about where to find the Wenzhounese transliterations my fic is more in need of...)
the_jack: a low-res style drawing of Te and Jack (Default)
[personal profile] the_jack
Inspired by both the Physical Disability Bingo Card and the Invisible Disability Bingo Card (and IDBC the sequel), I'd like to make a bingo card highlighting the horrifically unhelpful things people with disabilities all too often hear from people who should really, really know better: doctors (and other medical personnel including but not limited to nurses and EMTs, but primarily doctors).

My personal "favourite" is when I see a doctor for a follow-up appointment after they've ordered some tests, and they announce to me, "Great news! You don't have [insert diagnosis here]!" without actually having the real good news that they've identified the cause of the symptoms I came to them about. Especially when this is then followed by them essentially washing their hands of me, as they've looked for "everything" and "all the tests came out normal." Thanks, genius, unless your statement alone magically makes my body work again, it's not helpful at all.

I know other people probably have their own contributions to this category of fail!statements and fail!questions, and other people may come up with better phrasing than mine for many of them. (Brevity, alas, is rarely one of my virtues.) So please, contribute your own "favourite" inanities you've heard from doctor after doctor.

Another favourite of mine is "I'm not filling out any disability paperwork for patients (any more)" -- sometimes phrased as, "If you want the doctor to fill out disability paperwork, there's a fee of $___ for each form, which your insurance won't cover because oh right, it's actually illegal for us to charge for that especially when we're already billing for the office visit."

Then there's "No, I won't prescribe that medication for you, even though it's neither controlled nor a risk for addiction, and I actually don't have any particular reason for refusing, I'm just being stubborn."

Yet another favourite, though I haven't run into it personally in years, is "Either you really have that symptom/condition, OR you know some technical terms used to describe it in medical literature and other exclusive content like WebMD and Wikipedia; any patient who comes in and uses the correct terms to discuss either a symptom they claim to have or a specific diagnosis they want to be checked for is obviously either a hypochondriac, a malingerer or both!"

edited to add:
"If you just go back to your regular routine, you'll be feeling yourself again in no time." (Yes, this is different when it's actual medical advice and also being given in place of appropriate medical care, as opposed to when some doubtless-well-meaning layperson says it.)
and
"Your presenting with both symptom A and symptom B is suspicious, despite the fact that at least a dozen recognised illnesses feature both symptoms as common and/or diagnostic."
and
"I see that you're taking medication X, based on which I will assume that you have condition B, even though you helpfully wrote right next to the medication name and dosage that the medication was actually prescribed to treat condition A, and even though you wrote in the medical-history section that you have condition A and made no mention of condition B."

Although I've heard things like "but you're so young!" and "you seem fine / don't look disabled" from doctors and other medical professionals, I'm aiming for things which are profession-specific and haven't already been addressed on one of the other bingo cards.

As you can see I need help trimming these down from rant-size to bingo-card size, so suggestions toward that end are appreciated.


While I'm here... I've been wondering how screen readers and/or other assistive technology handle emphasised text, be it bolded, underlined, italicised or formatted with some other HTML tag, and whether some tags are more likely than others to get dropped by (or become illegible to) people using various kinds of assistive technology. Toward that end, some examples so people can tell how their tech does at letting them know what formatting the writer has applied:

1. This sentence has no HTML formatting tags.

2.
This sentence is enclosed in HTML "pre" tags.


3. This sentence is enclosed in HTML "B" (bold) tags.

4. This sentence is enclosed in HTML "U" (underline) tags.

5. This sentence is enclosed in HTML "I" (italic) tags.

6. This sentence is enclosed in HTML "em" (emphasis) tags.

7. This sentence is enclosed in HTML "S" (strikethrough) tags.

8. This sentence is enclosed in HTML "sub" (subscript) tags.

9. This sentence is enclosed in HTML "sup" (superscript) tags.

Those are most of the tags I use. If there are other tags other people use frequently and are willing to change their usage of, if necessary, so that their intended meaning can be better conveyed to those using assistive technology -- or tags that people who use assistive technology know don't come through for them -- please comment, and I'll modify this post to reflect those, too. Please also note which software and/or hardware you're using, not so much for me as for other AT users, so we can helpfully compare how text renders in different programs. I encourage people using magnification (or some other assistive technology) rather than or in addition to a screen-reader to contribute their experiences as well.

Finally, does the "fandom heart" emoticon, <3 (less-than / pointy-bracket numeral-three) get lost in translation for anyone? Would the ASCII ♥ be better?

(Please also suggest any tags -- post tags, that is, not html tags -- I ought to have included but didn't. Or, actually, other html tags would also be good! But for different purposes.)
jesse_the_k: text: Be kinder than need be: everyone is fighting some kind of battle (expectant)
[personal profile] jesse_the_k
Over on the [site community profile] dw_accessibility community, I proposed a way to make it easier to follow who's talking with whom on long comment threads.

Particularly if you use a smaller screen (netbook, phone), large print, audio or braille to read your Dreamwidth circle, I'd love your sampling the discussion and contributing your thoughts.
sasha_feather: dolphin and zebra gazing at each other across glass (dolphin and zebra)
[personal profile] sasha_feather
[personal profile] hope's post Nerdy PSA: Accessibility Tips for the Casual Coder is a good resource for how to make your blog or website more accessible for screen reader technology. Screen readers are tech that blind or sight-impaired people can use to read the internet (they read text aloud).

What I've done is bookmark this page and open it if I'm constructing a blog post in which I want to pay particular attention to access issues (say for instance one with images, but I try to do work on this generally, little by little). I also picked out a couple of things off hope's list of suggestions to work on, rather than tackling the whole list at once.

---

One in particular that I would like to see more of is descriptive links. Personally I'm much less likely to click on a link if I do not know where it will lead me.

So a non-descriptive link looks like: hey this is cool and pretty!

And a descriptive link looks like: Here is a cool photo on Flickr of some horses

The same link with a title tag: Photo of horses on Flickr (note how there is a text box that appears if you mouse over the link) ETA: See comments for why not to rely on title tags

Another thing to do is just tell the reader somewhere in your post where your links direct. For example. Hey, I like the movie Pitch Black (link goes to IMDB).

----

Here is the code for including a warning that is accessible for a screen reader. (Warnings are for posts/stories that have triggering content or triggering language).

(<a title="Skip this Warning" href="#skip">skip</a>)<span title="This is a spoiler. Highlight to read." style="color:#666;background-color:#666;">
Text-you-want-to-be-hidden-under-the-gray-bar
</span><a name="skip"></a>

which creates:
(skip)
Text-you-want-to-be-hidden-under-the-gray-bar



The "skip" link lets a speaking web browser stay silent about the warning.

May 2025

S M T W T F S
    123
45678910
111213141516 17
18192021222324
25262728293031

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags