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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 26 Sep 2010 04:32:11 -0500
Message-ID: <AANLkTi=pHHdQ-XxKOEZqbz5jVCzgnfeLX0n_2hs7d=mO@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report we have had one WONTFIX bug resolution. No other
bugs were resolved*. Seven NEW a11y bugs were reported.

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

Thirty-three total NEW a11y bugs existed on September 25, 2010. A
September 25 bug snapshot is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20100925

A backlog of sixty-eight a11y bugs on the HTML5 Spec await task force
decision of whether to apply the a11ytf keyword or not:

*NOTE: The data for this report was pulled before the Ian started
working bugs on Saturday. I'll catch those in next week's report.

Details are as follows.


1. WONTFIX BUGS:

1.1 Bug 10657: "integration of aria-autocomplete with the various
autocompletion mechanisms in html5" reported by Steve Faulkner.
Ian's Rationale: "Rationale: The request seems to be based on a
misunderstanding of the purpose of ARIA, as described in comment 1. I
would recommend rephrasing this request as a problem statement,
explaining it is that needs fixing, rather than saying what the fix
should be. In general it's very hard to evaluate proposals without
knowing what the problem is. In this particular instance, for example,
it's very much unclear what the problem is: what is it that is
inaccessible? What kind of Web pages would exhibit this problem?
Sample markup showing the problem would be useful; even better would
be examples of real Web pages demonstrating the problem."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10657


2. NEW BUGS:

2.1 Bug 10657: "integration of "aria-autocomplete" with the various
autocompletion mechanisms in html" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10657

2.2 Bug 10660: "use < and > and not &#8592; and &#8594; to indicate
previous and next" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10660

2.3 Bug 10661: "use an ISO 639-2 specified language for HTML5
documents" reported by Gregory J. Rosmaita.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10661

2.4 Bug 10693: "Need a means for navigating between related timed
tracks of media elements" reported by Silvia Pfeiffer.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10693

2.5 Bug 10710 : "Require controls to have programatically associated
names" reported by  Benjamin Hawkes-Lewis.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10710

2.6 Bug 10712: "Drag and Drop: Need a means for navigating between
related timed tracks of media elements" reported by Gez Lemon.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10712

2.7 Bug 10713: "Drag and Drop: Add guidance for keyboard-only"
reported by Gez Lemon.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10713


3. "A11yTF" KEYWORD BACKLOG:

We currently have sixty-eight 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

__ 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

__ 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/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


4. 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, 26 September 2010 09:32:44 GMT

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