Draft Minutes of IndieUI Teleconference 17 October 2012

Draft minutes are at

http://www.w3.org/2012/10/17-indie-ui-minutes.html

and below.

cy'all in Lyon.

andy


   - DRAFT -


   Independent User Interface Task Force Teleconference


     17 Oct 2012

Agenda
<http://lists.w3.org/Archives/Public/public-indie-ui/2012Oct/0012.html>

See also: IRC log <http://www.w3.org/2012/10/17-indie-ui-irc>


     Attendees

Present
     Michael_Cooper, Janina, Shawn, hober, jcraig, Andy_Heath,
     Joseph_Scheuhammer, Rich_Schwerdtfeger, Caroline, Doug_Schepers, Cooper
Regrets
Chair
     Janina_Sajka
Scribe
     andy


     Contents

   * Topics <#agenda>
      1. IndieUI Overview Page
 
http://lists.w3.org/Archives/Public/public-indie-ui/2012Oct/0006.html
         <#item01>
      2. TPAC http://www.w3.org/WAI/IndieUI/wiki/Meetings/TPAC2012 <#item02>
   * Summary of Action Items <#ActionSummary>

------------------------------------------------------------------------

<trackbot> Date: 17 October 2012

<janina> trackbot, start meeting

<trackbot> Meeting: Independent User Interface Task Force Teleconference

<trackbot> Date: 17 October 2012

<janina> Meeting: IndieUI Task Force telecon

<janina> scribe: andy


       IndieUI Overview Page
       http://lists.w3.org/Archives/Public/public-indie-ui/2012Oct/0006.html
 
<http://lists.w3.org/Archives/Public/public-indie-ui/2012Oct/0006.html>

Janina: item item 1

Sean didn't follow up with twekas

will review what the tweaks are

ty josep

Sean: first two changes are

<shawn> Indie UI: User Context will allow a web application to get
information about the configuration, settings, and assistive
technologies that the user is using.

main one - sentence says (divert to Shawn)

andy+

andy q_

<shawn> Indie UI: User Context will allow a web application to get
information about the configuration, settings, and assistive
technologies that the user is using. This will facilitate a web
application optimizing for specific user needs. There are significant
privacy and security issues that need to be resolved.

<Zakim> jcraig, you wanted to mention privacy

<jcraig> Andy: mentioned user needs

andy"user needs as well

<shawn> SLH: Suggest this is clear overview for now. And when we know
more, we can modify it

<clown> Indie UI: User Context will allow a web application to get
information about the configuration, settings, and assistive
technologies that the user is using. This will facilitate a web
application optimizing for specific user needs. There are significant
privacy and security issues that need to be resolved.

<clown> repasted richardschwerdtfeger ^

discussion of whether user needs should be included in the User Context
sentence

Accepted Caroline's mods

<Zakim> Joseph_Scheuhammer, you wanted to make one small change: user
needs and preference.

Joseph: add preferences to user needs

andy: "preferences" can be seen as trivial

<Zakim> jcraig, you wanted to express concern that making this interface
too complicated could prevent adoption

jcraig: the distinction between needs and preferences makes it
needlessly complex

decision: leave the wording as User Context will allow a web application
to get information about the configuration, settings, and assistive
technologies that the user is using. This will facilitate a web
application optimizing for specific user needs. There are significant
privacy and security issues that need to be resolved.

should we change the word scroll to zoom in the example for the overview
page

<clown> added scroll wheel to: 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. Indie UI will define a way for those different
interactions to be translated into a simple event - scroll down.

<shawn> examples in http://www.w3.org/WAI/intro/indieui

decision: leave as scroll

exit Shawn with thanks

<jcraig> jc: difference between user's needs and preferences is trivial
from an API perspective. No developer that actively ignores a
"preference" will be persuaded to respect a "need." Ex. minimum font size.


       TPAC http://www.w3.org/WAI/IndieUI/wiki/Meetings/TPAC2012

TPAC: Gottfried Zimmermann has asked to come as observer and present

agreed

TPAC Agenda - get past use cases

janina: TPAC is precious time
... get through the use cases

james: wants time to clarify how the event model works technically
... last day - work thtourgh whats missing to get a PWD out asap after tpac

janina: in case we need to recharter after the web events and pointer
events groups changes

jannina: need to show a continuing need for this geoup

s/geop/group/

janina: start thursday use cases,gottfried Friday morning, Friday pm
look for gaps

s/gpttfroend/gottfried/

rich: focus on developer-dependent stuff

rich will lead use case walk-through

rich: avoid repetition of technical issues across use cases

james: some things in the use cases already covered by click
... zoom, rotate as proposed as simplistic

<jcraig> jc: proposed as discrete notifications, but we need more for
items as complex as zoom and rotate.

janina: james - can we have editors report pls

james: everything in action 5 been dealt with

going through Rich and Andy's proposal

will be done by tpac

james: michael has alerted us to a place for source files

<jcraig> http://dvcs.w3.org/hg/IndieUI/raw-file/tip/src/events.html

<jcraig>
http://dvcs.w3.org/hg/IndieUI/raw-file/tip/src/user_context.html
<http://dvcs.w3.org/hg/IndieUI/raw-file/tip/src/user_context.html>

janina: will put them in the resources isection in future agendas

no table of contents yet

michael - when you load a file it will generate a TC

michael/james - ReSpec inclusion to be straightened out - will fix

Use Case Walkthrough

<clown> http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements
<http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements>

<janina> http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements
<http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements>

<richardschwerdtfeger>
http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements#S6:_Command_move_the_focus_point_within_a_UI_component_down_to_the_next_item_within_a_UI_component
<http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements#S6:_Command_move_the_focus_point_within_a_UI_component_down_to_the_next_item_within_a_UI_component>

Rich start at S6 - discussion of next item/previous item

Rich: could a command from the browser indicate direction
... could be done with a parameter
... component would receive and know the direction

james: next and previous should only be used when the AT knows which the
next and previous are but that's only a nitification
... next and prev should be separate from direction

left is not previous

broad discussion of this

notification of start navigation and end navigation important

have logical previous and next

james even a grid can be done with changing focus events

rich: iOS does it with key events

james: cannot pass navigation up to the web app because its too slow
... except where there is no next item to move to (e.g. because it needs
re-rendering)
... in a next/prev event request the AT sends the notification to the
web app then waits to see if its cancelled or not
... that is slower than handling it locally and detecting the change of
focus on the device

in other modalities we may not have a keypress

table this one for f2f

needs one hour at TPAC


     Summary of Action Items

[End of minutes]


Cheers

andy
-- 
__________________
Andy Heath
http://axelafa.com

Received on Wednesday, 17 October 2012 18:11:32 UTC