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

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

From: Anne van Kesteren <annevk@opera.com>
Date: Sat, 24 Jun 2006 13:07:25 +0200
To: "Timur Mehrvarz" <timur.mehrvarz@web.de>
Cc: public-cdf@w3.org
Message-ID: <op.tbnc6n1m64w2qv@id-c0020.www.planet.nl>

On Sat, 24 Jun 2006 13:02:12 +0200, Timur Mehrvarz <timur.mehrvarz@web.de>  
> 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?

I gave an example where that would be different. I also asked a question  
(on the first line) which is not answered by this reply.

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

Could you please elaborate on "explicitly made focusable"?

Aren't such things up to the UI of the particular device? For example,  
some browsers allow you to "focus" images so you send them to someone else  
or save them. Such things are important from an accessibility perspective.

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

>> 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
Received on Saturday, 24 June 2006 11:07:41 UTC

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