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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Thu, 30 Jun 2011 18:14:23 -0500
Message-ID: <BANLkTimMK5sn=NpF1q+Vo6+2MPGyspjXXQ@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

This is my last bug report. I hope that the task force co-facilitators
have found someone to continue these reports. Thanks for the
opportunity to have contributed to this aspect of task force work. Now
on to the report.

Since the last report we have had:

2 NEEDSINFO bugs. Details are in section 1.
1 FIXED bug. Details are in section 2.
2 NEW a11y bugs. Details are in section 3.

A backlog of eleven a11y bugs on the HTML5 Spec await the Bug Team's
decision of whether to apply the a11ytf keyword or not. An additional
backlog of ten a11y bugs on the Text Alternatives Techniques spec
await the Bug Team's decision of whether to apply the a11ytf keyword
or not. Details are in section 4.

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

Details are as follows.

1. NEEDSINFO BUGS:

1.1 Bug 12900: "A global attribute "contentaddedbyeditor" would be
incredibly useful when testing for accessibility..." reported by
contributor at WHATWG.
Aryeh Gregor marked this bug NEEDSINFO. Aryeh's comment: "I don't
understand the use-case. Please explain what this attribute would
actually be used for in practice. If possible, please give examples of
real-world web pages or software that would use it, and explain
exactly how they would use it, and what problems they face without it.
 Note that if the attribute is only intended for use by internal
processing tools, and not browsers or search engines or other things
that aren't under the author's control, there's no need for
standardization -- that's exactly what data-* is meant for."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12900

1.2 Bug 12875: "remove the link *Providing a text alternative that is
not null. (e.g., alt="spacer" or alt="image") for images that should
be ignored by assistive technology [WCAG20-TECHS]*." reported by
Michael Smith on behalf of Reinaldo Ferraz.
Steve's rationale: "Unsure about what the issue with the linked
reference is, can you provide more explanation?..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12875#c1


2. FIXED BUG:

2.1 Bug 12776: "Define process for deciding whether a draft is
REC-track or Note-track" reported by Maciej Stachowiak.
Maciej marked this bug fixed and commented "Defined here as per
comment #1: http://dev.w3.org/cvsweb/html5/decision-policy/decision-policy-v2.html.diff?r1=1.34&r2=1.33&f=h
"
Note 5.d: "If both sides provide rationale, we hold a survey. Since
this is a process, not a technical decision, the survey is by
individual not organization, and subject to quorum requirements,
majority wins. If we do not achieve quorum, the Chairs will decide
whether to re-run the survey or table the issue."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12776#c1


3. NEW BUGS:

3.1 Bug 13096: "Enhancement: Set single component for pixel" reported
by J. Chetwynd.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13096

3.2 Bug 13103: "Visual formatting of content inside the pre element
isn't available to assistive technologies" reported by Leonie Watson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13103


4. "A11yTF" KEYWORD BACKLOG:

We currently have eleven HTML5 Spec bugs awaiting the bug team's
decision of whether to apply the a11ytf keyword or not.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

We currently have ten bugs on the document "HTML5: Techniques for
providing useful text alternatives Bugs" awaiting the bug team's
decision  of whether to apply the a11ytf keyword or not.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#Text_Alternatives_Techniques_Bugs_Awaiting_Decision


5. 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/

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

Bug Triage Team:
http://www.w3.org/WAI/PF/HTML/wiki/Bug_Triage

Bug Triage Team Minutes:
http://www.w3.org/WAI/PF/HTML/wiki/Bug_Triage#Minutes

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 Thursday, 30 June 2011 23:14:50 GMT

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