The mission of the Indie UI Working Group, part of the WAI Technical Activity, is to develop event models for Application Programming Interfaces (APIs) that facilitate interaction in Web applications that are input method independent, and hence accessible to people with disabilities.
|End date||30 April 2015|
|Confidentiality||Proceedings are public|
|Initial Chairs||Janina Sajka|
|Initial Team Contacts
(FTE %: 15)
|Usual Meeting Schedule||Teleconferences: Bi-Weekly
Face-to-face: 1 per year
This group will develop a set of events to represent user intent in interaction with Web applications, regardless of device-specific interaction. These events allow the use of alternate input devices such as assistive technologies, while providing a simple model for authors to develop interaction for a wide array of devices. These capabilities are critical for accessibility, and they also benefit mainstream users.
The types of actions that can be represented in this model are those prevalent among GUI and Web applications at this time, 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. These are basic user interface gestures that are common to most platforms but are actuated in various ways depending on hardware features, system design, and user interaction modality, yet via Indie UI can be exposed in a simple and universal manner to Web applications.
These events enhance or complement APIs from other Working Groups, and provide an intermediate layer between device- and modality-specific events (which are out of scope) and the functionality needed by Web applications. This group will coordinate closely with groups that develop events for particular devices and modalities to ensure Indie UI provides a good translation layer to express user intent. The group may support enhanced deliverables of such groups instead of developing the model itself, and will form a joint task force with the Web Events WG.
The Deliverables section describes the documents that, together, specify Indie UI. No other Recommendation-track deliverables are in scope.
Tasks within this scope include:
Additionally it is hoped that two or more complete implementations are available in mainstream user agents and that "real" (not testing) Web sites use the technology.
Explicitly out of scope are any device-specific events, models, APIs, etc., such as (but not limited to) touch, gestures, and voice.
Only 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. are in scope of Indie UI; higher-order inferred intents that do not relate directly to concrete user interface interaction steps are out of scope. Other specifications, such as Web Intents, may address this level.
This group will produce the following Recommendation-track specifications:
The two deliverables in the Indie UI charter correspond to the "higher-level user-action events" mentioned as part of the overall deliverable of the Web Events charter. These specific aspects of the Web Events deliverable will be jointly owned by both the WebEvents and the Indie UI Working Groups, which would be reflected in the Status of This Document section for both deliverables. Members who join either Web Events or Indie UI would be able to work on the Indie UI deliverable. Importantly, Members who join Indie UI but do not join Web Events do not take on any intellectual property obligations for any other aspect of the Web Events work. The creation of a separate Indie UI Working Group allows Members that otherwise do not participate in Web Events to participate in this particular work.
Active deliverables are detailed on the Indie UI WG home page. The 1.0 version of Indie UI will focus on events that interface with actions common at the present time with mobile and desktop devices. It may provide an extension model for forwards compatibility, and future versions are expected to address additional user actions that become prevalent.
In addition to Recommendation-track documents, the group will publish supporting materials as Working Group Notes. These primarily consist of primers and best practices, and may also include requirements and analyses.
Note: The actual production of some of the deliverables may follow a different timeline. The group will document any schedule changes on the group home page.
|Note: The group will document significant changes from this initial schedule on the group home page.|
|Indie UI: Events||July 2012||July 2013||January 2014||July 2014||September 2014|
|Indie UI: User Context||November 2012||November 2013||May 2014||November 2014||January 2015|
The Indie UI Working Group coordinates in particular with the following Working Groups:
In addition to the above groups, the Indie UI Working Group also coordinates with the following Working Groups as needed. Additional detail on active liaisons is documented on the Indie UI WG home page.
Furthermore, Indie UI Working Group expects to follow these W3C Recommendations:
To be successful, the Indie UI Working Group is expected to have 7 or more active participants for its duration. Effective participation to Indie UI Working Group is expected to consume six hours per week for each participant; eight hours per week for editors. The Indie UI Working Group will allocate also the necessary resources for building Test Suites for each specification.
Participants are reminded of the Good Standing requirements of the W3C Process.
This group primarily conducts its work on the public mailing list email@example.com (firstname.lastname@example.org archive). Administrative and planning discussion may take place on the Member only mailing list email@example.com (firstname.lastname@example.org archive, Member-only link). Comments on deliverables may be sent to email@example.com (firstname.lastname@example.org archive).
Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the Indie UI Working Group home page.
As explained in the Process Document (section 3.3), this group will seek to make decisions when there is consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.
When deciding a substantive technical issue, the Chair may put a question before the group. When the Chair conducts a formal vote to reach a decision on a substantive technical issue, eligible voters may vote on a proposal one of three ways: for a proposal, against a proposal, or abstain. For the proposal to pass there must be more votes for the proposal than against. In case of a tie, the Chair will decide the outcome of the proposal.
This charter is written in accordance with Section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This charter for the Indie UI Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
$Date: 2012/05/22 20:42:36 $