W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 1998

Re: WAI Guidelines Naming

From: Geoff Freed <Geoff_Freed@wgbh.org>
Date: 29 Jan 1998 16:17:42 -0500
Message-ID: <n1326031134.44074@wgbh.org>
To: "Judy Brewer" <JBrewer@w3.org>, "Phill Jenkins" <pjenkins@us.ibm.com>
Cc: ij@w3.org, khudairi@w3.org, w3c-wai-gl@w3.org
        Reply to:   RE>>WAI Guidelines Naming

Phill Jenkins said...

From these titles I'm not sure where guidelines for the screen reader
manufactures, speaking browser manufactures, and the soon to come out
speaking agents (in automobiles) and other assistive technology developers
would be found.  So, I would suggest both a more general and specific
title: "Browsers and Assistive Technology".  I had considered "User Agents"
but rejected the term as "unknown and too academic" IMHO.  The code name
BROWSER"S" (with an s added) is fine.

>

Judy Brewer said...

Actually, "User Agents" is very clear, and probably no more unknown than
"Hosting."  Other reactions?

>

GF:  I think "user agent" is very unclear.  BROWSERS would be a better term (despite what I said earlier...), or BROWSERS AND something else.  Phill is right-- "user agent" is too academic and I don't think it conveys a concept that is instantly recognizable.  To everyone in the industry, "user agent" might mean something.  I don't think I've ever heard anyone else use it to refer to their browser.

geoff.

--------------------------------------
Date: 1/29/98 3:37 PM
To: Geoff Freed
From: Judy Brewer
At 02:50 PM 1/29/98 -0500, Phill Jenkins wrote:
>
>>  WAI Accessibility Guidelines: Master Reference Document
>>  WAI-MASTERREF
>PJ:: I agree (with 'Document' deleted, guidelines document is redundant
and sounds like a printed book)

Yes.

>
>>  WAI Accessibility Guidelines: Authoring Tools
>>  WAI-AUTHTOOLS
>PJ:: I would add "hosting" to include other tools that (for example)
automatically generate pages from non-html sources that don't really have
end-author interaction.  : Authoring and Hosting Tools. The code name
AUTHTOOLS is fine.
>
>>  WAI Accessibility Guidelines: Browsers
>>  WAI-BROWSER
>PJ:: From these titles I'm not sure where guidelines for the screen reader
manufactures, speaking browser manufactures, and the soon to come out
speaking agents (in automobiles) and other assistive technology developers
would be found.  So, I would suggest both a more general and specific
title: "Browsers and Assistive Technology".  I had considered "User Agents"
but rejected the term as "unknown and too academic" IMHO.  The code name
BROWSER"S" (with an s added) is fine.
>

Actually, "User Agents" is very clear, and probably no more unknown than
"Hosting."  Other reactions?

>>  WAI Accessibility Guidelines: Page Authoring
>>  WAI-PAGEAUTH
>PJ:: I really like the 'old EXISTING' title of MARKUP guidelines.  MARKUP
doesn't steer one to think of only pages, nor only authoring them, nor does
it sound like 'authoring tools' - which might be confusing later on. MARKUP
talks about the HTML source, whether authored by an individual using an
editor, or an authoring tools, or generated on the fly from pieces of
stuff, or style markup, or issues for whole sites (not just page).  Maybe I
missed the rational for changing, but I like MARKUP best.  : Markup.
WAI-MARKUP code name is fine.

Markup was confusing to a # of people, we kept getting questions.

>>  WAI Accessibility Guidelines: Users [if we do that set]
>>  WAI-USERS
>>GF:  I don't think "Users" is clear.  Is a user someone...
>>JB:  Yes, this name needs more work.
>PJ:: I would suggest "Surfers".  Surfing the web is a well known term,
includes the idea of reading, listening, even feeling the experience...
And, yes I think we need a set of guideline that would really be the base s

Has some zing, too...

WAI Accessibility Guidelines: Surfing
WD-WAI-SURF

- Judy
-------------------------------------------------------
Judy Brewer   jbrewer@w3.org     617-258-9741
Director, Web Accessibility Initiative International Program Office
World Wide Web Consortium (W3C)
MIT/LCS Room NE43-355
545 Technology Square, Cambridge MA 02139 USA
http://www.w3.org/WAI


------------------ RFC822 Header Follows ------------------
Received: by wgbh.org with ADMIN;29 Jan 1998 15:36:21 -0500
Received: by www19.w3.org (8.8.5/8.6.12) id PAA05061; Thu, 29 Jan 1998 15:29:45 -0500 (EST)
Resent-Date: Thu, 29 Jan 1998 15:29:45 -0500 (EST)
Resent-Message-Id: <199801292029.PAA05061@www19.w3.org>
Message-Id: <3.0.32.19980129152952.009516c0@sand.w3.org>
X-Sender: jbrewer@sand.w3.org
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Thu, 29 Jan 1998 15:29:55 -0500
To: Phill Jenkins <pjenkins@us.ibm.com>
From: Judy Brewer <JBrewer@w3.org>
Cc: <w3c-wai-gl@w3.org>, ij@w3.org, khudairi@w3.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: Re: WAI Guidelines Naming
Resent-From: w3c-wai-gl@w3.org
X-Mailing-List: <w3c-wai-gl@w3.org> archive/latest/121
X-Loop: w3c-wai-gl@w3.org
Sender: w3c-wai-gl-request@w3.org
Resent-Sender: w3c-wai-gl-request@w3.org
Precedence: list
Received on Thursday, 29 January 1998 16:30:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:46:57 GMT