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

Re: new Web API proposal - needs accessibility review

From: Charles McCathieNevile <chaals@opera.com>
Date: Fri, 11 May 2012 19:29:16 +0200
To: "User Agent Working Group" <w3c-wai-ua@w3.org>, "Jeanne Spellman" <jeanne@w3.org>
Message-ID: <op.wd5mu2xvwxe0ny@widsith-3.local>
On Fri, 11 May 2012 18:36:46 +0200, Jeanne Spellman <jeanne@w3.org> wrote:

> The W3C Web Apps working group is publishing 7 first public working  
> drafts shortly (within the next few weeks) for new APIs.  I thought it  
> would be advantageous to look at them and start commenting on  
> accessibility before they increase in maturity - since we usually don't  
> look at other specs until Last Call. I was chatting about these specs  
> with Michael Cooper (PF staff contact) and he did not know of available  
> resources in PF to review them this early.
> These two seemed closely related to UAAG 2.0 and of interest to members  
> of the group. Please let me know if you are interested and have some  
> time to review these Editor's drafts.  If you want to wait until the  
> FPWD is published, that is fine, too.
> 2. Pointer Lock;
> <http://dvcs.w3.org/hg/pointerlock/raw-file/tip/index.html>
> short-name = pointerlock
> 1-liner = "Defines an API that provides scripted access to raw mouse
> movement data while locking the target of mouse events to a single
> element and removing the cursor from view"

This is motivated by things like games - instead of the mouse moving the  
cursor, it will feed directional information to the page that will  
probably use it to pan the screen. Of course it is also useful for other  
panning, like maps applications, and exploring when you have zoomed into a  

Definitely one to watch.

> 3. Shadow DOM;
> <http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html>
> short-name = shadow-dom
> 1-liner = "Describes a method of establishing and maintaining functional
> boundaries between DOM subtrees and how these subtrees interact with
> each other within a document tree"

This is part of the Web Components work. The overarching idea is that you  
can make a bit of custom code (eg the MyFancyCatViewer element), use it in  
your code, and link it up to some javascript, css, etc that actually makes  
it work. The big thing to watch here is probably design patterns and how  
they hook into accessibility - e.g. when should things be lined to native  
HTML, when should they be using ARIA, etc. This is IMHO a pretty big one  
for accessibility - and it would be good if PF was closely following. (So  
I will forward this bit to them too...)



Charles 'chaals' McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg kan noen norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Friday, 11 May 2012 17:29:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:41 UTC