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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sat, 1 Jan 2011 06:59:10 -0600
Message-ID: <AANLkTi=2sX22bEq3O+-baSQkPcjGuLUMYW=4b62G460N@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

1. PRE-LAST CALL BUGS:

Fifty-One Pre-Last Call 1 accessibility task force (a11ytf) bugs exist
which have not been escalated to the HTML Tracker or marked "verified"
or marked "closed" as of January 1, 2011.

A detailed snapshot of these fifty-one bugs is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/SnapshotPLC1_20110101

Please check the snapshot details for bugs that you may have reported
and for bugs that may have been have been assigned to you. Please
close bugs that are satisfactorily resolved. Those not satisfactorily
resolved can be escalated to an issue. This will enable the full HTML
Working Group the ability to address the problem and the HTML Chairs
the ability to make a decision.

January 22, 2011 is the deadline for escalating Pre-Last Call 1 bugs
to a HTML WG Issue if the reporter, or the task force, or any
individual working group member for that matter, is not satisfied with
the editor's resolution. For details on escalating a Bug to an Issue
please refer to the instructions at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Escalating_a_Bug_to_an_Issue

Consequences of missing the January 22 deadline is that any further
escalations will be treated as Last Call comments.


2. "A11yTF" KEYWORD BACKLOG:

A backlog of 25 a11y bugs on the HTML5 Spec await task force decision
of whether to apply the "a11ytf" keyword or not. The majority of them
are Pre-Last Call 1 Bugs.
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


3. POST LAST CALL BUG ACTIVITY SINCE LAST REPORT:

Since the last report one a11y bug was marked INVALID, one was marked
WONTFIX, one was marked LATER. No new a11y bugs were reported.

3.1 INVALID BUG:

Post Last Call Bug 11238: "Enable canvas to support accessible rich
text editing" reported by Rich Schwerdtfeger.
Ian's Rationale: "Please file only one issue per bug...Note that as a
general rule, it is not good design to provide features to help
authors abuse other features. Authors who use just <canvas> and
JavaScript to create applications are abusing HTML, and should not be
supported."
Change Description: no spec change
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11238

3.2 WONTFIX BUG:

Post Last Call Bug 11140: "Physical Keys and Gestures for 'accesskey'
attribute The use of ASCII/Unicode code points for key binding has
numerous well-known drawbacks. There are vital physical keyboard keys
with no Unicode representation..." reported by contributor.
Ian's Rationale: "Support for keywords to reference specific things,
e.g. gestures or special keys (like F1), is something that is
intentionally left open for a future version, but before we go there
we really need more experience with the changes we've done so far."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11140

3.3 LATER BUG:

Post Last Call Bug 11199: "Need standard way to creating heading
streams" reported by Laurent Goderre.
Ian's Rationale: "As noted by reporter in comment 11, we should
revisit this for a future version."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11199


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

Pre-Last Call 1 Bug Snapshots
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/SnapshotPLC1

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

Best Regards,
Laura

--
Laura L. Carlson
Received on Saturday, 1 January 2011 12:59:46 GMT

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