Reminder: January Change Proposal Deadlines

Hello everyone,

Today while updating the "Accessibility Change Proposal Status" [1]
and Accessibility Issues in the HTML5 Tracker" [2] Wiki pages, I noted
several Accessibility Change Proposals are due this month. I'm not
sure who is working on what. But for everyone's information the
following are due:

* January 12: HTML-ISSUE-134, "Provide tablist and tab states for menu
and command elements respectively" [3] [4].  Bug-triage sub team
decided to add the a11yTF keyword to the bug for Issue 134 [5].

* January 19: HTML-ISSUE-135 "Put back direct link to the W3C version
of the canvas 2d context spec" [6] [7]. The bug team has not yet
indicated on bug 10921 whether this is a task force priority or not
[8] [9].

* January 26: HTML-ISSUE-142 "No alternative text description for
video key frame (poster)" [10] [11]. The bug for Issue 142 [12] is
marked with the "a11ytf" keyword. I think John is working on this one.

* January 26: HTML-ISSUE-146, "<video> should allow muted as a content
attribute" [13] [14]. Martin indicated that this is a task force
priority [15]. John is this something that the media team is pursuing?

In addition, last month HTML-ISSUE 133: "Add a modal attribute to
html5 to indicate a modal segment of the DOM (modal dialog)" was
closed without prejudice as no change proposals were received by the
December 10th deadline [16] [17] [18]. If anyone is interested in
writing a change proposal for Issue 133, I suspect  the HTML Chairs
might possibly reopen it as they did for Rich in Issue 130 [19] [20].

For information on writing accessibility change proposals please refer
to the Wiki [21].

Best Regards,
Laura

[1] http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status
[2] http://www.w3.org/WAI/PF/HTML/wiki/Issues
[3] http://www.w3.org/html/wg/tracker/issues/134
[4] http://lists.w3.org/Archives/Public/public-html/2010Nov/0416.html
[5] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831#c4
[6] http://www.w3.org/html/wg/tracker/issues/135
[7] http://lists.w3.org/Archives/Public/public-html/2010Dec/0068.html
[8] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10921
[9] http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML5_Spec_Bugs_Awaiting_Decision
[10] http://lists.w3.org/Archives/Public/public-html/2010Dec/0123.html
[11] http://www.w3.org/html/wg/tracker/issues/142
[12] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10642
[13] http://lists.w3.org/Archives/Public/public-html/2010Dec/0125.html
[14] http://www.w3.org/html/wg/tracker/issues/146
[15] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831#c4
[16] http://lists.w3.org/Archives/Public/public-html/2010Dec/0122.html
[17] http://www.w3.org/html/wg/tracker/issues/133
[18] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10645#c20
[19] http://lists.w3.org/Archives/Public/public-html/2010Dec/0132.html
[20] http://www.w3.org/html/wg/tracker/issues/133
[21] http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposals

--
Laura L. Carlson

Received on Monday, 3 January 2011 01:47:36 UTC