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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 17 Oct 2010 14:20:27 -0500
Message-ID: <AANLkTinXfDFqxLnTb-0n=AEgVUBkZ+qOH5dzKzp+p-NP@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report we have had:

6 WONTFIX bug resolutions. Details are in section 1.
9 NEEDSINFO bug resolutions. Details are in section 2.
1 REOPENED bug resolution. Details are in section 3.
4 FIXED bug resolutions. Details are in section 4.
1 ASSIGNED bug. Details are in section 5.
1 REMIND bug. Details are in section 6.
1 INVALID bug. Details are in section 7.
1 NEW a11y bug reported. Details are in section 8.
3 CLOSED bugs. Details are in section 9.
13 ESCALATED BUGS. Details are in section 10.
1 ESCALATED BUG to be DEESCALATED. Details are in section 11.

10 total NEW a11y bugs existed on October 16, 2010. An October 16 bug
snapshot is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20101016

A backlog of 101 a11y bugs on the HTML5 Spec await task force decision
of whether to apply the a11ytf keyword or not. Details are in section
11.

Details are as follows.


1. WONTFIX BUGS:

1.1 Bug 10837: "playbackrate: undefined behavior when the user agent
can't play back at the requested rate" reported by Frank Olivier.
Status: Rejected
Change Description: no spec change
Ian's Rationale: "The spec already handles all the described cases."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10837

1.2 Bug 10914: Allow multiple space separated values for the ARIA role
attribute" reported by Martin Kliehm.
Status: Rejected
Change Description: no spec change
Ian's Rationale: "This is out of scope for HTML, since HTML defers
entirely to the ARIA spec for the definition of role="" and its
conformance criteria for authors and user agents."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10914

1.3 Bug 10916: "Add a new <control> element to convey the common
semantics of a script enabled UI control" reported by Adrian Bateman.
Status: Rejected
Change Description: no spec change
Ian's Rationale: "It seems that there are two basic approaches for
this already specified, which should already be usable for the given
use case of a development environment being careful not to break pages
during editing..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10916

1.4 Bug 10921: "Put back direct link to the W3C version of the canvas
2d context spec" reported by Steve Faulkner.
Status: Rejected
Change Description: no spec change
Ian's Rationale: "The link to the WHATWG wiki is only temporary until
we find a better solution for registering these relations. In the
meantime, the WG decided to drop the 2D Canvas section from the HTMLWG
spec, and I've no interest in revisiting that subject."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10921

1.5 Bug 10963: "Table prohibited from being used as a layout aid"
reported by Rich Schwerdtfeger.
Status: Rejected
Change Description: no spec change
Ian's Rationale: "This restriction has been in HTML for over a decade
(and indeed since long before I was even out of high school). Allowing
HTML tables to be used for layout would undo literally over a decade's
worth of accessibility advocacy."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10963
Raised by Rich as Issue-130
http://www.w3.org/html/wg/tracker/issues/130

1.6 Bug 10994: "accessKeyLabel can expose new information about the
user and possibly also other origins" reported by Simon Pieters.
Status: Rejected
Change Description: no spec change
Ian's Rationale: "The increase in information leakage is far smaller
than the increase in usability that will result from this feature,
IMHO."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10994


2. NEEDSINFO BUGS:

2.1 Bug 9876: "Clarify that a figure can be any content with a
caption" reported by James Graham.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Rationale: I don't understand. Could you elaborate?
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9876

2.2 Bug 10713: "Drag and Drop: Add guidance for keyboard-only
interaction" reported by Gez Lemon.
Ian Marked NEEDSINFO on Oct 12.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10713

2.3 Bug 10841: "We require a method to allow the user to control
playback timing in order to have more time to understand the
material." reported by John Foliot.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Rationale: "see comment 1"
Ian's Comment 1: "Could you elaborate? What change to the spec would
satisfy this request, and what problem would that change address,
specifically?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10841#c1

2.4 Bug 10853: "HTML5 lacks a verbose description mechanism" reported
by Gregory J. Rosmaita.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Rationale: Gregory, please see comment 1. Thanks.
Ian's Comment 1: "Why is the <p> element not sufficient?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10853#c1
Shelley added the TrackerRequest keyword.
Sam removed the TrackerRequest keyword as this is already covered by ISSUE-30.

2.5 Bug 10888: "Access Command Requirements for HTML5" reported by
Gregory J. Rosmaita.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Rationale: "see comment 1"
Ian's Comment 1: "Could you clarify exactly what change you are
requesting and what problem that change resolves?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10888#c1

