Re: proposed change for simple words in labels etc.

Lisa,
I think that this edit removes a very important aspect of this sc - "unless it will result in a loss of meaning”. As well, I expect that we would get pushback on how we know that the top 1500 words or phrases are the ones that will provide a certain level of access for people – can you point me to where in the research this topic is addressed?

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Standards and Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk


From: "lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>" <lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>>
Date: Sunday, February 19, 2017 at 03:33
To: "public-cognitive-a11y-tf@w3.org<mailto:public-cognitive-a11y-tf@w3.org>" <public-cognitive-a11y-tf@w3.org<mailto:public-cognitive-a11y-tf@w3.org>>, WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: proposed change for simple words in labels etc.
Resent-From: "public-cognitive-a11y-tf@w3.org<mailto:public-cognitive-a11y-tf@w3.org>" <public-cognitive-a11y-tf@w3.org<mailto:public-cognitive-a11y-tf@w3.org>>
Resent-Date: Sunday, February 19, 2017 at 03:33

Hi Folks

Continuing the conversation on simple language, to address concern with testability (as user testing is not acceptable)  I want to suggest the following change to the clause on common words:

Change:
  *   Simple, clear, and common words: Use words or phrases that are most-frequently used for the current context, unless it will result in a loss of meaning or clarity. This includes not using abbreviations, words, or phrases, unless they are the common form to refer to concepts for beginners. Where word frequencies are known for the context, they can be used.

to:

  *   Simple, clear, and common words: Use the the most common 1500 words or phrases or, provide words, phrases or abbreviations that are the are most-common form to refer to the concept in the current context.


The scope is instructions, labels, navigational elements, and error messages which require a response to continue.

 Technique would include:

  *   Using a title tag to provide a simple language equivalent
  *   Using the coga-easylang attribute (prefered)
  *   Providing extra text via personalization semantics.
  *   Using simple words

Technology support includes: word frequency generator for a given context, (reads the URI's list and generates a word frequency list), existing word frequency lists, checker to test that words are in the most

There are also a list of exceptions that is quite long - issues 30 - and we are proposing to add a exception for long instructions (as per previous email) We could add an exception for user testing, but amazingly that is controversial.

The thinking is: the most common 1500 words is really trivial for testing tools to find and generate a warning. However using the most comment form to refer to something in the current context will, in this scope , take care of  the clarity issue and is also  testable with the tools above.

please do not bring up issues that are addressed in the exceptions or are out of the scope.



All the best

Lisa Seeman

LinkedIn<http://il.linkedin.com/in/lisaseeman/>, Twitter<https://twitter.com/SeemanLisa>