See also: IRC log
<trackbot> Date: 02 April 2014
<janina> zakimMeeting: IndieUI Task Force Teleconference
Participants introduce themselves, with details of backgrounds (see previous minutes for most of these).
Andrew Larkin (accessibility at Comcast) gives his introduction, with particular interest in UI frameworks and Web design patterns in use at Comcast in relation with accessibility.
There's an open-source interaction framework under development and available in Github.
Andrew also has a background in writing polyfills.
<jcraig> github.com/comcast/xooie
<jcraig> https://github.com/comcast/xooie
<janina> ack ??P1
<janina> next item
Janina notes Australian eastern standard time will be in effect in two weeks, per regular meeting schedule.
James: added some editorial changes clarifying goals for Events - mentioning polyfills as a transitional arrangement. While working on UI controller/trigger ideas, UIValueChangeRequest has been temporarily removed.
Based on work undertaken in ARIA, syntax highlighting has been introduced into the spec. Comments from screen reader users are solicited, for example, some samples are divided into separate elements. James plans to introduce CSS 3 speech properties for speaking punctuation.
The main normative edit is to include media playback request events (play/pause/toggle/stop/next and previous track).
James notes that this capability is not accessibility-specific, but will be useful to a range of users (including those with access needs) while attracting wider interest.
Additional events may be wanted for forward/rewind cases as continuous events.
These media events could be candidates for polyfill creation.
No one in the working group finds these changes objectionable.
Andrew notes that he is reviewing the spec in relation to his use cases and will identify any additions/changes that may be desired.
<janina> next item
Michael regards the requirements as incomplete at present. Use cases and corresponding requirements need to be documented, and requirements not so far identified need to be added.
Responding to Janina, Michael considers the material nearly ready for publication to obtain public review, but an additional (complete) draft would need to be published before the Events spec advances.
Michael clarifies that a purportedly final requirements draft should be published prior to Last CAll.
James notes that it would be helpful (but not necessary) to have polyfills available prior to Last Call. He notes that polyfills are effective in detecting bugs in the spec.
Michael: if Last Call is 4 months away or longer, there is time for two rounds of Requirements review, otherwise not.
James would like to have at least one more public working draft before Last Call (to be released during the next few months). James thinks we should wait for real implementations before Last Call, in order to avoid returning to Last Call a second time.
Michael: proposes to publish Requirements in the near future, including requests for review of specific components, then turn attention to testing and implementations while preparing a further draft of Requirements.
Michael thinks there is only minor work required to prepare it for publication and there are already useful editorial notes in place.
Michael: suggests publishing a first working draft of Requirements sooner rather than later.
Janina proposes to send out a call for consensus to publish the draft, giving wg participants a week during which to review it in case of any issues that would delay publication.
Substantive changes requiring further discussion may be considered at the next meeting, subject to extending the call for consensus if necessary.
Janina inquires about the possibility of changing the meeting day (but not the time). Given the time zones involved and the availability of participants, this seems unlikely to be feasible, except a last resort possibility for Friday afternoon Boston time.
Janina notes TPAC 2014 and the possibility of scheduling a face to face meeting there.
Proposed week of 27 October, leaving IndieUI available to meet on Thursday/Friday.
Meeting concludes.
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: jasonjgw Inferring Scribes: jasonjgw Default Present: +1.215.518.aaaa, jcraig, +1.215.518.aabb, janina, jasonjgw, +1.215.518.aacc, kurosawa, Michael_Cooper, Andrew_Larkin, Rich_Schwerdtfeger Present: +1.215.518.aaaa jcraig +1.215.518.aabb janina jasonjgw +1.215.518.aacc kurosawa Michael_Cooper Andrew_Larkin Rich_Schwerdtfeger Regrets: Rich_Simpson Found Date: 02 Apr 2014 Guessing minutes URL: http://www.w3.org/2014/04/02-indie-ui-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]