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

R:re-considering the title "Interdependent Components of Web Accessibility"

From: Pasquale Popolizio <pasquale@osservatoriosullacomunicazione.com>
Date: Fri, 11 Feb 2005 12:54:38 +0100
To: Shawn Henry <shawn@w3.org>, "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Message-ID: <BE325B8E.805A%pasquale@osservatoriosullacomunicazione.com>

Hi Shawn,
hi all.

I thought about it during my translation into Italian few days ago.

I found:
"Interdependent": "depending one on the other",
"essential": "of the utmost importance; necessary"
"vital": "of the utmost importance; essential"


What about:
"Essential components of Web accessibility"
or
"Vital components of Web accessibility".

Like in a clock mechanism, one component is "essential" or "vital" to let
the clock work. With a malfunction of a little gear, the clock cannot
function correctly.
In this metaphore, like in the Web development, the "interdipendence" of the
gears is implicit.


Regards
Ciao


Pasquale




Il 4-02-2005 14:34, "Sylvie Duchateau" <sylvie.duchateau@snv.jussieu.fr> ha
scritto:

> 
> Hello Shawn and all,
> I like proposal 5:
> 5. Understanding the Components of Web Accessibility
> 
> Regards
> 
> Sylvie
> A 14:15 04/02/2005, Shawn Henry a écrit :
> 
>> In an evaluation of the WAI redesign prototype[1], AIR[2] stated:
>> "The initial link in the Getting Started menu is admirably simple and easy
>> for accessibility novices to understand. The second link, however,
>> ³interdependent components² smacks of jargon. Its language is conceptually
>> much more complex than the links around it... Consider whether the second
>> link¹s name is in keeping with the overarching goal of the section, which is
>> to provide an initial overview..."
>> 
>> I wasn't totally happy with the title when it was "Components of Web
>> Accessibility" and I think adding the "Interdependent" to the beginning made
>> it way too much (I didn't choose to address it at the time due to pressure to
>> complete an initial version). I do think it is worth revisiting the title to
>> see if we can come up with something that:
>> * encourages people to read the document, is simple and relevant
>> * describes the content, or at least leads to the content, is not misleading
>> 
>> Here are some brainstorms on other approaches for titles:
>> 1. Dependencies in Web Accessibility (or Web Accessibility Dependencies)
>> 2. Requirements of Web Accessibility  (or Web Accessibility Requirements)
>> 3. The Web Accessibility System
>> 4. The Parts of Web Accessibility
>> 5. Understanding the Components of Web Accessibility
>> 6. Web Accessibility Depends on:
>> 
>> Note that if we change the title from the concept of "Interdependent
>> Components" we might change some related wording throughout the document to
>> match the new title concept.
>> 
>> This page is primarily in the site navigation:
>> - in the Getting Started section:
>> http://w3.org/2004/09/wai-nav/intro/components.html
>> - in the Guidelines and Techniques section:
>> http://w3.org/2004/09/wai-nav/guid-tech
>> as well as linked from many documents, such as:
>> - all the guidelines overview pages (e.g.,
>> http://w3.org/2004/09/wai-nav/intro/wcag)
>> - the "Introduction to Web Accessibility" page
>> (http://w3.org/2004/09/wai-nav/intro/accessibility.html)
>> 
>> ---
>> 
>> [1] prototype of information architecture and layout (NOT visual design and
>> markup!): http://w3.org/2004/09/wai-nav/
>> [2] AIR: http://www.air.org/usability/
>> 
>> 
>> 
> 
> ******************
> Sylvie Duchateau
> Association BrailleNet
> Tél.: +33 (0) 1 44 27 26 25
> Web: http://www.braillenet.org
> 
> 
> 
Received on Friday, 11 February 2005 11:55:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:53 UTC