public-html-a11y@w3.org from January 2011 by author

'Janina Sajka'

• Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Tuesday, 4 January)

Benjamin Hawkes-Lewis

• Re: Review of caret and selection proposal in current canvas API draft (Sunday, 30 January)
• Re: Use Case: setCaretSelectionRect - Canvas Accessibility Working Group (Sunday, 30 January)
• Re: Test Case: Option Role - Canvas Accessibility Working Group (Sunday, 30 January)
• Review of caret and selection proposal in current canvas API draft (Sunday, 30 January)
• Focusability of text span [Was: minutes: Canvas Subteam Call 2011-01-24 [draft]] (Tuesday, 25 January)
• Re: Solution to grammar, spelling, and (Sunday, 23 January)
• Re: HTML 5 Canvas Accessibility Call on January 10 (Sunday, 16 January)
• Canvas and access to remote desktop environments [Was: HTML 5 Canvas Accessibility Call on January 10] (Sunday, 16 January)
• Re: HTML 5 Canvas Accessibility Call on January 10 (Sunday, 16 January)
• Re: Solution to grammar, spelling, and (Sunday, 16 January)
• Re: Solution to grammar, spelling, and (Friday, 14 January)

Bruce Lawson

• Re: Issue 142: Video Poster (or, what's in a name?) (Thursday, 6 January)

bugzilla@jessica.w3.org

• [Bug 11893] define lexical processing rules for ARIA attributes (Thursday, 27 January)
• [Bug 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes (Thursday, 27 January)
• [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA) (Tuesday, 25 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Tuesday, 25 January)
• [Bug 11466] Reword 4.4.7 The hgroup element (Tuesday, 25 January)
• [Bug 10916] Add a new <control> element to convey the common semantics of a script enabled UI control (Tuesday, 25 January)
• [Bug 8673] Restriction on command element as part of a menu (Saturday, 22 January)
• [Bug 9326] HTML elements mapping to ARIA and A11y APIs (Saturday, 22 January)
• [Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference (Saturday, 22 January)
• [Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference (Saturday, 22 January)
• [Bug 9326] HTML elements mapping to ARIA and A11y APIs (Saturday, 22 January)
• [Bug 11207] Make track element additions technology neutral (Saturday, 22 January)
• [Bug 9326] HTML elements mapping to ARIA and A11y APIs (Saturday, 22 January)
• [Bug 10482] Specify how @usemap affects role (of <img> and <object>) (Saturday, 22 January)
• [Bug 10482] Specify how @usemap affects role (of <img> and <object>) (Saturday, 22 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Saturday, 22 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Saturday, 22 January)
• [Bug 10482] Specify how @usemap affects role (of <img> and <object>) (Saturday, 22 January)
• [Bug 10482] Specify how @usemap affects role (of <img> and <object>) (Saturday, 22 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Friday, 21 January)
• [Bug 11207] Make track element additions technology neutral (Friday, 21 January)
• [Bug 11207] Make track element additions technology neutral (Friday, 21 January)
• [Bug 10482] Specify how @usemap affects role (of <img> and <object>) (Friday, 21 January)
• [Bug 10497] What happens to role of <img alt="non-empty"> inside a <figure role="img">? (Friday, 21 January)
• [Bug 10605] Typo: Replace 'the alt attribute's value may be omitted' with '@alt may be omitted' (Friday, 21 January)
• [Bug 10618] Use "unmapped" rather than "no role" in the weak/strong ARIA tables (Friday, 21 January)
• [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA) (Friday, 21 January)
• [Bug 11207] Make track element additions technology neutral (Wednesday, 19 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Wednesday, 19 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Wednesday, 19 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Wednesday, 19 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Wednesday, 19 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Wednesday, 19 January)
• [Bug 11798] It has been brought to my attention by some browser vendors that browsers don't actually implement accessibility API annotations exactly the way the ARIA spec says to; instead, they have default mappings from HTML directly to the accessibility APIs that t (Wednesday, 19 January)
• [Bug 10915] clarify why a command element that is not in a menu is conforming (Tuesday, 18 January)
• [Bug 10781] are accesskeys case sensitive? (Tuesday, 18 January)
• [Bug 10775] how is user to decide which set of access keys to use? (Tuesday, 18 January)
• [Bug 10773] accesskey should chosen from document's declared charset (Tuesday, 18 January)
• [Bug 10963] Table prohibited from being used as a layout aid (Tuesday, 18 January)
• [Bug 10486] References to "image" ARIA role should be "img" (Monday, 17 January)
• [Bug 10963] Table prohibited from being used as a layout aid (Sunday, 16 January)
• [Bug 10963] Table prohibited from being used as a layout aid (Sunday, 16 January)
• [Bug 8000] ARIA roles added to the a element should be conforming in HTML5 (Saturday, 15 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_ (Thursday, 13 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Thursday, 13 January)
• [Bug 10486] References to "image" ARIA role should be "img" (Thursday, 13 January)
• [Bug 10693] Need a means for navigating between related timed tracks of media elements (Wednesday, 12 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Wednesday, 12 January)
• [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks. (Wednesday, 12 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Wednesday, 12 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Tuesday, 11 January)
• [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_ (Tuesday, 11 January)
• [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking (Tuesday, 11 January)
• [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking (Tuesday, 11 January)
• [Bug 11238] Enable canvas to support accessible rich text editing (Tuesday, 11 January)
• [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types (Tuesday, 11 January)
• [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking (Tuesday, 11 January)
• [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking (Tuesday, 11 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Tuesday, 11 January)
• [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default (Tuesday, 11 January)
• [Bug 11395] Use media queries to select appropriate <track> elements (Tuesday, 11 January)
• [Bug 11391] Provide examples of actual <track> usage, user agent implications (Tuesday, 11 January)
• [Bug 10963] Table prohibited from being used as a layout aid (Tuesday, 11 January)
• [Bug 10927] collection of all interactive (actionable, focusable) elements (Tuesday, 11 January)
• [Bug 10921] put back direct link to the W3C version of the canvas 2d context spec (Tuesday, 11 January)
• [Bug 10480] add role="presentation" on the ASCII fish image (Tuesday, 11 January)
• [Bug 10481] Default role of <IMG> should be "img" (Tuesday, 11 January)
• [Bug 10918] provide better examples (Tuesday, 11 January)
• [Bug 10917] modify user agent requirement for details element (Tuesday, 11 January)
• [Bug 10482] Should @usemap affect the default role of an IMG element? (Tuesday, 11 January)
• [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_ (Tuesday, 11 January)
• [Bug 10485] The img element with non-empty alt should default to the img aria role (Tuesday, 11 January)
• [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA) (Tuesday, 11 January)
• [Bug 10486] References to "image" ARIA role should be "img" (Tuesday, 11 January)
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking (Tuesday, 11 January)
• [Bug 10494] modify aria example and fix spelling (Tuesday, 11 January)
• [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types (Tuesday, 11 January)
• [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 (Tuesday, 11 January)
• [Bug 11395] Use media queries to select appropriate <track> elements (Tuesday, 11 January)
• [Bug 11391] Provide examples of actual <track> usage, user agent implications (Tuesday, 11 January)
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking (Tuesday, 11 January)
• [Bug 10484] default roles for figcaption and caption: Make it simple to achieve accessibility (Tuesday, 11 January)
• [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks. (Tuesday, 11 January)
• [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 (Tuesday, 11 January)
• [Bug 9773] 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. (Tuesday, 11 January)
• [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks. (Tuesday, 11 January)
• [Bug 10839] Providing visible indication that descriptions and captions are available. (Tuesday, 11 January)
• [Bug 11466] Reword 4.4.7 The hgroup element (Tuesday, 11 January)
• [Bug 11466] Reword 4.4.7 The hgroup element (Tuesday, 11 January)
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking (Tuesday, 11 January)
• [Bug 11473] Clarify proper tabindex usage (Tuesday, 11 January)
• [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking (Tuesday, 11 January)
• [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking (Monday, 10 January)
• [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking (Monday, 10 January)
• [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking (Monday, 10 January)
• [Bug 11395] Use media queries to select appropriate <track> elements (Monday, 10 January)
• [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types (Monday, 10 January)
• [Bug 11391] Provide examples of actual <track> usage, user agent implications (Monday, 10 January)
• [Bug 11533] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing." (Monday, 10 January)
• [Bug 8800] Cut/copy/paste should use dedicated events instead of overloading drag and drop (Monday, 10 January)
• [Bug 11441] "The img must not be used as a layout tool." Missing "element"? (Monday, 10 January)
• [Bug 9452] Handling of additional tracks of a multitrack audio/video resource (Wednesday, 5 January)
• [Bug 11238] Enable canvas to support accessible rich text editing (Sunday, 2 January)
• [Bug 9241] Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0 (Saturday, 1 January)
• [Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives (Saturday, 1 January)
• [Bug 9485] Mandate all conformance checkers and validators must refer to WCAG (Saturday, 1 January)
• [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives (Saturday, 1 January)
• [Bug 10888] Access Command Requirements for HTML5 (Saturday, 1 January)
• [Bug 11140] Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp (Saturday, 1 January)
• [Bug 11238] Enable canvas to support accessible rich text editing (Saturday, 1 January)

Charles McCathieNevile

• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Monday, 17 January)

Cynthia Shelly

• regrets RE: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes (Wednesday, 26 January)
• regrets RE: Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes (Wednesday, 12 January)

David Bolter

• Re: html5 editor has a change of tack on ARIA conformance requirements in HTML5 (Wednesday, 19 January)
• Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Monday, 17 January)

David Singer

• Re: Media: Question about autoplay (video in browsers) (Monday, 31 January)
• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Re: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Wednesday, 26 January)
• Re: Issue 142: Video Poster (or, what's in a name?) (Friday, 7 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Wednesday, 5 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Tuesday, 4 January)
• Re: Reminder: January Change Proposal Deadlines (Monday, 3 January)

Denis Boudreau

• Re: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes (Wednesday, 26 January)
• Re: Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes (Thursday, 6 January)

Eric Carlson

• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Re: Media: Question about autoplay (video in browsers) (Thursday, 27 January)
• Re: Media: Question about autoplay (video in browsers) (Thursday, 27 January)
• Re: Issue 142: Video Poster (or, what's in a name?) (Thursday, 6 January)
• Re: Reminder: January Change Proposal Deadlines (Tuesday, 4 January)

Frank Olivier

• RE: HTML 5 Canvas Accessibility Call on January 10 (Monday, 10 January)

Geoff Freed

• Re: Agenda: HTML-A11Y Media Subteam on 26 January at 22:00Z for 90 Minutes (Wednesday, 26 January)
• Re: Agenda: HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes (Wednesday, 19 January)
• UltraViolet and captions (Friday, 14 January)
• Re: Agenda: HTML-A11Y Media Subteam on 12 January at 22:00Z for 90 Minutes (Wednesday, 12 January)
• Re: Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes (Wednesday, 5 January)

Gez Lemon

• Re: updated Drag and Drop spec in HTML5 draft (Monday, 31 January)

Gregory J. Rosmaita

• minutes: Canvas Accessibility Subteam meeting, 2011-01-31 [draft] (Monday, 31 January)
• minutes: Canvas Subteam Call 2011-01-24 [draft] (Monday, 24 January)
• minutes: HTML Accessibility Task Force telecon 2011-01-20 [draft] (Thursday, 20 January)
• minutes: CANVAS subteam of HTML5 A11y TF telecon 2011-01-10 [draft] (Monday, 10 January)
• longdesc implementation info (was Re: minutes: HTML A11y TF Telecon 2011-01-06 [draft]) (Thursday, 6 January)
• minutes: HTML A11y TF Telecon 2011-01-06 [draft] (Thursday, 6 January)
• Re: Issue 142: Video Poster (or, what's in a name?) (Thursday, 6 January)

Gunderson, Jon R

• RE: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Monday, 17 January)

HTML Accessibility Task Force Issue Tracker

• A11Y-ISSUE-1 (setCustomValidity): Forms validation using setCustomValidity [ARIA mapping] (Monday, 17 January)

Janina Sajka

• Re: Status on reopening longdesc Issue 30 (was Re: longdesc use cases) (Monday, 31 January)
• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Minutes from Media Telecon on 26 January (Wednesday, 26 January)
• Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes (Wednesday, 26 January)
• Agenda: HTML-A11Y Media Subteam on 26 January at 22:00Z for 90 Minutes (Wednesday, 26 January)
• Re: addition of ARIA related specification text to HTML5 (Wednesday, 26 January)
• Re: blog post by ann van kesteren: My Formal Objection to WAI-ARIA (Saturday, 22 January)
• Agenda: HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes (Wednesday, 19 January)
• HTML-A11Y Telecon Begins on the Hour! (Thursday, 13 January)
• IMPORTANT: The HTML-A11Y Task Force Starts 1 Hour Early This Week (Thursday, 13 January)
• HTML-A11Y Media Subteam Minutes for 12 January (Wednesday, 12 January)
• Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes (Wednesday, 12 January)
• Agenda: HTML-A11Y Media Subteam on 12 January at 22:00Z for 90 Minutes (Wednesday, 12 January)
• IMPORTANT: The HTML-A11Y Task Force Starts 1 Hour Early This Week (Tuesday, 11 January)
• Re: Issue 30 - longdesc (Saturday, 8 January)
• Re: Issue 142: Video Poster (or, what's in a name?) (Thursday, 6 January)
• Re: Issue 142: Video Poster (or, what's in a name?) (Thursday, 6 January)
• Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes (Wednesday, 5 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Tuesday, 4 January)

Jim Allan

• Re: Media: Question about autoplay (video in browsers) (Thursday, 27 January)
• Media: Question about autoplay (video in browsers) (Thursday, 27 January)

John Foliot

• MODIFIED: Call for Consensus - Draft statement to be delivered to WAI / WCAG WG (Thursday, 27 January)
• Call for Consensus - Draft statement to be delivered to WAI / WCAG WG (Thursday, 27 January)
• RE: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Tuesday, 25 January)
• RE: ISSUE-142 (poster-alt): Chairs Solicit Proposals (Tuesday, 25 January)
• [media] Following up on Media Bugs (Tuesday, 11 January)
• RE: Issue 30 - longdesc (Friday, 7 January)
• Issue 30 - longdesc (Thursday, 6 January)
• RE: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Wednesday, 5 January)
• RE: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Wednesday, 5 January)
• RE: Reminder: January Change Proposal Deadlines (Monday, 3 January)
• RE: Reminder: January Change Proposal Deadlines (Monday, 3 January)

Joshue O Connor

• Re: Agenda: Januarry 25: HTML Accessibility Bug Triage Sub-Team (Tuesday, 25 January)
• Re: HTML 5 (sic) and A11y (Tuesday, 25 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• HTML 5 (sic) and A11y (Monday, 24 January)
• Re: Agenda: Januarry 18: HTML Accessibility Bug Triage Sub-Team (Tuesday, 18 January)

Laura Carlson

• Re: Status on reopening longdesc Issue 30 (was Re: longdesc use cases) (Monday, 31 January)
• Weekly Resolved & Rejected Bugs Report (Saturday, 29 January)
• HTML-ISSUE-31 (Thursday, 27 January)
• January/February 2011 HTML 5 Accessibility Browser Support Update (Thursday, 27 January)
• Re: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes (Wednesday, 26 January)
• Status on reopening longdesc Issue 30 (was Re: longdesc use cases) (Monday, 24 January)
• Weekly Resolved & Rejected Bugs Report (Saturday, 22 January)
• Re: Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes (Thursday, 20 January)
• Re: ISSUE-129 CCP - copied for review and comment (Tuesday, 18 January)
• longdesc use cases (Tuesday, 18 January)
• Weekly Resolved & Rejected Bugs Report (Saturday, 15 January)
• Re: Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes (Thursday, 13 January)
• Weekly Resolved & Rejected Bugs Report (Saturday, 8 January)
• Re: longdesc implementation info (was Re: minutes: HTML A11y TF Telecon 2011-01-06 [draft]) (Thursday, 6 January)
• Re: minutes: HTML A11y TF Telecon 2011-01-06 [draft] (Thursday, 6 January)
• Re: Change proposal: Title attribute is not a substitute for alternative text. (Thursday, 6 January)
• Re: Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes (Thursday, 6 January)
• Issue 9: Video Accessibilty [was Issue 142: Video Poster] (Thursday, 6 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Thursday, 6 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Wednesday, 5 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Wednesday, 5 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Tuesday, 4 January)
• Re: Reminder: January Change Proposal Deadlines (Monday, 3 January)
• Re: Reminder: January Change Proposal Deadlines (Monday, 3 January)
• Re: Reminder: January Change Proposal Deadlines (Monday, 3 January)
• Reminder: January Change Proposal Deadlines (Monday, 3 January)
• Weekly Resolved & Rejected Bugs Report (Saturday, 1 January)

Léonie Watson

• HTML A11y TF Weekly telecon minutes (Thursday, 27 January)
• RE: Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes (Thursday, 20 January)
• RE: Issue 142: Video Poster (or, what's in a name?) (Thursday, 6 January)
• Change proposal: Title attribute is not a substitute for alternative text. (Thursday, 6 January)

Maciej Stachowiak

• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Tuesday, 18 January)
• Re: Issue 30 - longdesc (Saturday, 8 January)
• Re: Solution to grammar, spelling, and (Friday, 7 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)

Martin Kliehm

• Minutes: Januarry 25: HTML Accessibility Bug Triage Sub-Team (Tuesday, 25 January)
• Agenda: Januarry 25: HTML Accessibility Bug Triage Sub-Team (Tuesday, 25 January)
• Minutes: 11 January HTML Accessibility Bug-Triage (Tuesday, 11 January)
• Agenda: Januarry 11: HTML Accessibility Bug Triage Sub-Team (Monday, 10 January)

Michael Cooper

• Minutes Bug Triage sub-team 18 January 2011 (Tuesday, 18 January)
• Survey on text alternatives (Thursday, 13 January)
• Confirmed Face to Face meeting of HTML Accessibility Task Force (Thursday, 13 January)
• Survey on Face to Face possibilities (Wednesday, 5 January)

Michael(tm) Smith

• Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes (Thursday, 6 January)

Michael[tm] Smith

• updated Drag and Drop spec in HTML5 draft (Thursday, 27 January)
• Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes (Thursday, 20 January)

Paul Cotton

• RE: request to re-open issue 133 due to submission of a change prposal. (Monday, 31 January)

Philip Jägenstedt

• Re: Media: Question about autoplay (video in browsers) (Thursday, 27 January)
• Re: Media: Question about autoplay (video in browsers) (Thursday, 27 January)
• Re: Media: Question about autoplay (video in browsers) (Thursday, 27 January)

Ranon, Marco

• RE: Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes (Thursday, 20 January)

Richard Schwerdtfeger

• Re: Review of caret and selection proposal in current canvas API draft (Sunday, 30 January)
• Agenda: January 24, 2011 Canvas Accessibility Working Group (Friday, 21 January)
• Re: Solution to grammar, spelling, and (Thursday, 20 January)
• Minutes: January 17, 2011 HTML Canvas Accessibility subteam meeting (Monday, 17 January)
• Agenda: January 17, 2011 Canvas Accessibility Working Group (Friday, 14 January)
• RE: HTML 5 Canvas Accessibility Call on January 10 (Friday, 14 January)
• Re: HTML 5 Canvas Accessibility Call on January 10 (Monday, 10 January)
• RE: HTML 5 Canvas Accessibility Call on January 10 (Friday, 7 January)
• Agenda: January 10, 2011 Canvas Accessibility Working Group (Friday, 7 January)
• Solution to grammar, spelling, and (Friday, 7 January)

Sam Ruby

• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: Issue 30 - longdesc (Thursday, 6 January)

Sean Hayes

• HTML-A11Y Media Subteam - Action (Monday, 24 January)
• Minutes of HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes (Wednesday, 19 January)
• RE: UltraViolet and captions (Saturday, 15 January)
• RE: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)

Silvia Pfeiffer

• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Re: Media: Question about autoplay (video in browsers) (Friday, 28 January)
• Fwd: Google Feedback on the HTML5 media a11y specifications (Friday, 14 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Thursday, 6 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Thursday, 6 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)
• Re: Media TextFormats Accessibility Comparison Summary Released (Thursday, 6 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Wednesday, 5 January)
• Re: Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes (Wednesday, 5 January)

Steve Faulkner

• request to re-open issue 133 due to submission of a change prposal. (Saturday, 29 January)
• addition of ARIA related specification text to HTML5 (Tuesday, 25 January)
• Re: Accessibility Taskforce ARIA mapping subteam meeting tuesday 25th, January (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• Re: HTML 5 (sic) and A11y (Monday, 24 January)
• blog post by ann van kesteren: My Formal Objection to WAI-ARIA (Saturday, 22 January)
• html5 editor has a change of tack on ARIA conformance requirements in HTML5 (Wednesday, 19 January)
• Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Tuesday, 18 January)
• Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Tuesday, 18 January)
• Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Monday, 17 January)
• Re: ISSUE-129 CCP - copied for review and comment (Monday, 17 January)
• default roles of elements with accesskey set (Monday, 17 January)
• Accessibility Taskforce ARIA mapping subteam meeting tuesday 18th, January (Monday, 17 January)
• Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide (Saturday, 15 January)
• HGROUP revisited (Friday, 14 January)
• counter proposal for ISSUE-129 ARIA in HTML5 (Thursday, 13 January)
• Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines] (Thursday, 6 January)

Last message date: Monday, 31 January 2011 23:29:56 UTC