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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Fri, 13 May 2011 03:05:06 -0500
Message-ID: <BANLkTimWWQW=C3YG3dJP_geLsFS-n7CEfA@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report we have had:

2 WONTFIX bugs. Details are in section 1.
1 NEEDSINFO bug. Details are in section 2.
1 WORKSFORME bug resolution. Details are in section 3.
3 FIXED bugs. Details are in section 4.
1 REOPENED bug. Details are in section 5.
1 INVALID bug. Details are in section 6.

Details are as follows.

1. WONTFIX BUG:

1.1 Bug 12244: "Warn when interactive/forms associated content appears
inside role=childrenArePresentational elements" reported by Leif
Halvard Silli.
Ian's Rationale: "I agree with the report, but it seems like something
WAI-ARIA should require, not HTML: the same problem would exist if you
were using SVG+ARIA or MathML+ARIA with no HTML in sight."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12244#c2

1.2 Bug 12363: "Include @longdesc in Microdata" reported by Leif Halvard Silli.
Ian's Rationale: "This would be utterly wrong. longdesc="" is not a
description of the current document. It would also be a waste of time,
since longdesc="" values are almost uniformly either bogus or useless,
and the element is non-conforming so new valid documents won't use
it."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12363#c2


2. NEEDSINFO BUG:

2.1 Bug 11956: "Restrict use of role=presentation" reported by Steve Faulkner.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Ian's comment: "I still don't understand the problem here. If the
problem is just that bug 10919 was resolved in a way that you disagree
with, please reopen or escalate that bug as per comment 4. If the
problem is that ARIA doesn't define what happens when the user focuses
focusable element with role=presentation, then that's a bug in ARIA,
regardless of whether that combination is allowed or not. If the bug
is that browsers don't do what ARIA says, then file the bugs with the
browsers. Note that allowing a role on an element has no relationship
with whether browsers will support that role on an element, so the
"that is how it is implemented" part of comment 0 makes no sense."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11956#c12


3. WORKSFORME BUG:

3.1 Bug 8800: "Cut/copy/paste should use dedicated events instead of
overloading drag and drop" reported by Maciej Stachowiak.
Status: "Rejected"
Change Description: "no spec change"
Rationale: "There is now a spec for this."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8800#c9


4. FIXED BUGS:

4.1 Bug 10618: "Use "unmapped" rather than "no role" in the
weak/strong ARIA tables" reported by Leif Halvard Silli.
Ian's rationale: "Concurred with reporter's comments."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10618#c6
Check-in comment: "Define 'no role' more explicitly."
http://html5.org/tools/web-apps-tracker?from=6121&to=6122

4.2 Bug 12214: "Canvas fallback content implementation is
underspecified" reported by Rich Schwerdtfeger.
Ian's rationale: "I've tried to clarify the reported problem."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12214#c2
Check-in comment: "clarify what 'focus' means"
http://html5.org/tools/web-apps-tracker?from=6096&to=6097

4.3 Bug 12226: "Incorrect example in section 1.9.2 syntax errors"
reported by Steve Faulkner.
Ian's rationale: "concurred with reporter's comments...though the fact
that the spec now allows people to mark rows as cells is pretty
crazy."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12226#c2
Check-in comment: "correctness"
http://html5.org/tools/web-apps-tracker?from=6097&to=6098


5. REOPENED BUG:

5.1 Bug 10919: "Allow role="presentation" to override the default role
of any element" reported by Martin Kliehm.
Reopened by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10919


6. INVALID BUG:

6.1 Bug 12290: "The user agent must allow the element to be focused,
should allow the element to be reached using sequential focus
navigation, and should place the element in the sequential focus
navigation order so that it is..." reported by contributor@whatwg.
Ian's Rationale: "I don't understand. Could you elaborate?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12290#c1


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

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

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

"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

HTML Last Call Timeline and Action Plan
http://www.w3.org/html/wg/wiki/LastCallTimeline

Best Regards,
Laura

--
Laura L. Carlson
Received on Friday, 13 May 2011 08:05:33 GMT

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