W3C home > Mailing lists > Public > public-html-a11y@w3.org > June 2014

FW: Editing TF and list

From: Cynthia Shelly <cyns@microsoft.com>
Date: Thu, 26 Jun 2014 19:31:13 +0000
To: PF <public-pfwg@w3.org>, "public-indie-ui@w3.org" <public-indie-ui@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
CC: Ben Peters <Ben.Peters@microsoft.com>, Robin Berjon <robin@w3.org>
Message-ID: <34d8bba667be41a8a99679da9384c491@BLUPR03MB166.namprd03.prod.outlook.com>
This came up on the html-a11y call this morning, and I wanted to fill people in a little more.  
There is an effort in webapps to create command events that are based on user intention, particularly related to content editing scenarios.  I've been working with my colleague, Ben Peters, on this effort for a while, and think that this proposal does a good job of considering accessibility.  We all know that accessibility for rich text editors is a big problem, and I think this can solve it.  I’m really excited about this work.

There is also a lot of overlap with IndieUI.  The scenario is more limited (just editing), but the idea is very similar.  Below is the announcement of the taskforce and list dedicated to this effort.  They would very much like to work with us (I've already joined) to create a harmonized product.  

Please join the TF and start the discussion.

The best place to get started understanding this work is the explainer that Ben wrote:  
http://w3c.github.io/editing-explainer/commands-explainer.html 

The last paragraph is about indieUI
<blockquote>
8. Relationship to IndieUI

IndieUI: Events 1.0 is solving a similar problem. The abstract of that spec says "This provides an intermediate layer between device- and modality-specific user interaction events, and the basic user interface functionality used by web applications." The list of intentions it handles is given in the Event List of that document. A great deal of effort and work has gone into that document, and it has many valuable insights. 

The Commands Explainer is solving this problem by starting with concepts that the Editor uses today, such as Commands, Selection, and contentEditable. IndieUI appears to be starting with concepts from Accessibility. It is important for these two efforts to come together and solve these problems for both of these scenarios. Understanding a user's intentions is crucial when there are so many ways that a user can declare them.  
</blockquote>

The TF archive and charter are linked in the announcement from Robin, below.

Thanks,
Cynthia

-----Original Message-----
From: Robin Berjon [mailto:robin@w3.org] 
Sent: Monday, June 23, 2014 6:59 AM
To: HTML WG (public-html@w3.org); WebApps WG
Subject: Editing TF and list

Hi all,

this email is to announce the creation of the task force working on editing, jointly between WebApps and HTML, based on the decision made previously[0].

The mailing list's address is public-editing-tf@w3.org and signing up is at mailto:public-editing-tf-request@w3.org?subject=subscribe.

The rationale for having this specific list is in the "charter"[1]. 
Feedback and suggestions are welcome on that document, which is informal and mostly means to document the group's purpose.

I suggest that for a short while (~a week, mostly covering existing
threads) people cross-post. After that, though, all discussion ought to have been redirected there.

Thanks!


[0] http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0842.html

[1] http://w3c.github.io/editing-explainer/tf-charter.html


--
Robin Berjon - http://berjon.com/ - @robinberjon

Received on Thursday, 26 June 2014 19:31:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:39 UTC