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: Fri, 10 Jun 2011 04:06:39 -0500
Message-ID: <BANLkTikwcb4jLCAu16yVDqjVd6FKb5F_gw@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report we have had:

2 WONTFIX bugs. Details are in section 1.
1 NEEDSINFO bug. Details are in section 2.
2 WORKSFORME bugs. Details are in section 3.
2 REOPENED bugs. Details are in section 4.
8 NEW a11y bugs. Details are in section 5.

Details are as follows.

1. WONTFIX BUGS:

1.1 Bug 12726: "Document should be on the Note-track" reported by Sam
Ruby on behalf of Lachlan Hunt.
Steve's Rationale: "As noted, there is no such distinction such as a
note track and rec track based on whether a document contains
normative requirements or not, it is appropriate to be considered a
recommendation if there is an intention that the document is to be
evolved over time, rather than written and then left to go stale. The
alt spec is definitley a document that is written to provide current
best practice and authoring requirements based on the realities of
browser and assistive technology support for HTML features and as such
will require updating on a regular basis and that is the intention."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12726#c2

1.2 Bug 12906: "Canvas should not pretend that it can be used to
replace some input elements" reported by Tab Atkins Jr.
Ian's Rationale: "Revert requested by the Chairs. Tab, if you want
this back to FIXED, you need to use the escalation path in the
Decision Process."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12906#c4


2. NEEDSINFO BUGS:

2.1 Bug 12727: "Contradicts HTML5" reported by Sam Ruby on behalf of
Lachlan Hunt.
Steve's comment: "The working group has not reached consensus on
whether the HTML5 specification is the canonical source of
requirements or advice in regards to the provision of text
alternatives for images. As editor I intend to identify and note
points of difference in normative requirements and informative advice
between the alt spec and the HTML5 spec, people will then be free to
file bugs against the differences. Differences are due to:
* requirements in HTML5 not taking into account current browser, AT
support realities
* watering down of WCAG 2.0 requirements
* lack of normative and/or informative advice in HTML5 for some use cases
* The requirement and advice deficiencies in the current HTML5 may
result in authors providing inaccessible content."
Change Description: None.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12727#c2


3. WORKSFORME BUGS:

3.1  Bug 12848: "'Subtitle' I am deaf. I love html5, it is wonderful
tool. One problem with html5 video is no subtitle or closed
caption..." reported by contributor at whatwg.com.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12848
Silvia marked this bug WORKSFORME and sent the reporter an email.
http://www.w3.org/Bugs/Public/show_activity.cgi?id=12848
http://lists.w3.org/Archives/Public/public-html-a11y/2011Jun/0033.html

3.2  Bug 12848: "This is not the proper WG for this document" Reported
by Sam Ruby on behalf of Janina Sajka.
Steve's comment: "The argument that due to its content this document
is being developed in the wrong working group must also be applied to
the parts of the HTML5 specification that outline advice and
requirements for the provision of text alternatives, as HTML5 contains
similar requirements and advice. As long as the HTML5 specification
contains such content, the right place for the alt spec is this
working group. There is no obvious impediment to it's further
development and maintenance by interested parties in the WAI just
because it is being developed and maintained as a HTML working group
product."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12728#c1


4. REOPENED BUGS:

4.1 Bug 9213: "HTML5 Lacks a Way to Programmatically-Determine Missing
Text Alternatives" reported by Laura Carlson.
Reopened by Laura Carlson.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9213#c5

4.2 Bug 12141: "<video> Specifically state that all <track> options be
exposed to the end user " reported by John Foliot.
Ian's comment: "Did Not Understand Request"
Change Description: "no spec change".
Rationale: I don't understand. Is this asking about UI requirements or
about API requirements? If there is a confusion here, could someone
who is confused let me know what is misleading them? I'm happy to fix
the spec, I just don't get what's wrong here..."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12141#c11
Reopened by Silvia:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12141#c12


5. NEW BUGS:

5.1 Bug 12873: "suggested addition to *Examples of scenarios where
users benefit from text alternatives for images*" reported by
Michael[tm] Smith on behalf of Reinaldo Ferraz.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12873

5.2 Bug 12874: "question on use of image maps" reported by Michael[tm]
Smith on behalf of Reinaldo Ferraz.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12874

5.3 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[tm] Smith on behalf of Reinaldo Ferraz.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12875

5.4 Bug 12876: "suggestion for Example 6.4" reported by Michael[tm]
Smith on behalf of Reinaldo Ferraz.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12876

5.5 Bug 12877: "remove section 3.11" reported by Michael[tm] Smith on
behalf of Reinaldo Ferraz.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12877

5.6 Bug 12900: "A global attribute "contentaddedbyeditor" would be
incredibly useful when testing for accessibility..." reported by
contributor@whatwg.org.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12900

5.7 Bug 12900: "A global attribute "contentaddedbyeditor" would be
incredibly useful when testing for accessibility..." reported by
contributor@whatwg.org.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12900

5.8 Bug 12906: "Canvas should not pretend that it can be used to
replace some input elements" reported by Tab Atkins Jr.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12906


6. 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 Friday, 10 June 2011 09:07:07 GMT

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