HTML Accessibility TF - Minutes for 2015-02-05

HTML:
http://www.w3.org/2015/02/05-html-a11y-minutes.html

Text:


   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

              HTML Accessibility Task Force Teleconference

05 Feb 2015

   See also: [2]IRC log

      [2] http://www.w3.org/2015/02/05-html-a11y-irc

Attendees

   Present
          chaals1, janina, ShaneM, JF, Joanmarie_Diggs,
          +1.617.319.aaaa, MarkS, LJWatson, Adrian_Roselli, IanP,
          Chaals, Cynthia_Shelly, David_MacDonald,
          Rich_Schwerdtfeger

   Regrets
   Chair
          Chaals

   Scribe
          MarkS

Contents

     * [3]Topics
         1. [4]Any other items for the agenda?
         2. [5]Transcripts
         3. [6]Action item review -
            https://www.w3.org/WAI/PF/HTML/track/actions/open
         4. [7]Proposed Work Items -
            http://www.w3.org/WAI/PF/html-task-force ,
            http://www.w3.org/WAI/PF/HTML/wiki/51wishlist
         5. [8]Web Payments work (chaals)
         6. [9]face to face meetings
     * [10]Summary of Action Items
     __________________________________________________________

   <trackbot> Date: 05 February 2015

   <scribe> scribe: MarkS

Any other items for the agenda?

Transcripts

   <JF> [11]Use cases and stuff for a transcript element,
   attributeā€¦

     [11] https://www.w3.org/html/wg/wiki/ISSUE-194/TranscriptElement

   JF: Back before plan 2014, Media sub team did work on this.
   quite a bit
   ... Syliva Pfeiffer, chaals, janina and I met a number of times
   to iron out a proposal. we ended up with transcript element and
   transcript attribute
   ... apple wanted to have the link visible on page
   ... put together a change proposal, never had a decision from
   chairs
   ... probably our best place to start
   ... 4 different use cases and examples in the wild
   ... satisfies all of the req in the Media Accessibility User
   Requirements doc
   ... video element would take transcript attribute which would
   take an ID
   ... the the transcript attribute would point to transcript
   element
   ... this should satisfy apple's requirements
   ... its very complete. should be a great place to start.
   includes use cases
   ... if we can get wider review from this group, we should be
   able to start an extension spec

   CN: I would encourage everyone to look at the use cases and
   reqs stuff very carefully. We should be clear that these are
   right

   JF: I think we spent at least 5-6 hours working collaboratively
   on this.
   ... its very comprehensive

Action item review -
[12]https://www.w3.org/WAI/PF/HTML/track/actions/open

     [12] https://www.w3.org/WAI/PF/HTML/track/actions/open

   <chaals> close action-300

   <trackbot> Closed action-300.

   CN: we can close JF's action item

   <chaals> action-298

   <trackbot> action-298 -- Charles McCathie Nevile to Set the
   focus management discussion up in html wg -- due 2015-01-22 --
   OPEN

   <trackbot> [13]http://www.w3.org/WAI/PF/HTML/track/actions/298

     [13] http://www.w3.org/WAI/PF/HTML/track/actions/298

   CN: 298, is still open

   JF: you can close 301

   CN: Shane alt doc changes, do you want to put that on agenda

   SM: not this week, lets do it next week

   CN: Coordinate with WCAG chairs. I've contacted them

   SM: you can close 302

   CN: 303 is due in a week then

   <chaals> action-303 due in 1 week

   <trackbot> Set action-303 Present alt doc changes due date to
   2015-02-12.

   <chaals> close action-302

   <trackbot> Closed action-302.

   <chaals> close action-304

   <trackbot> Closed action-304.

Proposed Work Items - [14]http://www.w3.org/WAI/PF/html-task-force ,
[15]http://www.w3.org/WAI/PF/HTML/wiki/51wishlist

     [14] http://www.w3.org/WAI/PF/html-task-force
     [15] http://www.w3.org/WAI/PF/HTML/wiki/51wishlist

   CN: looking to finalize our work items
   ... should be accurate for at least the next 6 months (or until
   completion)
   ... possible to take on new work as well
   ... we've been working from the wishlist
   ... in about a week, I would hope to have a call for consensus
   on our work items
   ... it will be in a wiki page.
   ... make it easier to keep it up to date

   LW: i picked up the date picker stuff from last week

   <LJWatson> [16]http://www.w3.org/WAI/PF/HTML/wiki/Datepickers

     [16] http://www.w3.org/WAI/PF/HTML/wiki/Datepickers

   CN: cyns, are you going to do menu work, slated for this summer

   CS: Fall is actually more likely
   ... i will look at it this summer, but it will take longer to
   complete the work

   CN: we're trying to keep the work statement accurate. we may
   not want to put it on there now. we are putting work items on
   wiki, so it will be easier to keep up to date
   ... may want to hold off putting it on there until later then.
   ... any more on work item/statement stuff

   LW: I talked to brian kardell about moving panel work into this
   space.

