W3C home > Mailing lists > Public > public-wai-evaltf@w3.org > October 2011

Re: "website" vs "web content" vs other (was Re: Short name for Methodology)

From: Detlev Fischer <fischer@dias.de>
Date: Tue, 18 Oct 2011 08:39:16 +0200
Message-ID: <4E9D1F14.7080101@dias.de>
To: public-wai-evaltf@w3.org
Hi Shady,

I am still not sure how we can clearly delineate the difference between 
the wider term "web content" (as in WCAG)  and "website" as explained on
- <http://www.w3.org/WAI/ER/methodology-reqs/#website>

Maybe we should clearly state in the definition whether "website" 
includes any content offered via plugin technologies like Flash? Thisa 
has practical implications. For example, if Flash would be included, the 
testing procedure would then either have to be *very* general (actually 
more general than in many tests of techniques, which do reference tools 
like aDesigner2) or fork depending on HTML, FLASH, etc.

Regards,
Detlev

  Am 17.10.2011 15:15, schrieb Shadi Abou-Zahra:
> Dear Detlev, All,
>
> On 17.10.2011 10:15, Detlev Fischer wrote:
>> I have now fully caught up with the discussion of the term "website" and
>> I realise it can be (or has been) defined to include web apps etc.
>
> Correct:
> - <http://www.w3.org/WAI/ER/methodology-reqs/#website>
>
>
>> Still, since the term "website" has been avoided in the title of WCAG
>> and also carries connotations of a traditional hierachical site, ist
>> seems more congenial to me to use "Web content" instead (even if it
>> makes the acronym still thornier).
>
> It is not about the acronym but rather about the scope of WCAG versus
> that of the Methodology. Web content is used to build websites. WCAG
> applies to any web content while our Methodology is limited to websites.
>
> I think we should either use the term "website" to denote static and
> dynamic web pages, web applications, intranets, mobile sites, etc, or
> come up with another term that applies to websites in their entirety.
>
> Regards,
> Shadi
>
>
>> Detlev
>>
>> Am 17.10.2011 08:40, schrieb kvotis@iti.gr:
>>> Hello everyone
>>>
>>> i aggree with the following comment of Detlev and this was also my
>>> comment
>>> to a previous mail. I cannot understand why we are refereeing only to
>>> Websites. I think that we need a more general term including also Web
>>> applications, Mobile Web applications,etc...
>>>
>>> regards
>>>
>>> kostas
>>>
>>>
>>>
>>>
>>>> Hi everyone,
>>>>
>>>> back from holidays, I am trying to catch up with discussions now.
>>>>
>>>> I do not mind WAEM even though I do not think it is particularly easy
>>>> to pronounce (other then spelling out double-U - E - A - M).
>>>>
>>>> I have some concern regarding the W for "website", as in the current
>>>> full title
>>>> "Website Accessibility Evaluation Methodology". The "WC" of WCAG
>>>> sounds a lot more general than the term "website". This also relates
>>>> to the important comments by Aaron Leventhal regarding the scope of
>>>> the methodology, tool independence, and the possible need to cover
>>>> different web content and UA scenarios.
>>>>
>>>> Is what we develop here focused on websites and not on things like web
>>>> apps for mobile UAs? If we want to be as general as WCAG we might need
>>>> to change the full name of the methodology and accordingly, the
>>>> acronym.
>>>>
>>>> Regards,
>>>> Detlev
>>>>
>>>>
>>>>
>>>>
>>>> Zitat von "Velleman, Eric"<evelleman@bartimeus.nl>:
>>>>
>>>>> Dear all,
>>>>>
>>>>> We decided in the call to discuss the short name in the list. Below
>>>>> are some short names from the discussions we had sofar and a
>>>>> proposed shortlist of requirements:
>>>>>
>>>>> Requirements for a short name:
>>>>> - It should be short
>>>>> - Easy to pronounce
>>>>> - Clear to all what it means (selfexplanatory)
>>>>> - Be about the methodology
>>>>>
>>>>> Shortnames (Make your choice or add new ones):
>>>>> - SiteAccess
>>>>> - WCAG-Method
>>>>> - WCAG-EM
>>>>> - WAEM (really using the title)
>>>>> - WCAG-Check
>>>>> - AccessSite
>>>>> - WCAG-Site
>>>>> - AccessCheck
>>>>> - SiteCheck
>>>>> - CheckSite
>>>>> - WAMBAM
>>>>> - WAME
>>>>> - MCEWA
>>>>> - CEWA
>>>>> - CEW2WCAG2
>>>>> - UWEM
>>>>> - SITE
>>>>> - MAWA
>>>>> - MDWC
>>>>> - EWAMAC
>>>>> - EMAWC
>>>>> - WEM
>>>>>
>>>>> Kindest regards,
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> ---------------------------------------------------------------
>>>> Detlev Fischer PhD
>>>> DIAS GmbH - Daten, Informationssysteme und Analysen im Sozialen
>>>> Gesch?ftsf?hrung: Thomas Lilienthal, Michael Zapp
>>>>
>>>> Telefon: +49-40-43 18 75-25
>>>> Mobile: +49-157 7-170 73 84
>>>> Fax: +49-40-43 18 75-19
>>>> E-Mail: fischer@dias.de
>>>>
>>>> Anschrift: Schulterblatt 36, D-20357 Hamburg
>>>> Amtsgericht Hamburg HRB 58 167
>>>> Gesch?ftsf?hrer: Thomas Lilienthal, Michael Zapp
>>>> ---------------------------------------------------------------
>>>>
>>>
>>>
>>>
>>
>>
>


-- 
---------------------------------------------------------------
Detlev Fischer PhD
DIAS GmbH - Daten, Informationssysteme und Analysen im Sozialen
Geschäftsführung: Thomas Lilienthal, Michael Zapp

Telefon: +49-40-43 18 75-25
Mobile: +49-157 7-170 73 84
Fax: +49-40-43 18 75-19
E-Mail: fischer@dias.de

Anschrift: Schulterblatt 36, D-20357 Hamburg
Amtsgericht Hamburg HRB 58 167
Geschäftsführer: Thomas Lilienthal, Michael Zapp
---------------------------------------------------------------
Received on Tuesday, 18 October 2011 06:40:22 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:52:12 GMT