W3C home > Mailing lists > Public > public-wai-rd@w3.org > June 2012

Fwd: IndieUI Task Force Call for Proposals

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Tue, 19 Jun 2012 23:13:40 +0200
Message-ID: <4FE0EB84.8070402@w3.org>
To: RDWG <public-wai-rd@w3.org>
Dear RDWG,

In case you are not subscribed to the WAI Interest Group (IG) mailing 
list (which is probably a useful thing to do), this work on "IndieUI" 
that is currently ramping up at W3C/WAI seems relevant to our upcoming 
Mobile Accessibility symposium.


-------- Original Message --------
Subject: IndieUI Task Force Call for Proposals
Date: Mon, 18 Jun 2012 21:48:23 -0400
From: Janina Sajka <janina@rednote.net>
To: W3C WAI Protocols & Formats <w3c-wai-pf@w3.org>,        WAI XTech 
<wai-xtech@w3.org>, w3c-wai-ig@w3.org

       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 
Working Group are now seeking proposals from W3C members for their  two 

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 
such as scrolling the view, canceling an action, changing the value of a 
input widget, selecting a range, placing focus on an object, etc. 
platforms will take modality-specific user input, user idiosyncratic 
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 

In addition to inputs for the above deliverables, we also welcome and 
Use Cases and Requirements for these deliverables. Please see the 
related wiki
that includes some initial Use Case inputs:

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 
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

The WAI Independent User Interface (IndieUI) Working Group Home Page is at:

The Web Events Working Group Home Page is at:


Janina Sajka,	Phone:	+1.443.300.2200
		Email:	janina@rednote.net

The Linux Foundation
Chair, Open Accessibility:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/
Received on Tuesday, 19 June 2012 21:14:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:42 UTC