#sight impared

I was wondering about blind and sight impared readers and how I can make my posts accessible for their reading software. So I called my local institution and they pointed me to a website that lists tips on how to make a website accessible for any surfer, be it blind readers, readers who can’t use a mouse, deaf readers, colorblind readers, epileptic readers, readers with RSI etc. Because about 15% of the population is not able-bodied.

The reading software I mention is software that reads a website out loud, based on the code behind it. Not only blind and sight impared people use it, but also people whose body isn’t fit to work with a mouse and/or a keyboard.

Since the list they pointed me to is not in English, I want to translate it for you. Here’s what I learned for tumblr posts. Spread the word!

1 Navigation

1.1 Use the structuring tools tumblr provides

Use the title feature for (sub)titles, so that the software knows it’s a (sub)title. A text in bold, cursive, or in a different or larger font type is just a plain text for the software. It doesn’t know that it’s a title.

If you make a list, don’t write a dash (-) or an asterisk (*) in front of the listed elements. Use the list feature, like I did in this list.

Don’t write *** between paragraphs to structure your text.

1.2 Your links are meaningful

The reading software makes a list of all the hyperlinks in a text. It’s confusing for your reader if it lists the word “here” five times. Provide context and meaning in your hyperlinked text.

Don’t write: “You can find more interesting articles here.” but write: “You can find more interesting articles here.”

Don’t write: “Sources: (x), (x) and (x)”, but write “Source 1, source 2 and source 3.

2 Content

2.1 Your post has a meaningful title

You don’t read every post from beginning to end, you scan to see if there’s anything interesting. So does this software. It scans the main title and any subtitles formatted in the title feature, so the reader can decide if it’s worth reading the plain text as well.

2.2 Images are described or have an alternative

The software can detect that there is an image, but can’t read it.

If you can avoid it, don’t give text in an image. If you share for example a poster of an event, with a date and a venue, that’s essential information the software can’t read.

Alternatively, you can add an image description, for example: “[Image description: a printscreen of my manuscript, with the word THE END in all caps underneath the last paragraph]”.

Sometimes an image works better than describing it in words. For some of my more complex writing advice posts, I choose to put information in an image because it works better than writing it all out. In that case, I will add the image description underneath the cut (”read more”) and mention above the cut that readers can find it there.

2.3 Video and sound

Like with images, label video and sound.

Subtitle videos (because automatically generated subtitles are not dependable).

Don’t let video and sound start automatically.

This is also relevant for able-bodied readers who are in a loud environment, or choose not to activate the sound or video because of slow internet connection etc.

3 Format/design

Don’t use spaces and other characters to format your text.

Chose texts and images that don’t blink more than 3 times per second, for epileptic readers.

Make sure colorblind people can understand your post, don’t use color as a differentiating feature.

Make sure your links are distinctly recognisable as links.

I hope you find this as useful as I did. I realised that it takes me little effort to include all kinds of readers into my posts, so I will take this into account with future posts.

Feel free to add to this, or correct me if I’m wrong, or if I accidentally gave information that is specific for my language. I don’t need to use it myself, but I want to include everyone.

I’m finishing off a post on writing advice in which I switch back and forth between text explanation and image examples. I want to provide image descriptions. What is the best approach?

Also, what does your software read out loud besides the text? Does it read enters and paragraph breaks? Interpunction? Bold and cursive? All caps?