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, 10 Oct 2010 06:13:47 -0500
Message-ID: <AANLkTim=YX9RoUfQtetiOaFE=Bo-W+Zk-SRed_t1aig3@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report we have had:

2 WONTFIX bug resolutions. Details are in section 1.
8 NEEDSINFO bug resolution. Details are in section 2.
1 WORKSFORME bug resolution. Details are in section 3.
3 FIXED bug resolutions. Details are in section 4.
3 ASSIGNED bugs. Details are in section 5.
3 NEW a11y bugs reported. Details are in section 6.
6 VERIFIED bugs. The bug team verified four and Ms2ger verified two.
Details are in section 7.

The latest A11y Resolved Bug Comparison is at:
http://www.d.umn.edu/~lcarlson/html5bugchart/20101009/

22 total NEW a11y bugs existed on October 9, 2010. A October 9 bug
snapshot is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20101009

A backlog of 106 a11y bugs on the HTML5 Spec await task force decision
of whether to apply the a11ytf keyword or not.

Details are as follows.


1. WONTFIX BUGS:

1.1 Bug 10906: "make the conforming use of placeholder dependent on
the presence of a label" reported by Steve Faulkner.
Ian's Rationale: "There's no problem here. Yes, browsers have to
implement their UI accessibly, but the spec doesn't preclude that."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10906

1.2 Bug 10917: "modify user agent requirement for details element"
reported by Steve Faulkner.
Ian's Rationale: "closed per comment 2"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10917#c2


2. NEEDSINFO BUGS:

2.1 Bug 10693: "Need a means for navigating between related timed
tracks of media elements" reported by Silvia Pfeiffer.
Sam Ruby's comment: "NEEDSINFO is the correct state for a bug 'with
more details forth coming'.  Please do not REOPEN until sufficient
information is present for the bug to be evaluated."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10693

2.2 Bug 10709: "@title should be a required attribute for FRAME and
IFRAME in HTML5" reported by Gregory J. Rosmaita.
Sam Ruby's comment: "NEEDSINFO is the correct state for a bug 'with
more details forth coming'.  Please do not REOPEN until sufficient
information is present for the bug to be evaluated."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10709

2.3 Bug 10840: "Allow the user to independently adjust the volumes of
the audio description and original soundtracks."reported by John
Foliot.
Ian marked this bug: "NEEDSINFO" on October 6th. No comment.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10842

2.4 Bug 10842: "Support the isolation of speech from other background
sounds in AV media" reported by John Foliot.
Sam Ruby's comment: "NEEDSINFO is the correct state for a bug 'with
more details forth coming'.  Please do not REOPEN until sufficient
information is present for the bug to be evaluated."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10842

2.5 Bug 10843: "Support user control over the visual presentation of
caption text" reported by John Foliot.
Ian's comment: "I don't understand. Could you elaborate?"
Change Description: "no spec change."
http://www.w3.org/Bugs/Public/show_activity.cgi?id=10843

2.6 Bug 10849: "provide means to add image content catagories to
images" reported by Steve Faulkner.
Ian's comment: "Before we add new features we should make sure that we
have implementor interest. I presume ATs are the target implementation
class here; can we get confirmation from AT vendors that they are
interested in implementing this feature?."
Change Description: "Did Not Understand Request. no spec change"
http://www.w3.org/Bugs/Public/show_activity.cgi?id=10849

2.7 Bug 10938: "Add <textual/> - a visible textual substitute element
w/link capability" reported by Leif Halvard Silli.
Ian's comment: "Did Not Understand Request...What's wrong with using
<a href=""> for this, possibly with a rel="" value if necessary?"
Change Description: "no spec change".
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10938

2.8 Bug 10964: "Canvas needs to support a backing store in the DOM
subtree capable of supporting screen reading" reported by Rich
Schwerdtfeger.
Change Description: "no spec change".
Ian's comment: "Did Not Understand Request. Change Description: no
spec change. Concurred with comment 2"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10964


3. WORKSFORME BUGS:

