First draft of status for User Context FPWD June_2014_FPWD
authorMichael Cooper <cooper@w3.org>
Mon, 16 Jun 2014 14:20:11 -0400
branchJune_2014_FPWD
changeset 219 98e9e4954292
parent 218 df94a88b06a5
child 221 4c3f1dd10f1b
First draft of status for User Context FPWD
src/indie-ui-context.html
--- a/src/indie-ui-context.html	Mon Jun 16 14:16:16 2014 -0400
+++ b/src/indie-ui-context.html	Mon Jun 16 14:20:11 2014 -0400
@@ -92,7 +92,16 @@
 		</section>
 
 		<section id="sotd">
-			<p>@@ Status for FPWD</p>
+			<p>This is a First Public <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsWD">Working Draft</a> by the <a href="http://www.w3.org/WAI/IndieUI/">IndieUI Working Group</a> (IndieUI WG) of the <a href="http://www.w3.org/WAI/">Web Accessibility Initiative</a>. The Working Group has produced this document based on initial proposals and review of features critical to include for this first review opportunity. The <a href="http://www.w3.org/WAI/IndieUI/track/products/3">IndieUI: User Context tracker</a> lists open issues and actions, and links to closed issues and actions, which are the basis for most of the previous and upcoming updates; newer issues are tracked in <a href="https://www.w3.org/Bugs/Public/buglist.cgi?component=IndieUI%3A%20User%20Context&amp;product=IndieUI&amp;version=1.0"><abbr title="World Wide Web Consortium">W3C</abbr> Bugzilla for IndieUI: User Context</a>. The Working Group has published <a href="http://www.w3.org/TR/indie-ui-requirements/">use cases
+				and requirements</a> that are expected to be met by this specification; feedback on these is encouraged as well. Also see the <a href="http://www.w3.org/WAI/intro/indieui">IndieUI Overview</a>.  <!--A <a href="#changelog">history of changes to UndieUI: User Context</a> is available in the appendix.--> </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, send email to <a href="mailto:[email protected]?subject=Comment%20on%20IndieUI:%20User%20Context%2026%20June%202014">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-indie-ui-comments/">comment archive</a>) or <a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=IndieUI&amp;component=IndieUI:%20Events&amp;version=1.0">file an issue in <abbr title="World Wide Web Consortium">W3C</abbr> Bugzilla</a>. Comments should be made by <strong>1 August 2014</strong>. In-progress updates to the document may be viewed in the <a href="https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-context.html">publicly visible editors' draft</a>.</p>
 		</section>
 		
 		<!-- :::::::::::::::::::: INTRO :::::::::::::::::::: -->