
Are you writing for accessibility?

Are you writing for accessibility?

Writing content for the web is no easy-feat; it’s a complex task that requires you to think about the structure, format and words you use. While getting the right words on the page is important, you must also consider certain technicalities when writing web content.

Writing for accessibility is crucial for web content. It means creating content that has no barriers and allows complete access to, or interaction with the website. What you write affects the delivery of your information online.

The Web Content Accessibility Guidelines (WCAG) 2.0 provides important information on how to make web content more accessible. Federal, state and territory government departments need to comply with levels A and AA of WCAG 2.0 to make their content as accessible as possible. It’s recommended you use these guidelines whenever developing content for the web.

Use our list of accessibility tips below, as well as the WCAG 2.0 guidelines to ensure your writing can be understood by all users.

  1. Write for everyone

When creating content for your website, always write in a style that is inclusive and easy to understand. It needs to be customer-focused, written in plain language, relevant and engaging.

Reading words on a page is very different to reading words on a screen. The type, quantity and layout of information online should appear differently to a printed document. When writing for the web, consider:

  • Headings – make sure they clearly describe the topic to help navigate users around the site.
  • Page titles – use a clear title to clearly describe the page and its intentions.
  • Writing style – Plain English is the best way to write content. It means readers can understand the document quickly and easily. Aim for age 9 reading level (Australian Year 3 or Year 4) so everyone can understand your content.
  1. Images

When selecting images, consider if they can be interpreted by screen readers, voice recognition and keyboard navigation. For example, only include images on a page if they meet a real user need and add to the text. If you choose to use images, use meaningful alternative (alt) text to accurately describe it. Also, use different text for the caption and alt text to help sight impaired users listening to the page through assistive technology.

  1. Audio and Video

All audio and video files on your website must have a transcript for people with a disability. The transcript must tell the story and present the same information as the pre-recorded content. Also include accurate captions to explain what the multi-media is about. Don’t rely on auto-captioning options because they will not always accurately describe the text.

Creating accessible content is an important part of online writing and you should refer to these tips when developing content for government clients.

If you want to know more about creating content for web, check out our Ultimate 10 Step Content Creation Checklist for Government Communications.


Each week a staff member puts pen to paper to write about an aspect of content communication that speaks to them, and hopefully, informs you. This is a space where our passion for writing, learning and sharing information comes to shine.

Leave a Reply

Your email address will not be published. Required fields are marked *

Want to know how to innovate in the government communications space?
https://contentgroup.com.au/2019/04/are-you-writing-for-accessibility/
contentgroup.com.au
crawl=CC-MAIN-2019-47
80287
application/http; msgtype=response
sha1:TMODZ54JHUDVUXFDE76C6ZACSNJBMMAQ
<urn:uuid:751123d0-a653-42f9-b6f6-43711253e668>
2019-11-12T16:42:16Z
77.104.170.92
text/html
sha1:BPHHDRV6M6K5MXNRIIIIHH2EBPQBTFL6
<urn:uuid:5261de3f-9add-4193-bd57-aaeed48a6dfb>
https://contentgroup.com.au/2019/04/are-you-writing-for-accessibility/
response
<urn:uuid:a7c0c15f-1ac4-4c57-b479-fd323552900f>
isPartOf: CC-MAIN-2019-47
publisher: Common Crawl
description: Wide crawl of the web for November 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-104.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/