Web Payments work (chaals)

   CN: this is something we should keep an eye on. I have a task
   to get more info on this work
   ... there was a workshop on this yesterday
   ... there are some documents around that people can
   review.links:

   <chaals> [17]CG use cases - being provided to the IG as input

     [17] http://opencreds.org/specs/source/use-cases/

   CN: one of the things that the payments group is doing is that
   they want to make sure they meet accessibility requirements
   ... think PF may want to keep an open dialog with this group

   <chaals> [18]Use cases for payment

     [18] https://dvcs.w3.org/hg/webpayments/raw-file/default/latest/use-cases/index.html

   CN: they are also clear that they don't want to do this only in
   their own tiny space, they want to open it up to other experts
   from other groups, like HTML, a11y ,etc

   <chaals> s|->
   [19]http://opencreds.org/specs/source/use-cases/ CG use cases -
   being provided to the IG as input||

     [19] http://opencreds.org/specs/source/use-cases/

   CN: they have a draft document of use cases. I thought it was
   hard to understand as a non-web-payments person. the minutiae
   of the web payments system
   ... hoping it will become more clear
   ... there are many issues in the use cases that are not HTML
   specific, but interesting nonetheless (from and a11y
   perspective)
   ... its a complex and important space

   <Zakim> ShaneM, you wanted to mention my (notional) involvement
   in web payments

   SM: I just wanted to say that I have been monitoring this and
   credentialing work. I will be ramping up my activity in web
   payments, so I will keep a close eye on this.

   JF: shane answered my question. I was hoping we had people
   dedicated to this. I know chaals, katie haritos shea and now
   shane, so that's good

   CN: The chair of the group, david E is not someone many of us
   know, but he is interested in supporting a11y. technical guy.

face to face meetings

   CN: waiting for decisions from HTML and WebApps. seems like
   HTML group will meet in Redmond
   ... if you are going to that meeting, good. it will be HTML
   focused, but encourage a11y reps to attend if they can.
   ... proposed dates are 13-17 of april
   ... informal note. if anyone is going to CSUN, the SVG a11y
   people are going to try to get together to do some technical
   work
   ... RS will know more

   RS: yes.
   ... Tuesday night

   CN: meeting adjourned

   <chaals> [adjourned]

Summary of Action Items

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [20]scribe.perl version
    1.140 ([21]CVS log)
    $Date: 2015-02-05 16:35:15 $
     __________________________________________________________

     [20] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [21] http://dev.w3.org/cvsweb/2002/scribe/

Scribe.perl diagnostic output

   [Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30
Check for newer version at [22]http://dev.w3.org/cvsweb/~checkout~/2002/
scribe/

     [22] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s|[23]https://www.w3.org/html/wg/wiki/ISSUE-194/TranscriptEle
ment|-> [24]https://www.w3.org/html/wg/wiki/ISSUE-194/TranscriptElement
Use cases and stuff for a transcript element, attributeā€¦|
Succeeded: s/element/attribute/
Succeeded: s/sins/cyns/
FAILED: s|-> [25]http://opencreds.org/specs/source/use-cases/ CG use cas
es - being provided to the IG as input||
Found Scribe: MarkS
Inferring ScribeNick: MarkS
Default Present: chaals1, janina, ShaneM, JF, Joanmarie_Diggs, +1.617.31
9.aaaa, MarkS, LJWatson, Adrian_Roselli, IanP, Chaals, Cynthia_Shelly, D
avid_MacDonald, Rich_Schwerdtfeger
Present: chaals1 janina ShaneM JF Joanmarie_Diggs +1.617.319.aaaa MarkS
LJWatson Adrian_Roselli IanP Chaals Cynthia_Shelly David_MacDonald Rich_
Schwerdtfeger
Found Date: 05 Feb 2015
Guessing minutes URL: [26]http://www.w3.org/2015/02/05-html-a11y-minutes
.html
People with action items:

     [23] https://www.w3.org/html/wg/wiki/ISSUE-194/TranscriptElement
     [24] https://www.w3.org/html/wg/wiki/ISSUE-194/TranscriptElement
     [25] http://opencreds.org/specs/source/use-cases/
     [26] http://www.w3.org/2015/02/05-html-a11y-minutes.html


   [End of [27]scribe.perl diagnostic output]

     [27] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm

Received on Thursday, 5 February 2015 16:39:07 UTC