W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 1999

Analysis of UAGL/WCAG relationship

From: Ian Jacobs <ij@w3.org>
Date: Fri, 21 May 1999 18:43:20 -0400
Message-ID: <3745E188.7E29A10B@w3.org>
To: w3c-wai-ua@w3.org
CC: w3t-wai@w3.org

I've gone through the WCAG checklist and tried to figure
out which ones are/are not/should be/should not be addressed
in the UAGL. The results are at [1]. It's pretty sketchy, so
all comments are welcome. There are a couple of proposals
embedded in it:


1) Add a checkpoint that says that UAs should allow users to
   turn off flicker. This is not the same as blinking (already
   covered by 4.4.6 and 4.4.7 

2) Modify Guideline 7.1 to include these checkpoints: 
   a)  Implement W3C specifications when they are 
       available and appropriate for a task and
       implement the latest versions when supported. 
       Note. Some W3C specifications are
       cumulative (e.g., HTML 4.0, CSS, DOM). 

   b)  Implement accessibility features defined by supoprted 
       W3C Recommendations. [The techniques would provide 
       links to documents where these are defined.] 

   c)  Support deprecated features of W3C Recommendations. 

3) Allow users to configure UA support for preferred 
   language/list of languages. [Techniques: HTTP Content-Language
   and "lang" in HTML, "xml:lang" in HTML for document root]

 - Ian

[1] http://www.w3.org/WAI/UA/1999/05/ua-wcag-checklist


Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Telephone May 1999 only:     (212) 688-4489
Cell phone May 1999:         (917) 450-8783
Otherwise Tel/Fax:           (212) 684-1814
Received on Friday, 21 May 1999 18:43:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:22 UTC