HTML Accessibility Task Force Teleconference -- 04 Dec 2014

<trackbot> Date: 04 December 2014

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

<scribe> scribe: JF

Image Description (Longdesc) Update

<janina> http://www.w3.org/TR/html-longdesc/

JS: likely not yet announced, but Image Description is now Proposed Rec at URL posted

HTML Modularization; e.g. https://specs.webplatform.org/html-aria/webspecs/master/

JS: asking about what this document is. Looks like an excerpt from HTML5 / ARIA content

thanking Steve F for attending for clarification

curious to understand how, what, were, why?

i.e. how do we understand this and contribute to this?

JS: Perhaps SAm (who is on call) may want to go first

SR: yes, this now makes Last Call optional, but it is in experimentation mode, so there remains some open questions, but essentially the same procss minus Last CAll

JS: note that it is on a different site, curious of impact on that

SR: This is very much an experiment, so it is not clear what things may bring

SF: this is essentially an unofficial editors document
... for this to become a WG deliverable, at that time there may be more process added

<rubys> https://github.com/webspecs/url/blob/develop/docs/workmode.md#preface

SR: this outlines how we may apply a process to this. circulating the above proposal and soliciting feedback

SF: through discussions at TPAC and prior, looking at something to start the modularization process roling

one item here is that there is very little dependancies here, making it an easy place to start

SF: another point is that it defines certain mapping requirements - those requirements are removed from this new document, as they are defined elsewhere
... this may not yet be very clear, as this is a very early rough draft - still working things out, including getting to know the system - very much a work in progress

SR: agree, work in progress - seeking feedback. Timing now however is good to start looking at this as an alternative

JS: can almost predict that with HTML5.0 being finished, it is a good time to start rethinking things and proposing new ideas
... if I am to understand steve, this makes it easier to break out this

SR: definately different definition than xhtml modularization currently understood. rather it is about multi-thread authoring
... different contributors working at different speeds

JB: a few questions
... know that PFWG worked hard to have ARIA integrated into HTML spec
... curious if the reasoning for that has changed
... second question - seeing a lot of new work on ARIA in PF, and it is still easy for things to get fragmented. Will this approach undue that integration?
... third question - question around current copyright statement there - may not match how ARIA is currently published
... that may be easy to iron out via email, but first two questions I'm more hoping for discussion on here

SR: First, this is very different kind of modularization - recognizes HTML5 as an umbrella spec
... reminder as well that this is an exploration by STeve - no decision has been made, this is just an exploration

JB: want to circle back - given that ARIA is coming from PF, shouldn't this be a jont effort?

SF: the work in the HTML5 specification happened inside of that WG - with contributions from many of the same actors

but the work happened in the HTML WG

Currently the HTML spec has embedded in it a note that there are certain dependancies/requiremenst for ARIA implementation and the spec points back to the WAI-ARIA spec

so actual implementation requirements are the only requirements in the document, likely bvelong in the mapping specification

that specification is jointly published by PF and HTML WGs

<janina> Doing pretty well, JF, thanks!

SF: in the general sense, it is not just this part of the spec taht is being pulled out, but rather the start of a proces to pull out a lot of the pieces out to allow them to be worked on asyncronously
... re: copyright issue - that should be something that Robin could better respond to when he returns (he is out for unspecified time)
... however based on some earlier discussion, believes that the copyright issue is not an issue

JS: want to note that some may disagree that ARIA was developed in the HTML WG

there is a lot more nuance there

SF: the content used in the HTML spec, has been edited as part of the HTML spec, so if there is a bug there it comes through the HTMLW G bug system

JS: yes, however there is a history.
... one question is, wouldn't it make sense to label the web-platform doc that it is an experiment, so that it is clear what is happening?

just a suggestion to clarify that

SF: yes - again, that is being coordinated

being driven by folks like Robin B and Mike S

<Zakim> janina, you wanted to say others may disagree whether ARIA was developed first in PF or HTML

SF: looking for the document that outlines the thinking behind this

PLH: the whole webplatform effort is very much a work in progress

<SteveF> https://specs.webplatform.org/docs/

believe that folks like Robin will take all suggestions - feels like trying to frame a moving effort. Providing feedback encouraged, but we don't want to box things in too much as it is very fluid now

SF: agree that adding some "experimental language" notice would make sense
... there is content being added all the time - a work in progress

JS: are there other little pieces of HTML5 that are in process that may drift over to webplatform.org

SF: haven't started yet, but looking to move all the elements work over there

looking to improve author conformance and author advice. This will be a much larger work-effort here, and not suggesting that there will be a lot of changes

but it is looking at a better presentation - it will be more developer/author-centric in the explanation and presentation

SF: so it will be a "style" change as much
... that will start to emerge over the next couple of months

what I've been trying is using ARIA as the test experiment now

SR: notice a lot of process problems, and this is an attempt to address some of those issues

<Zakim> liam, you wanted to note we're on www.w3.org now

Alt Note Status; Shane and Liam

<liam> [longdesc now on www.w3.org homepage]

<SteveF> JF: minutes look fine - thanks!

SM: STeve and I will be filing bugs as we go - slight delay due to US Holiday
... it is an ongoing process

Media Subteam Update -- Janina, John, Shane

JS: just received some new comments from BBC this week. next meeting is next monday, and we will look at them at that time

goal is to get MAUR published as a W3C NOte

good to have solid implementor feedback

JS: want to note that when PF met with Web and TV IG, we had a request for some best practices implementation
... so hope to follow up on that with BBC. There was interest in Clean Audio

Ian P: Clean Audio came out of BBC R&D - will attempt to get more feedback and will report back next week

JS: Nigel is participating in the media sub-team, so we can follow up directly with him
... hoping to get all comment feedback out over the next few weeks. May delay a bit, but no more than a month - perhaps publish by end of January

Canvas 2D Update -- Mark

JS: defer since MarkS sent regrets

Transcript Update -- John

JS: believe I know the story, but please go

<janina> < janina> scribe: janina

<janina> < janina> jf: Transcript was left unresolved in 5.0; We don't have a programatic way to associate a transcript with media

<janina> < janina> jf: It remains on us in the TF

<janina> < janina> jf: We do have a couple proposals, include an element, or an attribute, and a one other -- not recalling at the moment

<janina> < joanie> janina: wrong channel

<janina> < janina> jf: Work will now move forward in the Media Subteam after the MAUR closes

TF Work Items (HTML.Next)

JS: Chaals is not here - no other work in progress that requires any update. Chaals is working on accesskey

Other Business

JS: however both JS and Chaals will not be available next Thursday - asking Liam to chair that call, but there is a possibility that the meeting may be cancelled if Liam cannot take the baton

- DRAFT -

HTML Accessibility Task Force Teleconference

04 Dec 2014

Attendees

Contents