HTML Accessibility Task Force Teleconference -- 18 Jun 2015

<trackbot> Date: 18 June 2015

<paulc> I get a "Connecting" icon. Has the meeting started?

<chaals> s/I get a "Connecting" icon. Has the meeting started?//

John, We're starting the call ...

There's also direct dial: +1.617.324.0000

<paulc> If Janina is here I would like an update on https://lists.w3.org/Archives/Public/public-html-admin/2015Jun/0014.html

<scribe> scribe: janina

face to face meeting in Zaragoza - https://www.w3.org/WAI/PF/HTML/wiki/Meetings/HAT2015-zaragoza

CMN: chaals has created a registration page -- Chaals and Steve registered so far

… Free accomodations are available

alternative text guidance status?

No Liam or Shane today. So deferred.

There are related bugs dependent on this draft.

Chaals, proposes we set this task aside pending to be continued however HTML decides to work going forward

Paul: Won't that delay even further

<chaals> JS: Understand from Shane that there is activity on that expected from Liam.

<chaals> JB: Liam is out this morning so cannot report on that.

Paul: Perhaps we should ask for a written report on this?

Judy: Have done, and will followup

canvas 2D

PLH: We have a CR draft -- close to LC except for 2 typos
... We have left over bugs

<paulc> HTML WG CfC

PLH: Have closed the bugs because no longer relevant
... Look at the "Won't Fix" to see them
... End of CR will be July 26
... We have identified what's missing -- tests to write and run

Chaals: Do we expect they'll pass?

Paul: That's what CR is for!

Rich: We don't expect the spec would change

transcript draft - https://github.com/chaals/html-transcript

Chaals: Have substantially updated in the past day
... Draft shows what tech solutions for transcript
... Shows problems using src:
... Would like to formally get this adopted as a TF work item
... Proposes to run a CfC on this question

Paul: Wondering where to look for how this proposal relates to old issues on the question of a transcript

Chaals: Pointer to the Wiki, which references, but we need to aded that kind of material
... Also, we need to add Use Cases and Requirements

Paul: Encourages this

Chaals: To restate the obvious, this needs to come from HTML Media eventually, but we can move this forward in the meantime.

<chaals> JS: Do we intend this becomes a task force extension, or hand it over?

<paulc> Would the best forum for this work be the proposed ICG?

Janina: Wonders who ends up owning and publishing this spec?

Paul: Should it be in the Incubator CC?

Chaals: Happily deferring the question of whether extension spec, who owns, etc

PLH: Think it's good to shop this around for now

<Zakim> JF, you wanted to say where it lives is less important than the fact we keep moving forward with this

jf: An important question, but most important that we not lose this feature

Bug Triage status

Leonie: Met past Friday
... Need to understand how we make changes in the HTML spec before we can close a number of the bugs

SF: Much of the problem is the WHAT content being auto imported into 5.1
... Also the pending modularizaion of the spec docs

<paulc> Wouldn't the best plan be to add the proposed solution text to each bug and then later we can figure out how to actually make the changes.

Chaals: Believe that's what we're doing with the bugs

Paul: If these are 5.0 bugs -- Any thoughts for errata?

sf: The process for errata is up in the air -- even for spelling errors

<Zakim> chaals, you wanted to say yes… and to

Date pickers

Chaals: So, good progress, but blocked on how we actually accomplish the edits
... Stuck
... Have proposed this as an item for the F2F
... I'm interested to own this item, but even more interested in offers from others to do so

PLH: i18n is one of the main issues

<chaals> JS: Seems you could do a lot of things if people agreed on a simple ISO interchange…

<paulc> How close is this to the work of the Editing TF?

PLH: Styling is another concern

<chaals> PLH: The goal is to provide a UI, too, and that doesn't work. A major problem is stylability - if you can't style them people don't want to use them.

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

Leonie: Collecting info

plh: Web componants possible approach

Chaals: A lot of consensus on the problems, but not on solutions

HTML plan

plh: Most recent proposal was a split of HTML and Webapps several groups
... No particular set of details solves all concerns
... However, idea is to merge with Web Apps
... So Would be Web Apps WG and a Media WG
... Also discussion of splitting the HTML spec document itself
... Proposal is a 12-month charter to see how the new arrangement works
... Merging avoids duplicated overhead
... We have 4 proposed Co-Chairs
... Also to have 3 team contacts
... We're increasingly comfortable using github
... We're working on set of tools to help groups track work in github
... Notes it's possible to get github to update via email, even to the extent that it behaves much like an email list
... Notes underlying pipeline for media support is an important work item
... Current HTML to be extended by 3 months while the above is under consideration
... Would allow for completing Canvas 2D and DOM4

Chaals: One obvious question is what happens to this TF if the HTML-WG goes away
... At the moment, we don't know
... Notes that Web Apps work approach is different from HTML
... Organizes informally around particular spec docs

<richardschwerdtfeger> +1

Chaals: Believes it's an a11y friendly environment up front

<LJWatson> +1 to Chaals.

Chaals: Notes that TF Chairs have just begun discussion on how things might work
... Good news is that trust and communications are not the concerns
... Am confident that we can develop a solution that accomodates different styles of participants

plh: Noting preferences for telecons, f2f, email, github --- a challenge
... Has noted that people have sometimes not known how to review/evaluate Web Apps specs -- how do they fit together?
... Encourages discussion on how to deal with the complexities

Rich: What's the tie in with CSS?

plh: Using CSS to illustrate spec complexity

Rich: We have problems with things like Flexbox, Content injection, etc in CSS

plh: Believe CSS-WG willing to address issues

Chaals: Out of scope for this meeting

Paul: This TF a bridge between HTML and PF
... There are explicit mentions of PF relations in the new charter; PF should review the proposed Charter
... Notes some specs copublished with PF

<chaals> proposed super group charter

new process for documents?

<chaals> JS: expect to run a CfC and get a positive answer in about aweek

Paul: It's one thing to put things in the new process, and something else to go automated

<chaals> PLH: we are looking at putting notes onto the automatic publishing train.

- DRAFT -

HTML Accessibility Task Force Teleconference

18 Jun 2015

Attendees

Contents