Sunday, March 11, 2018

Accessibility as default

Over the last couple of years I have become increasingly aware of accessibility issues in online education. I admit to previously not giving much thought to how people whose hearing, sight, physical mobility or cognitive abilities are different to my own, interact with digital media. However by meeting and discussing with people involved in this area, I have gained a few insights into accessibility questions and a whole new world has opened itself to me.

An article on the Webinar blog, Webinar Slides And Text-To-Speech, highlights the issue of writing to facilitate text-to-speech applications. If we follow some simple guidelines we can make sure that all our digital resources are more accessible. Instead of making alternative accessible versions, why not make accessibility default?

In a perfect world, we would make a version of presentation materials that are optimally designed for a sighted audience listening to a narrator, along with a second set of hardcopy materials that can be referenced by a larger and more physically diverse audience. But there are practical considerations for how much time and effort presenters can dedicate to their materials. If you can only make one version, why not make it accessible to everyone?

The article refers to an excellent guide to writing for accessibility: the British Dyslexia Association's Writing for text to speech. For example, when writing presentation slides, extra attention to punctuation can make an enormous difference for those who need to listen to the text. If you write bullet points without a full stop or semi-colon at the end of each point, then the text-to-speech app will simply read all points as one long sentence. With punctuation, however, it will be read as a list with pauses between points. Some other simple tips:

  • Write numbers manually in bullet lists since the automatic numbering is not picked up by the text-to-speech apps.
  • Dates should be written using the name of the month rather than combinations of digits (11 March 2018).
  • Times should use a colon instead of a stop to separate hours and minutes (10.30). 
  • Put stops in acronyms, otherwise the app may say it as a word (U.S.A. or e.g. would be best). 
  • Use styles to show headings or sub-headings rather than bold normal text. 
The list goes on. The point is that by following some simple rules, you can easily make your texts more accessible. Furthermore we also make our resources clearer and more consistent for all. Text-to-speech is used by many with perfect sight, for example listening to text in a mobile. Shouldn't we make sure we teach accessibility as default and not as an optional extra?

We all have so much to learn!

No comments:

Post a Comment