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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sat, 12 Jun 2010 08:08:05 -0500
Message-ID: <AANLkTilALqF6mI_qfyQkeDhqR1HH-RHNvKKTJraTQnZU@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

No bugs were resolved since the last report.

Four new a11y bugs were reported. Details are in section one below.
Via last week's teleconference resolution and follow up by Janina, I
was asked to advise, as to which bugs should be assigned the a11ytf
keyword. I will do my best based on the draft keyword bug criteria.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria

A draft survey for the CAPTCHA bug was presented to Mike Smith twelve
weeks ago. A status update would be useful. Details are in section two
below.

We currently have a number of bugs awaiting task force keyword
decision. Details are in section three below.

Full details are as follows.

1. NEW BUGS:

1.1 Bug 9871: "Provide normative advice to conformance checkers about
use of onevent handler attributes" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9871
Recommendation: Apply the a11ytf keyword, if Steve or another task
force member volunteers and agrees to actively work on and see this
bug through to closure. This bug meets the draft a11ytf bug criteria.

1.2 Bug 9872: "Trigger a conformance error when javascript is included
in href attribute" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9872
Recommendation: Apply the a11ytf keyword, if Steve or another task
force member volunteers and agrees to actively work on and see this
bug through to closure. This bug meets the draft a11ytf bug criteria.

1.3 Bug 9876: "Clarify that a figure can be any content with a
caption" Reported by contributor@whatwg.org.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9876
Recommendation: Apply the a11ytf keyword, if a task force member
volunteers and agrees to monitor and see this bug through to closure.
This bug meets the draft a11ytf bug criteria. In particular the figure
element is a feature that the task force has made a resolution
committing us to work on it and make it better.
http://lists.w3.org/Archives/Public/public-html-a11y/2010Apr/0183.html

1.4 Bug 9893: "tabindex not listed in Table of Contents". Reported by
Laura Carlson on behalf of Gregory J. Rosmaita due to technical
difficulties.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9893
Recommendation: Apply the a11ytf keyword, if Gregory or another task
force member volunteers and agrees to see this bug through to closure.
9893 is mainly editorial but it meets the draft a11ytf bug criteria.
It doesn't hurt to track it so that it doesn't fall through the
cracks.


2. CAPTCHA BUG:

A draft survey for the CAPTCHA bug was delivered to Mike Smith on March 21.
http://www.w3.org/WAI/PF/HTML/wiki/CAPTCHA_Survey
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0437.html
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0402.html

As discussed at the March 18 teleconference, the target time frame to
go live was over eleven weeks ago.
http://www.w3.org/2010/03/18-html-a11y-minutes.html#item02

Mike, what's up with this? Has it been decided to not hold a survey or
postpone a survey or cancel a survey? Is this bug now considered
superseded by the alt Change Proposals? Should I drop this item from
this weekly report?


3. "A11yTF" KEYWORD BACKLOG:

We currently have thirty-six HTML Spec bugs awaiting task force
decision. Ian Hickson is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

We currently have five Bugs on Document "HTML5: Techniques for
providing useful text alternatives Bugs" awaiting task force decision.
Steve Faulkner is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Text_Alternatives_Techniques_Bugs_Awaiting_A11yTF_Keyword_Decision

The initial set of "A11y" bugs, which were determined to have the
"A11yTF" keyword applied to them in January 2010, are at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/accepted

The initial set of "A11y" bugs, which were determined not to have the
"A11yTF" keyword, applied to them in January 2010 are at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected


4. RELATED REFERENCES:

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

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

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

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, 12 June 2010 13:08:34 GMT

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