See also: IRC log
LW: Welcome to joseph and adrian.
[introductions]
LW: this task force keeps an eye on bugs that are filed against HTML5 and 5.1 specs that involve accessibility
...discuss new bugs on this call each week. Those that are worth the TF to champion and pursue we will bring it to the TF and assign it to a TF member.
...these meetings are informal, look at bugs, discuss them from varying angles.
...collectively, we usually have an opinion on most things. Sometimes we are at a loss and we bring it to the TF for their feedback.
...with regard to 5.0 and 5.1 specs, things are fairly quiet at this time. During certain stages in the publication process, things can get much busier.
LW: how does this time work for everyone?
[discussion - not ideal but there aren't many other options considering our locations]
AR: because of my work schedule, there will be times when I won't be able to make a meeting.
...what is protocol for regrets.
LW: email the bug triage list with regrets.
MC: there are formalities for limiting a person's right to vote if they haven't been around for awhile. The TF isn't very formal and we are happy to have you when you can make it.
LW: most of us work full time and won't be able to make every meeting.
LW: one member of the team typically keeps an eye on new bugs filed since last meeting and emails the group prior to the meeting.
...hans hillen has played this role in the past but will not be able to continue.
... we will need someone to replace him in that role.
... hans has had a filter query that he runs through bugzilla search.
... emails the bug triage list with a brief summary regarding why it was possibly tagged.
MC: working on the bug triage sub-team requires working knowledge of bugzilla.
...there are a number of keywords we use for tracking: 'a11y' means somebody thinks the bug is accessibility related.
...'a11ytf' means the TF has formally decided to track the bug and work on its resolution. this is usually added to a11y. normally someone from TF will add this keyword.
<LJWatson> The different keywords are described here: https://www.w3.org/Bugs/Public/describekeywords.cgi
...keywords for 'media'
LW: goes through all of the bugs that have been filed and will add the a11y keyword, emails the list around, then we discuss the implications during our call.
...add a11ytf keyword to those which are worthy of the TF involvement.
<LJWatson> https://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&chfieldfrom=-2w&chfieldto=Now&chfield=[Bug+creation]
...is anyone interested in taking up this responsibility?
... ok i can reach out to JF or ST
LW: The last report was on May 8th. so lets start working through these.
<LJWatson> https://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&chfieldfrom=-3w&chfieldto=Now&chfield=[Bug+creation]
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21971
MC: going to go through this quickly by reading the bug ID. I will paste the URL into the minutes. Unless we need to look more closely, we can just move on.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21977
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21985
... 21971: filed on the spec itself
... 21985: already tagged as a11yTF by RS himself.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21987
CN: 21987 is mine and I just closed it.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21988
... same with 21988
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21994
MC: 21994: not related to us
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=21995
... 21995: editorial
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22002
...22002: seems like an editorial issue on the spec.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22007
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22008
...22007: same difference
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22019
...22008: marked as fixed
...22019: editorial issue
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22022
...22022: not a11y related
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22023
...22023: not a11y
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22035
MC: 22035: should at least keep an eye on this to monitor it.
CN: do we have a mechanism for tracking a bug through to solution to see if it affects a11y
[discussion]
ACTION for chaals to propose solution for shadow bug process
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22047
<scribe> ACTION: chaals to propose solution for shadow bug process [recorded in http://www.w3.org/2013/05/29-a11y-bugs-minutes.html#action01]
MC: reading from SF's proposal. should we track it or let Steve follow it.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22049
agreement
CN: I think we should track 22049
agreement to add a11y and a11ytf and a11y_table_headers
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22050
MC: 22050: document outline, is most likely an a11y issue. track it.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22074
LW: steve can take care of 22074
CN: 22187, 22188 and 22190 are all longdesc related, assigned to me. editorial related.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22191
MC: 22191 ARIA, editorial.
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22195
...22195: steve is tracking this.
LW: I will keep track of new bugs filed between now and next week.