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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Tue, 16 Mar 2010 18:59:52 -0500
Message-ID: <1c8dbcaa1003161659n68903ddbhed00f4b57a676301@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since last week's report Maciej put six a11ytf bugs into the VERIFIED
state. Five have had the "TrackerIssue" keyword applied. Rich's Bug
7721 "Drag and Drop" is in jeopardy. Maciej has said VERIFIED bugs
will be marked NoReply in a month unless the bug is tagged
"TrackerRequest" or "TrackerIssue"; or the bug is reopened; or the bug
is closed. A NoReply puts a bug in a terminal state.

Since last week's report we have had one bug CLOSED; four bugs
REOPENED; and two NEW bugs reported.

We have 15 bugs that I have nominated for A11YTF keyword status. These
bugs would benefit from group attention, on the bug itself or the
larger issue of which it is a part. I have made recommendations and
provided rationale on these bugs in prior weekly bug reports. However,
it is unclear to me now, if I should just add the A11yTF keyword and
not bother the teleconference folks to make an explicit decision, as
members of the task force have added the A11yTF keyword individually
to other bugs without task force authorization. Advice from the
facilitators would be appreciated.

This afternoon thirteen accessibility bugs were marked FIXED but not
by Ian.  No description of the fix or rationale was given for these
bugs. Maciej later reopened them. Thanks Maciej.

The details are as follows.

1. VERIFIED BUGS:

As a small part of a HTML working group mass bug move, Maciej [1] set
the following six A11yTF bugs to VERIFIED. Five have had the
TrackerIssue keyword applied. The one exception is Rich's "Drag and
Drop" bug. Maciej has said VERIFIED bugs will be marked NoReply in a
month unless one of the following happens:

*  The bug is moved to CLOSED (and optionally tagged with the Disagree keyword).
*  The bug is tagged with TrackerRequest or TrackerIssue keywords.
*  The bug is reopened.

NoReply puts a bug in a terminal state. [2]

If Rich so desires he should do one of the three for Drag and Drop.

Bug 7721: "Drag and Drop is not keyboard accessible" reported by Rich
Schwerdtfeger.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7721

Bug 5758: "<audio> and <video> do not have sufficient support for
synchronized accessibility content"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5758

Bug 7011: "Canvas accessible fallback provision is under specified"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7011

Bug 7362: "inclusion of the title as a case where the alt may be
omitted" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7362

Bug 7539: "Since @summary is an official part of the table element, it
is no longer obsolete. Sufficient warning language exists in it's
definition that this entry should be removed" reported by
contributor@whatwg.org.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7539

Bug 7633: The use of @summary should be encouraged when circumstances
warrant" reported by Shelley Powers.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7633


2. CLOSED BUG:

Bug 8554: "<progress> element should be labelable with a label"
reported by Maciej Stachowiak.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8554
Ian accepted this bug. Maciej said that it looks good to him. The
Check-in comment is at:
http://html5.org/tools/web-apps-tracker?from=4530&to=4531
LC suggestion: Task force members who are interested, make sure that
the bug fix works for you.


3. REOPENED BUGS:

Bug 6496: "Allow <img aria-labelledby> to act as a text alternative"
originally reported by Simon Pieters. Reopened by Laura Carlson to
give Ian another opportunity to fix the bug.
LC Suggestion: Add the a11ytf keyword to this bug as WAI CG Consensus
Resolutions on Text alternatives in HTML 5 specifically recommends the
use of @aria-labelledby for a short text alternative and it is part of
the change proposal, "Replace img Guidance for Conformance Checkers"
for HTML WG Issue 31.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6496

Bug 7056: "<caption> and <figure><legend> elements should allow flow
content children" originally reported by James Graham. Reopened by
Leif Halvard Silli to give Ian an opportunity to fix the bug.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056
But  James Graham, the original reporter, and Maciej disagree that the
bug is substantially related to the issue 32. Leif added the "a11ytf"
and "a11y_table_summary" keywords.
The task force should advise on this one.

Bug 8646: "Private communication exception" reported by Gez Lemon.
Reopened by Laura Carlson to give Ian another opportunity to fix the
bug.
LC Suggestion: Add the a11ytf keyword to this bug as is part of the
change proposal, "Replace img Guidance for Conformance Checkers" for
HTML WG Issue 31.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056

Bug 8716: "Replace img Guidance for Conformance Checkers with
Suggested Text for Short Text Alternatives " reported and reopened by
Laura Carlson to give Ian another opportunity to fix the bug.
This bug already has the a11ytf keyword applied. It is part of the
change proposal, "Replace img Guidance for Conformance Checkers" for
HTML WG Issue 31.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8716


4. NEW BUGS:

Bug 9233: "Incorporate a Link to UAAG with appropriate wording into
browser sections" reported by Shelley Powers.
LC Suggestion: Add the a11ytf keyword to this bug. It is related to
issue 66 as well as bug 9241.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9233

