Re: Neutral language in W3C specifications

What an amazing step to take! Wonderful! The ideas keep getting better and
better.

** katie **

*Katie Haritos-Shea*
*Principal ICT Accessibility Architect*


*Senior Product Manager/Compliance/Accessibility **SME*
*, **Core Merchant Framework UX, Clover*


*W3C Advisory Committee Member and Representative for Knowbility *


*WCAG/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy,* *IAAP CPACC+WAS = *
*CPWA* <http://www.accessibilityassociation.org/cpwacertificants>

*Cell: **703-371-5545 <703-371-5545>** |* *ryladog@gmail.com
<ryladog@gmail.com>* *| **Seneca, SC **|* *LinkedIn Profile
<http://www.linkedin.com/in/katieharitosshea/>*

People may forget exactly what it was that you said or did, but they will
never forget how you made them feel.......

Our scars remind us of where we have been........they do not have to
dictate where we are going.






On Wed, Jul 22, 2020 at 12:02 PM Lisa Seeman <lisa1seeman@gmail.com> wrote:

> Hi folks
>
> Can we have some examples of how to do this in practice for, easy to
> understand,  user examples and personas?
>
> We have a lot of them in https://www.w3.org/TR/coga-usable/  (I found
> over 60 uses of the word "his" and over 80 uses of the word "her")
>
>
> All the best
> Lisa
>
> On Wed, 22 Jul 2020, 12:22 Léonie Watson, <lwatson@tetralogical.com>
> wrote:
>
>> Denis, this is a really positive step, thank you to you and the team.
>>
>> One suggestion - is it possible for PubRules to check for gender
>> specific pronouns (he/she, him/her etc.) too?
>>
>> They are rare in specifications, but do sometimes feature as part of use
>> cases or examples.
>>
>> Léonie.
>>
>> On 22/07/2020 09:40, Denis Ah-Kang wrote:
>> > Dear editors and chairs,
>> >
>> > In order to offer the best environment possible to its
>> > community, W3C is supporting the push for a more inclusive and
>> > neutral language, especially in our specifications.
>> >
>> > In the upcoming weeks, pubrules [1] will show a warning if
>> > terms like "master", "slave", "grandfather", "sanity" or
>> > "dummy" are detected in a specification and this will also
>> > be reflected in the Manual of style [2] with a list of
>> > alternatives.
>> > Note, since it may take time for the editors to change the
>> > branch name "master" to something else, we will not flag the
>> > URLs containing that word in the first place.
>> >
>> > Going forward, we will audit all the specification repositories
>> > and open issues if they contain problematic terms.
>> >
>> > Let me know if you have any comments/suggestions.
>> >
>> > Denis
>> > W3C Systems team
>> >
>> > [1] https://www.w3.org/pubrules/
>> > [2] https://w3c.github.io/manual-of-style/
>> >
>>
>> --
>> Director @TetraLogical
>> https://tetralogical.com
>>
>>