HTML Accessibility Task Force Teleconference -- 21 Aug 2014

<trackbot> Date: 21 August 2014

<janina> Meeting: HTML-A11Y Task Force Teleconference

Identify Scribe http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List

<scribe> scribe: David

JB: Change agenda to delay formal Obj.
... to allow others to join regarding LongD

LW: Bug triage... time has come for stepping down as Bug Triage facilitator

JS: Thanks for a job fabulously done, helped accessibility in spec a lot

LW: Congratulates other participants in BTriage
... It's a good time to consider closing... since it's quiet
... May need it later

Longdesc

JS: Look at implementation report, we have new implementers, who's just joined
... Received formal obj. from apple late yesterday
... Point of CR is to get implementations

JB: i'm very interested in seeing what's necessary on timeline. i want to handle process considerations, to get TF opinion to move forward

JS: Implementation report

<plh> http://w3c.github.io/test-results/html-longdesc/cr-report.html

JS: Charles will walk though implementation report

CM: Will add header and footer... doc shows that requirements by 4 user agents are met by more than 2 Ua for each requireme t... essentially demonstrates people can implement it and get it right

we haven't put in every permutation because not required... if people implement it without talking to each other they'll get it right

JS: Does group agree with Charles position that if people implement it without talking to each other they'll get it right

Phillippe: Director doesn't need format perfect and this Implementation report is better than many others

RS: Are there links to the tests

CM: Yes

Rs: Sounds like you've got it
... does implen. reoort include two major broawers

CM: Yes

RS: don't need any more

JS: an
... Any reason one API

CM: there are two APIs ... DOM and UA

JS: let's wrap it up... the report is sufficient to clear CR... no challenges here in group

S/UA/MSAA

Joanie: points out you also have ATK/AT-SPI2

JS: Let's add that to table

RS: how is it exposed in MSAA?

Cynthia: In IE: URL that LD points to is a String in ACCDESC

<joanie> https://git.gnome.org/browse/orca/commit/?id=f190cabcd786e80e24c73da5381d623f14d268a5

<joanie> there's your results

<scribe> ACTION: Charles and Joanie to sync to add her tests to implementation report [recorded in http://www.w3.org/2014/08/21-html-a11y-minutes.html#action01]

<trackbot> Created ACTION-280 - And joanie to sync to add her tests to implementation report [on Charles McCathie Nevile - due 2014-08-28].

CW: you can put any Screen reader on the planet except VO on a web page with this and they can get it

Orca implementation with Joanie

<janina> https://git.gnome.org/browse/orca/commit/?id=f190cabcd

Joanie: I thought what I sent was our proposal, worthy of consideration... some is already done properly by GECKO,

JB: are they nice to have or critical

<joanie> http://lists.w3.org/Archives/Public/public-html-a11y/2014Aug/0029.html

JS: can we walk through them

Joanie: I don't think it should be the only way be LD, if ebook user offline should be able to get it
... (reading through issue in list from url http://lists.w3.org/Archives/Public/public-html-a11y/2014Aug/0029.html

CM: we tried to avoid generalities i the spec on UA, my pushback would be it's not things specifically limited to longdesc

Joanie: Why does it say UA must make link available to all users... they include keyboard users also... why not take that text out...

JF: Joanie, we can't tell authors what they must and must not do... i agree feedback for autnors is useful, we've never said LD is THE sloution... it ks A solution... Should could go to WCAG

<MarkS> +1 to onus of testing and usability on author

JF: we have this problem with other thinks like link... don't want to over manipulate authors... bottom line... no revisions to author section

<janina> ack ??P

JB: are the changes requested normative or informative

Joanie: Not going to block anything

JB: asking because it changes how we treat the comments, and address them
... LD not be all and end all, we are looking to develop additional things in the future.

JS: need to discuss further on list.

CM: if we don't make these changes will LD not work, will it be worse... or are prososals just going to improve that we can add at a later date... lets frameit like that

Formal Objection from Apple

<janina> http://lists.w3.org/Archives/Public/public-html-admin/2014Aug/0031.html

<MarkS> http://lists.w3.org/Archives/Public/public-html-a11y/2014Aug/0028.html

JB: trying to determine kf they are new arguments or not... didn't see any new ones... but there are specific requests at the end... TF needs to look at them and see how to advise the co-facilitators to address this

JS: next action when and how much time do we need for CFC, need to look a Joanie's feedback and Apples Formal Obj.

Joanie: My stuff can be informative

CM: anything in FA unaddressed prevviously and
... any new issues? that is the critical question

JB: can Facilitators come out with cfcs?

<scribe> ACTION: Janina and Charles to work with facilitators to move questions discussed her forward [recorded in http://www.w3.org/2014/08/21-html-a11y-minutes.html#action02]

<trackbot> Created ACTION-281 - And charles to work with facilitators to move questions discussed her forward [on Janina Sajka - due 2014-08-28].

<MarkS> +1 to joanie

JS: to Joanie, was it hard to implement Longdesc?

Joanie: Actually it was easy!

- DRAFT -

HTML Accessibility Task Force Teleconference

21 Aug 2014

Attendees

Contents

Identify Scribe http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List

Longdesc

Orca implementation with Joanie

Formal Objection from Apple

Summary of Action Items

Scribe.perl diagnostic output