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: Sat, 30 Oct 2010 11:51:17 -0500
Message-ID: <AANLkTinZDdwMBwshODRTWGkqqxKzuKL2W=gbOZ0zVUE1@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>, Michael Cooper <cooper@w3.org>, "Michael(tm) Smith" <mike@w3.org>, Janina Sajka <janina@rednote.net>
Hello Everyone,

Since the last report we have had:

3 ESCALATED bugs. Details are in section 1.
1 ISSUE SCOPE CHANGE of PREVIOUSLY ESCALATED BUGs. Details are in section 2.
2 NEEDSINFO bug resolutions. Details are in section 3.
1 ASSIGNED Drag and Drop bug had several check-ins. Details are in section 4.
1 WORKSFORME bug. Details are in section 5.
1 INVALID bug. Details are in section 6.
1 VERIFIED bug. Details are in section 7.
2 NEW a11y bugs were reported. Details are in section 8.

No bugs were marked fixed, won't fix, remind, later, or closed.

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

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

Details are as follows.

1. ESCALATED BUGS:

Michael Cooper added the TrackerIssue keyword to the following three
bugs and commented: "Bug triage sub-team thinks this is a A11Y TF
priority because it's related to longdesc (ISSUE-30
http://www.w3.org/html/wg/tracker/issues/30). Adding dependency on
10455 to reflect this, and TrackerIssue keyword to reflect
relationship to ISSUE-30. Note the ultimate engineering of longdesc
solutions may or may not support the suggestion in this bug, so this
will have to be addressed when longdesc is complete."

1.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#c3

1.2 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#c7

1.3 Bug 10938: "Add <textual/> - a visible textual substitute element
w/link capability" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10938#c7

MichaelC, since HTML ISSUE 30 has been decided and CLOSED by the HTML
Chairs, a few questions:
 * Why is the bug team escalating bugs to a dead tracker issue?
 * What does the bug team mean by "Note the ultimate engineering of
longdesc solutions may or may not support the suggestion in this bug,
so this will have to be addressed when longdesc is complete."?
 * What does the bug team recommend this task force do to achieve the
"ultimate engineering" and to ensure "longdesc is complete"?
  - Reopen Issue 30?...and if this is the case, how?...what is the action plan?
  - Formally Object to the HTML Chairs' Issue 30 decision?
  - Something else?

Thanks.

Please note that longdesc research continues for John Foliot's Formal Objection:

 * Examples In the Wild (well over 100 sites using longdesc)
   http://www.d.umn.edu/~lcarlson/research/ld.html#wild
 * Guidelines, Laws, Policy, and Standards
   http://www.d.umn.edu/~lcarlson/research/ld.html#glps
 * Tools (browsers, assistive technology, authoring tools)
   http://www.d.umn.edu/~lcarlson/research/ld.html#tools
 * Online Tutorials and Documentation
   http://www.d.umn.edu/~lcarlson/research/ld.html#tutorials
 * HTML5 ISSUE 30 Info:
   http://www.d.umn.edu/~lcarlson/research/ld.html#issue
 * Notice of Impending Formal Objection to HTML5 Issue 30 Decision
(@longdesc) - John Foliot
  http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0027.html

Question to the Task Force Chairs:
Janina and Mike, Will the Accessibility Task Force be formally
supporting John's longdesc Formal Objection? Is this something that
this group will help John pursue?


2. ISSUE SCOPE CHANGE of PREVIOUSLY ESCALATED BUGs.

2.1  Bugs 9077 and 9081 "Lady of Shalott examples..." were escalated
to HTML ISSUE 122.

The HTML Chairs expanded ISSUE 122 to apply to ALL HTML Working Group
deliverables. Counter-proposals, alternate proposals and revised
proposals are due by November 27.
http://lists.w3.org/Archives/Public/public-html/2010Oct/0393.html

If the HTML Chairs find, "that we have WG consensus on the statement
mentioned in the  top only Change Proposal that we have to date,
namely 'Do not make it non-conforming in HTML5 for authors to provide
text alternatives for  images considered to enhance the themes or
subject matter of the page content', then we would expect every WG
document to be updated to match that consensus. Given that the two
documents are inconsistent, we expecting each change proposal to
describe at least one set of changes which makes these documents
consistent."
http://lists.w3.org/Archives/Public/public-html/2010Oct/0400.html

http://www.w3.org/html/wg/tracker/issues/122
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9077
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9081


3. NEEDSINFO BUGS:

3.1 Bug 10777: "User agent assignment of modifier keys subset of
accesskey processing subset" reported by Gregory J. Rosmaita.
Joshue O Connor changed the status on this bug from WONTFIX to
NEEDSINFO and commented: "The HTML A11y Bug Triage Subteam decided
that this not an issue and that Gregory should escalate this bug if he
feels it is warranted."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10777#c2

3.2 Bug 10778: "Use element.accessKeyLabel to generate list of
available accesskeys" reported by Gregory J. Rosmaita.
Joshue O Connor changed the status on this bug from WONTFIX to
NEEDSINFO. No bug comment provided.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10778


4. ASSIGNED BUG:

4.1 Bug 10712: "Drag and Drop: Add an attribute to identify drop
targets" reported by Gez Lemon.
This bug has had several check-ins by contributor@whatwg.org:

* "dropzone 1/5: the new model"
http://html5.org/tools/web-apps-tracker?from=5645&to=5646
* "dropzone 2/5 and 3/5: Update the spec to use the new DND model. In
theory, this makes no normative difference, but I'm sure  made some
mistakes... let me know if you spot any."
http://html5.org/tools/web-apps-tracker?from=5646&to=5647
* "dropzone 4/5, part 1: DataTransferItems (WIP); also contains some
WebIDL terminology fixes"
http://html5.org/tools/web-apps-tracker?from=5649&to=5650
* "dropzone 4/5, part 2/2: DataTransferItem"
http://html5.org/tools/web-apps-tracker?from=5650&to=5651
* "dropzone 4/5, part, um, 3/2: some bits I somehow missed in the
previous checkin. Oops."
http://html5.org/tools/web-apps-tracker?from=5651&to=5652
* "dropzone 5/5, part 1: skeleton of dropzone='' section; update DND
processing model; enumerate where sections that need updating."
http://html5.org/tools/web-apps-tracker?from=5657&to=5658
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10712


5. WORKSFORME BUG:

5.1 Bug 10988: "add slider element" reported by Jim Michaels.
Jim Michaels changed Status to RESOLVED WORKSFORME.
Change Description:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10988#c29


6. INVALID BUG:

6.1 Bug 10935: "Consider 10.4 Bindings impact on UAG" reported by
Cynthia Shelly on the alt techniques spec.
Steve's Rationale: "This is not a bug about the alt techniques so am
closing it."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10935#c1


7. VERIFIED  BUG.

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 Decision Policy for details:
http://dev.w3.org/html5/decision-policy/decision-policy.html#states-and-keywords

7.1 Bug 10919: "Allow role="presentation" to override the default role
of any element" reported by Martin Kliehm.
VERIFIED NEEDSINFO by Martin.
http://www.w3.org/Bugs/Public/show_activity.cgi?id=10919
No comment provided.


8. NEW BUGS:

8.1 Bug 11140: "Physical Keys and Gestures for "accesskey" attribute"
reported by contributor@whatwg.org.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11140

8.2 Bug 11152: "Polyglot spec should mention accessibility" reported
by Tony Ross.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11152


9. "A11yTF" KEYWORD BACKLOG:

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


10. 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 Saturday, 30 October 2010 16:51:54 GMT

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