- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Fri, 24 Jun 2011 06:54:01 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since the last report we have had: 3 WONTFIX bugs. Details are in section 1. 1 FIXED bugs. Details are in section 2. 1 REOPENED bug. Details are in section 3. 3 NEW a11y bugs. Details are in section 4. Details are as follows. 1. WONTFIX BUGS: 1.1 Bug 12545: "<video> MEDIA CONTROLLER requires loop attribute for grouped multitrack" reported by John Foliot. Ian's Rationale: "Not supporting this was intentional: completeness is not a use case, and only makes sense when it would be simpler than the alternative, which is not the case here." http://www.w3.org/Bugs/Public/show_bug.cgi?id=12545 1.2 Bug 12546: "<video> MEDIA CONTROLLER requires autoplay attribute for grouped multitrack" reported by John Foliot. Ian's Rationale: "see comment 2" http://www.w3.org/Bugs/Public/show_bug.cgi?id=12546 1.3 Bug 12547: "<video> MEDIA CONTROLLER requires readyState for grouped multitrack" reported by John Foliot. Ian's Rationale: "see comment 2" http://www.w3.org/Bugs/Public/show_bug.cgi?id=12547 2. FIXED BUGS: 2.1 Bug 12548: "<video> MEDIA CONTROLLER requires onended event" reported by John Foliot. Ian's rationale: "Concurred with reporter's comments." http://www.w3.org/Bugs/Public/show_bug.cgi?id=12548 Check-in comment: "Provide an .onended event handler for MediaController to expose the event more easily." http://html5.org/tools/web-apps-tracker?from=6246&to=6247 3. REOPENED BUGS: 3.1 Bug 12405: "<video> There's a problem with overlaying a sign-language video and using native controls, because the overlaid video overlaps the native controls" reported by contributor@whatwg.org Ian's Rationale for not fixing: "This isn't a problem specific to sign language tracks - it applies to everything that might be overlaid on the video, if the UA renders the controls at the z-index of the video element. So the UA shouldn't do that. :-) " http://www.w3.org/Bugs/Public/show_bug.cgi?id=12405 Reopened by Simon Pieters. Simon's comment: "The rendering section doesn't say to use a different z-index for the native controls." http://www.w3.org/Bugs/Public/show_bug.cgi?id=12405#c6 4. NEW BUGS: 4.1 Bug 12971: "A lot of times, perhaps the majority of the time, authors use <em> or <strong> to make text italic or bold, when in fact the intention has nothing to do with emphasizing or strongly emphasizing the text. The result is terrible in aural browsers..." reported by contributor@whatwg.org http://www.w3.org/Bugs/Public/show_bug.cgi?id=12971 Aryeh Gregor (Simetrical+w3cbug@gmail.com) marked this bug WORKSFORME. http://www.w3.org/Bugs/Public/show_activity.cgi?id=12971 4.2 Bug 12984: "Contributions to HTML5: Techniques for providing useful text alternatives" Reported by Steve Faulkner. http://www.w3.org/Bugs/Public/show_bug.cgi?id=12984 4.3 Bug 13023: "New: removing CSS outline bad for accessibility" Reported by HTML WG bugbot on behalf of Reinaldo Ferraz. http://www.w3.org/Bugs/Public/show_bug.cgi?id=13023 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 Friday, 24 June 2011 11:54:29 UTC