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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 4 Apr 2010 05:29:48 -0500
Message-ID: <w2t1c8dbcaa1004040329xac9cdcf5i6f814f2aca83b185@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since last week's report we have had five NEEDSINFO bug resolutions,
six WONTFIX bug resolutions, one WORKSFORME bug resolution, two FIXED
bug resolutions, and one LATER bug resolution. Three quarters of the
bugs are for text alternatives, Tracker Issue 31.

It is anticipated that the survey for the CAPTCHA bug will happen
soon, as a draft was presented to Mike Smith two weeks ago.

We still need to agree on criteria for applying the "a11yTF" keyword.
I strongly recommend that this is be completed soon, as it is a
blocker for task force pursuit of work items key to our mission
(text-alternatives, ARIA, canvas).

The details are as follows.

1. NEEDSINFO BUGS:

1.1 Bug 8171: "Implement the text alternatives proposal from WAI,"
reported by Michael Cooper.
Ian's Rationale: "I still have no idea what the problem for this bug
is. Could you state clearly what the bug is so that I can fix it?"

My View: I strongly recommend that we expedite this, as it is part of
the change proposal, based on WAI-CG's consensus document, to resolve
tracker ISSUE-31 missing-alt. I suggest that the task force officially
take up work on bug 8171 and all of its dependent bugs in an effort to
supply Ian the needed information.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8171
http://www.w3.org/Bugs/Public/showdependencytree.cgi?id=8171
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
http://www.w3.org/html/wg/tracker/issues/31

1.2 Bug 8716: "Replace img Guidance for Conformance Checkers with
Suggested Text for Short Text Alternatives"
Ian's Rationale: "I have no idea what's going on with this bug. What
is the problem I'm supposed to be fixing?"

My View: I strongly recommend that we expedite this, as it is part of
the change proposal, based on WAI-CG's consensus document. I suggest
that the task force officially take up work on bug 8716 and all of its
dependent bugs in a concerted effort to supply Ian the needed
information to fix tracker ISSUE-31 missing-alt.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8716
http://www.w3.org/Bugs/Public/showdependencytree.cgi?id=8716
http://www.w3.org/html/wg/tracker/issues/31
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126

1.3 Bug 9213: "HTML5 Lacks a Way to Programmatically-Determine Missing
Text Alternatives" reported by Laura Carlson.
Ian's Rationale: "I don't understand. Could you restate the bug
description? Are you asking for a way to programmatically detect (e.g.
from JS?) that an image is missing alt text?"

My View: Bug 9213 is the idea that Matt put forward in the WAI CG text
alternative meetings last year. I suggest that the A11ytf keyword be
applied to this bug so that the task force can work collectively to
supply the needed information. I recommend that we expedite this, as
it is part of the change proposal, based on WAI-CG's consensus
document, to resolve tracker ISSUE-31 missing-alt.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9213
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
http://www.w3.org/html/wg/tracker/issues/31

1.4 Bug 9217: "Remove the Paragraph-Section-Heading loophole for not
providing a text alternative" reported by Laura Carlson.
Ian's Rationale: "Laura, please clarify if the suggestion above would
satisfy your request. Thanks!"

My View: Bug 9217 is not my sole request. It is part of the change
proposal, based on WAI-CG's consensus document, to resolve tracker
ISSUE-31 missing-alt. It needs concerted input from the task force as
a collective. I strongly recommend that the A11ytf keyword be applied
to this bug so that the group as a whole has the opportunity to say if
the Paragraph-Section-Heading loophole should be allowed in HTML5.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9217
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
http://www.w3.org/html/wg/tracker/issues/31

1.5 Bug 7721: "Drag and Drop is not keyboard accessible" reported by
Rich Schwerdtfeger.
Ian's Rationale: "Returning to NEEDSINFO per comment 10" which was "It
is unclear what change is being requested at this time."
My View: I suggest that the task force collectively work on this bug.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7721

