Events/Requirements

From Independent User Interface
Revision as of 20:55, 24 July 2013 by Cooper (Talk | contribs)

Jump to: navigation, search

These are scenarios for the Indie UI Events and Indie UI User Context specifications, of the Indie UI WG.

Contents

Use Cases and Scenarios

The following consolidations were made from the previous version of the scenarios:

  • Combine S3 and S4
  • Combine S6, S7, S8, S9
  • Combine S10, S11, S12
  • Combine S14, S15
  • Combine S18, S19
  • Combine S20, S21
  • Combine S22, S23, S24, S25
  • Combine S26, S27, S28, S29
  • Combine S31, S32

Scenario 1: Manipulating a map

A person is using a map to find the location and layout of a local park in a web-based mapping application so they can print it out, using their touch-screen laptop. They know the general location, and see the green area on the lower-left-hand corner of the map on the screen. They touch that part of the screen, and use a zooming gesture to center and zoom in on that section of the screen, then fine-tune the centering using the arrow keys on their keyboard and zoom in further using the context menu on their laptop's trackpad. Finally, they use a rotation gesture on the touchscreen to re-orient the map around the point of interest. Once they have the view they want, they use the browser's control menu to print the map.

S1 Notes

  1. add note here

Specification Scope: Indie UI Events or Indie UI User Context

S1 Priority

Priority: MEDIUM (?)

Consensus decision: link to minutes or email

S1 Related Requirements

  • Multi-Input
    • An interaction through any input type (screen, keyboard, mouse) must not prevent using a different input type for subsequent interactions
    • Authors should not have to write multiple code paths for the same type of interaction event (e.g. pan, zoom, rotate)
  • Optional point-of-regard
    • An interaction can have an explicit or implicit point of regard. For example, zooming with a touch screen explicitly zooms around a specific point, while zooming with a keyboard may use an implicit point like the center of the object.
  • Units of interaction that correspond precisely with units of display on a screen.
    • It should be possible to implement a map such that all touch-screen interactions keep the same points positioned under the user's fingers. That is, a user could touch two locations on a map, then do a complex series of pinch, pan, and rotate gestures and at the end still have those two locations under their fingers.
    • The units of interaction must be at least as granular as the pixel units. Eg. it should be possible to drag the object exactly one pixel on the screen with a mouse.
  • Multiple concurrent and inter-related interactions
    • Panning, zooming and rotation may all occur with the same type of gesture on a touch screen (eg. two fingers on the screen moving). A single hardware-level event (eg. one finger moving) may result in multiple logical interactions (eg. rotate and zoom) which should ideally be applied as a single operation.

S2: Command to execute a popup

A user whose point of regard (focus) is on a UI object that support popups performs an action that causes the web application to render the popup. A popup could be a popup dialog box or a popup menu. The user would like to be made aware that either of these popup options are available and be able to cause the popup to render using a variety of device input interaction methods such as a keyboard command, a gesture, a voice command, or a right mouse click.

S2: Notes

  • WAI-ARIA provides a property, aria-haspopup, that indicates the UI Widget supports a popup.

S2 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S2 Related Requirements

  • Notification event
    • The device should post a notification to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S3: Command to open or collapse a tree branch, menu, expandable grid cell, or expandable section

A user whose point of regard (focus) is on a UI object that indicates the UI object is expandable / collapsible to reveal / hide subordinate content would like to perform an action to cause the web application to reveal / hide the content. Common UI objects that support this function are tree items in tree controls, gridcells in treegrids that expand to reveal new rows, accordion tabs which reveal / hide panels of content, or expandable and collapsible regions (e.g. portlets). The user would like to be made aware that these options are available and be able to reveal / hide the content using a variety of device input interaction methods such as a keyboard command, a gesture, a voice command, or possibly a mouse click.

S3 Notes

  • WAI-ARIA provides an aria-expanded property that indicates that is expandable when it is set to false.
  • WAI-ARIA has a container role of dialog that this could be applied to. Essentially this would be equivalent to an escape key

S3Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S3 Related Requirements

  • Notification Event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S4: Command to collapse a tree branch, expandable grid cell, or expandable section

