This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.
Bugs/New A11Y Bug Snapshot 20100821
New A11Y Bug Snapshot as of August 21, 2010
|Bug id||Open Date||Number of Days Open as of August 21, 2010||Reporter||Bug Status||Component||Short Description||Number Count|
|9452||4/9/10 8:firstname.lastname@example.org||NEW||HTML5 spec (editor: Ian Hickson)||Handling of additional tracks of a multitrack audio/video resource||1|
|9471||4/9/10 22:email@example.com||NEW||HTML5 spec (editor: Ian Hickson)||Introduce declarative markup to associate timed text resources with media elements||2|
|9589||4/25/10 2:firstname.lastname@example.org||NEW||HTML5 spec (editor: Ian Hickson)||HTML5 should give examples for how to present @title when the user can't use a pointing device||3|
|9623||4/30/10 0:email@example.com||NEW||HTML5 spec (editor: Ian Hickson)||<details> and <summary> are missing from the "strong aria semantics" table||4|
|9773||5/20/10 9:firstname.lastname@example.org||NEW||HTML5 spec (editor: Ian Hickson)||There is not a clear difference between "subtitles" and "captions". These are mostly used to describe "closed captions" (binary transmissions in TV broadcasts) vs "subtitles" (text files), as far as I know.||5|
|9774||5/20/10 9:email@example.com||NEW||HTML5 spec (editor: Ian Hickson)||"consecutive lines displayed below each other" - since subtitles tend to be rendered at the bottom, it's actually better for new subtitles to be rendered higher up. Of course, the individual lines of each subtitle still extend downwards, but it's still po||6|
|9775||5/20/10 9:firstname.lastname@example.org||NEW||HTML5 spec (editor: Ian Hickson)||"positioned to a multiple of the line dimensions of the first line of the cue" - enforcing the same line height for every line ihurts text rendering appearance for no apparent reason. This is especially true if text styling is supported (bold text is larg||7|
|9817||5/27/10 18:email@example.com||NEW||HTML5 spec (editor: Ian Hickson)||Details element Focus problem||8|
|9876||6/8/10 9:firstname.lastname@example.org||NEW||HTML5 spec (editor: Ian Hickson)||Clarify that a figure can be any content with a caption||9|
|10026||6/28/10 20:email@example.com||NEW||HTML5 spec (editor: Ian Hickson)||Scope attribute for TD||10|
|10066||7/2/10 13:firstname.lastname@example.org||NEW||HTML5 spec (editor: Ian Hickson)||replace section 3.2.6 with the alternative spec text provided||11|
|10077||7/4/10 17:email@example.com||NEW||HTML5 spec (editor: Ian Hickson)||The <embed> should support an alt attribute. While the embedded content should provide for accessibility of the embedded object, the developer doesn't always have control over those content, some embeddable formats are inherently less accessible, and th||12|
|10168||7/14/10 18:firstname.lastname@example.org||NEW||alt techniques (editor: Steven Faulkner)||Please consider adding a section on role="presentation"||13|
|10248||7/28/10 15:email@example.com||NEW||HTML Canvas 2D Context (editor: Ian >Hickson)||Canvas requires a Caret Drawing call method||14|
|10249||7/28/10 17:firstname.lastname@example.org||NEW||HTML Canvas 2D Context (editor: Ian Hickson)||Canvas requires a content selection method||15|
Bug 7260 is ignored which is about an A11Y test suite. There are also 3 "open" (REOPENED) much older A11Y bugs which are not include these in computing the "age" value above since they are quite a bit older and would have biased the statistic.
About half of the NEW bugs that existed last week were processed this week.