1.6 Use the clearest and simplest language appropriate

WAI checkpoint 14.1

Full WAI text: "Use the clearest and simplest language appropriate for a site's content."

Unless a site features very specialised content requiring specialised terminology, the language used to communicate information should be understandable by the widest possible audience.

Rationale

Overuse of jargon makes content difficult to understand. Complex, or long sentences and paragraphs are difficult to read and comprehend. Users do not like reading large tracts of text online and you should therefore structure content so that it can be -skimmed' easily. Skimming involves reading quickly over headings, titles and bullet lists to get a feel for the broad content of a page before reading it in detail.

Directions and Techniques

Create a style guide for written content

A style guide will help you to consistently provide accessible, easy to understand content by providing content contributors with direction on writing style, tone of voice and language usage.

Review content to ensure that it is clear and simple

Set up an editorial procedure to ensure that content is free of jargon and written to facilitate reading online, before it is published.

Consider providing a glossary of terms

If there are specialised terms which must be used on the site, provide a glossary which allows users to look up the meaning of difficult or unfamiliar words.

Use clear, concise headings and link titles

Headings provide context and help people to determine the structure of written information. Titles, including link titles, should provide an overview or a clue of the associated content.

Break content into small, easily read 'chunks'

Use paragraphs, bullet lists and sub headings to break content into small chunks which are easier to read and scan.

Use clear, simple language in audio tracks

If you provide information through audio or video, ensure that the language is simple and clear.

How you could check for this:

There are no specific test methods recommended for this guideline.

- View WAI checkpoint 14.1