Review of IndiueUI: Events 1.0 Draft 7 January 2013

Suggested Changes and Comments:

Abstract:

<change>
This specification, in conjunction with the User Context Module, is
intended address the problem of device-, OS-, and localization-independent
control of web content, including custom widgets. See the introduction for
background and usage examples.
</change>

<to>
This specification, in conjunction with the User Context Module, is
intended address the problem of device-independent, OS-neutral, and
localization-independent control of web content, including custom widgets.
See the introduction for background and usage examples.
</to>

1.1 Background:

Paragraph 1:

<change>
alternate assistive technologies including
</change>
<to>
assistive technologies that use alternate forms of input such as
</to>

1.2 Goals:

Bullet 1: <change< agnostic</change> <to> input agnostic </to>

Bullet 3: A comment: Just wanted to point out that another group is doing
Pointer events which are more agnostic. We might want to limit this to
command and control functions.

General change:

Both sections 2 and 3 should say "This section is normative."  as the
preceding sections say they are non-normative. ... or you should separate
these sections into  a normative part of the spec. Either way would be
fine.

3. UI Request Events

Are there going to be incidents where the request event is NOT sent to the
element with the Point of Regard. IOW should the Point of Regard always be
moved to make all requests? We should look into this.

3.1.3 UIRequestEventType

Each of these are separated by a black and red color. I am not sure why we
are differentiating by color. e.g.:
Undo Request undorequest

If we are differentiating by color that is an accessibility issue.

Why don't we just get rid of the first part and have undorequest? You have
the definition following it.


3.2.1 UIManipulationRequest

We need to prototype this to know whether we have this right.

Glossary:

Point-of-Regard:

The definition should start out as the point of user focus within which UI
actions are directed. ...  and then follow with the rest of it.

This is the extent of my comments for this first working draft. It is a
good first draft. We need to dig into these deeper and provide greater
specificity such as scrolling increments. We are all aware of that.