Weekly Resolved & Rejected Bugs Report

Hello Everyone,

Since last week's report we have had three NEW a11y bugs reported.
Details are in section 1 below. No bugs have been fixed or resolved in
any way.

A draft survey for the CAPTCHA bug was presented to Mike Smith six
weeks ago. Details are in section 2 below. Mike, What is the status on
this?

The Task Force still has not agreed on criteria or procedure for
applying the "a11yTF" keyword to new bugs. Details are in section 3
below. Janina and Mike, should task force members simply use their own
judgment and individually tag bugs "a11yTF" as they see fit or will
criteria and a procedure be defined?

Michael Cooper has proposed an action plan to dispose of display,
focus, labels, and semantics bugs. Please review the proposal to
determine if you are in agreement. A dozen task force members are
specifically mentioned in Michael's proposal. Please check to see if
you are named in the proposal. Details are in section 4 below.


1. NEW BUGS:

1.1 Bug 9673: "Remove any reference to a specific Time Stamp format
for video captioning from the specification at this time", reported by
John Foliot.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9673
The "a11ytf" keyword was applied to this bug without a decision from
the task force.

My View: I suggest that we expedite figuring out what the status is
with the "a11ytf" keyword criteria and procedures (see section 3
below). After that is settled, I recommend that the "a11ytf" keyword
be applied, if this bug meets the criteria.  If it does not meet the
criteria, I recommend the "a11ytf" keyword be removed.

1.2 Bug 9678: "Add rationale for providing an alt when inline
description is available" Reported by Steve Faulkner on is Steve
Faulkner's "Techniques for providing useful text alternatives"
document.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9678
http://dev.w3.org/html5/alt-techniques/

My View: I suggest that we expedite figuring out what the status is
with "a11ytf" keyword criteria and procedures. After that is settled,
I recommend that the "a11ytf" keyword be applied, if this bug meets
the criteria.

1.3 Bug 9679: "Consider expanding the explanation of a null alt
attribute (alt="")" reported by Laura Carlson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9679

My View: Same as for bug 9678.


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 five 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?


3. ESTABLISHING "A11yTF" KEYWORD CRITERIA:

The Task Force still has not agreed on criteria for applying the
"a11yTF" keyword to NEW bugs. I have previously recommended that we
develop criteria, because on March 18, Mike Smith said that a non
trivial cost exists to tagging bugs "a11ytf" and that the task force
needs to agree on criteria for our decisions to take on bugs.
http://www.w3.org/2010/03/18-html-a11y-minutes.html#item02

Mike, what is the status with this? Has it been decided not to have
the group document and to agree criteria in advance of tagging bugs
"a11yTF"?

Should task force members use their own judgment and tag bugs "a11yTF"
as they see fit? That would seem to be a simpler procedure.

I had started a Wiki page to brainstorm ideas for criteria but maybe
that is irrelevant now?
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0438.html

We currently have thirty HTML Spec bugs awaiting task force decision.
Ian Hickson is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#HTML5_Spec_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

We currently have five bugs that I am aware of that have the Keyword
"a11ytf" applied with no approval decision from the task force:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8674
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8715
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8827
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9673

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. DISPOSITION OF DISPLAY, FOCUS, LABELS, AND SEMANTICS BUGS:

Michael Cooper has proposed an action plan to drive or dispose of
display, focus, labels, and semantics bugs. Please check his email and
the document attached to his email to see if you agree with the
proposal. If you have comments please speak up. Ben Caldwell, Charles
McCathieNevile, Cynthia Shelly, Gez Lemon, Gregory Rosmaita, Jim
Allan, John Foliot, Joshue O'Connor, Kelly Ford, Rich Schwerdtfeger,
Sally Cain, and Steve Faulkner are all specifically mentioned in
Michael's proposal.
http://lists.w3.org/Archives/Public/public-html-a11y/2010May/0030.html
http://lists.w3.org/Archives/Public/public-html-a11y/2010May/att-0030/display_focus_label_semantic.html


5. RELATED REFERENCES:

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

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 May 2010 11:27:10 UTC