2.6 Bug 10900: "HTML to Platform Accessibility APIs Implementation
Guide" "reported by Steve Faulkner.
Status: "Partially Accepted"
Change Description: no spec change yet"
Rationale: "That seems reasonable. I'll mark this bug NEEDSINFO in the
meantime. Please re-open the bug if a plurality of implementors do
indeed agree that this document is helpful enough to the point that it
should be given the special status of being explicitly referenced from
the spec."

2.7 Bug 10918: "provide better examples" reported by Steve Faulkner.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Rationale: "Do you have any suggestions?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10918

2.8 Bug 10927: "collection of all interactive (actionable, focusable)
elements" reported by Cynthia Shelly.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Rationale: "see comment 2"
Ian's Comment 2: "Could you give an example of a script that would use
such an API? I don't understand the use case."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10927#c2

2.9 Bug 10933: "add link types that create hyperlinks to 7.4.2 Focus
management" reported by Cynthia Shelly.
Status: "Did Not Understand Request"
Change Description: "no spec change"
Rationale: "see comment 1"
Ian's Comment 1: "All links can be focused if the platform focuses
links; why would specific link types be listed here? I don't
understand what problems is being resolved here. Can you describe a
situation where interoperability would be harmed if we don't have this
requirement?"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10933#c1


3. REOPENED BUGS:

3.1 Bug 10988: "add slider element" reported by Jim Michaels.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10988


4. FIXED BUGS:

4.1 Bug 10419: "<video> should allow muted as a content attribute"
reported by Adrian Bateman.
Ian's rationale: "I've added a feature equivalent to the requested
feature, though using a slightly different syntax, for the reasons
discussed in this bug."
Checked in as WHATWG revision r5636.
Check-in comment: Add <video audio=muted>.
http://html5.org/tools/web-apps-tracker?from=5635&to=5636

4.2 Bug 10450: "Allow lists to be used as menus or tab sets" reported
by Maciej Stachowiak.
Ian's rationale: "Maciej did some digging in the ARIA specs and found
the following...The remaining issue in this bug therefore seems to be
handled by bug 10919. I'll fix it there and am returning this bug to
the FIXED state as per comment 1."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450#c19
Steve added the TrackerIssue Keyword for HTML WG Issue 129

4.3 Bug 10919: "Allow role="presentation" to override the default role
of any element" reported by Martin Kliehm.
Ian's rationale: "See bug 10450 comment 19. It seems that the ARIA
spec is very confused on this issue, but in the interests of
expediency, and under the assumption that the ARIA spec will be
corrected to match implementations, I've changed the spec to allow
role=presentation everywhere."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10919
Check-in comment: "Allow role=presentation everywhere"
http://html5.org/tools/web-apps-tracker?from=5632&to=5633

4.4 Bug 11012: "Allow role="presentation" to override the default role
of any element" reported by Leif Halvard Silli.
Ian's rationale: "I added text similar to what you suggest, but I
didn't include the mention of the target="" attribute since opening
new windows leads to a poor user experience (and all the more so to AT
users)."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11012
Check-in comment: suggest another alternative for longdesc
http://html5.org/tools/web-apps-tracker?from=5629&to=5630
Note: This bug went from NEW to ASSIGNED to FIXED this week.


5. ASSIGNED BUGS:

5.2 Bug 10903: "provide an introduction to wai-aria in the wai aria
section of the spec" reported by Steve Faulkner.
Ian assigned this bug to himself.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10903


6. REMIND BUGS:

6.1 Bug 10941: " Media elements need control-independent "pause" for
presenting lengthy descriptions/captions" reported by Masatomo
Kobayashi.
Ian's Rationale: "Without actual implementation experience, it's hard
to know if the suggestion in comment 7 would actually solve the
problem. I agree that we will need to address this. My recommendation
would be to have implementations of audio descriptions experiment with
this to find what the best user experience is. Once we have a clear
solution, then we can update the specification accordingly. We don't
want to specify something prematurely, because doing so would risk
disenfranchising the very people we are trying to help, by requiring
suboptimal behaviour. I've marked this REMIND so that I can check on
it regularly to see if any real-world experience has been obtained.
Feel free to reopen this if a browser vendor implements <video> with
audio descriptions and has found a solution to this problem (either
now or in the future)."
Status: Partially Accepted
Change Description: none yet
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10941


7. INVALID BUGS:

7.1 Bug 10905: "Clarify how assigning an accesskey to an element
affects the elements default role" reported by Steve Faulkner.
Ian's Rationale: "This bug does not seem to request a change to the spec."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10905


8. NEW BUGS:

8.1 Bug 11012: "Also say that <area>/image maps is an alternative to
@longdesc" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11012


9. CLOSED BUGS:

