Monday, 31 January 2011
- RE: request to re-open issue 133 due to submission of a change prposal.
- Re: Status on reopening longdesc Issue 30 (was Re: longdesc use cases)
- Re: Status on reopening longdesc Issue 30 (was Re: longdesc use cases)
- minutes: Canvas Accessibility Subteam meeting, 2011-01-31 [draft]
- Re: Media: Question about autoplay (video in browsers)
- Re: updated Drag and Drop spec in HTML5 draft
Sunday, 30 January 2011
- Re: Review of caret and selection proposal in current canvas API draft
- Re: Review of caret and selection proposal in current canvas API draft
- Re: Use Case: setCaretSelectionRect - Canvas Accessibility Working Group
- Re: Test Case: Option Role - Canvas Accessibility Working Group
- Review of caret and selection proposal in current canvas API draft
Saturday, 29 January 2011
- request to re-open issue 133 due to submission of a change prposal.
- Weekly Resolved & Rejected Bugs Report
Friday, 28 January 2011
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
Thursday, 27 January 2011
- MODIFIED: Call for Consensus - Draft statement to be delivered to WAI / WCAG WG
- Call for Consensus - Draft statement to be delivered to WAI / WCAG WG
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- Re: Media: Question about autoplay (video in browsers)
- HTML-ISSUE-31
- HTML A11y TF Weekly telecon minutes
- [Bug 11893] define lexical processing rules for ARIA attributes
- [Bug 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes
- Media: Question about autoplay (video in browsers)
- updated Drag and Drop spec in HTML5 draft
- January/February 2011 HTML 5 Accessibility Browser Support Update
Wednesday, 26 January 2011
- regrets RE: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes
- Minutes from Media Telecon on 26 January
- Re: Agenda: HTML-A11Y Media Subteam on 26 January at 22:00Z for 90 Minutes
- Re: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes
- Re: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes
- Re: ISSUE-142 (poster-alt): Chairs Solicit Proposals
- Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes
- Agenda: HTML-A11Y Media Subteam on 26 January at 22:00Z for 90 Minutes
- Re: addition of ARIA related specification text to HTML5
Tuesday, 25 January 2011
- Minutes: Januarry 25: HTML Accessibility Bug Triage Sub-Team
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
- [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
- [Bug 11466] Reword 4.4.7 The hgroup element
- [Bug 10916] Add a new <control> element to convey the common semantics of a script enabled UI control
- Re: Agenda: Januarry 25: HTML Accessibility Bug Triage Sub-Team
- Agenda: Januarry 25: HTML Accessibility Bug Triage Sub-Team
- Re: HTML 5 (sic) and A11y
- addition of ARIA related specification text to HTML5
- Focusability of text span [Was: minutes: Canvas Subteam Call 2011-01-24 [draft]]
- RE: ISSUE-142 (poster-alt): Chairs Solicit Proposals
- RE: ISSUE-142 (poster-alt): Chairs Solicit Proposals
Monday, 24 January 2011
- Status on reopening longdesc Issue 30 (was Re: longdesc use cases)
- HTML-A11Y Media Subteam - Action
- Re: Accessibility Taskforce ARIA mapping subteam meeting tuesday 25th, January
- minutes: Canvas Subteam Call 2011-01-24 [draft]
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- Re: HTML 5 (sic) and A11y
- HTML 5 (sic) and A11y
Sunday, 23 January 2011
Saturday, 22 January 2011
- [Bug 8673] Restriction on command element as part of a menu
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs
- [Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference
- [Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs
- [Bug 11207] Make track element additions technology neutral
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs
- Re: blog post by ann van kesteren: My Formal Objection to WAI-ARIA
- blog post by ann van kesteren: My Formal Objection to WAI-ARIA
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>)
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>)
- Weekly Resolved & Rejected Bugs Report
- [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
- [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
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>)
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>)
Friday, 21 January 2011
- [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
- Agenda: January 24, 2011 Canvas Accessibility Working Group
- [Bug 11207] Make track element additions technology neutral
- [Bug 11207] Make track element additions technology neutral
- [Bug 10482] Specify how @usemap affects role (of <img> and <object>)
- [Bug 10497] What happens to role of <img alt="non-empty"> inside a <figure role="img">?
- [Bug 10605] Typo: Replace 'the alt attribute's value may be omitted' with '@alt may be omitted'
- [Bug 10618] Use "unmapped" rather than "no role" in the weak/strong ARIA tables
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
Thursday, 20 January 2011
- minutes: HTML Accessibility Task Force telecon 2011-01-20 [draft]
- RE: Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes
- RE: Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes
- Re: Solution to grammar, spelling, and
- Re: Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes
- Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes
Wednesday, 19 January 2011
- Minutes of HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes
- Re: Agenda: HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes
- [Bug 11207] Make track element additions technology neutral
- [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
- Re: html5 editor has a change of tack on ARIA conformance requirements in HTML5
- [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
- [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
- [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
- [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
- html5 editor has a change of tack on ARIA conformance requirements in HTML5
- [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
- Agenda: HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes
Tuesday, 18 January 2011
- Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- Re: ISSUE-129 CCP - copied for review and comment
- Minutes Bug Triage sub-team 18 January 2011
- [Bug 10915] clarify why a command element that is not in a menu is conforming
- [Bug 10781] are accesskeys case sensitive?
- [Bug 10775] how is user to decide which set of access keys to use?
- [Bug 10773] accesskey should chosen from document's declared charset
- [Bug 10963] Table prohibited from being used as a layout aid
- longdesc use cases
- Re: Agenda: Januarry 18: HTML Accessibility Bug Triage Sub-Team
Monday, 17 January 2011
- [Bug 10486] References to "image" ARIA role should be "img"
- Minutes: January 17, 2011 HTML Canvas Accessibility subteam meeting
- RE: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- A11Y-ISSUE-1 (setCustomValidity): Forms validation using setCustomValidity [ARIA mapping]
- Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- Re: Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- Re: ISSUE-129 CCP - copied for review and comment
- default roles of elements with accesskey set
- Accessibility Taskforce ARIA mapping subteam meeting tuesday 18th, January
Sunday, 16 January 2011
- Re: HTML 5 Canvas Accessibility Call on January 10
- [Bug 10963] Table prohibited from being used as a layout aid
- Canvas and access to remote desktop environments [Was: HTML 5 Canvas Accessibility Call on January 10]
- Re: HTML 5 Canvas Accessibility Call on January 10
- [Bug 10963] Table prohibited from being used as a layout aid
- Re: Solution to grammar, spelling, and
Saturday, 15 January 2011
- Weekly Resolved & Rejected Bugs Report
- Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide
- [Bug 8000] ARIA roles added to the a element should be conforming in HTML5
- RE: UltraViolet and captions
Friday, 14 January 2011
- Agenda: January 17, 2011 Canvas Accessibility Working Group
- HGROUP revisited
- UltraViolet and captions
- RE: HTML 5 Canvas Accessibility Call on January 10
- Fwd: Google Feedback on the HTML5 media a11y specifications
- Re: Solution to grammar, spelling, and
Thursday, 13 January 2011
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default
- Survey on text alternatives
- Confirmed Face to Face meeting of HTML Accessibility Task Force
- HTML-A11Y Telecon Begins on the Hour!
- [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
- [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
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default
- [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_
- Re: Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes
- counter proposal for ISSUE-129 ARIA in HTML5
- [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
- [Bug 10486] References to "image" ARIA role should be "img"
- IMPORTANT: The HTML-A11Y Task Force Starts 1 Hour Early This Week
Wednesday, 12 January 2011
- [Bug 10693] Need a means for navigating between related timed tracks of media elements
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default
- HTML-A11Y Media Subteam Minutes for 12 January
- Re: Agenda: HTML-A11Y Media Subteam on 12 January at 22:00Z for 90 Minutes
- regrets RE: Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes
- [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks.
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default
- Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes
- Agenda: HTML-A11Y Media Subteam on 12 January at 22:00Z for 90 Minutes
Tuesday, 11 January 2011
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default
- [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking
- [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking
- [Bug 11238] Enable canvas to support accessible rich text editing
- [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking
- [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
- Minutes: 11 January HTML Accessibility Bug-Triage
- [Bug 11395] Use media queries to select appropriate <track> elements
- [Bug 11391] Provide examples of actual <track> usage, user agent implications
- [Bug 10963] Table prohibited from being used as a layout aid
- [Bug 10927] collection of all interactive (actionable, focusable) elements
- [Bug 10921] put back direct link to the W3C version of the canvas 2d context spec
- [Bug 10480] add role="presentation" on the ASCII fish image
- [Bug 10481] Default role of <IMG> should be "img"
- [Bug 10918] provide better examples
- [Bug 10917] modify user agent requirement for details element
- [Bug 10482] Should @usemap affect the default role of an IMG element?
- [Bug 10483] <figcaption> should be considered the caption of <figure> _itself_
- [Bug 10485] The img element with non-empty alt should default to the img aria role
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
- [Bug 10486] References to "image" ARIA role should be "img"
- [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking
- [Bug 10494] modify aria example and fix spelling
- [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types
- [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 11395] Use media queries to select appropriate <track> elements
- [Bug 11391] Provide examples of actual <track> usage, user agent implications
- [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking
- [Bug 10484] default roles for figcaption and caption: Make it simple to achieve accessibility
- IMPORTANT: The HTML-A11Y Task Force Starts 1 Hour Early This Week
- [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks.
- [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
- [media] Following up on Media Bugs
- [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.
- [Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks.
- [Bug 10839] Providing visible indication that descriptions and captions are available.
- [Bug 11466] Reword 4.4.7 The hgroup element
- [Bug 11466] Reword 4.4.7 The hgroup element
- [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking
- [Bug 11473] Clarify proper tabindex usage
- [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking
Monday, 10 January 2011
- [Bug 11241] Canvas support accessible Focus Ring tracking independent of caret or selection tracking
- [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking
- [Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking
- minutes: CANVAS subteam of HTML5 A11y TF telecon 2011-01-10 [draft]
- Agenda: Januarry 11: HTML Accessibility Bug Triage Sub-Team
- [Bug 11395] Use media queries to select appropriate <track> elements
- Re: HTML 5 Canvas Accessibility Call on January 10
- [Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types
- [Bug 11391] Provide examples of actual <track> usage, user agent implications
- [Bug 11533] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing."
- [Bug 8800] Cut/copy/paste should use dedicated events instead of overloading drag and drop
- [Bug 11441] "The img must not be used as a layout tool." Missing "element"?
- RE: HTML 5 Canvas Accessibility Call on January 10
Saturday, 8 January 2011
Friday, 7 January 2011
- RE: HTML 5 Canvas Accessibility Call on January 10
- Re: Issue 142: Video Poster (or, what's in a name?)
- RE: Issue 30 - longdesc
- Re: Solution to grammar, spelling, and
- Agenda: January 10, 2011 Canvas Accessibility Working Group
- Solution to grammar, spelling, and
Thursday, 6 January 2011
- Re: Issue 30 - longdesc
- Issue 30 - longdesc
- Re: longdesc implementation info (was Re: minutes: HTML A11y TF Telecon 2011-01-06 [draft])
- longdesc implementation info (was Re: minutes: HTML A11y TF Telecon 2011-01-06 [draft])
- Re: Media TextFormats Accessibility Comparison Summary Released
- Re: minutes: HTML A11y TF Telecon 2011-01-06 [draft]
- Re: Change proposal: Title attribute is not a substitute for alternative text.
- Re: Issue 142: Video Poster (or, what's in a name?)
- Re: Issue 142: Video Poster (or, what's in a name?)
- minutes: HTML A11y TF Telecon 2011-01-06 [draft]
- RE: Issue 142: Video Poster (or, what's in a name?)
- Change proposal: Title attribute is not a substitute for alternative text.
- Re: Issue 142: Video Poster (or, what's in a name?)
- Re: Issue 142: Video Poster (or, what's in a name?)
- Re: Issue 142: Video Poster (or, what's in a name?)
- Re: Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes
- Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes
- Issue 9: Video Accessibilty [was Issue 142: Video Poster]
- RE: Media TextFormats Accessibility Comparison Summary Released
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Media TextFormats Accessibility Comparison Summary Released
- Re: Media TextFormats Accessibility Comparison Summary Released
- Re: Media TextFormats Accessibility Comparison Summary Released
Wednesday, 5 January 2011
- RE: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- RE: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes
- [Bug 9452] Handling of additional tracks of a multitrack audio/video resource
- Survey on Face to Face possibilities
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes
- Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
Tuesday, 4 January 2011
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Reminder: January Change Proposal Deadlines
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Re: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
Monday, 3 January 2011
- Re: Reminder: January Change Proposal Deadlines
- RE: Reminder: January Change Proposal Deadlines
- RE: Reminder: January Change Proposal Deadlines
- Re: Reminder: January Change Proposal Deadlines
- Re: Reminder: January Change Proposal Deadlines
- Re: Reminder: January Change Proposal Deadlines
- Reminder: January Change Proposal Deadlines
Sunday, 2 January 2011
Saturday, 1 January 2011
- [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 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives
- [Bug 9485] Mandate all conformance checkers and validators must refer to WCAG
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives
- Weekly Resolved & Rejected Bugs Report
- [Bug 10888] Access Command Requirements for HTML5
- [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
- [Bug 11238] Enable canvas to support accessible rich text editing