- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Thu, 21 Jun 2012 08:32:38 -0400
- To: James Craig <jcraig@apple.com>
- CC: Independent User Interface Task Force <public-indie-ui@w3.org>
Hi James - during yesterday's IndieUI call, you gave an overview ([1]) of the "User Interface Independence for Accessible Rich Internet Applications" document [2]. Would you please clarify if this document is now an input for the IndieUI Events spec? -Thanks, Art Barstow [1] http://www.w3.org/2012/06/20-indie-ui-minutes.html#item06 [2] http://lists.w3.org/Archives/Public/www-dom/2010JulSep/att-0106/UserInterfaceIndependence.html On 6/18/12 9:43 PM, ext Janina Sajka wrote: > Call for Proposals: Use Cases, Requirements and Specification Inputs > Independent User Interface Task Force > World Wide Web Consortium > 18 June 2012 > > The WAI Independent User Interface (IndieUI) Working Group and the Web Events > Working Group are now seeking proposals from W3C members for their two joint > deliverables: > > 1.) Indie UI: Events 1.0, an abstraction between device-specific user > interaction events and inferred user intent such as scroll, activate, etc. This > provides an intermediate layer between device- and modality-specific user > interaction events, and the basic user interface functionality used by Web > applications. Indie UI: Events focuses on granular user interface interactions > such as scrolling the view, canceling an action, changing the value of a user > input widget, selecting a range, placing focus on an object, etc. Implementing > platforms will take modality-specific user input, user idiosyncratic heuristics > to determine the specific corresponding Indie UI event, and send that to the > Web application (along with details of the modality-specific input such as > mouse or keyboard events should applications wish to process it). > > 2.) Indie UI: User Context 1.0, a set of properties and methods related to > the environmental context of a specific user, and a vehicle to access them to > facilitate a Web application's ability to adapt to the user's needs. This is > meant to provide information about whether a user is using a screen reader, > screen magnifier, or other Assistive Technology, and to expose relevant user > settings, allowing optimal adaptation of the Web application's user interface. > > In addition to inputs for the above deliverables, we also welcome and encourage > Use Cases and Requirements for these deliverables. Please see the related wiki > that includes some initial Use Case inputs: > http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements > > Proposals received will be evaluated for use as initial starting points in the > creation of these deliverables by the IndieUI Task Force, which is the locus of > joint work on these deliverables for the WAI_IndieUI WG and the Web Events WG. > > Proposals should be submitted by 15 July 2012, and should be submitted to the > IndieUI Task Force's email list (public-indie-ui@w3.org). Proposals submitted > after that date are still welcome but may not be included in First Public > Working Drafts. > > More information concerning the work of the IndieUI Task Force, including > instructions on how to participate, is available on the IndieUI Task Force Home > Page: > http://www.w3.org/WAI/IndieUI/IUITF > > The WAI Independent User Interface (IndieUI) Working Group Home Page is at: > http://www.w3.org/WAI/IndieUI/ > > The Web Events Working Group Home Page is at: > http://www.w3.org/2010/webevents/ > >
Received on Thursday, 21 June 2012 12:33:15 UTC