--- a/src/indie-ui-requirements.html Wed Apr 02 14:47:11 2014 -0700
+++ b/src/indie-ui-requirements.html Tue Apr 08 16:53:25 2014 -0400
@@ -2,7 +2,7 @@
<html lang="en-us" xmlns="http://www.w3.org/1999/xhtml">
<head>
<!--<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />-->
- <title>Requirements for IndieUI: Events 1.0</title>
+ <title>Requirements for IndieUI 1.0</title>
<link href="./css/screen.css" rel="stylesheet" type="text/css" />
<script type="text/javascript" src="./loc/en/strings.js" class="remove"></script>
<script type="text/javascript" src="./js/utils.js" class="remove"></script>
@@ -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 http://www.w3.org/TR/short-name/
shortName: "indie-ui-requirements",
@@ -27,7 +27,7 @@
// subtitle : "Events for User Interface Independence",
// if you wish the publication date to be other than today, set this
- //publishDate: "2013-01-22",
+ publishDate: "2014-04-17",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -82,6 +82,9 @@
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/54953/status",
+
+ // not Rec track
+ noRecTrack: true,
};
</script>
@@ -90,7 +93,14 @@
<body>
<section id="abstract">
- <p>@@</p>
+ <p>This document outlines the requirements that the IndieUI Working Group has set for development
+ of IndieUI 1.0. These requirements will be used to determine if the IndieUI WG has met its
+ goals as IndieUI 1.0 advances through the <a
+ href="http://www.w3.org/2005/10/Process-20051014/tr.html#Reports">W3C Recommendation Track
+ Process</a>. This document introduces a series of user scenarios and a list of technical
+ requirements needed to meet those scenarios. It also provides information about how the
+ requirements are addressed in <a href="http://www.w3.org/TR/indie-ui-events/">IndieUI:
+ Events 1.0</a> and IndieUI: User Context 1.0.</p>
</section>
<section id="sotd">
@@ -99,7 +109,11 @@
<!-- :::::::::::::::::::: INTRO :::::::::::::::::::: -->
<section id="intro">
<h2>Introduction</h2>
- <p>@@Why IndieUI, might take some intro material from spec</p>
+ <p>Scripting usable interfaces can be difficult, especially when one considers that user interface design patterns differ across software platforms, hardware, and locales, and that those interactions can be further customized based on personal preference. Individuals are accustomed to the way the interface works on their own system, and their preferred interface frequently differs from that of the web application author's preferred interface. Some complex web applications can provide a much better experience if given access to information such as a user's preferred color, font, screen, and even <em>restricted</em> assistive technology settings such as a preference to render captions, or whether a screen reader is on. </p>
+ <p>Custom interfaces often don't take into account users who access web content via assistive technologies that use alternate forms of input such as screen readers, switch interfaces, or speech-based command and control interfaces. For example, a web page author may script a custom interface to look like a slider (e.g. one styled to look like an <abbr title="Hypertext Markup Language">HTML</abbr> "range" input) and behave like a slider when using standard mouse-based input, but there is no standard way for the value of the slider to be controlled programmatically, so the control may not be usable without a mouse or other pointer-based input.</p>
+ <p>IndieUI defines a way for web authors to register for these <em>request events</em>. Authors declaritively define which actions or behaviors a view responds to, and when it is appropriate for browsers to initiate these events. It also provides authorized web applications access to information about a user's relevant settings and preferences, to provide the best possible user experience to all users. General web pages developed using best practices may never need access to restricted user settings, but complex web applications can utilize this information to enhance the performance and user interface.</p>
+ <p>One of the core principles behind IndieUI is that that it operates on a backwards-compatible, opt-in basis. In other words, the web application author has to first be aware of these events, then explicitly declare each event receiver and register an event listener, or user agents behave as normal and do not initiate these events. If a web application does not respond to the event, the user agent may attempt fallback behavior or communicate to the user that the input has not been recognized.</p>
+
</section>
<!-- :::::::::::::::::::: END INTRO :::::::::::::::::::: -->
@@ -552,7 +566,9 @@
</section>
-->
- <section id="acknowledgements" class="appendix" data-include="./include/ack.html"></section>
+ <section id="acknowledgements" class="appendix" data-include="./include/ack.html">
+ <p>Placeholder for acknowledgements</p>
+ </section>
</body>
</html>