Re: [Getting Started Tips Input]

Dear Kazuhito,

Thanks very much for your review and comment on the recently published Getting Started Tips. WAI relies on community review and your contribution is appreciated. The Getting Started Tips were developed by the Education and Outreach Working Group (EOWG.) After reviewing and carefully considering your suggestion, they group decided to leave the titles as they are. I would like to provide you with some background to help put that decision in perspective.    
The approach to naming the categories was subjected to lengthy consideration at the early stages of the development of this resource. The aim was to provide a title that was quite short while describing the broad project activity. We also avoided making reference to specific project roles as there is so much variation in job terminology.

Group discussion concluded that your suggested section titles are longer, may be too restrictive in their scope, or may introduce terminology that some might find unclear. Specifically:

'Designing' covers elements of user interface design as well as visual design.
'Content Authoring' is sometimes used more broadly to cover the writing of code or creation of multimedia or imagery.
'Developing' covers other technologies including JavaScript, CSS, and ARIA.
Thanks again for your suggestion, it was helpful for us to review the categories and consider how they are presented. In this particular instance, however the decision is to leave the titles as they are for reasons of brevity and clarity.

Please let us know if the rationale is acceptable or if further discussion of the issue is needed

Regards,

Kevin

——
Kevin White
W3C Web Accessibility Initiative (WAI)
e-mail: kevin@w3.org <mailto:kevin@w3.org>
about: http://www.w3.org/People/#kevin <http://www.w3.org/People/#kevin>

> On 2 Oct 2015, at 09:13, Kazuhito Kidachi <k-kidachi@mitsue.co.jp> wrote:
> 
> Hello,
> 
> I think "Tips for Getting Started" content seems great starter kit for newbies, but its categories seem a bit confusing. My suggestion for its structure is:
> 
> 1. Visual Design for Web Accessibility
> 2. Content Authoring for Web Accessibility
> 3. HTML Coding for Web Accessibility
> 
> The words like "Designing" "Writing" "Developing" seem to have broader scope of meaning, so...
> 
> Best,
> 
> Kazuhito
> -- 
> Kazuhito Kidachi
> Mitsue-Links Co.,Ltd.
>