Re: Notes and Resources on Plain Language

On Tue, 03 Apr 2018 17:54:58 +0200, Hall, Charles (DET-MRM)  
<Charles.Hall@mrm-mccann.com> wrote:

>
> First, the focus of the discussion that emerged during and following the  
> Design Sprint was split between >2 main considerations:
> Regardless of terminology choice between “Plain Language” or “Simple  
> Language”, should we >adopt an existing external standard or create one?

To the extent that we use a formal standard, we should definitely adopt  
one rather than try to create one.

>
> Does the fact that the standard already exists lend credibility to  
> Silver and align to its goals?
> Is there any licensing or restrictions involved in using the standard?
> Requirements (or guidelines) – likely in the form of a style guide –  
> will need to be defined for >explicitly how to write criteria and any  
> supporting ‘understanding’ documents in plain language in >EACH  
> supported language.

I presume by supported language you mean for each translation ito a  
different language. If so, yes, this is true. And that will be a challenge.

As noted, checking documents that have been translated in two or three  
languages is a helpful technique to identify things that should be  
simplified.

Actually making them simple is hard. We can do it at the end of the work -  
and we need to make sure we check at the end of the work if we did it, and  
maybe do it again then.

cheers

Chaals

>
>
> Here are some resources I have located for consideration when discussing  
> plain language:
>
>
> W3C Reading Level Understanding SC 3.1.5
>
> https://www.w3.org/TR/UNDERSTANDING-WCAG20/meaning-supplements.html
>
> Cites being ‘adapted from’ the UNESCO standard based on education level.
>
>
> CRPD Article 2 – Definitions, Plain Language
>
> https://www.un.org/development/desa/disabilities/convention-on-the-rights-of-persons-with->disabilities/article-2-definitions.html
>
>
> U.S. Government Publishing Office, Plain Writing Act of 2010
>
> https://www.gpo.gov/fdsys/pkg/PLAW-111publ274/content-detail.html
> Supported by 2 Executive Orders and Office of Management and Budget  
> Guidelines
>
>
> Federal Plain Language Guidelines (U.S.)
>
> https://www.plainlanguage.gov/
>
> U.S. Securities and Exchange Commission Plain English Handbook
>
> https://www.sec.gov/pdf/handbook.pdf
>
> European Commission Publications, How to Write Clearly
>
> https://publications.europa.eu/en/publication-detail/-/publication/bb87884e-4cb6-4985->b796-70784ee181ce/language-en
>
>
> Gov.UK Guidance for Government Digital Publishing and Services
>
> https://www.gov.uk/topic/government-digital-guidance/content-publishing
>
> Information for all – European Standards [Lifelong Learning Programme &  
> Inclusion Europe]
>
> http://easy-to-read.eu/wp-content/uploads/2014/12/EN_Information_for_all.pdf  
> [pdf]
>
>
> How to Write Standards – ISO (2016)
>
> https://www.iso.org/publication/PUB100335.html
> https://www.iso.org/files/live/sites/isoorg/files/archive/pdf/en/how-to-write-standards.pdf  
> [pdf]
>
>
> What Is Plain Language? – Plain Language Association International  
> (PLAIN)
>
> http://plainlanguagenetwork.org/plain-language/what-is-plain-language/
>
> Plain language: accessibility for information – Whitney Quesenbery  
> (2014) Article
>
> https://rosenfeldmedia.com/a-web-for-everyone/plain-language-accessibility-for-information/
>
> Plain language: accessibility for information – Whitney Quesenbery  
> (2016) Slide Deck
>
> https://www.slideshare.net/whitneyq/plain-language-is-accessibility-for-content
>
>
> 3.1.5 – Reading Level (Level AAA) – Luke McGrath, WUHCAG (2014)
>
> https://www.wuhcag.com/reading-level/
>
> Inclusivity, Gestalt Principles, and Plain Language in Document Design –  
> Jennifer Turner and Jessica >Schomberg (2016)
>
> http://www.inthelibrarywiththeleadpipe.org/2016/accessibility/
>
>
> Plain Legal Language General Resources – Clarity International
>
> http://www.clarity-international.net/plain-language-resources/general-resouces/
>
>
> Plain Language – Wikipedia
>
> https://en.wikipedia.org/wiki/Plain_language
>
>
>
> Finally, I would consider this required reading for anyone discussing or  
> working on translating the >current WCAG SCs into plain language, since  
> this effort is exactly that:
>
>
> Web Content Accessibility Guidelines—for People Who Haven’t Read Them –  
> Alan Dalton (2017)
>
> https://24ways.org/2017/wcag-for-people-who-havent-read-them/
>
>
>
> Charles Hall
>
> UX Architect, Technology
>
>
> t / 248.203.8723  m / 248.225.8179
>
> e / charles.hall@mrm-mccann.com
>
> skype / charles.h.all
>
> 360 W Maple, Birmingham MI 48009
>
> w / www.mrm-mccann.com
>
>
>
>
> Creativity. Technology. Performance.
>
> This message contains information which may be confidential and  
> privileged. Unless you are the intended recipient (or authorized to  
> receive this >message for the intended recipient), you may not use,  
> copy, disseminate or disclose to anyone the message or any information  
> contained in the >message.  If you have received the message in error,  
> please advise the sender by reply e-mail, and delete the message.  Thank  
> you very much.



-- 
Chaals: Charles (McCathie) Nevile find more at https://yandex.com
Using Opera's long-abandoned mail client: http://www.opera.com/mail/
Is there really still nothing better?