3.1 Bug 10932: "add area to 7.4.2 Focus management" reported by Cynthia Shelly.
Ian's Rationale: "<area> is more complicated for historical reasons
and is instead listed in the paragraph immediately following the
list."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10932


4. FIXED BUGS:

4.1 Bug 10775: "how is user to decide which set of access keys to
use?" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10775#c5
Check-in comment: "Explain accesskey better."
http://html5.org/tools/web-apps-tracker?from=5595&to=5596

4.2 Bug 10915: "clarify why a command element that is not in a menu is
conforming" reported by Steve Faulkner.
Ian's rationale: "I don't want to hardcode the states for <command>s
in random places because that would preclude later using the
command="" attribute idea with <command>s in random places."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10915#c1
Check-in comment: "mention what <command> can be used for"
http://html5.org/tools/web-apps-tracker?from=5581&to=5582

4.3 Bug 10931: "Add details or summary to focus management section"
reported by Cynthia Shelly.
Ian's Rationale: "It's not <details> or <summary> that are focusable,
so much as the disclosure widget that <details> exposes. However, I've
made sure the spec mentions this."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10931#c1
Check-in comment: "<details> has a focusable component."
http://html5.org/tools/web-apps-tracker?from=5585&to=5586


5. ASSIGNED BUGS:

5.1 Bug 10919: "Allow role="presentation" to override the default role
of any element for presenting lengthy descriptions/captions" reported
by Martin Kliehm.
Assigned To: Ian 'Hixie' Hickson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10919
	
5.2 Bug 10927: "collection of all interactive (actionable, focusable)
elements" reported by Cynthia Shelly.
Assigned To: Ian 'Hixie' Hickson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10927

5.3 Bug 10941: "Media elements need control-independent "pause" for
presenting lengthy descriptions/captions" reported by Masatomo
Kobayashi.
Assigned To: Ian 'Hixie' Hickson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10941


6. NEW BUGS:

6.1 Bug 10967: "Add @desclink, a description link attr. for any
embedded element + figure" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10967

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

6.3 Bug 10994: "accessKeyLabel can expose new information about the
user and possibly also other origins" reported by Simon Pieters.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10994


7. VERIFIED BUGS:

The following bugs were marked "VERIFIED" by the bug subteam. Marking
a bug VERIFIED starts a TWO WEEK clock to take action. If no action is
taken, the bug is marked NoReply. A NoReply puts a bug in a terminal
state. See the HTMLWG Descion Policy for details:
http://dev.w3.org/html5/decision-policy/decision-policy.html#states-and-keywords

7.1 Bug 8622: "Activation behaviour and pre-click activation" reported
by Gez Lemon.
VERIFIED NEEDSINFO by Joshue O Connor.
Josh's comment: "Related issues are addressed in more precise bugs, for example
http://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywords_type=allwords&keywords=a11y_focus"
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8622#c4

7.2 Bug 8737: "Allowing option with no value to be a command"
reported by Gez Lemon.
VERIFIED INVALID by Ms2ger.
No comment made.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8737

7.3 Bug 8740: "How do pseudo-class selectors interact with WAI-ARIA?"
reported by by Gez Lemon.
VERIFIED NEEDSINFO by Michael Cooper.
Michael's comment: "Bug triage sub-team has decided that this bug does
not need to be addressed in the context of the HTML specification, but
can be incorporated into the ARIA to HTML mapping document that is
under development."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8740#c6

7.4 Bug 8753: "Undo for drag and drop" reported by by Gez Lemon.
VERIFIED INVALID by Ms2ger.
No comment made.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8737

7.5 Bug 10605: "Typo: Replace 'the alt attribute's value may be
omitted' with '@alt may be omitted'" reported by Leif Halvard Silli.
VERIFIED FIXED by Martin Kliehm.
Martin's comment: "Confirmation that this change made it into the W3C spec."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10605#c3

7.6 Bug 10649: "drag and drop" reported by contributor.
VERIFIED INVALID by Martin Kliehm.
Martin's comment: "Confirming that this is not a bug report."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10649#c2


8. "A11yTF" KEYWORD BACKLOG:

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


13. 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, 10 October 2010 11:14:21 GMT

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