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

Re: Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Mon, 13 Dec 2010 06:53:38 -0600
Message-ID: <AANLkTinVuTq4odrjU+4jBhBk+fXPkD6yhuCo7Ggkksky@mail.gmail.com>
To: Paul Cotton <Paul.Cotton@microsoft.com>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi Paul,

On 12/11/10, Paul Cotton <Paul.Cotton@microsoft.com> wrote:
> It would probably be useful to split this analysis to separately cover
> pre-Last Call bugs and those that are Last Call bugs.  For example WG
> members now have until Jan 22 to escalate any pre-Last Call bugs [1] for
> which they disagree with the current disposition.  It would be a shame to
> miss that date for a A11Y bug for the sake of spending time on Last Call
> bugs for which we have a MUCH longer time to worry about.
>
> /paulc
>
> [1] http://lists.w3.org/Archives/Public/public-html/2010Sep/0074.html

All bugs listed are pre-Last Call bugs with the exception of the one new bug.

Best Regards,
Laura


> -----Original Message-----
> From: public-html-a11y-request@w3.org
> [mailto:public-html-a11y-request@w3.org] On Behalf Of Laura Carlson
> Sent: Saturday, December 11, 2010 11:42 AM
> To: HTML Accessibility Task Force
> Subject: Weekly Resolved & Rejected Bugs Report
>
> Hello Everyone,
>
> Since the last report we have had:
>
> One WONTFIX bug resolutions. Details are in section 1.
> One NEEDSINFO bug resolution. Details are in section 2.
> Three FIXED bug resolutions. Details are in section 3.
> One LATER bug. Details are in section 4.
> One NEW a11y bug reported. Details are in section 5.
>
> A backlog of 58 a11y bugs on the HTML5 Spec await task force decision of
> whether to apply the a11ytf keyword or not. Details are in section 11.
>
> 15 total NEW a11y bugs existed on December 11, 2010. A December 11 bug
> snapshot is at:
> http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20101211
>
> Details are as follows.
>
>
> 1. WONTFIX BUGS:
>
> 1.1 Bug 10451: "Consider restricting the roles allowed for the label
> element" reported by Maciej Stachowiak.
> Reopened by Martin Kliehm per Comment:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10451#c3
> Ian then re-resolved it WONTFIX.
> Ian's Rationale: "alert, log, marquee, status and timer make no sense for
> <label>. presentation is already allowed. If this is to be handled in an
> issue, then the bug should not be open."
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10451#c5
>
>
> 2. NEEDSINFO BUGS:
>
> 2.1 Bug 9452: "Handling of additional tracks of a multitrack audio/video
> resource" reported by Silvia Pfeiffer.
> Maciej changed the status to NEEDSINFO and Paul added the TrackerRequest
> keyword.
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=9452
>
>
> 3. FIXED BUGS:
>
> 3.1 Bug 10168: "Please consider adding a section on role="presentation""
> reported by Laura Carlson on the Text Alternatives Techniques Spec.
> Status: partially accepted by Steve Faulkner.
> Change Description: "example of role="presentation" will be added to spec".
> Steve's Rationale: "agree that its use should be explained."
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10168#c2
> I don't see an addition yet in:
> http://dev.w3.org/html5/alt-techniques/
>
> 3.2 Bug 10489: "Use or @role is not mentioned as single time in the draft"
> reported by Leif Halvard Silli on the Text Alternatives Techniques Spec.
> Status: partially accepted by Steve Faulkner.
> Change Description: "will add examples of role use to spec."
> Steve's Rationale: "agree that examples of role use would be beneficial to
> understanding their for the provision of text alternatives".
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10489#c3
> I don't see an addition yet in:
> http://dev.w3.org/html5/alt-techniques/
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10489
>
> 3.3 Bug 10660: "use < and > and not &#8592; and &#8594; to indicate previous
> and next" reported by Gregory J. Rosmaita.
> Status: Accepted.
> Mike Smith's cooment: "Updated the spec splitter such that arrows in the
> next/previous links are now generated using CSS, as described in comment
> 6...The solution Michael Cooper proposed in comment 6 seems to be the best
> way to address the original request from Gregory."
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10660#c7
> http://dev.w3.org/cvsweb/html5/spec/tools/spec-splitter.py.diff?r1=1.7&r2=1.8&f=h
>
>
> 4. LATER BUGS:
>
> 4.1 Bug 11027: "Provide text alternatives for images feedback from Everett
> Zufelt" reported by Everett Zufelt on the Text Alternatives Techniques
> Spec.
> Status: accepted
> Change Description: "In process of adding additional examples of decorative
> image use to spec text."
> Steve's Rationale: agree that these are important considerations.
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11027
>
>
> 5. NEW BUGS:
>
> 5.1 Bug 11473: "Clarify proper tabindex usage" reported by Peter Winnberg.
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=11473
>
>
> 6. "A11yTF" KEYWORD BACKLOG:
>
> We currently have 58 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
>
> Two bugs 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
>
>
> 7. 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
>
>
>


-- 
Laura L. Carlson
Received on Monday, 13 December 2010 12:54:11 GMT

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