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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sat, 5 Mar 2011 04:09:52 -0600
Message-ID: <AANLkTin3FFP_D1-EgmsMha-iJQpdtzRYGPr2XngwOT7t@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report we have had:

1 WONTFIX bug. Details are in section 1.
2 FIXED bugs. Details are in section 2.
1 REOPENED bug. Details are in section 3.
1 INVALID bug. Details are in section 4.
4 NEW a11y bugs reported. Details are in section 5.

Details are as follows.


1. WONTFIX BUG:

1.1 Bug 10518: "Add example showing how to use <a> elements in image
maps" reported by Leif Halvard Silli.
Ian's Rationale: "Whether it's inside or adjacent doesn't seem to
materially affect how easy this is to maintain. I don't mind using the
other style if we have reason to include another example, but at this
point this seems like bikeshedding on an example."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10518#c13


2. FIXED BUGS:

2.1 Bug 10486: "References to "image" ARIA role should be "img""
reported by Maciej Stachowiak.
Ian's Rationale: "Ok, I think I got them all. Please reopen the bug if
I missed any."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10486#c5
Check-in comment: typo
http://html5.org/tools/web-apps-tracker?from=5938&to=5939

2.2 Bug 10693: "Need a means for navigating between related timed
tracks of media elements" reported by Silvia Pfeiffer.
John Foliot marked this bug FIXED and added the TrackerRequest keyword.
http://www.w3.org/Bugs/Public/show_activity.cgi?id=10693
Sam escalated Bug 10693 to HTML TrackerIssue-163.
http://www.w3.org/html/wg/tracker/issues/163


3. REOPENED BUG:

3.1 Bug 10066: "replace section 3.2.6 with the alternative spec text
provided (ARIA)" reported by Steve Faulkner.
Reopened by Sam Ruby. Sam's comment:
"Per
http://lists.w3.org/Archives/Public/public-html/2011Mar/0005.html :
The HTML Working Group hereby adopts the ARIA in HTML5: change some
role mappings Proposal for ISSUE-129, with some specific exclusions.
Of the Change Proposals before us, this one has drawn the weaker
objections.
http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAinHTML5
The specific exclusions are:
 * Any changes to how <hgroup> elements are to be interpreted, or how
headings contained within such an <hgroup> are to be interpreted.
 * Allowing slider, scrollbar, or progressbar for <button>, <input
type=image>, or <input type=image>
 * Allowing progressbar, radio, slider, or scrollbar for <a>
 * Allowing button, checkbox, option, radio, slider, spinbutton, or
scrollbar on <h1>-<h6>
Please execute the remaining edits specified in the Change Proposal."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10066#c31


4. INVALID BUG:

4.1 Bug 7601: "refer to pronunciations for TTS PLS with link rel value
'pronunciation'" reported by Nick Levinson.
Ian's Rationale: "Putting the link relation on the wiki page is
sufficient to reserve it, but it also has to be implemented to
actually be of any use in the world (and that's a prerequisite to
being added to the spec, in principle). Discussion of this kind of
thing is probably best done in one of the W3C lists such as
public-html or the voice-related working group mailing lists."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7601#c15


5. NEW BUGS:

5.1 Bug 12214: "Canvas fallback content implementation is
underspecified" reported by Rich Schwerdtfeger.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12214

5.2 Bug 12226: "incorrect example in section 1.9.2 syntax errors"
reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12226

5.3 Bug 12228: "All Media Elements should have the ability to have
both short and longer textual descriptions associated to the element."
reported by John Foliot.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12228

5.4 Bug 12244: "Warn when interactive/forms associated content appears
inside role=childrenArePresentational elements" by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12244


6. "A11yTF" KEYWORD:

We currently have four HTML5 Spec bugs awaiting task force decision of
whether to apply the a11ytf keyword or not.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision


7. RELATED REFERENCES:

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

A11y Resolved Bug Comparisons:
http://www.d.umn.edu/~lcarlson/html5bugchart/

New Bug Snapshots
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot

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

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

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, 5 March 2011 10:10:25 GMT

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