W3C home > Mailing lists > Public > public-html-a11y@w3.org > March 2010

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Tue, 9 Mar 2010 18:39:23 -0600
Message-ID: <1c8dbcaa1003091639g11381ca7u4c3f61763fe95c83@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since last week's report we have had zero WONTFIX, NEEDSINFO,
WORKSFORME, INVALID, or FIXED bug resolutions. No bugs have been
reopened.

Seven NEW a11y bugs were reported.

Seventeen bugs need an A11yTF decision on whether to be tagged
"A11yTF" or not. It would be good if this could happen at one of the
next teleconferences so we don't get too far behind. I think I have
previously made recommendations on most of the 17 bugs in the weekly
bug reports or in this one.

Maciej sent a message to the HTML working group today regarding the
process and a specific timetable for VERIFYING and CLOSING old bugs
and moving them to a terminal state. I queried the a11ytf subset for
what is relevant to this group.

The details are as follows.

1. NEW BUGS:

I filed seven new bugs. Maciej had asked me [1] to provided bugs for
the differences between Ian's draft and the Change Proposal that I
drafted to implement WAI CG's text alternative consensus document. [2]

I suggest that the  a11ytf keyword be applied to the seven bugs as
there are dependencies on Bug 8171 "Implement the text alternatives
proposal from WAI" and are directly related to HTML Issue 31.

The bugs are:

Bug 9212: "Change the Generator Mechanism for img from Document Level
to Element Level".
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9212

Bug 9213: "HTML5 Lacks a Way to Programmatically-Determine Missing
Text Alternatives".
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9213

Bug 9214: Allow role="presentation" on img.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9214

Bug 9215: "Provide a Webcam example that is in accord with WCAG 2 or
Defer to 'HTML5: Techniques for providing useful text alternatives'".
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9215

Bug 9216: "Provide a CAPTCHA example that is in accord with WCAG 2 or
Defer to "HTML5: Techniques for providing useful text alternatives'".
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9216

Bug 9217: "Remove the Paragraph-Section-Heading loophole for not
providing a text alternative.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9217

Bug 9218: "Enable Automatic Validators to Programmatically Determine
the Presence or Absence of a Set of Text Alternatives".
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9218


2. BUGS THAT NEED A11YTF DECISIONS ON WHETHER TO BE TAGGED "A11YTF" OR NOT.

We have fifteen HTML5 spec bugs that await an A11yTF decision on
whether  to be tagged "A11yTF" or not.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#HTML5_Spec_Bugs_Awaiting_A11yTF_Decision

We have two text alternatives techniques bugs that await an A11yTF
decision on whether to be tagged "A11yTF" or not.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Text_Alternatives_Techniques_Bugs_Awaiting_A11yTF_Consideration

LC Suggestion: The task force should decide on these at one of the
next teleconferences so we don't get too far behind. I have previously
made recommendations on most of the 17 bugs in these weekly bug
reports.


3. OLD RESOLVED BUGS:

Maciej sent a message [2] today to the HTML working group regarding
the process and timetable for VERIFYING and CLOSING old bugs. I have
queried the relevant a11ytf subset.

We have 41 a11ytf bugs in the RESOLVED state that have not been moved
to VERIFY or CLOSED, and so they are not in a terminal state per the
HTML WG decision policy:
http://tinyurl.com/ycntekw

Seven of the 41 were moved to RESOLVED before last October, when the
HTML WG started discussing the new Decision Policy:
http://tinyurl.com/y9gomut

Maciej strongly encourages everyone to review bugs they originated and
place them in CLOSED state if they accept the resolution, or reopen or
escalate the bug if not.

Bugs 7404 and 7011 seem to have been escalated to the canvas issue
although 7404 doesn't say that on it.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7404
http://www.w3.org/html/wg/tracker/issues/74

Bug 7362 was escalated to the title issue. It explicitly says that on the bug.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7362
http://www.w3.org/html/wg/tracker/issues/80

Bugs 7633 and 7539 seem to have been escalated to the table summary
issue although 7539 doesn't explicitly say  that on the bug.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7539
http://www.w3.org/html/wg/tracker/issues/32

Bug 5758 video seem to have been escalated to the video issue although
5758 doesn't explicitly say that on the bug.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5758
http://www.w3.org/html/wg/tracker/issues/9

The only bug that appears not to have been escalated to an issue is
Rich Schwerdtfeger's Bug 7721 for Drag and Drop.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7721

Maciej has said that he will be moving these older type bugs that are
not escalated to VERIFIED [4] by the end of the week. If any are still
in VERIFIED after a month from Friday, then he will mark them as
NoReply, putting them in a terminal state.

I suggest the 6 bugs be explicitly linked to the appropriate tracker
issue. And for the drag and drop Bug if Rich so desires he could
reopen the bug or raise a new issue for it.

4. REFERENCES:

[1]  http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0007.html
[2] http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
[3] http://lists.w3.org/Archives/Public/public-html/2010Mar/0193.html
[4] http://dev.w3.org/html5/decision-policy/decision-policy.html#states-and-keywords

Weekly Resolved and Rejected Bugs Reports Archive
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Weekly_Resolved_and_Rejected_Bugs_Reports

Bug Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Bug_Status_Table

Accepted Bugs:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/accepted

Bugs With No Official Task Force Work Plan
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected

Escalating a Bug to an Issue:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Escalating_a_Bug_to_an_Issue

Accessibility Issues in the HTML5 Tracker:
http://www.w3.org/WAI/PF/HTML/wiki/Issues

Accessibility Change Proposal Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status


Best Regards,
Laura

--
Laura L. Carlson
Received on Wednesday, 10 March 2010 00:39:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:03 GMT