A user whose point of regard (focus) is on a UI object that indicates the UI object is collapsible to hide associated content and would like to perform an action to cause the web application to hide the visible content. Common UI objects that support this function are tree items in tree controls, gridcells in treegrids that expand to hide associated rows, accordion tabs which collapse to hide panels of content until the user needs to use it again, or expandable and collapsible regions (e.g. portlets). The user would like to be made aware that either of these popup options are available and be able to cause the popup to render using a variety of device input interaction methods such as a keyboard command, a gesture, a voice command, or possibly a mouse click.

S4: Notes

  • WAI-ARIA provides an aria-expanded property that indicates that it is collapsible when it is set to true.
  • WAI-ARIA has a container role of dialog that this could be applied to. Essentially this would be equivalent to an escape key

S4 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S4 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S5: Command to activate a UI component

A user whose point of regard (focus) is on a UI object, that can be activated, and would like to perform an action to activate it. Example UI objects that support activation are push buttons, radio buttons, checkboxes, and menu items. The action could be in the form of a tap, a gesture, a voice command, a mouse click, a keyboard key, or a command from an alternative input device.

S5: Notes

  • This has been proposed in the past and the legacy "click" was used instead - DOMActivate.

S5 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S5 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S6: Command move the focus point within a UI component down to the next item within a UI component

A user whose focus is on a UI object that supports supports up and down navigation within the UI component would like to control the UI to move its current active item (usually rendered visibly as its point of regard) to the next item logically down within its internal navigation sequence. This might be the next item down within a listbox, tree widget, menu, menubar, or gridd, treegrid, select, or any other type of UI Component supporting this function. The action could be in the form of a gesture, a voice command, a right mouse click, a keyboard key, or an alternative input device. Some UI components may choose to force a selection of the item in response to the downward navigation notification.

S6: Notes

  • We cannot assume we know all UI components capable of supporting this function.
  • Some UI components may move its internal point of regard back to the beginning of its navigation sequence after it reaches the end.
  • This movement is not response to a tab notification which should be designed to move among widgets and interactive controls that are not managed by another UI component.

S5 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S6: Command to move the focus point within a UI component down to the next / visual right / visual down, or previous / visual left / visual up item within a UI component

A user whose focus is on a UI object that supports next and previous navigation within the UI component would like to control the UI to move its current active item (usually rendered visibly as its point of regard) to the next or previous item within its internal navigation sequence. This might be the next or previous item within a listbox, tree widget, menu, menubar, or grid, treegrid, select, or any other type of UI Component supporting this function. Visually the next item is usually right or down, and the previous item is usually left or above. The action could be in the form of a gesture, a voice command, a right mouse click, a keyboard key, or an alternative input device. Some UI components may choose to force an item selection in response to the action.

S6: Notes

  • We cannot assume we know all UI components capable of supporting this function.
  • Some UI components may move its internal point of regard back to the beginning of its navigation sequence after it reaches the end.
  • This movement is not response to a tab notification which should be designed to move among widgets and interactive controls that are not managed by another UI component.
  • This would not be applicable to Dialogs or form elements that intended to be in the tab sequence.
  • "Visual right" vs "next element" / "visual left" vs "previous element" are two different things. Right and left are locale-independent. Next / previous element would change direction based on locale, for example, in RTL languages like Arabic.
  • We cannot assume that moving the point of the regard to the right will not move the point of regard back to the left-most managed object when starting from the right-most managed UI object.

S5 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S6 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S10: Command to direct a media player to start, stop, or pause playing

A user whose point of regard (focus) is within a media player would like to notify the application to start, stop, or pause the playing of the video, audio, or animation. When a notification to start, stop, or pause the player is received the rendering starts, stops, or pauses. Start starts playing form the current time in the media play sequence. Stop moves the current time in the media play back to the start of the media sequence. Pause stops playback but does not move the time pointer. Example UI components would be a video player or audio player. The action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S10: Notes

  • Do we want to include animation such as SVG animation? This would require the user agent to respond to the notification.

S10 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S10 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S13: Command to the media player to toggle rendering captions

