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

RE: WAI Guidelines Naming

From: Judy Brewer <JBrewer@w3.org>
Date: Sat, 31 Jan 1998 23:29:56 -0500
Message-Id: <3.0.32.19980131232924.0099a550@sand.w3.org>
To: w3c-wai-gl@w3.org, w3c-wai-cg@w3.org
A word of caution:  please don't post this thread onto the WAI IG list (two
messages have already gone there, I think by accident); if it generates 30
messages on the GL list I dread the volume it will generate on the IG list.

I did not suspect such impassioned debate about naming.

Thank you to Phill Jenkins for summarizing the dialog so far.  Lots of good
points made.  Regarding the suggestion to work it out in the charters, the
charters have already been developed & approved by W3C, & I think they
clearly state their scope and expected deliverables.  If you look back at
the charters and feel that there are gaps, please send comments to the
chair of that group.  Working group charters are periodically revised & we
can adjust scope at that time.

I suggest we leave the discussion here, and let the chairs of the three
guidelines-related groups work it out between them, in coordination with
WAI/W3C.

- Judy

At 02:43 PM 1/30/98 -0500, you wrote:
>My new comments are marked PJ::  Some of the discussion is leaning towards
>"what should be in the charter", which does influence the "title" of that
>charter's output, namely the guideline.  If  you want, we could create new
>threads for each group's charter and guideline content and leave it up to the
>chairs to "pick" the title.
>
>Regards,
>Phill Jenkins, IBM
>
>WAI Accessibility Guidelines: Master Reference
>WAI-MASTER
>JG:...a name that reflects that this set deals with the fundamental issues
and
>the interactions between the other guidelines? For example: Issues and
>Strategies for WWW Technology Accessibility
>GV: How about "Central Reference Document"
>JB: WAI Accessibility Guidelines: Central Reference
>
>PJ:: I prefer "Master", but as long as it's clear in the charter that this
is a
>total collection of all the guidelines with additional explanation as to why
>something is in one guideline versus another.  We could also delete
"Central or
>Master" and just have "Reference" WAI-REFERENCE.
>
>
>WAI Accessibility Guidelines: Browsers
>WAI-BROWSER
>PJ: ...Guidelines: Browsers and Assistive Technologies
>AG: ...Actually, User Agents is very clear
>DD: I like Al's "Client Software"
>JB: Not as clear nor familiar to many as "Browsers"
>JW: ...WAI client software user interface guidelines
>JB: ...also looking at issues between browsers & assistive technology;
>JB: ...guidance that [accessibility] are fully implemented.  So, I think that
>takes us back to:WAI Accessibility Guidelines: Browsers
>
>PJ:: I missed any discussion on why not "Browsers and Assistive
Technologies".
>This title would include client AND SERVER software, user interface, and use
>terms very familiar yet not so narrow. Again, the charter is more
important to
>me than the title.  The guidelines need to include where the browser
>developer's responsibility stops and where the screen reader developer's
>responsibility starts.  The older "dumb" screen reader developers may have
some
>development to do...
>
>
>WAI Accessibility Guidelines: Page Authoring
>WAI-PAGEAUTH
>PJ: I really like the 'old EXISTING' title of MARKUP guidelines...
>JB: Markup was confusing to a # of people, we kept getting questions.
>DD: ...these guidelines are really for people that *knows* about the Markup,
>not just people authoring pages with a nice GUI tool. So I prefer Markup too.
>JB: ...If these guidelines are only for people who really know technical
>mark-up in depth, then we've missed part of our task.  But I think they're
for
>both, so I'm still rooting for Page Authoring.
>
>PJ:: I agree that the charter is for both, but the title "Page Authoring"
seems
>to emphasize the using of authoring tools over the marked up source.  It is
>guidelines on how the markup should be regardless of editor, or GUI tool, or
>auto-generation on-the-fly wizard server and client software generating the
>HTML markup.  So I'm back to "HTML Markup".
>
>
>WAI Accessibility Guidelines: Authoring Tools
>WAI-AUTHTOOLS
>PJ: I would add "hosting" to include other tools...
>DD: I don't really understand what Hosting means in that context.
>DD: The AU group charter doesn't specify, so it's for both.
>
>PJ:: I withdraw my nomination for adding"hosting" and suggest "Web Site
>Building Tools".  Here is a snipet of a recent tool manufacturer's
>announcement.  This manufacturer is one of the intended readers of this
>guideline along with the HTML MARKUP guideline: NetObjects Fusion 3.0 offers
>Web site builders an open site-building environment, providing... easily lay
>out pageS, control and edit HTML code, adding DHTML-based interactivity and
>animation, publish for different browsers, and integrate sites with existing
>databases and commerce applications.
>
>
-------------------------------------------------------
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
Received on Saturday, 31 January 1998 23:29:21 GMT

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