Re: how to move forward with plian language

That is a very good example, if it is the word, phrases or abbreviations that are the most-common form to refer to the concept, then that is fine for the current wording.

We would need automated  texting tools for that however  which we do not currently have. The manual way to test it might be to look at a thesaurus and see if any of the words are more common. Do you have another way to test?


MS and IBM have tools that can test for the most common word. The question is can we make it a SC without automated tools being available.
 

All the best

Lisa Seeman

LinkedIn, Twitter





---- On Mon, 22 May 2017 12:07:09 +0300 Alastair Campbell<acampbell@nomensa.com> wrote ---- 

      > Something we could try is a phone call explaining the frequency lists and  show how you could change a page.
  
   Perhaps you could take the example I posted to the list? The main navigation of johnlewis.co.uk is fairly typical of ecommerce sites.  It has over 1500 items in the main navigation, many of which you can’t rename.
 I have to be honest and say I don’t see a useful way forward for it under a testable guidelines approach, I’ll repeat my WCAG post below.
 Cheers,
  -Alastair
  
 
 Jason wrote:
 > As mentioned, I’m still thinking through the implications and the feasibility here, but we do need to look beyond conventional approaches to defining and evaluating content requirements if we are to take some issues (especially but not only cognitive ones) into account in an authentic and effective way.
 Indeed, I have long maintained [1] that where improving accessibility crosses over into usability, you need to apply a certain process rather than guidelines. Most of the work my company does is apply user-centred-design, i.e. UX services for clients.
 Taking an example relevant to plain language (i.e. using 1500 common words), if you want to ensure a usable navigation menu for a content-oriented website then I would want to follow a particular process such as:
  -      Open card sorting to establish how your audience think about the groupings of content and what grouping terms they associate with the content [2].
  -      Create a navigation that seems to work for that content & mental model based on the results.
  -      Closed card sorting (often with larger numbers) to refine and prove it works [3]. You can put then percentages on how well each term & content grouping works, and refine until it is optimised enough.
 The two points I’d make are:
  1.    There is no guideline that can help you predict the outcome of what a ‘usable’ navigation will be, it is based on content, context and audience. Every time in the last 16 years we have run the above process we massively improve a navigation that was created without it. Provably.
  2.    Arbitrarily using words from a common list it likely to make it less usable for the majority of the audience and cost organisations money.
 Take the navigation of an ecommerce store for example: https://www.johnlewis.com/  I think there are more than 1500 words in the navigation! Also, it has (I assume) been finely honed over the years to maximise the usability for their customers.
 There is no reasonable argument to say that restricting their navigation to an arbitrary 1500 words is going to improve the experience for anyone. You could argue the interface should be simplified (e.g. like the small screen version) so less is presented at once, but many of the terms are objects or categories of things you can buy with specific names you can’t change.
 If they were asking my advice, I could not in good conscience tell them to restrict their navigation terms to the top 1500 words, it would cost them a lot of money for zero improvement for anyone.
 On the other hand, usability testing (with anyone but especially people with cognitive issues) or using the card-sorting process above would hugely improve most navigations for everyone, and with less political resistance (in an organisation) because they see the improvements first hand.
 For me this is something that needs to be dealt with in Silver, and a key part of Silver needs to be dealing with the *process* of making sites usable, as well as accessible. Ideally drawing on (or referring to) the ISO standards for user-centred-design and highlighting aspect particularly relevant for cognitive (and other) disabilities.
 In the meantime, can we move this one to the Cognitive TF note going out next to 2.1?
 Kind regards,
 -Alastair
 1] https://lists.w3.org/Archives/Public/w3c-wai-gl/2015JulSep/0037.html
 2] https://www.usability.gov/how-to-and-tools/methods/card-sorting.html
 3] https://www.optimalworkshop.com/treejack