minutes: Canvas Accessibility Subteam meeting, 2011-01-31 [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
request to re-open issue 133 due to submission of a change prposal.
Weekly Resolved & Rejected Bugs Report
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
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)
- 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)
updated Drag and Drop spec in HTML5 draft
January/February 2011 HTML 5 Accessibility Browser Support Update
regrets RE: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes
Minutes from Media Telecon on 26 January
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
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
Agenda: Januarry 25: HTML Accessibility Bug Triage Sub-Team
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
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]
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
[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
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>)
[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)
minutes: HTML Accessibility Task Force telecon 2011-01-20 [draft]
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: 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
Minutes of 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
[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
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
[Bug 10486] References to "image" ARIA role should be "img"
Minutes: January 17, 2011 HTML Canvas Accessibility subteam meeting
A11Y-ISSUE-1 (setCustomValidity): Forms validation using setCustomValidity [ARIA mapping]
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
[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]
[Bug 10963] Table prohibited from being used as a layout aid
Weekly Resolved & Rejected Bugs Report
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: 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
Agenda: January 17, 2011 Canvas Accessibility Working Group
HGROUP revisited
UltraViolet and captions
Fwd: Google Feedback on the HTML5 media a11y specifications
[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_
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
[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
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
[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
[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"?
Weekly Resolved & Rejected Bugs Report
RE: HTML 5 Canvas Accessibility Call on January 10
Agenda: January 10, 2011 Canvas Accessibility Working Group
Solution to grammar, spelling, and
- Re: Solution to grammar, spelling, and
- Re: Solution to grammar, spelling, and
- Re: Solution to grammar, spelling, and
Issue 30 - longdesc
minutes: HTML A11y TF Telecon 2011-01-06 [draft]
Change proposal: Title attribute is not a substitute for alternative text.
Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes
- Re: Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes
- Re: 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: Media TextFormats Accessibility Comparison Summary Released
- Re: Media TextFormats Accessibility Comparison Summary Released
- Re: Media TextFormats Accessibility Comparison Summary Released
[Bug 9452] Handling of additional tracks of a multitrack audio/video resource
Survey on Face to Face possibilities
Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes
- Re: Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes
- Re: Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes
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
- 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: 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: 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: 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: 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: Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]
- 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 (or, what's in a name?)
- Re: Issue 142: Video Poster (or, what's in a name?)