W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2011

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sat, 22 Jan 2011 03:54:02 -0600
Message-ID: <AANLkTinVyHNiGgdddQV8BK_-bvkeAi3Apgyi5QAB3+aH@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Today January 22, 2011 is the deadline for escalating Pre-Last Call
bugs to HTML WG Issues. Fifty Pre-Last Call accessibility task force
(a11ytf) bugs exist which have not been escalated to the HTML Tracker
or marked "verified" or marked "closed".

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

Please check the snapshot 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.

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.
http://www.w3.org/html/wg/wiki/LastCallTimeline

Since the last report we have had:

3 REOPENED bugs. Details are in section 1.
1 NEW bugs reported. Details are in section 2.
2 CLOSED bugs. Details are in section 3.
3 TRACKER REQUESTS. Details are in section 4.

4 ISSUES with upcoming due dates and no change proposals submitted to
the working group yet. Details are in section 4.
2 ISSUES with change proposals past due. Details are in section 5.

We are down to a backlog of three a11y bugs on the HTML5 Spec awaiting
task force decision of whether to apply the a11ytf keyword or not.
Many thanks to the bug team for working on this. Details are in
section 6.


Details are as follows.

1. REOPENED BUGS:

1.1 Pre-Last Call Bug 10482: "Specify how @usemap affects role (of
<img> and <object>)" reported by Leif Halvard Silli.
Reopened by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10482#c4

1.2 Pre-Last Call Bug 10618: "Use "unmapped" rather than "no role" in
the weak/strong ARIA tables" reported by Leif Halvard Silli.
Reopened by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10618#c5

1.3 Pre-Last Call Bug 10518: "Add example showing how to use <a>
elements in image maps" reported by Leif Halvard Silli.
Reopened by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10518#c12


2. NEW BUGS:

2.1 Bug 11798: "It has been brought to my attention by some browser
vendors that browsers don't actually implement accessibility API
annotations exactly the way the ARIA spec says to; instead, they have
default mappings from HTML directly to the accessibility APIs that
they use unless an explicit role="" has been given. So it might make
sense to change this section so that it is nothing but conformance
criteria for authors, removing the UA conformance criteria relating to
ARIA and platform AAPIs from the HTML spec altogether." reported by
contributor@whatwg.org.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11798


3. CLOSED BUGS:

3.1  Pre-Last Call Bug 10497: "What happens to role of <img
alt="non-empty"> inside a <figure role="img">?" reported by Leif
Halvard Silli; closed by Leif.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10497

3.2  Pre-Last Call Bug 10605: "Typo: Replace 'the alt attribute's
value may be omitted' with '@alt may be omitted'" reported by Leif
Halvard Silli; closed by Leif.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10605


4. TRACKER REQUEST BUGS:

4.1  Pre-Last Call Bug 9428: "Permit <object> to be used without the
data or type attribute present" reported by Leif Halvard Silli. Leif
added the TrackerRequest keyword.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9428

4.2  Pre-Last Call Bug 9657: "Content model of object" reported by
Leif Halvard Silli. Leif added the TrackerRequest keyword.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9657

4.3  Pre-Last Call Bug 10482: "Specify how @usemap affects role (of
<img> and <object>)" reported by Leif Halvard Silli. Leif added the
TrackerRequest keyword.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10482


4. UPCOMING CHANGE PROPOSAL DUE DATES:

The following are accessibility task force issues for which no
proposals have been submitted to the working group yet:

* 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

* February 21: HTML-ISSUE-131, "caret-location-API". I think Rich is
working on this one. Deadline to submit a proposal to HTML Working
Group is February 21.
http://www.w3.org/html/wg/tracker/issues/131
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11239
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11240
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11241
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11241
http://dev.w3.org/html5/status/issue-status.html#ISSUE-131

* February 21: HTML-ISSUE-152, "multitrack-media-resources". Deadline
to submit a proposal to HTML Working Group is February 21. The Media
Subgroup wrote a Change Proposal quite some time ago for this issue
but I don't think it has been officially submitted to the working
group.
http://www.w3.org/WAI/PF/HTML/wiki/Media_MultitrackAPI
http://www.w3.org/html/wg/tracker/issues/152
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9452
http://dev.w3.org/html5/status/issue-status.html#ISSUE-152

For all Accessibility Change Proposal due dates please refer to:
http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status


5. CHANGE PROPOSALS PAST DUE:

* HTML-ISSUE-133 "Add a modal attribute to html5 to indicate a modal
segment of the DOM (modal dialog)" was due December 10. Everett Zufelt
reported the associated bug. Everett took an action to write a Change
Proposal. The deadline was missed and the issue was closed without
prejudice. Everett's action was reassigned to Cynthia on December 16.
http://www.w3.org/html/wg/tracker/issues/133
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831
http://www.w3.org/WAI/PF/HTML/track/actions/86
http://lists.w3.org/Archives/Public/public-html/2010Dec/0122.html

* HTML-ISSUE-134 "Provide tablist and tab states for menu and command
elements respectively" was due January 12. Everett Zufelt reported the
associated bug and took an action to write a Change Proposal. The
action was reassigned to Gregory December 16.
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

For all Accessibility Change Proposal due dates please refer to:
http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status


6. "A11yTF" KEYWORD BACKLOG:

We currently have three 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 the 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 the 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

HTML Last Call Timeline and Action Plan
http://www.w3.org/html/wg/wiki/LastCallTimeline

Best Regards,
Laura

--
Laura L. Carlson
Received on Saturday, 22 January 2011 09:54:35 GMT

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