Level
Foundation
Reading time
150 min
Entries
18 lessons
You get
Certificate (70% to pass)
/ Courses

Accessible Content & Plain Language

For content authors, editors and marketers. Most accessibility barriers are created in the words, not the code. Learn the writing habits that make content usable for people with cognitive, visual and reading disabilities - and better for every reader.

27 quiz questions

Read the first lesson

The whole of lesson one, as written. The rest of the course reads the same way.

Picture two versions of the same sentence. One says, "Utilise the aforementioned functionality in the event that remuneration has not been received subsequent to the due date." The other says, "If you have not paid by the due date, use this feature." Same information, same code, same design. One of them excludes readers before they finish the first line.

Most accessibility barriers people picture are technical: a missing alt attribute, a button a keyboard cannot reach. But a huge share of the barriers a reader actually meets are written, not coded, dense jargon nobody defines, a link that says "click here" five times on one page, a heading that reads as a pun instead of a signpost, a photo captioned only with its camera filename. None of those need a developer to fix. They need a content author who knows what to change.

That is the promise of this course. It is built for anyone who writes for a website or app, editors, marketers, support staff, and it needs no code. Each lesson gives you one concrete habit, and the method stays the same throughout: pick one real page you own and rework it as you go, so you finish with a genuinely improved page and a repeatable checklist, not just theory.

Content authorAnyone who writes or edits words a reader will see: page copy, product text, support articles, captions.
Plain languageWriting built to be understood on a first read: short sentences, familiar words, clear structure.
Assistive technologySoftware and devices, screen readers among them, that people use to access content on their own terms.
Why it matters

A developer can ship a perfectly coded page, and your words can still turn a reader away, or quietly welcome them in. Content decisions are accessibility decisions, made by whoever writes the words, no code required.

Lesson 1 of 18.

Syllabus

  1. Writing in plain language

    6 lessons · module test

    1. 01Words are accessibility too
    2. 02Short sentences, active voice, everyday words
    3. 03One idea per paragraph and the inverted pyramid
    4. 04Jargon, acronyms, idioms, and numbers
    5. 05Testing readability: read it aloud, then measure it
    6. 06Who plain language serves, and why it is not dumbing down
  2. Structure readers can navigate

    6 lessons · module test

    1. 07How people actually read: skim, jump, listen
    2. 08One H1 and a hierarchy that never skips
    3. 09Headings that describe, not decorate
    4. 10Real lists and real tables
    5. 11Structure in documents: Word, Google Docs, and PDF
    6. 12Page anatomy: titles, summaries, and chunking
  3. Links, images, and readable data

    6 lessons · module test

    1. 13Links that make sense out of context
    2. 14Buttons and link etiquette
    3. 15Alt text that conveys purpose
    4. 16Decorative, informative, or complex: the three-way call
    5. 17Readable data: charts, tables, and numbers
    6. 18The editorial checklist and your next steps
Enroll
Free