A user whose point of regard (focus) is within a media player would like to notify the application to toggle the rendering of video or audio captions. When a notification to toggle captions is received the player the toggles the rendering of the caption track at the synchronization point within the video or audio stream play. Example UI components would be a video player or audio player. The action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S13: Notes

  • HTML5 has a a new media controller API that could be used to facilitate this happening.

S13 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S13 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S14: Command to the media player increase or decrease the volume

A user whose point of regard (focus) is within a media player would like to notify the application to increase or decrease the video or audio volume. When a notification to increase or decrease the volume is received the player increases or decreases the rendering volume. Example UI components would be a video player or audio player. The action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S14: Notes

  • The increments would need to depend on the granularity of the player
  • Do we want to be able to change the volume increments?
  • Should we make this more generic to increase a control - such as a modifiable range object (slider)?

S14 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S14 Related Requirements

S16: Command to zoom in

A user whose point of regard (focus) is within a zoomable object would like to notify the application to zoom in on the object. When a notification to zoom in a particular factor is received, the object zooms in by that factor and optionally provides more detail. Example UI components would be an SVG rendering of a CAD drawing or a key component of a scatter plot. The notification could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S16: Notes

  • Do we want to separate Drill Down from Zoom Out or should we leave that up to the applications? A drill down might provide more information. An end user may think zoom simply enlarges an area vs. providing more detail.
  • Is this distinct in any way from the zoom operation discussed in the map scenario? Should we just have zoom, pan and rotate as separate scenarios (or even just a single combined scenario)?

S16 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S16 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S17: direct the UI object to pan right, left, up, or down

A user whose point of regard (focus) is within a media player would like to direct the ui object to pan up, down, left, or right so that more information can be revealed to the user in the direction of the pan. Example UI components would be a chart, subway map, CAD drawing, etc. The action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S17: Notes

  • Do we want to include animation such as SVG animation? This would require the user agent to respond to the notification.

S17 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S17 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S18: direct the UI object move its point of regard to the beginning or end of its navigation sequence

A user whose point of regard is rendered within a focused UI Object that manages its own navigation and would like to direct the ui object to move the point of regard to the beginning or end of the navigation sequence similar to a "Home" or "End" button. Example UI components would be a listbox, video player, audio player, tree widget, contenteditable area, tree widget, gridd, treegrid, or tablist. The action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S18: Notes

S18 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S18 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S20: grab, move, and release grabbable UI object

A user whose point of regard is non a UI object would like to grab the object for the purposes of moving it such as in a drag operation. After moving the point of regard, they drop the currently grabbed object on the object with focus at the current point of regard location. Example UI components to grab and move would be a light box, a lisbox item, a tree item, or a drawing object. Example UI components on which an item could be dropped would be a light box empty box or a line indicating a location between light box items, a lisbox item to drop the item before or after the current listbox item, a tree item to add a new item in a subtree, or a region of the web application or a drawing object. The action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S20: Notes

  • WAI-ARIA has an aria-grabbed property such that when set to false indicates that it may be grabbed for the purposes of moving it.
  • WAI-ARiA defines roles for objects such as regions
  • Should this be left up to the user agent?
  • Should the drop occur if the target does not have aria-dropeffect set?

S20 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S20 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S22: 'Continuous or discontinuous multi-slection within a UI object

A user whose point of regard is on a UI object would like to select multiple continuous or discontinuous items within a supporting UI control. Once initiated it would tell the UI component to start a run of either continuous or discontinuous item selections with in the UI control. For continuous selection, as the user navigates the items within the UI Object container each item navigated to is automatically selected until the multi-selection process terminates. For discontinuous selection, a separate command would be given to actually select individual items within the UI object but navigation among items in the UI object would not cause an actual selection to occur. When selection is complete, the user directs the UI object either to save the currently selected items and exit the selection process, or to cancel the selection process and clear the selection. Examples are options in a listbox, gridcells withing a gridd, or treeitems within a tree. This action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S22: Notes

  • WAI-ARIA has an aria-selected state that can be used to reflect the selected state of the item within a UI object..

S22 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S22 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S26: Increase or Decrease Size of UI object by a small or large increment