Bug 9241: Explicitly state, 'For guidance on accessibility
requirements for text alternatives authors should consult WCAG 2.0'
and link to WCAG 2.0".
LC Suggestion: Add the a11ytf keyword to this bug as WAI CG Consensus
Resolutions on Text alternatives in HTML 5 specifically recommends
this text. It is directly related to HTML WG Issue 31.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9241


5. BUGS RECOMMEND FOR A11YTF KEYWORD

I recommend that the following 15 bugs be tagged A11yTF. I have made
recommendations and provided rationale on these bugs in prior weekly
bug reports. However, it is unclear to me now if I should just add the
A11yTF keyword and not bother the teleconference folks to make an
explicit decision, as members of the task force have added the A11yTF
individually to other bugs without task force authorization.
http://lists.w3.org/Archives/Public/public-html/2010Mar/0343.html
http://lists.w3.org/Archives/Public/public-html-bugzilla/2010Jan/0762.html

Advice from the facilitators would be appreciated. Anyway the 15 bugs are:

9241: "Explicitly state, 'For guidance on accessibility requirements
for text alternatives authors should consult WCAG 2.0' and link to
WCAG 2.0"
9233: "Incorporate a Link to UAAG with appropriate wording into
browser sections"
9218: "Enable Automatic Validators to Programmatically Determine the
Presence or Absence of a Set of Text Alternatives"
9217: "Remove the Paragraph-Section-Heading loophole for not providing
a text alternative.
9216: "Provide a CAPTCHA example that is in accord with WCAG 2 or
Defer to "HTML5: Techniques for providing useful text alternatives'"
9215: "Provide a Webcam example that is in accord with WCAG 2 or Defer
to 'HTML5: Techniques for providing useful text alternatives'"
9214:  Allow role="presentation" on img
9213: "HTML5 Lacks a Way to Programmatically-Determine Missing Text
Alternatives"
9212: "Change the Generator Mechanism for img from Document Level to
Element Level"
9098: "Correct the img element definition. Replace with suggested text."
9061: "Allow image maps on the canvas element"
8872: "Split out and modify parts of Section 4.8.2.1 the img element"
8646: "Private communication exception"
8000: "ARIA roles added to the a element should be conforming in HTML5"
6496: "Allow aria-labelledby to act as a text alternative"

If anyone knows of other bugs that should be tagged a11ytf, please speak up.


6. BOGUS FIXED BUGS:

The following 13 bugs were marked FIXED but not by Ian. They were
marked fixed by kesha <kidz1stav@yahoo.com>. No description of the fix
or rationale was given. Maciej a.k.a. Ms2ger <Ms2ger@gmail.com> reopen
them:

Bug 9241: Explicitly state, "For guidance on accessibility
requirements for text alternatives authors should consult WCAG 2.0"
and link to WCAG 2.0.
Bug 9233: Incorporate a Link to UAAG with appropriate wording into
browser sections .
Bug 9218: Enable Automatic Validators to Programmatically Determine
the Presence or Absence of a Set of Text Alternatives.
Bug 9217: Remove the Paragraph-Section-Heading loophole for not
providing a text alternative.
Bug 9216: Provide a CAPTCHA example that is in accord with WCAG 2 or
Defer to "HTML5: Techniques for providing useful text alternatives".
Bug 9215: Provide a Webcam example that is in accord with WCAG 2 or
Defer to "HTML5: Techniques for providing useful text alternatives".
Bug 9214: Allow role="presentation" on img.
Bug 9213: HTML5 Lacks a Way to Programmatically-Determine Missing Text
Alternatives.
Bug 9212: Change the Generator Mechanism for img from Document Level
to Element Level.
Bug 9098: Correct the img element definition. Replace with suggested text.
Bug 8716: Replace img Guidance for Conformance Checkers with Suggested
Text for Short Text Alternatives.
Bug 8646: Private communication exception.
Bug 6496: Allow <img aria-labelledby> to act as a text alternative.


7. REFERENCES:

[1] http://lists.w3.org/Archives/Public/public-html/2010Mar/0344.html
[2] http://lists.w3.org/Archives/Public/public-html/2010Mar/0193.html

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

Accepted Bugs:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/accepted

Bugs With No Official Task Force Work Plan
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected

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

Accessibility Issues in the HTML5 Tracker:
http://www.w3.org/WAI/PF/HTML/wiki/Issues

Accessibility Change Proposal Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status

a11ytf Bugs changed since the last report:
http://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywords=a11ytf&bug_status=RESOLVED&chfieldfrom=2010-03-10&chfieldto=2010-03-16

Best Regards,
Laura

--
Laura L. Carlson
Received on Wednesday, 17 March 2010 00:00:21 GMT

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