RE: RE: Impact Analysis for Guideline 4.2

 
Its 2 am here in London so im not real swift but what comes to mind are such
things as screen reader access to the text (previous require text but not
access to it) and all the things listed from UAAG for user agents  -- but
since you are in effect creating (or packaging) your own user agent... we
said - they must follow user agent guidelines. 

Yes?   Don't we still need to say this?   At least I thought it would be
good to discuss to make sure we are covered. 
 
 
Gregg

 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 
Professor - Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 


-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of lguarino@adobe.com
Sent: Tuesday, April 05, 2005 8:12 PM
To: Gregg Vanderheiden
Cc: w3c-wai-gl@w3.org
Subject: Re: RE: Impact Analysis for Guideline 4.2


We were having trouble coming up with any examples that weren't already
covered by the rest of the guidelines. For instance, we still require
keyboard access, and separation of content and presentation. What did we
miss that would be covered by this requirement, assuming a suitable user
agent?

> 4.2 was also where we covered  "if you create an interface with your 
> content
> - that goes beyond the users default user agent, then that interface 
> must meet the UAAG specifications"
>
> How is this covered?

Received on Wednesday, 6 April 2005 01:23:28 UTC