Independent User Interface Task Force Teleconference -- 04 Sep 2013

<trackbot> Date: 04 September 2013

<janina> Meeting: IndieUI Task Force Teleconference

<janina> OK, Ted, thanks!

Two new staff members have joined W3C/WAI, based at MIT and Beihang University respectively.

preview agenda with items from two minutes

TPAC2013 http://www.w3.org/WAI/IndieUI/wiki/Meetings/TPAC2013

<jcraig> rewrote feature detection section based on feedback from DOM WG. https://dvcs.w3.org/hg/IndieUI/

<jcraig> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-events.html#feature-detection

Editor's Report

<jcraig> rewrote feature detection section based on feedback from DOM WG. https://dvcs.w3.org/hg/IndieUI/

<jcraig> https://dvcs.w3.org/hg/IndieUI/raw-file/default/src/indie-ui-events.html#feature-detection

The only edits since the last meeting relate to feature detection in the Events module, based on comments from the Web Applications wg. Object detection is now used.

<jcraig> https://www.w3.org/WAI/IndieUI/track/products/2

James reviews the issues list: secondary/contextual menu is the main feature noted as required for 1.0; media issues; mark request; various editorial issues; issue about activate requests, focus etc. 9 actions and 3 issues over-all.

Everything else can, he thinks, be postponed beyond 1.0.

Janina notes that we need to determine which features should be included in 1.0. We also need a second implementation.

<janina> ACTION: Janina to check with Mozilla and Blink re plans to implement IndieUI Events for CR exit timeline [recorded in http://www.w3.org/2013/09/04-indie-ui-minutes.html#action01]

<trackbot> Created ACTION-68 - Check with mozilla and blink re plans to implement indieui events for cr exit timeline [on Janina Sajka - due 2013-09-11].

James thinks the remaining features mentioned above in the issues list should be on the agenda for 1.0, but there may be additional missing features - he proposes a call for additional features so that the requirements for 1.0 can be finalized.

<jcraig> ACTION: jcraig to inform IndieUI list of remaining issues/actions for Events 1.0 and ask others to speak up if they need to add more. [recorded in http://www.w3.org/2013/09/04-indie-ui-minutes.html#action02]

<trackbot> Created ACTION-69 - Inform indieui list of remaining issues/actions for events 1.0 and ask others to speak up if they need to add more. [on James Craig - due 2013-09-11].

James raises the concern that some of the announcements associated with IndieUI are insufficiently specific about how the standards would work and how it would be implemented.

Some organizations, he notes, have expressed concerns about "accessibility-only" technologies and have a misimpression that IndieUI is such a technology; he notes that our work should not be so regarded and the documents need to reflect the broad benefits of the technologies.

Janina notes that we need to engage people whose engineering concerns are not related to accessibility. One way to address this would be in usage examples mentioned in announcements and other publicity related to the working group's activities.

<jcraig> The W3C Announcement was worded in lay terms: "For example, if a user wants to scroll down a page, they might use their finger on a touch screen, or click a scroll bar with a mouse, or use a scroll wheel, or say 'scroll down' with a voice command. With IndieUI, these are all sent to the Web app as simply: scroll down."

Rich notes that the new Events module makes applications more portable across platforms, and makes it easier to write code that moves responsibility for low-level event handling out of the Web application.

<jcraig> My argument is that this is a technical audience, so we need to reduce the implication that this is too "magical." I suggested the text, "For example, if a user wants to scroll down a page, they might use their finger on a touch screen, or click a scroll bar with a mouse, or use a scroll wheel, or say 'scroll down' with a voice command. When a web developer registers for an IndieUI scroll request event, these are all sent to the web app as a single type of

<jcraig> "scroll request" event that includes contextual information such as X/Y delta values."

Rich also notes benefits for automated testing of Web applications when IndieUI Events are implemented.

James notes issues with announcements and how minor changes could clarify the purpose of the work for potential implementors.

Janina suggests a discussion with Shawn Henry and EO.

James acknowledges that a few features may be perceived as assistive technology-related, notably point of regard focus.

Rich characterizes this as the platform's having a known location where it directs its operation - the point of regard can be used not just by keyboard interfaces but also eye-tracking software for example.

Janina summarizes: it's a common feature that arises in different types of interface, and this should be acknowledged.

<janina> ACTION: Janina to follow up with Shawn re edits to the way IndieUI is discussed in W3C materials [recorded in http://www.w3.org/2013/09/04-indie-ui-minutes.html#action03]

<trackbot> Created ACTION-70 - Follow up with shawn re edits to the way indieui is discussed in w3c materials [on Janina Sajka - due 2013-09-11].

Events Requirements Update http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements

Michael has consolidated the requirements and use cases, now separated in the document.

He notes that there are additional requirements inherent in the scenarios/use cases that should be documented (as requirements).

Action for everyone: review the requirements and use cases to identify additional requirements. Some requirements can be shared among the use cases.

<trackbot> Error finding 'for'. You can review and register nicknames at <http://www.w3.org/WAI/IndieUI/track/users>.

Janina observes the importance of requirements at the CR stage, where the need for each feature has to be documented and clearly articulated.

<janina> jason: We need to make sure all our events are noted as issues have associated requirements and are covered by scenarios and use cases, especially any that might be considered controversial

Michael concurs that events should be associated with requirements and use cases.

Janina observes that the requirements need to be ready by Last Call.

Michael accordingly suggests publishing a first public draft of requirements prior to Events last call.

This entails, Janina notes, publishing the requirements draft ahead of TPAC.

Events Testing Update

<janina> jason: Michael and I are in conversation about how to synthesize events for testing purposes

<janina> jason: Dialog continues, though Michael much occupied by ARIA and by WCAG2ICT the past two weeks

User Context Update

<janina> jason: Looked at ISO 24751 and note that many items there not currently covered in our reqs don't seem all that germane to use

<janina> jason: There are a few we might extract

<janina> jason: How does the wg wish to proceed?

<janina> jason: e.g. a weighting for context preferences

<janina> james: I should be able to get the doc, but can we point the group to a public copy of this, or is it always locked behind the paywall?

<janina> janina: Unaware of a publically referencable copy of 24751

<janina> jason: Also untagged PDF

<janina> janina: Don't believe we'll be looking to make any references to 24751, certainly not normative ones

<jcraig> Just to be clear, this would be related to IndieUI User Context, not IndieUI Events.

<richardschwerdtfeger> michael please unmute me

<richardschwerdtfeger> Michael, please unmute me

Janina notes the main concern is to coordinate vocabulary (in the need/preference profiles).

<janina> janina: Main concern will be to use terms consistently

<richardschwerdtfeger> I am not unmuted

<jcraig> janina, unmute Rich

Rich notes a proposal to establish a community group to foster the necessary coordination. There are additional items (for profile vocabularies) arising from educational communities.

<richardschwerdtfeger> http://www.imsglobal.org/apip/index.html

- DRAFT -

Independent User Interface Task Force Teleconference

04 Sep 2013

Attendees

Contents