1.6 Bug 9326: "HTML elements mapping to ARIA and A11y APIs reported"
by Cynthia Shelly.
Sam Ruby's marked this bug NEEDSINFO. Sam's rationale: "Marking as
NEEDSINFO per agreement at
http://www.w3.org/2010/03/25-html-wg-minutes.html#item12. Simply
REOPEN and assign to the relevant editor when the full list of changes
is available. Alternately, open separate bugs on each change (this
latter option being preferred)."
My View: As I recommended last week, I suggest that the A11ytf keyword
also be applied so the task force can officially work on this bug.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9326


2. WONTFIX BUGS:

2.1 Bug 8646: "Private communication exception (No text alternatives
on email images loophole)" reported by Gez Lemon.
Ian's Rationale: "I still don't understand what 'policy level' means
or the relevance of businesses here. It would be futile to argue..."

My View: As bug 8646 is part of the change proposal, based on WAI-CG's
consensus document, to resolve tracker ISSUE-31 missing-alt, I
strongly recommend that we apply the A11ytf keyword so that that the
task force can work collectively to determine course of action.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8646
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
http://www.w3.org/html/wg/tracker/issues/31

2.2 Bug 9098: "Correct the img element definition. Replace with
suggested text." reported by Laura Carlson on behalf of Vlad
Alexander.
Ian's Rationale: "That's what I had originally specified, back in
2005. See for instance the spec as it stood in 2006:
http://www.whatwg.org/specs/web-apps/2006-01-01/#the-img
However, people complained about this, giving some pretty compelling
arguments that this is wrong, e.g.:
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-April/010837.html
(This is not the only e-mail on the subject, but I cite it as it is
the one that resulted in the spec changing.) Objectively, it seems
that the latter e-mail has a more compelling case, unfortunately."

My View: I strongly recommend that the A11ytf keyword be applied to
bug 9098 so that the task force can officially work on this bug. The
rationale that Ian provided seems to be the impetus for most all of
the of text alternative loopholes, which caused ISSUE-31 missing-alt
and three years of working group conflict.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9098

2.3 Bug 6496: "Allow <img aria-labelledby>" reported by Simon Pieters.
Ian's Rationale: "To reply to comment 2, there's no need to expose the
element at all if the description and replacement is completely
expressed elsewhere in the page, as far as I can tell."

My View: As bug 8646 is part of the change proposal, based on WAI-CG's
consensus document, to resolve tracker ISSUE-31 missing-alt, I
strongly recommend that we apply the A11ytf keyword so that that the
task force can work collectively to determine course of action.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6496
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
http://www.w3.org/html/wg/tracker/issues/31

2.4 Bug 9061: "Allow image maps on the canvas element" reported by
Steve Faulkner.
Ian's Rationale: Unfortunately if we provide this we will be causing
authors huge headaches, because while it would be possible to use
canvas with image maps for the most trivial of pictures (pictures much
better rendered on the server side), it becomes vastly more
complicated to use image maps to do the slightest dynamic work once
the canvas is made in any way more advanced. For example, any use of
transforms, any use of large strokes, anything animated, etc, quickly
makes it inordinately difficult to use image maps. In the meantime,
all the use cases of image maps are trivially handled today using the
API. Therefore I think it would be a design mistake to do this."

My View: I suggest that the A11ytf keyword be applied so the task
force can officially work on this bug as part of ISSUE 74.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9061

2.5 Bug 9233: "Incorporate a Link to UAAG with appropriate wording
into browser sections" reported by Shelley Powers.
Ian's Rationale:
"http://www.w3.org/TR/UAAG10-TECHS/guidelines.html#tech-missing-alt
doesn't seem to provide anything that the HTML5 spec doesn't already
provide, except that the former is more vague (since it isn't specific
to HTML). I don't understand how this would be an improvement or how
it would result in browsers doing things better..."
My View: I suggest that the A11ytf keyword be applied so the task
force can work collectively to determine course of action as it is
part of ISSUE 66.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9233
http://lists.w3.org/Archives/Public/public-html/2010Jan/1189.html
http://lists.w3.org/Archives/Public/public-html/2010Jan/1131.html