9.1 Bug 9936: "onclick attributes on any element that is not focusable
should trigger a conformance error" reported by Steve Faulkner.
Status: CLOSED NEEDSINFO by Sam Ruby per:
http://lists.w3.org/Archives/Public/public-html/2010Oct/0135.html
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9936

9.2 Bug 9871: "Provide normative advice to conformance checkers about
use of onevent handler attributes" reported by Steve Faulkner.
Status: CLOSED WONTFIX by Sam Ruby per:
http://lists.w3.org/Archives/Public/public-html/2010Oct/0135.html
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9871

9.3 Bug 9872: "Trigger a conformance error when javascript is included
in href attribute" reported by Steve Faulkner.
Status: CLOSED WONTFIX by Sam Ruby per:
http://lists.w3.org/Archives/Public/public-html/2010Oct/0135.html
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9872


10. ESCALATED BUGS:

10.1 Bug 10921: "Put back direct link to the W3C version of the canvas
2d context spec" reported by Steve Faulkner.
Status: RESOLVED WONTFIX
Shelley Powers added the TrackerRequest keyword.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10921

10.2 Bug 10444: "ARIA section does not list elements that have no
default role or role restrictions" reported by Maciej Stachowiak.
Status: RESOLVED WONTFIX
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10444

10.3 Bug 10448: "Consider broadening the set of allowed roles for
command elements" reported by Steve Faulkner.
Status: RESOLVED WONTFIX
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10448

10.4 Bug 10449: "Consider allowing various command-like ARIA roles for
h1-h6" reported by Maciej Stachowiak.
Status: RESOLVED WONTFIX
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449

10.5 Bug 10450: "Allow lists to be used as menus or tab sets" reported
by Maciej Stachowiak.
Status: ASSIGNED
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450

10.6 Bug 10462: "merge ARIA mapping tables and list" reported by Steve Faulkner.
Status: RESOLVED WONTFIX
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10462

10.7 Bug 10481: "Default role of <IMG> should be "img"" reported by
Leif Halvard Silli.
Status: RESOLVED INVALID
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10481

10.8 Bug 10592: "h1 to h6 element that does have an hgroup ancestor
not listed in ARIA section" reported by Steve Faulkner.
Status: RESOLVED WONTFIX
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10592

10.9 Bug 10493: "Allow lists to be used as menus or tab sets" reported
by Steve Faulkner.
Status: RESOLVED FIXED
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10493

10.10 Bug 10594: "conforming use of various aria attributes not
specified" reported by Steve Faulkner.
Status: RESOLVED WONTFIX
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10594

10.11 Bug 10478: "modify table, tr and td roles" reported by Steve Faulkner.
Status: RESOLVED FIXED
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10478

10.12 Bug 10603: "Clarify what default roles UAs may assign to
elements not listed in the ARIA section" reported by  Benjamin
Hawkes-Lewis.
Status: RESOLVED FIXED
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10603

10.13 Bug 10903: "provide an introduction to wai-aria in the wai aria
section of the spec" reported by Steve Faulkner.
Status: ASSIGNED
Steve added the TrackerIssue Keyword for HTML WG Issue 129
http://www.w3.org/html/wg/tracker/issues/129
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10903


11. DEESCALATED BUGS.

11.1. Bug 9077: "Lady of Shalott example doesn't really 'enhance the
themes or subject matter of the page content'" reported by Ian 'Hixie'
Hickson.
Ian's comment: "I won't have time to properly address this issue in
the timeframe given, so I'd rather withdraw this escalation if that's
ok with the chairs."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9077#c8
Bug 9077 had been escalated to Issue 122:
http://www.w3.org/html/wg/tracker/issues/122
Steve had drafted a null change proposal for ISSUE-122:
http://www.w3.org/html/wg/wiki/ChangeProposals/thematicimages


12. "A11yTF" KEYWORD BACKLOG:

We currently have 101 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

One bug on document "HTML5: Techniques for providing useful text
alternatives Bugs" awaits task force decision. Michael(tm) Smith is
editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML:_The_Markup_Language_Reference_Bugs_Awaiting_Decision

One bug on document "HTML Working Group Decision Policy" awaits task
force decision. Maciej Stachowiak, Paul Cotton, Sam Ruby are the
editors of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML_Working_Group_Decision_Policy_Bugs_Awaiting_Decision

No bugs on document on the document "HTML5: Techniques for providing
useful text alternatives Bugs" await task force decision. Steve
Faulkner is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#Text_Alternatives_Techniques_Bugs_Awaiting_Decision


12. 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 Sunday, 17 October 2010 19:20:56 GMT

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