Text Subteam Minutes for 31 July
[Bug 18450] Consider adding a screen capture example
[Bug 10896] enable device independent access to event handlers
[media] Fwd: dotSUB Newsletter July 2012 - Embed Interactive Transcripts
[text] HTML-A11Y Text, Tues 31 July 2012, 17:00 Z, (1PM Eastern), 90 min
- Re: [text] HTML-A11Y Text, Tues 31 July 2012, 17:00 Z, (1PM Eastern), 90 min
- Re: [text] HTML-A11Y Text, Tues 31 July 2012, 17:00 Z, (1PM Eastern), 90 min
Re: ISSUE-30: longdesc "LongdescZeroEdit" - outlook
[Bug 18438] The Table summary attribute
Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
[Bug 18384] Consider adding an adaptive image element
A request concerning a11y related emails
[Fwd: Re: issues with public-html-a11@w3.org (solved)]
[Fwd: Re: Updates to Issue-201 Change Proposal per our conversation]
[Fwd: ISSUE-30: longdesc "InstateLongdesc" - outlook]
[Fwd: ISSUE-204: aria-hidden - Straw Poll for Objections]
Response: Straw Poll for Issue 194
Minutes from the 26 July teleconference
FW: Editorial team for HTML5
Re: Discussion on ISSUE-201: canvas-fallback
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
Agenda: HTML-A11Y Task Force on 26 July at 15:00Z for 60 minutes
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
[Bug 18384] Consider adding an adaptive image element
[Bug 18384] Consider adding an adaptive image element
[Bug 18384] Consider adding an adaptive image element
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
Fwd: ISSUE-206: meta-generator
Re: Updating Change Proposals for ISSUE-131: caret-location-api
Re: Working Group Decision on ISSUE-205: caret-location-api
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
Updates to Issue-201 Change Proposal per our conversation
- Re: Updates to Issue-201 Change Proposal per our conversation
- Re: Updates to Issue-201 Change Proposal per our conversation
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
regrets
[Bug 18384] Consider adding an adaptive image element
[Bug 18384] Consider adding an adaptive image element
[Bug 18384] Consider adding an adaptive image element
[Bug 18384] Consider adding an adaptive image element
[Bug 18384] Consider adding an adaptive image element
Re: Proposed adaptive image element
- Re: Proposed adaptive image element
- Re: Proposed adaptive image element
- Re: Proposed adaptive image element
- Re: Proposed adaptive image element
[Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc)
Frank's response on Issue-131 Updating
WG Chairs seeking Issue-131 Updates
WG Decision on Issue-205 Published
[Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
Re: Moving forward with Issue-204
Re: Fwd: Moving forward with Issue-204
[Bug 11891] add role attribute to list of global attributes and add definition for it
48-Hour Consensus Call: Issue-194 Survey
Minutes: HTML-A11y TF telecon on 19th July 2012
Agenda: HTML-A11Y Task Force on July 19 at 15:00Z for 60 minutes
RE: ISSUE-204, ISSUE-30 and ISSUE-203 processing order
Accessible supplemental materials delivered with video
FW: ISSUE-151: whatwg-references - Status
FW: ISSUE-201: Aligning the two change proposals
FW: ISSUE-204, ISSUE-30 and ISSUE-203 processing order
SMPTE-TT on HBO GO
[aapi] Agenda for July 17 HTML to AAPI mapping meeting
[Bug 10713] Drag and Drop: Add guidance for keyboard-only interaction
[Bug 12885] WF3: Provide a way for the author to specify what kind of keyboard behaviour to use for text inputs on multimodal keyboards (e.g. show the numeric keyboard, capitalise the first character by default, etc)
[Bug 13512] Need a DOM event for AT to catch when content is inserted
[Bug 13574] Accessibility API support for dropzone
[Bug 13359] <track> A way is needed to identify the type of data in a track element
Re: Fw: ISSUE-201: Aligning the two change proposals
Fwd: ISSUE-201: Aligning the two change proposals
Agenda: HTML-A11Y Task Force on 12 July at 15:00Z for 60 minutes
- Re: Agenda: HTML-A11Y Task Force on 12 July at 15:00Z for 60 minutes
- Re: Agenda: HTML-A11Y Task Force on 12 July at 15:00Z for 60 minutes
regrets
[aapi] Agenda for July 10 HTML to AAPI mapping meeting
Re: ISSUE-194
FW: 答复: ISSUE-194
Minutes: Accessibility Task Force - July 5th
RE: Moving forward with Issue-204
RE: ISSUE-201: Aligning the two change proposals
Agenda: HTML-A11Y Task Force on July 5 at 15:00Z for 60 minutes
Re: 答复: Using ARIA in HTML
Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- RE: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- RE: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- RE: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- RE: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- RE: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- Re: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)
- RE: @longdesc scope (was: HTML Media Transcript, Issue-194: Are we done?)