Checkpoint 4.1 Ideas
This is a collection of ideas and proposals related to Checkpoint 4.1.
Master compiled list
As a group, we need to sort the items listed below into the categories
listed in the next section. For example, some of the proposals that apply to
other checkpoints have been included under the appropriate heading at the end
of the list.
- content under site control is written as clearly and simply as the
author feels [appropriate / possible] for the purpose of the content.
[1]
- a statement is provided on the site which asserts that those
responsible for the site have reviewed the materials on the site and the
content under their control is written as clearly and simply as they feel
is [appropriate / possible] for the purpose of the content. [1]
- summaries and/or simpler forms are provided for key pages or sections
of the site. [1]
- Provide an outline or a summary for your document. [1]
- Break up long paragraphs into shorter ones, with one idea per
paragraph. [1]
- Break up long sentences into shorter ones. [1]
- Provide accurate unique page titles. [1]
- Ensure that headings and link text are unique and that they make sense
when read out of context. [1]
- Provide definitions for any jargon or specialized terminology used in
your document. [1]
- Provide explanations of figurative, metaphorical, or idiomatic uses of
language (for example, 'haven't seen you in a coons age' or 'the sight
tore my heart out')." [1]
- Language is used that your intended audience ought to be familiar with,
[1]
- When introducing new concepts or terms, they are defined or annotated
in language that the audience should be familiar with or definitions or
explanations are linked to that might be easier to understand. [1]
- avoid confusing and distracting content [2]
- In instructions, use: a, active voicing b, visual references, absolute
reference (rather than relative ones) [3]
- if a simplified/controlled language exists for your industry/field, use
it. [4]
- Do not use more then one negative in a sentence. [3]
- Use simple verb tenses. [3]
- Avoid split infinitives [3]
- State meanings explicitly. [3]
- Use concrete words[3]
- avoid redundancy <importance = 0.6> (we would need to add that
this is only redundancy in text itself)</importance> - omit
needless words [3]
- Avoid noun sandwiches e.g.: Underground mine worker safety protection
procedures development (add "OF" AND "FOR")[3]
- Readable sentences are simple, active, affirmative, and
declarative.[3]
- State one thing and only one thing in each sentence.[3]
- Divide long sentences into two or three short sentences.[3]
- Strive for a simple sentence with a subject and verb. Eliminate
unnecessary modifiers.[3]
- Use a known Lexicon, and stick to it.[3]
- Use language consistently <importance = 0.1>(yup we are having
that problem with the word "content")</importance>[3]
- If only one or two simple conditions must be met before a rule applies,
state the conditions first and then state the rule.[3]
- If two or more complex conditions must be met before a rule applies,
state the rule first and then state the conditions.[3]
- Use prompts for procedures and support decision making.[3]
- Structure tasks, provide step-by-step instructions. [3]
- Use a two-step "select and confirm" to reduce accidental selections,
especially for critical functions. cue sequences. [3]
- use goal/action structure for menu prompts. [3]
- define feedback cues[3]
- Provide defaults and make it easy to re-establish them. [3]
- provide calculation assistance, or reduce the need to calculate.[3]
- provide a mode with minimum functionality.<importance = 0.1> -
Eliminate or hide what isn't essential. with simple screen layouts or one
thing at a time presentation.</importance > this can be done with
Markup.[3]
- If only one or two simple conditions must be met before a rule applies,
state the conditions first and then state the rule. If two or more
complex conditions must be met before a rule applies, state the rule
first and then state the conditions.[3]
- Highlight key words and information, <importance = 0.1>(a bit
different from what is in [1.3A] Provide structure and then 3.2
-highlight it. I am talking about <em> keywords</em>
mid-sentence </importance> [3]
- [use the] simplest word (for lowest reading age in the area were the
highest percent of target audience) that does not change the meaning,
[2]
- incorporate "intended audience" into the success criteria as
appropriate. [5]
- incorporate a list of cognitive skills and ask the author to decide
which skills are required for cognition of the subject matter. [6]
- use markup to support the conversion of test into non text -supply an
illustration for each instruction [7]
- create a non text equivalent for all textual content. [7]
- write in plain language (suggestions for rewording checkpoint) [8]
- minimize complex syntax [8]
- reduce the usage of "and", "if" and other augment words (use
bulleted list or more sentences)
- reduce the usage negatives (one negative term per sentence)
Categories:
Fairly solid items
Items which are possible, questionable, or need work
Items that depend on something which does not yet exist
Items which address 4.1 but really are parts of other checkpoints
- We must have make each word unambiguous or Hebrew and Arabic without
Vowels will stay acceptable. [2]
- Acronyms and Abbreviations are defined the first time they appear in
text. - without a short term memory, acronyms remain confusing. Mark them
up, all the time.[2]
- Highlight key information (relates to 3.3) [2]
Links to threads on clear and simple writing
References
[1] WCAG 2.0 Latest Draft
[2] 4.1
[3] All
Together
[4] Plain
Language references and thoughts
[5] checkpoint
4.1
[6] RE:
checkpoint 4.1
[7]
ftf in Linz success criteria
[8]
summary of ftf work on 4.1
$Date: 2002/07/18 20:32:04 $ Ben Caldwell