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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 19 Sep 2010 06:10:12 -0500
Message-ID: <AANLkTi=81WzRErnWZcBSmh8dJtaaCs_AeChjhTOUEBmM@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since the last report no bugs were resolved FIXED or REOPENED. None
were marked WONTFIX, NEEDSINFO, WORKSFORME, LATER, or DUPLICATE.

The latest A11y resolved bug comparison is at:
http://www.d.umn.edu/~lcarlson/html5bugchart/20100918/

Seven NEW a11y bugs were reported since the last report. Section one
below provides details.

Twenty-six total NEW a11y bugs in total existed on September 18, 2010.
A September 18 bug snapshot is at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20100918

One bug was marked INVALID since the last report. Section two below
provides details.

Three bugs were marked "VERIFIED WONTFIX" by the bug subteam. Marking
a bug VERIFIED starts a TWO WEEKS clock to take action. If no action
is taken, the bug is marked NoReply. A NoReply puts a bug in a
terminal state.  Section three provides details on how that works and
the particular bugs placed in that state since the last report.

A backlog of sixty-one a11y bugs on the HTML5 Spec await task force
decision of whether to apply the a11ytf keyword or not. Section four
provides details on VERIFIED bugs.

Full details are as follows.


1. NEW BUGS:

1.1 Bug 10603: "Clarify what default roles UAs may assign to elements
not listed in the ARIA section" reported by Benjamin Hawkes-Lewis.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10603

1.2 Bug 10604: "Don't say 'empty' about @alt anywhere, say 'empty
string' everywhere" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10604

1.3 Bug 10605: "Typo: Replace 'the alt attribute's value may be
omitted' with '@alt may be omitted'" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10605

1.4 Bug 10606: "Define what alt="<whitespace>" means for <img>"
reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10606

1.5 Bug 10618: "Use "unmapped" rather than "no role" in the
weak/strong ARIA tables" reported by Leif Halvard Silli.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10618

1.6 Bug 10642: "No alternative text description for video key frame
(poster)" reported by Everett Zufelt.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10642

1.7 Bug 10645: "Add a modal element, or attribute, to html5 to
indicate a modal segment of the DOM (modal dialog)" reported by
Everett Zufelt.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10645


2. INVALID BUGS:

2.1 Bug 10649: "drag and drop" reported by contributor@whatwg.org.
Anne marked 10649 INVALID commenting "Not a bug report."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10645


3. VERIFIED BUGS:

When a bug is placed in the VERIFIED state, the editor's response
should be reviewed and one of following actions should be taken.
 * Reopen the bug. (Anyone can do this.)
 * Apply the "TrackerRequest" keyword. (Anyone can do this.)
 * Apply the "TrackerIssue" keyword. (Anyone with HTML WG Tracker
privileges can do this.)
 * Close the bug.

TWO WEEKS are allowed from the time a bug is marked VERIFIED to take
action. If no action is taken, the bug is marked NoReply. A NoReply
puts a bug in a terminal state. For more information consult the HTML
Working Group Decision Policy:
http://dev.w3.org/html5/decision-policy/decision-policy.html#bugzilla-bug

The bug team placed the following three bugs in the VERIFIED state.

3.1 Bug 8674: "Add popup as a value for the type attribute for menu
element" reported by Gez Lemon.
VERIFIED WONTFIX added by Michael Cooper on behalf of the bug triage
team saying, "Bug triage sub-team thinks the approach in the editor
response addresses the issue."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8674#c4

3.2 Bug 8681: "Separator menu items" reported by Gez Lemon.
VERIFIED WONTFIX added by Martin Kliehm on behalf of the bug triage
team saying: "The specification says that an option with an empty
value, disabled state and one or more hyphens as text creates a
seperator node. Since the option is disabled it will not effect screen
readers and is purely presentational. The HTML Accessibility TF Bug
Triage Sub-team does not consider this as an accessibility issue and
proposes to close the bug."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8681#c3

3.3 Bug 8754: "Overflow when text is resized" reported by Gez Lemon.
VERIFIED WONTFIX added by Michael Cooper on behalf of the bug triage
team saying, "Bug triage sub-team accepts disposition of this issue.
There is a general user agent issue, but we believe this should be
addressed in Implementing UAAG 2.0 and will refer this to the UAWG."
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8754#c4


4. "A11yTF" KEYWORD BACKLOG:

We currently have sixty-one HTML5 Spec bugs awaiting task force
decision of whether to apply the a11ytf keyword or not. They are
listed in the Wiki at:
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 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


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/

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 Sunday, 19 September 2010 11:10:47 GMT

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