A user whose point of regard is on a UI object would like to ask it to increase or decrease its size by a small or large increment. This is very common in drawing objects such as drawing objects in a flow diagram or presentation tool where the user is attempting to create a visual UI. For people with mobility impairments this is very hard to do with a pointing device and alternate forms of input are necessary. This action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S26: Notes

  • We should provide an ARIA property for ARIA 2.0 that conveys that an object is resizeable.

S26 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S26 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S30: Move a UI object

A user whose point of regard is on a UI object would like to be able to move the object in different directions by both small and large ingrements. This is very common in drawing objects such as drawing objects in a flow diagram or presentation tool where the user is attempting to create a visual UI. For people with mobility impairments this is very hard to do with a pointing device and alternate forms of input are necessary. This action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S30: Notes

  • We should provide an ARIA property for ARIA 2.0 that conveys that an object is moveable.
  • We need to decide how we can do this in terms of the number of different types of events we use. This requires more group discussion.

S30 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S30 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S31: Reveal or hide additional text without selection

User indicates that further information about an object is desired and should be shown, or once seen, no longer needed and should be hidden. This further information may be a hint similar to Hover on a mouse based system. Content may be timed or something that completes display. This action could be in the form of a gesture, a voice command, a keyboard key combination, or an alternative input device.

S31: Notes

  • Should we use a hover device independent event instead and leave this up the developer?
  • This is related to S32, S33, and S34

S31 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S31 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S33: Change nearness indication without selection

User safely tests whether an object is active and can be selected. This further information may be a change in visual appearance, but not an actual selection or activation. (Similar to MouseOver on a mouse based system)

S33: Notes

  • Should we use a hover device independent event instead and leave this up the developer?
  • This is related to S31, S32, and S34

S33 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S33 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.

S34: User causes a non-selection active state indicator to disable.

The result is an a dormant state indication. (Similar to Mouse Exit on a mouse based system)

S34: Notes

  • Should we use a hover device independent event instead and leave this up the developer?
  • This is related to S31, S32, and S34

S34 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S34 Related Requirements

  • Notification event
    • The device should post a notification event to the UI object either by a bubbled event from a descendant object or directly.
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

S35: User causes a suspend/resume of live updates to the page (Can very from live regions, live blogging, twitter stream, live download.

S35: Notes

  • Discussed at November 1, 2012 TPAC Face to Face?

S35 Priority

Priority: HIGH, MEDIUM, LOW

Consensus decision: link to minutes or email

S35 Related Requirements

  • Notification event
    • The notification should not provide any device specific information about the devices that sent it.
    • The device must ensure that a keyboard device is capable of sending the notification.

Requirements

This is a list of requirements.

Matching Use Cases and Requirements

This is a table of requirements, with links to which section of the spec satisfies the requirement.

Requirement # Specification Section Link Test Links

Other Considerations

Sources and Inspiration

Specifications

These descriptions are derived from the Indie UI WG charter.

Indie UI: Events 1.0

A specification defining an abstraction between device-specific user interaction events and inferred user intent such as scroll, activate, etc. This provides an intermediate layer between device- and modality-specific user interaction events, and the basic user interface functionality used by Web applications. Indie UI: Events focuses on granular user interface interactions such as scrolling the view, canceling an action, changing the value of a user input widget, selecting a range, placing focus on an object, etc. Implementing platforms will take modality-specific user input, user idiosyncratic heuristics to determine the specific corresponding Indie UI event, and send that to the Web application (along with details of the modality-specific input such as mouse or keyboard events should applications wish to process it).

Indie UI: User Context 1.0

A specification defining a set of properties and methods related to the environmental context of a specific user, and a vehicle to access them to facilitate a Web application's ability to adapt to the user's needs. This is meant to provide information about whether a user is using a screen reader, screen magnifier, or other Assistive Technology, and to expose relevant user settings, allowing optimal adaptation of the Web application's user interface. This has important privacy implications because the information exposed may imply facts about the user's disability, which can be socially or legally problematic if misused. These issues are important to resolve and the group will consult with the Privacy Interest Group and Web Application Security Working Group to help ensure these issues are fully addressed.