Dyslexia

The Accessible Web #4: Text and typographyMarch 13th, 2009

An ongoing series of articles about web accessibility issues, tips, tricks, and standards.

It’s amazing that something as simple as how the body text looks on the page or screen can help or hinder with reading. Font selection, spacing, line length and the alignment of the text can all make a massive difference.

Font selection

Sadly there isn’t much choice in font selection on the web just now, since with most browsers the font needs to be on the user’s computer. This pretty much limits you to a small list of fonts including Verdana, Times New Roman, Arial/Helvetica, Gill Sans and Lucida Sans.

Font selection should still be taken with care; fonts have their own character and very often Verdana and Times New Roman are overused (and should only be used as fallback).

Contrary to typography rules for paper, you will likely be better off choosing a sans-serif font for your body text. This is because the relatively low resolution of a computer monitor will make those fonts with serifs a little harder to read than those without them. Having a serif font for the header will however often make a nice contrast.

Leading and kerning

Leading (pronounced to rhyme with heading) is the amount of space between two lines of type: the name comes from the thin block of lead originally used to increase the space. Kerning is the space between two letters.

Both leading and kerning can affect how quickly and easily the copy can be read: too big a leading and the reader will struggle to read down to the next line. Too small a leading or kerning and the letters and words might be hard to distinguish. If you’re unsure, you ought to leave these to the defaults.

Line length

Again, speed and ease of reading is affected by line length. If the line is too long then the muscles in the eye and neck need to be used, which is tiring for the reader. It also affects how easily you can find the next line: the eye has to travel a relatively great distance to go back to the start of the line.

Alignment

In Latin languages, body text should be left aligned; any other alignment will be confusing for the reader. Right and centre aligned text is fine in some cases, such as the tag and category information that is displayed at the bottom of this post.

Justified text should never be used: using this alignment means that gaps appear between words and so ‘rivers’ of space will form. This can be disconcerting for those with dyslexia and so they will find it hard to read the copy.

The Accessible Web #2: All about colourDecember 19th, 2008

Picking the right colours for your site can be a tricky thing, and the accessibility considerations only makes things a bit trickier. But if you ask me, the limits imposed will make your website easier to see and read by everybody: somebody doesn’t have to be colour-blind to struggle to read green text on a red background.

Help the colour-blind

A large chunk of people are colour-blind: about 1 in 10 males have red-green colour-blindness, this is when the person cannot easily discriminate between red and green hues. A less common form of colour-blindness is blue-yellow colour-blindness, where the individual struggles to discriminate between blue and yellow.

The quick and simple solution to make life easier for those who are colour-blind is to not use the red/green and blue/yellow colour combinations where discrimination is important (for example having green text on a red background, or having red and green as the two colours on a graph). To check how a site looks to somebody who is colour-blind, take a screenshot and convert the image to greyscale.

Give the colours sufficient contrast (WCAG2 1.4.3/1.4.6)

Giving the background and foreground colours enough contrast makes it easier for those with visual difficulties to read the text, and makes the site easier to read in general by everybody (I’m sure we’ve all squinted at some yellow text, struggling to read it).

A formula (based on ISO-9241-3) is used to gauge a ratio of the contrast between two colours. To meet WCAG2 Level AA this should be at least 4.5:1 (3:1 for text larger than 18pt), which is increased to 7:1 (4.5:1 for large text) if you want to meet Level AAA. Some websites prefer to have an option to change the colour scheme to a high contrast one, which is perfectly acceptable.

Don’t use too much contrast!

Having said that, try not to have too much contrast. People who have dyslexia sometimes struggle to read text (particularly small text) which has a high amount of contrast (black on white is a classic example).

For a quick and simple fix, don’t use black on white. Depending on your site’s colour scheme, you might want to use a dark shade of grey (BBC use the colour value #4d4d4d) or you might want to introduce a light background colour.

Using colour correctly (WCAG2 1.4.1)

When using colour, don’t forget that not everybody can see it. If you were to say “click the red button to continue”, you need to keep in mind that people may not be able to see which is the red button (this isn’t to say that using colour-coding is bad, just make sure you don’t rely on the colour to identify objects or an as an action prompt).

Many website owners and developers don’t realise this, but only using colour to identify a link and identifying failed/required fields with colour only may fail WCAG2 guidelines.

Final thoughts

The best way to ensure your site is viewable by everybody is to go out there and test it. You don’t even have to do formal testing to get colour right, since colour blindness and dyslexia are relatively common. Chances are you have a family member, friend or colleague who have one of the two, so run the site past them to see if they struggle at all.