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 14:15:13 +0200
To: "Chris Lilley" <chris@w3.org>
Cc: public-cdf@w3.org
Message-ID: <op.tbngbnvj64w2qv@id-c0020.www.planet.nl>

On Sat, 24 Jun 2006 14:02:10 +0200, Chris Lilley <chris@w3.org> wrote:
>>> WICD Core assumes identical treatment, for as long as (scalable)
>>> child elements are not explicitly made focusable.
> AvK> Aren't such things up to the UI of the particular device?
> No, not by default; thats why CDF is working on a specification for
> them. So that authors can actually design usable content with meaningful
> navigation and have it work the same in multiple implementations.

Authors should just be concerned with making sure that each element the  
user should be able to navigate to is declared as such. They can also give  
hints as to where the UA should go next but the final descision for such  
things should be up to the UA.

> AvK> For example,
> AvK> some browsers allow you to "focus" images so you send them to  
> someone else
> AvK> or save them. Such things are important from an accessibility  
> perspective.
> All of which is possible at user option, not precluded by having a
> standardized defauly focus and navigation scheme, and thus a poor
> argument against having this well specified.

Users normally don't configure their browser. I don't think any  
specification should contrain the particular UI implementation of a UA.

Anne van Kesteren
Received on Saturday, 24 June 2006 12:15:22 UTC

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