See also: IRC log
<trackbot> Date: 13 March 2014
<janina> Meeting: HTML-A11Y Task Force Teleconference
<scribe> scribe: MarkS
JS: propose we skip next week
with the CSUN conference taking place.
... assuming that today's low attendance may be due to time
change.
[pinging various people]
JS: Chaals has announced that he
will not be able to attend HTML WG F2F
... Mark will be there focusing on Canvas
JB: Want to make sure that we are prepared for any issues that may be raised during the F2F in regards to a11y.
JS: They will be clearing all the bugs. Zero issues and zero at risk items
CS: They will not be clearing any 5.1 bugs. focus is on 5.0
JB: have we done the comprehensive check? Should we do a walk through now?
JS: Not sure what's at risk.
http://www.w3.org/html/wg/drafts/html/CR/
CS: no concerned about any of these
JF: A little concerned about details and summary
MS: Steve has been discussing the outline algorithm on the lists
JF: It's fantasy at this point
JS: It's not gonna happen if there are no implementations.
MS: details and summary
JS: we will have that covered in aria soon.
JF: we were using that as a solution for the removal of the summary attribute on tables
CS: have that well covered with
aria-describedby and aria-label, etc.
... think we should make it a work item for 5.1
JB: We don't have a workflow for keeping these on our radar.
JS: we have a 5.1 list.
... its linked in the agenda. probably need to update it and
look at it more frequently
JS: nothing to concern us here.
MS: Just David MacDonald's bug RE headshots. Steve has said he is working on this.
https://www.w3.org/2002/09/wbs/44061/media-a11y-tf-2/
Open for 7 days after CSUN so any interested members have time to fill out the survey
JB: should we send around timezone links since the dates in the survey are only good for 2 weeks?
MS: I will send around links to timeanddate.com that are adjusted to the future dates so they are accurate for when the group would start meeting, not during this daylight savings time limbo.
MS: The coordination team continues to make progress on the Exit Criteria. We are getting closer to reaching consensus. Good news is the implementation report is getting developed in parallel.
http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#hit-regions
MS: After reviewing the draft I proposed last week at our weekly teleconfernce, we came to agreement on a version of Hit Regions that could be reintegrated back into the L1 Spec.
...Jay Munro has already taken care of that.
...Rik may have identified a couple of additional issues which we will be discussing at our next meeting.
JS: Just wanted to say that after attending the last two meetings, I was impressed at seeing how well that group operates.
MS: They have all been great to work with.
JS: Steve will be giving us an update at CSUN. HTML chairs are expecting it.
MS: All of the bugs discussed in the last 3 months in both the TF and the Triage subteam have been processed according to the new directives we received from Paul last week.
...While reviewing all of those bugs, I created a wiki page that lists bugs I felt were left in an unresolved state and may require further work.
...Some are dependent on groups that are not currently active (media) or don't exist yet (aria sub teams)
https://www.w3.org/WAI/PF/HTML/wiki/Current_Bug_Triage_Issues
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13129
JF: summary attribute is obsolete. went to a vote.
JS: weren't we promised that
details and summary would cover this use case?
... and now that is at risk...
JB: assuming we are talking about
5.1 here. We can't make enough progress on this in reasonable
time.
... is there an angle we can pursue in 5.1 for this?
JF: the argument against summary
was the same they used against longdesc, hidden
metatdata.
... the fact that details/summary is at risk means we probably
need to follow up with this in 5.1 or we reverse the decision
to remove summary attribute and propose an extension spec
JS: we should go back in read the
decision. it would be easy to put summary back in. going back
into LC is a good time to do that.
... I am personally not for putting summary back in, since we
have good coverage by aria. But we do have options.
CS: If you're going to do something, an extension spec would be the way to do it. This bug isn't about that though. Its about accessible tables.
JB: the F2F could be a good time to address this with the WG.
JF: all of those interested in
this will be at CSUN. Should we have a sit down and talk about
this?
... could talk about this at the WCAG F2F
... look for techniques
JS: implementations are still there
CS: John, can you put something together?
JF: yes, probably a working breakfast, maybe thursday