Merge with TR-20130122
authorMichael Cooper <>
Wed, 06 Feb 2013 08:51:15 -0500
changeset 82 3735fed45714
parent 75 3218cf34862d (current diff)
parent 81 1ccd467eaacb (diff)
child 83 b08debffb8cc
Merge with TR-20130122
--- a/src/css/screen.css	Fri Jan 18 11:05:58 2013 -0800
+++ b/src/css/screen.css	Wed Feb 06 08:51:15 2013 -0500
@@ -76,7 +76,7 @@
 html kbd {
 	text-transform: lowercase;
 	font-variant: small-caps;
-	font-style: bold;
+	font-weight: bold;
 html pre { /* more specific selector than the default W3C style sheet */
--- a/src/indie-ui-events.html	Fri Jan 18 11:05:58 2013 -0800
+++ b/src/indie-ui-events.html	Wed Feb 06 08:51:15 2013 -0500
@@ -17,7 +17,7 @@
 		<script class="remove">
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "ED",
+          specStatus:           "FPWD",
           // the specification's short name, as in
           shortName:            "indie-ui-events",
@@ -27,19 +27,19 @@
           subtitle   :  "Events for User Interface Independence",
           // if you wish the publication date to be other than today, set this
-          // publishDate:  "2009-08-06",
+          publishDate:  "2013-01-22",
           // if the specification's copyright date is a range of years, specify
           // the start date here:
-          // copyrightStart: "2012",
+          // copyrightStart: "2013",
           // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
           // and its maturity status
-          // previousPublishDate:  "1977-03-15",
+          // previousPublishDate:  "2013-01-22",
           // previousMaturity:  "WD",
           // if there a publicly available Editor's Draft, this is the link
-          edDraftURI:           "",
+          edDraftURI:           "",
           // if this is a LCWD, uncomment and set the end of its review period
           // lcEnd: "2009-08-05",
@@ -67,7 +67,7 @@
           // name of the WG
-          wg:           "Independent User Interface (Indie UI) and Web Events Working Groups",
+          wg:           "Independent User Interface (Indie UI) Working Group",
           // URI of the public WG page
           wgURI:        "",
@@ -94,6 +94,15 @@
 		<section id="sotd">
+			<p>This is a First Public <a href="">Working Draft</a> by the <a href="">IndieUI Working Group</a> (IndieUI WG) of the <a href="">Web Accessibility Initiative</a>. The Independent User Interface Task Force has produced this document based on initial proposals and review of features critical to include for this first review opportunity. The task force has identified <a href="">use cases and requirements</a> to inform this draft, although not all requirements are yet addressed in this version. Open issues and actions are tracked in the <a href="">IndieUI: Events tracker product</a>. A <a href="">history of changes to IndieUI: Events 1.0</a> is available.</p>
+			<p>The Independent User Interface Task Force is comprised of members of the IndieUI Working Group and the <a href="">Web Events Working Group</a>. The <a href="">IndieUI Working Group charter</a> specifies that this document is a joint deliverable with the Web Events Working Group. Since the time this charter was approved, the Web Events WG has become a maintenance-only group with its work items superceded by deliverables of the new <a href="">Pointer Events Working Group</a>. Therefore this document is now a publication solely of the IndieUI Working Group.</p>
+			<p>Feedback on this specification is essential to success of the technology. The IndieUI WG asks in particular:</p>
+			<ul>
+				<li>Does the spec meet its requirements, and are the requirements complete?</li><li>Does the spec meet both accessibility and mainstream use cases successfully without compromising one for the other?</li>
+				<li>Is this approach useful and necessary compared to existing techniques? </li>
+				<li>Is this approach easy to implement? If not, why not?</li>
+			</ul>
+			<p>To comment on this document, start with the <a href="">instructions for commenting</a> page to submit comments (preferred), or send email to <a href="mailto:[email protected]?subject=Comment%20on%20IndieUI:%20Events%2022%20January%202013">[email protected]</a> (<a href="">comment archive</a>). Comments should be made by <strong>22 February 2013</strong>. In-progress updates to the document may be viewed in the <a href="">publicly visible editors' draft</a>.</p>
 		<!-- :::::::::::::::::::: INTRO :::::::::::::::::::: -->