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, 18 Apr 2010 12:10:41 -0500
Message-ID: <s2l1c8dbcaa1004181010g397f922pb52c8e2b418f4ba6@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since last week's report we have had two WONTFIX bugs, one FIXED bug,
and one NEW bug.

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

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

The details are as follows.

1. WONTFIX BUGS:

Bug 9485: "Mandate in HTML5 that all conformance checkers and
validators must refer to the appropriate WCAG document and section
that provides remedial guidance to authors whenever text alternatives
are unknown or missing" reported by Laura Carlson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9485
Ian's Rationale: "As Henri says, we try to avoid defining UI
requirements. I would recommend putting such a requirement in a UAAG
analogue for validators."

My View: I suggest that we expedite defining "a11ytf" keyword criteria
and procedures so we know if the task force can officially work on
this item. Currently not having the "a11ytf" keyword designation
blocks the task force from officially working on bugs key to the task
force mission. After criteria is agreed to, I recommend that the
a11ytf keyword be applied, if this bug meets the criteria. 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 for criteria and procedures for the 'a11yTF' keyword".
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria

Bug 9437: Change ARIA section title and add extra text about use of
ARIA" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9437
Ian's Rationale: "While in theory ARIA could be exposed to other
users, it would do a disservice to AT users to try to convince authors
that ATs aren't the main target audience here."

My View: Same as for bug 9485.


2. FIXED BUGS:

Bug 9217: "Remove the Paragraph-Section-Heading loophole for not
providing a text alternative." reported by Laura Carlson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9217
Ian's Rationale: "The complexity argument is a fair one."

My View: The spec revision for this bug looks good to me. Thanks to
Gez for his advice to file this bug in the first place and to Ian and
Maciej for their work in the resolution. This bug is one from the set
of bugs for ISSUE-31 missing alt.
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0007.html
Spec Change:
http://html5.org/tools/web-apps-tracker?from=5025&to=5026

If anyone thinks bug 9217 is not fixed properly please speak up.


3. NEW BUGS:

Bug 9471: "Introduce declarative markup to associate timed text
resources with media elements". Reported by Silvia Pfeiffer.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9471
(I missed reporting this one last week as Bugzilla Mail wasn't
working. Sorry Silvia.)
My View: Same as for bug 9485.


4. CAPTCHA BUG:

Hopefully the survey for the CAPTCHA bug will happen soon. A draft was
delivered to Mike Smith on March 21. The target time frame to go live
was over three weeks 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?


5. ESTABLISHING "A11yTF" KEYWORD CRITERIA:

We still need to agree on criteria and procedure 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
(text-alternatives, ARIA, canvas, media).

As previously mentioned, 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-seven 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 seven bugs that I am aware of that have the keyword
"a11ytf" applied with no stamp of 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
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9437
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9452
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9471

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 that 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


10. 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, 18 April 2010 17:11:16 GMT

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