RE: User Agent Push

A wish list would be helpful. Especially if the items fell outside of current UAAG requirements. 

There is overlap between UAAG and WCAG. There are topics that bridge the guidelines. For example, 
in UAAG we have 
3.3 Toggle animated or blinking text (P1)

   1. Allow configuration to render animated or blinking text content as motionless, unblinking text. Blinking text is text whose visual rendering alternates between visible and invisible, at any rate of change.

BUT, animations and other moving content can be created in many ways (gif, javascript, flash, svg, etc.), the UA can only control those things it knows about, like animated gifs. A simple ESC key will stop animated gifs (and marquee and blink if created with the 'marquee' and 'blink' elements). Authors use many tools to animate information many of which occur outside the UA process. So, the UA cannot control these particular animations, and it falls to the author to do the right thing by following 

WCAG 2.2.2 Blinking: Content does not blink for more than three seconds, or a method is available to stop all blinking content in the Web page. (Level AA).

We look forward to the dialog. 


Jim


> -----Original Message-----
> From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On
> Behalf Of Jan Richards
> Sent: Wednesday, August 22, 2007 2:30 PM
> To: Charles McCathieNevile
> Cc: Michael Cooper; UAAG
> Subject: Re: User Agent Push
> 
> 
> 
> Hi,
> 
> I agree with Charles that UAAG is effectively that list. And I think it 
> would be very helpful to the work on UAAG 2.0 for the WCAG-WG to put 
> together a wishlist of user agent features.
> 
> Cheers,
> Jan
> 
> Charles McCathieNevile wrote:
> > 
> > On Tue, 21 Aug 2007 22:53:35 +0200, Michael Cooper 
> <cooper@w3.org> wrote:
> > 
> >> The WCAG Working Group sometimes determines that a success criterion
> >> would be much more easily met if only user agents supported a given
> >> feature. Because we only document techniques that are known to 
> yield the
> >> accessibility benefit intended, we tend to have to create "workaround"
> >> techniques that we consider far less desirable. We are starting a "wish
> >> list" of user agent features that would make all our lives easier - the
> >> User Agent Push
> >> <http://trace.wisc.edu/wcag_wiki/index.php?title=User_Agent_Push> list.
> >>
> >> We'd like to know from UAAG if a similar list exists, or if it would
> >> make sense to collaborate on the development of such a list. We'd also
> >> like to work through the UAAG WG on encouraging user agent 
> developers to
> >> implement some of these features. Would there be interest in this?
> > 
> > The User Agent Accessibility Guidelines, as I read them, are 
> effectively 
> > such a list. If the WCAG group were to look carefully and select the 
> > things that are really pain points now, and list them, or link to the 
> > relevant bit of UAAG for each feature they want, it would help. 
> (The one 
> > thing listed is extremely vague at the moment. If it means 
> being able to 
> > navigate headers, then I am happy to report that we do it 
> already. If it 
> > means something else, please clarify so we can work out if we do or 
> > don't :) ).
> > 
> > Cheers
> > 
> > Chaals
> > 
> 
> -- 
> Jan Richards, M.Sc.
> User Interface Design Specialist
> Adaptive Technology Resource Centre (ATRC)
> Faculty of Information Studies
> University of Toronto
> 
>    Email: jan.richards@utoronto.ca
>    Web:   http://jan.atrc.utoronto.ca
>    Phone: 416-946-7060
>    Fax:   416-971-2896
> 
> 
> 
>

Received on Wednesday, 22 August 2007 20:18:14 UTC