W3C home > Mailing lists > Public > wai-eo-editors@w3.org > June 2017

Re: [style guide] Thoughts on approach

From: Bakken, Brent <brent.bakken@pearson.com>
Date: Fri, 30 Jun 2017 10:21:43 -0500
Message-ID: <CAE6qf-FHVdpnNzy2Tkb7eD+Zoibg1hAL26Eefb9DhLHgBeQqWQ@mail.gmail.com>
To: Sharron Rush <srush@knowbility.org>
Cc: wai-eo-editors <wai-eo-editors@w3.org>, Sarah Pulis <sarah@intopia.digital>
>
> ​
> *Specialist language* – Since this is a specialized filed, should we
> include any guidance on how to reference disability, W3C process,
> referencing materials or anything else that is super-specialized for our
> environment?


​+1​ specifically



Brent A. Bakken
Director, Accessibility Strategy & Education Services
Pearson

512 202 1087
brent.bakken@pearson.com

Learn more at pearson.com

[image: Pearson]


On Fri, Jun 30, 2017 at 10:14 AM, Sharron Rush <srush@knowbility.org> wrote:

> I am thinking about how this will be presented and would like to suggest
> this format.  Sarah and Shawn, if you agree I will format the wiki to
> reflect these sections:
>
> *Introduction* – What the guide is meant to do, how it will make our job
> easier, and how to use it.
>
> *Voice* – Can we make a statement about what we want the quality of the
> voice to be? I am thinking about some of the adjectives we used to describe
> how we wanted the web site to be.  Some words that will suggest rhythm, and
> maybe a list of voice qualities to avoid. Each statement could then be
> explained it in more detail and examples provided for how to put it into
> practice
>
> *.Tone* – This seems a bit trickier and might entail how to use the voice
> we agree on with different tones. There will be variation depending on
> different scenarios, do you agree?  This may be a place to reference our
> personas.
>
> *Style* – After introducing the guide and setting voice and tone, that's
> when I think we get into the style guide items that Shawn and Annabelle
> started and Sarah expanded on.
>
> *Specialist language* – Since this is a specialized filed, should we
> include any guidance on how to reference disability, W3C process,
> referencing materials or anything else that is super-specialized for our
> environment?
>
> Throughout I strongly believe that we should use as many examples as
> possible and be specific to our own stuff, as the first set of guides has
> done. Is this an approach we can agree on? or have I overlooked or
> misunderstood any of it? This is new to me so don't hesitate to let me
> know.
>
> Thanks,
> Sharron
>
> --
> Sharron Rush | Executive Director | Knowbility.org | @knowbility
> *Equal access to technology for people with disabilities*
>
Received on Friday, 30 June 2017 15:22:16 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 23 June 2020 20:41:51 UTC