public-html-a11y@w3.org from December 2010 by subject

[Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)

[Bug 10419] <video> should allow muted as a content attribute

[Bug 10438] math should be changed changed from no role to "math" role

[Bug 10439] <input type=file> has "button" role, but is typically a compound control

[Bug 10440] menu type=context should have "menu" role

[Bug 10441] <link> that represents a hyperlink should probably have no role by default

[Bug 10444] ARIA section does not list elements that have no default role or role restrictions

[Bug 10445] Certain elements with no role should have that as a strong semantic

[Bug 10446] Consider limiting the roles of certain media and plugin elements

[Bug 10447] <output> should not have a status role by default after all

[Bug 10448] Consider broadening the set of allowed roles for command elements

[Bug 10449] Consider allowing various command-like ARIA roles for h1-h6

[Bug 10450] Allow lists to be used as menus or tab sets

[Bug 10451] Consider restricting the roles allowed for the label element

[Bug 10452] Consider documenting attributes that map to ARIA properties in a separate table

[Bug 10455] Mint a describedby attribute for the img element

[Bug 10462] merge ARIA mapping tables and list

[Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference

[Bug 10464] provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec

[Bug 10465] provide correct aria mapping and role info for the table element

[Bug 10467] provide headings in the WAI-ARIA section of the spec to make it easier to understand

[Bug 10478] modify table, tr and td roles

[Bug 10479] add role=radiogroup to details element

[Bug 10482] Should @usemap affect the default role of an IMG element?

[Bug 10496] fix error in aria conformance checker advice

[Bug 10497] What happens to role of <img alt="non-empty"> inside a <figure role="img">?

[Bug 10525] Please try to improve Bugzilla's accessibility/usability problems before Last Call

[Bug 10603] Clarify what default roles UAs may assign to elements not listed in the ARIA section

[Bug 10605] Typo: Replace 'the alt attribute's value may be omitted' with '@alt may be omitted'

[Bug 10606] Define what alt="<whitespace>" means for <img>

[Bug 10618] Use "unmapped" rather than "no role" in the weak/strong ARIA tables

[Bug 10619] [WebSRT voice] Allowing A WebSRT voice declaration when the cue payload is WebSRT metadata text does not make sense, I think.

[Bug 10645] Add a modal attribute to html5 to indicate a modal segment of the DOM (modal dialog)

[Bug 10657] integration of "aria-autocomplete" with the various autocompletion mechanisms in html5

[Bug 10660] use < and > and not &#8592; and &#8594; to indicate previous and next

[Bug 10773] accesskey should chosen from document's declared charset

[Bug 10775] how is user to decide which set of access keys to use?

[Bug 10778] use element.accessKeyLabel to generate list of available accesskeys

[Bug 10779] triggering the Action of the command via accesskey

[Bug 10780] reference to definition of Action insufficient for definition of accesskey

[Bug 10781] are accesskeys case sensitive?

[Bug 10839] Providing visible indication that descriptions and captions are available.

[Bug 10915] clarify why a command element that is not in a menu is conforming

[Bug 10919] Allow role="presentation" to override the default role of any element

[Bug 10963] Table prohibited from being used as a layout aid

[Bug 10964] Canvas needs to support a backing store in the DOM subtree capable of supporting screen reading

[Bug 11152] Polyglot spec should mention accessibility

[Bug 11207] Make track element additions technology neutral

[Bug 11395] Use media queries to select appropriate <track> elements

[Bug 11447] New: Please document in the decision policy the procedure for reopening an issue

[Bug 11447] Please document in the decision policy the procedure for reopening an issue

[Bug 11473] Clarify proper tabindex usage

[Bug 11533] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing."

[Bug 11540] The willful violation clause is most unwise. A standard should not violate another standard for any reason. This wouls lead to 2 things : 1) Content correctly encoded content would never be displayed correctly. 2) All future standards would need to includ

[Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default

[Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default. It's redundant and encourages authors to add roles in cargo-cult fashion on the theory that this will improve their accessibility. See IRC for proof: http://kr

[Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types

[Bug 6496] Allow <img aria-labelledby> to act as a text alternative

[Bug 7076] Client-side image maps attributes missing on the a element

[Bug 8171] Implement the text alternatives proposal from WAI

[Bug 8646] Private communication exception

[Bug 9213] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives

[Bug 9217] Remove the Paragraph-Section-Heading loophole for not providing a text alternative.

[Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives

[Bug 9233] Incorporate a Link to UAAG with appropriate wording into browser sections

[Bug 9241] Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0

[Bug 9452] Handling of additional tracks of a multitrack audio/video resource

[Bug 9485] Mandate all conformance checkers and validators must refer to WCAG

[Bug 9774] "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

[media] handling multitrack audio / video

[media] Ian's timed tracks message on the WHATWG list

[media] Posted without further comment

[Minutes] Media Sub Team of the Accessibility Task force - Dec. 15, 2010

Action 92: Accessible Rich Text editing for <canvas> proposed alternative to native contenteditable APIs

Agenda: December 13, 2010 Canvas Accessibility Working Group

Agenda: December 14: HTML Accessibility Bug Triage Sub-Team

Agenda: December 20, 2010 Canvas Accessibility Working Group

Agenda: December 21: HTML Accessibility Bug Triage Sub-Team

Agenda: December 7: HTML Accessibility Bug Triage Sub-Team

Agenda: HTML-A11Y Media Subteam on 1 December at 22:00Z for 90 Minutes

Agenda: HTML-A11Y Media Subteam on 15 December at 22:00Z for 90 Minutes

Agenda: HTML-A11Y Media Subteam on 8 December at 22:00Z for 90 Minutes

Agenda: HTML-A11Y Task Force on 09 December at 16:00Z for 60 minutes

Agenda: HTML-A11Y Task Force on 16 December at 16:00Z for 60 minutes

Agenda: HTML-A11Y Task Force on 2 December at 16:00Z for 60 minutes

Bug 9452 - Handling of additional tracks of a multitrack audio/video resource

Bug-triage: current state of a11yTF tagged bugs

CANCELED HTML A11Y TF 23 and 30 December 2010

Canvas Accessibility Sub-Team meeting 2010-12-13 cancelled

Change Proposal text for HTML WG ISSUE-122 (HTML5 section 4.8.1.1.7)

disposition of ISSUE 30 cited in bug 10967 insufficient

DRAFT analysis of fallback mechanisms for embedded content ACTION-66

Draft Summary Doc for our Media Call Today

Forwarding Our Comparison [Was: Media Gaps Document--36 Hour Consensus Call]

Issue 130

ISSUE-142 (poster-alt): Chairs Solicit Proposals

Making an ISSUE-122 change proposal more explicit

Media Gaps Document--36 Hour Consensus Call

Media Subteam Minutes for 1 December

Media TextFormats Accessibility Comparison Summary Released

Minutes from Media Subteam Teleconference on 8 December

Minutes: 14 December HTML Accessibility Bug-Triage

Minutes: December 14: HTML Accessibility Bug Triage Sub-Team

Minutes: December 2, 2011 HTML Accessibility Task Force Meeting

Minutes: December 20, 2010 HTML Canvas Accessibility working group

Minutes: December 6, 2010 W3C HTML Canvas Accessibility Subteam meeting

Minutes: December 7: HTML Accessibility Bug Triage Sub-Team

minutes: HTML Accessibility Task Force 2010-12-09 [draft]

minutes: HTML Accessibility Task Force Telecon 2010-12-16 [draft]

Posted without further comment

Requirement 1 of the Verbose Description Requirements

role=presentation must not be applied to focusable elements

status on HTML WG issue 133?

Tracker prefix

Use of ARIA markup for rich text editing

Video Poster image

Video Poster image (was RE: DRAFT analysis of fallback mechanisms for embedded content ACTION-66)

Weekly Resolved & Rejected Bugs Report

Last message date: Tuesday, 28 December 2010 10:03:39 UTC