W3C home > Mailing lists > Public > public-cdf@w3.org > June 2006

Re: [WICD] focusable child elements / Action-383

From: Timur Mehrvarz <timur.mehrvarz@web.de>
Date: Sat, 24 Jun 2006 13:02:12 +0200
Message-Id: <E6968C4A-2F7B-4B61-B12D-F1935A839E8F@web.de>
Cc: "public-cdf@w3.org" <public-cdf@w3.org>
To: "Anne van Kesteren" <annevk@opera.com>

Your concern is not fully clear to me. Could you explain, how focus  
management would/should be different, for instance in [1], if SVG  
objects were used as child elements, instead of bitmap images?

WICD Core assumes identical treatment, for as long as (scalable)  
child elements are not explicitly made focusable.


[1] http://lab.vodafone.com/lp/WICD-core-1/buttons/2d-nav.xhtml

On 20. Jan 2006, at 19:31, Anne van Kesteren wrote:

> In <http://www.w3.org/TR/2005/WD-WICD-20051219/#focus-management>  
> it is not clear to me what "must be treated like bitmap images"  
> means. In addition, doesn't that violate some accessibility  
> contrain that content should be accessible by keyboard in some way?  
> For example, if I would reference a text file which obviously has  
> no element or attribute to make it focusable and I would display it  
> in such a way that a scrollbar appears the user needs the ability  
> to scroll the respective document to get access to all the content.  
> Given the current definition that does not seem possible.
> -- 
> Anne van Kesteren
> <http://annevankesteren.nl/>
> <http://www.opera.com/>
Received on Saturday, 24 June 2006 11:01:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:21 UTC