Re: process of a site development

Lets see,
if we were to write "testing" and include in parenthesis "can include: , QA,
project managers, usability consultants, automated done on four staging
servers"

Well - everyone does testing (or at least pretend they do) so that is not
intimidating, no one will be put off by by a "can include " thing

keep the terms general, detail by the side.
Just like WCAG 2
Lsa

-----Original Message-----
From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
To: Matt May <mcmay@bestkungfu.com>
Cc: Robert Neff <rneff@bbnow.net>; Lisa Seeman <seeman@netvision.net.il>;
WAI <w3c-wai-gl@w3.org>
Date: Wednesday, January 31, 2001 8:30 AM
Subject: Re: process of a site development


>At 11:03 AM 1/26/2001 , Matt May wrote:
>>- I'm reluctant to put down too much practical (specifically, large
>>team-oriented) information into a flow such as this, because it would look
>>daunting to smaller design teams ("you must be THIS BIG to make an
>>accessible site"). One person can design something that's accessible, and
>>I'd hate to scare that one person off by saying s/he needs to hire an
>>information architect, development resources, QA, project managers, and
>>usability consultants, and buy a content management system, automated
>>testing suite, and four staging servers in order to make
myquiltingpage.com
>>accessible.
>
>I second everything Matt said.
>
>Nothing more to add.
>
>--Kynn
>
>
>--
>Kynn Bartlett  <kynn@idyllmtn.com>                http://kynn.com/
>Technical Developer Relations, Reef           http://www.reef.com/
>Chief Technologist, Idyll Mountain Internet   http://idyllmtn.com/
>Contributor, Special Ed. Using XHTML     http://kynn.com/+seuxhtml
>Unofficial Section 508 Checklist       http://kynn.com/+section508
>
>
>