Louise's eLearning Blog

Posts Tagged ‘accessibility

While checking how long a document I had written was I stumbled upon another great feature of Google Docs that can help identify when a document may not be as accessible as it could be.

The Word Count (Tools: Word Count) function not only shows the number of words and characters in the document it also includes information / statistics from a selection of different readability scales.

Google Docs Word Count Screen

The document the screen grab is from is one of my own blog posts, which would not be very accessible for readers with lower literacy levels – but where should individuals be aiming? Should the content sometimes dictate the audience and their ‘assumed’ ability? Do I naturally write at the level my own education has reached – and is that therefore a problem if I need my documents to be easily digestible by a variety of people?

Flesch–Kincaid readability test – From Wikipedia

Scores can be interpreted as shown in the table below.*

Score Notes
90.0–100.0 easily understandable by an average 11-year-old student
60.0–70.0 easily understandable by 13- to 15-year-old students
0.0–30.0 best understood by university graduates

Reader’s Digest magazine has a readability index of about 65, Time magazine scores about 52, an average year 7 student’s (eleven years old) written assignment has a readability test of 60-70 (and a reading grade level of 6-7) and the Harvard Law Review has a general readability score in the low 30s. The highest (easiest) readability score possible is around 120 (e.g. every sentence consisting of only two one-syllable words); there is no theoretical lower bound on the score

* The Flesch Reading Ease Readability Formula

Therefore by using the numbers proactively it is possible to make a document more readable. For example by shortening sentences and using simpler terminology, readers with a lower reading age will find the document more accessible to them.

So next time you are creating a document why not see how readable it is – even if you don’t need to know how many words it has got!

I have just discovered a cute little tip for using Google Docs to create accessible learning resources!

Having collaborated with a colleague to create a how-to sheet, for a tutor wanting to know how to add a Hot Potatoes quiz with images to our VLE (Moodle), we discovered a good use for the alternative types of downloadable files.

Initially we were just going to save the file (which included screen grabs) as a PDF and upload to Moodle. However on noticing the “HTML (zipped)” option we decided to give that a try. It works really well!

The advantages in relation to accessibility are that the images are named so have alt text in the code generated (whatever they were named as individual files) which results in roll-over pop-ups. Also because it is HTML individuals viewing our VLE from a mobile device or games console for example will still be able to see the content, which would not be the case (generally) with PDF files.

Give it a try!


Previous Posts