Weekly Resolved & Rejected Bugs Report

Hello Everyone,

Since the last report we have had:

1 WONTFIX bug. Details are in section 1.
1 REOPENED bug. Details are in section 2.
5 CLOSED bugs. Details are in section 3.
1 ESCALATED bug. Details are in section 4.

Five accessibility change proposals are due this month. Key deadlines
are January 12, 17, 19, and 26. Details are in section 5.

Fifty Pre-Last Call 1 accessibility task force (a11ytf) bugs exist
which have not been escalated to the HTML Tracker or marked "verified"
or marked "closed" as of January 8, 2011.

A detailed snapshot of these fifty-one bugs is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/SnapshotPLC1_20110108

Please check the snapshot details for bugs that you may have reported
and for bugs that may have been have been assigned to you. Please
close bugs that are satisfactorily resolved. Those not satisfactorily
resolved can be escalated to an issue. This will enable the full HTML
Working Group the ability to address the problem and the HTML Chairs
the ability to make a decision.

January 22, 2011 is the deadline for escalating Pre-Last Call 1 bugs
to a HTML WG Issue if the reporter, or the task force, or any
individual working group member for that matter, is not satisfied with
the editor's resolution. For details on escalating a Bug to an Issue
please refer to the instructions at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Escalating_a_Bug_to_an_Issue

Consequences of missing the January 22 deadline is that any further
escalations will be treated as Last Call comments.

A backlog of 25 a11y bugs on the HTML5 Spec await task force decision
of whether to apply the a11ytf keyword or not. The majority these 25
are Pre-Last Call Bugs. Details are in section 6.

Details are as follows.


1. WONTFIX BUG:

1.1 Pre-Last Call Bug 8716: "Replace img Guidance for Conformance
Checkers with Suggested Text for Short Text Alternatives" reported by
Laura Carlson.
This bug had already been escalated for HTML Issue 31 and the Change
Proposal has been written. I added the TrackerIssue keyword per
Comment 6 and changed the status to WONTFIX as the editor has written
his own No-Change Change-Proposal for Issue 31.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8716#c15


2. REOPENED BUG:

2.1 Post-Last Call Bug 11238: "Enable canvas to support accessible
rich text editing" reported by Rich Schwerdtfeger.
Reopened by Rich Schwerdtfeger.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11238#c3


3. CLOSED BUGS:

3.1 Pre-Last Call Bug 9218: "Enable Automatic Validators to
Programmatically Determine the Presence or Absence of a Set of Text
Alternatives" reported by Laura Carlson.
I closed this bug as it is a duplicate of bug 8716.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9218

3.2 Pre-Last Call Bug 9169: "Consider adding a CAPTCHA example"
reported by Laura Carlson.
I closed this bug as Steve fixed it.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9169

3.3 Pre-Last Call Bug 9174: "Consider adding a Webcam example"
reported by Laura Carlson.
I closed this bug as Steve fixed it.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9174

3.4 Pre-Last Call Bug 9679: "Consider expanding the explanation of a
null alt attribute (alt="")" reported by Laura Carlson.
I closed this bug as Steve fixed it.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9679

3.5 Pre-Last Call Bug 9893: "tabindex not listed in Table of Contents"
reported by Laura Carlson.
I closed this bug as Ian fixed it.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9893


4. NEW ESCALATED BUGS:

4.1 Pre-Last Call Bug 9452: "Handling of additional tracks of a
multitrack audio/video resource" reported by Silvia Pfeiffer.
Sam raised this issue on behalf of Silvia as HTML Issue 152.
http://www.w3.org/html/wg/tracker/issues/152
The HTML Chairs have not set a deadline yet for change proposals.
However, quite a while back the Media Subgroup wrote one:
http://www.w3.org/WAI/PF/HTML/wiki/Media_MultitrackAPI


5. UPCOMING CHANGE PROPOSAL DEADLINES FOR ESCALATED BUGS:

* January 12: HTML-ISSUE-134 "Provide tablist and tab states for menu
and command elements respectively". Everett Zufelt reported the
associated bug. Gregory Rosmaita is writing a change proposal for this
issue. Deadline to submit a proposal to HTML Working Group is January
12.
http://www.w3.org/html/wg/tracker/issues/134
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831
http://www.w3.org/WAI/PF/HTML/track/actions/87
http://dev.w3.org/html5/status/issue-status.html#ISSUE-134

* January 17: ISSUE 129: "replace section 3.2.6 with the alternative
spec text provided (ARIA)". Steve Faulkner reported the associated bug
and wrote a Change Proposal.
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10066
http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAinHTML5
http://dev.w3.org/html5/status/issue-status.html#ISSUE-129

* January 19: HTML-ISSUE-135 "Put back direct link to the W3C version
of the canvas 2d context spec". Steve Faulkner reported the associated
bug. Steve has indicated he is working on the issue. Deadline to
submit a proposal to HTML Working Group is January 19.
http://www.w3.org/html/wg/tracker/issues/135
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10921
http://lists.w3.org/Archives/Public/public-html/2010Dec/0075.html
http://dev.w3.org/html5/status/issue-status.html#ISSUE-135

* January 26: HTML-ISSUE-142 "No alternative text description for
video key frame (poster)". Everett Zufelt reported the associated bug.
John Foliot is writing change proposal for this issue. Deadline to
submit a proposal to HTML Working Group is January 26.
http://www.w3.org/html/wg/tracker/issues/142
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10642
http://www.w3.org/WAI/PF/HTML/track/actions/94
http://dev.w3.org/html5/status/issue-status.html#ISSUE-142

* January 26: HTML-ISSUE-146, "<video> should allow muted as a content
attribute". Adrian Bateman reported the associated bug and the bug
team gave it the a11ytf  keyword. No one that I am aware of has
indicated that they are writing change a proposal for this issue.
Deadline to submit a proposal to HTML Working Group is January 26.
http://www.w3.org/html/wg/tracker/issues/146
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10419
http://dev.w3.org/html5/status/issue-status.html#ISSUE-146


6. "A11yTF" KEYWORD BACKLOG:

We currently have 25 HTML5 Spec bugs awaiting task force decision of
whether to apply the a11ytf keyword or not. The majority are Pre Last
Call Bugs.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

One bug on document "HTML5: Techniques for providing useful text
alternatives Bugs" awaits task force decision. Michael(tm) Smith is
editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML:_The_Markup_Language_Reference_Bugs_Awaiting_Decision

One bug on document "HTML Working Group Decision Policy" awaits task
force decision. Maciej Stachowiak, Paul Cotton, Sam Ruby are the
editors of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML_Working_Group_Decision_Policy_Bugs_Awaiting_Decision

No bugs on document on the document "HTML5: Techniques for providing
useful text alternatives Bugs" await task force decision. Steve
Faulkner is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#Text_Alternatives_Techniques_Bugs_Awaiting_Decision


7. RELATED REFERENCES:

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

Pre-Last Call 1 Bug Snapshots
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/SnapshotPLC1

Backlog of Bugs Awaiting "A11yTF" Keyword Decision
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

A11y Resolved Bug Comparisons:
http://www.d.umn.edu/~lcarlson/html5bugchart/

New Bug Snapshots
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot

"A11yTF" Keyword Criteria (Draft)
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria

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

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

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 Saturday, 8 January 2011 10:51:25 UTC