Action item on user interfaces

Here is an action item to consider in connection with yesterday's
discussion of user interfaces, XForms, UIML etc.

Ian suggested making it clear in the document which checkpoints should be
applicable to user interfaces. So far as the output side of a user
interface is concerned, there seems to be little difference in principle
from a "static document" (the distinction between content and style still
applies; text equivalents need to be provided where necessary;
navigational hierarchies, of user interface controls for example, need to
be clear and consistent, etc.).

On the input side, guideline 5 applies.

Action items:

1. Review guidelines 1-4 and 6, together with their associated
checkpoints, and determine whether any special notes or qualifications
should be added with respect to user interfaces, and how many of the
checkpoints readily apply to user interface design, taking XForms, HTML
forms, WML, scripting etc., into consideration. Note that guideline 2
refers to markup languages and data models, the latter encompassing the
case in which the content is being supplied by software (for example a
programmatic object) and not by a resource such as a document, written in
a markup language.

2. Review guideline 5, with XForms and related technologies in mind, and
decide whether any changes should be made, or further requirements added.
For instance, the possibility that different interfaces can be constructed
for different devices (speech grammars for speech devices; graphical
dialogues for visual displays etc.) isn't taken into account in guideline
5. How should we address it? Are there other issues?

Received on Thursday, 5 October 2000 22:50:31 UTC