Re: omissions and mistakes in the draft

Ok - thanks for the update Lisa.

Josh

> lisa.seeman <mailto:lisa.seeman@zoho.com>
> 20 February 2017 at 19:40
> Hi
>
> Unfortunately some of our very high priority SC because the editors 
> were tracking old versions and thought it was not ready to be 
> published. The coga taskforce and Michael agree that the following two 
> Success criteria are a good enough standard to go into the draft.
>
> 1. Manageable blocks is now Short sentences
>
> *Short sentences: Statements which instruct a user to make a choice or 
> take an ACTION: have only one instruction per sentence, except when 
> two things have to be done simultaneously; use sentences of no more 
> than 15 words; should have no more than one relative pronoun per 
> sentence. Glossary entry: Relative pronouns are any of the words 
> "who", "whom", "that", "which", "whose", "where", "when" and "why".*
>
> 2.
>
>
>       Support personalization (minimum): Contextual information and
>       author settable properties of regions, critical features and
>       important information are programmatically determinable so that
>       personalization is available.
>
>
>
> Also the language is old for the plain language SC
>
> Plain language: Provide clear and simple language in instructions, 
> labels, navigational elements, and error messages which require a 
> response to continue, so that all of the following are true.
>
>
>   * Simple tense: Use present tense and active voice.
>   * Simple, clear, and common words: Use the most common 1500 words or
>     phrases or, provide words, phrases or abbreviations that are the
>     most-common form to refer to the concept in the identified context.
>   * Double negatives are not used.
>   * Concrete language: Non-literal language is not used, or can be
>     automatically replaced, via an easy-to-set user setting. All
>     meaning must be retained when non-literal text is replaced.
>   * Instructions: Each step in instructions is identified
>
>
> New definition
>
> identified context is defined as  - context and a context specific 
> word frequency list (and glossary) has been identified in an 
> accessibility statement or other known technique. A word frequency 
> list has to be generated from at least 1000 sources from the same 
> context or how ever many pages can reasonably be found
> All the best
>
> New exception
> If there are no tools available in the language of the content that 
> identify uncommon words, instructions that are longer then 400 words 
> are exempt unless they directly relate to a critical service.
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter 
> <https://twitter.com/SeemanLisa>
>
>

-- 
Joshue O Connor
Director | InterAccess.ie