2.6 Bug 7076: "Client-side image maps attributes missing on the a
element" Reported by Giovanni Campagna.
Ian's Rationale: "This bug is about whether <a coords> is conforming
or not. Based on UA feedback, it was removed from the UA requirements
and made non-conforming. This bug is not about extra examples or other
material. Please file separate bugs for each request so that they can
be tracked separately."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7076
My View: It looks like Leif added the "a11y" keyword to this bug on March 15.
http://lists.w3.org/Archives/Public/public-html-bugzilla/2010Mar/0767.html
I added the task force email CC when I happened to notice it on April 1.
My View: I suggest applying the A11ytf keyword if Leif or anyone else
wants to work on this bug.


3. WORKSFORME BUGS:

3.1 Bug 9214: Allow role="presentation" on img reported by Laura Carlson.
Ian's Rationale: "role="presentation" is already allowed on <img>. It
is already possible to programmatically convey to assistive technology
that an image is presentational and not of interest. Therefore this
seems to already be solved. This bug also had apparently unrelated
comments but they were responded to above (in particular in comments
13 and 15)."

My View: As bug 9214 is part of the change proposal, based on WAI-CG's
consensus document, to resolve tracker ISSUE-31 missing-alt, I
strongly recommend that we apply the A11ytf keyword so that that the
task force can work collectively to determine course of action.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9214
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElement20090126
http://www.w3.org/html/wg/tracker/issues/31


4. FIXED BUGS:

4.1 Bug 9241: "For guidance on accessibility requirements for text
alternatives authors should consult WCAG 2.0" and link to WCAG 2.0"
reported by Laura Carlson.
Ian's Rationale: "Change Description: see diff given below
Rationale: I added the suggested text to the W3C HTML5 draft. I used
'are encouraged to also consult' instead of "should consult" because
'should' has a special meaning due to RFC2119."

My View: The WAI CG document requested using the normative word
"should". I suggest that the A11ytf keyword be applied so the task
force can officially work on this issue.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9241
Checked in as WHATWG revision r4935.
http://html5.org/tools/web-apps-tracker?from=4934&to=4935

4.2 Bug 7056: "<caption> and <figure><legend> elements should allow
flow content children" reported by James Graham.
Ian's Rationale: "Reresolving as FIXED since that was the resolution
of this bug. Do not reopen this bug for tangential issues, please file
new separate bugs for each issue."
My View: Leave this bug labeled fixed and if task force members are
interested, a new one could be opened using Bugzilla dependencies
features if appropriate.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056


5. LATER BUG:

5.1 Bug 9280: "Add default button option/attribute for forms" reported
by Jonathan Avila.
Ian's Rationale: "The spec defines how default buttons are to be
selected...I agree that we should probably make it possible to
explicitly pick a button as the default. However, we've already added
quite a lot to the forms part of the spec and not all of it has been
widely implemented yet, so I'd rather we wait some more before adding
such a feature."
My View: Anyone else interested make sure there is agreement on the
postponement and time frame.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9280


6. CAPTCHA BUG:

Hopefully the survey for the CAPTCHA bug will happen soon. A draft was
delivered to Mike on March 21. The target time frame to go live was
over a week ago.
http://www.w3.org/WAI/PF/HTML/wiki/CAPTCHA_Survey
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0437.html

Mike, do you need any more help with this? Is there anything else I
can do to help move this forward?


7. ESTABLISHING "A11yTF" KEYWORD CRITERIA:

We still need to agree on criteria for applying the "a11yTF" keyword.
It would be good to settle this soon as this is a blocker for the task
force pursuit of items key to our mission (i.e. Text Alternatives,
ARIA).

The March 18, 2010 teleconference minutes indicated 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. A Wiki page
brainstorms ideas begun in the email "Criteria for 'a11yTF' keyword
application".
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 twenty-three 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_Decision

We currently have four 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_Decision

We currently have four bugs that I am aware of that have Keyword
"a11ytf" applied with no approval 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

The initial set of "A11y" bugs which were determined to have the
"A11yTF" keyword applied to them in January 2009 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 2009 are at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected


8. 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 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

Best Regards,
Laura

--
Laura L. Carlson
Received on Sunday, 4 April 2010 10:30:21 GMT

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