Friday, 28 September 2012
- Re: Longdesc extension specification
- [Bug 13176] The bounds of canvas fallback content, as rendered on the canvas, are not provided by the user agent to an assistive technology.
- [Bug 17438] the term "hand authored" is undefined and ambiguous
- [Bug 18915] Encouraged cite attribute behavior is unlikely to be implemented and so should be dropped
- [Bug 17438] the term "hand authored" is undefined and ambiguous
- [Bug 17438] the term "hand authored" is undefined and ambiguous
- [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)
Thursday, 27 September 2012
- Minutes from Sept 27 meeting
- List of actively developed extension specifications (was: the maincontent element)
- the maincontent element- an HTML5 extension specification
- RE: Agenda: HTML-A11Y Task Force on 27 September at 15:00Z for 60 minutes
- Agenda: HTML-A11Y Task Force on 27 September at 15:00Z for 60 minutes
Wednesday, 26 September 2012
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Minutes from yesterday's call
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 18574] @hidden should have a weak mapping to aria-hidden=true
- Re: TPAC
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- TPAC
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
Tuesday, 25 September 2012
- [Bug 19072] Allow placeholder for color and date+ types
- [Bug 19049] Provide access to global accessibility settings
- [Bug 19020] <audio> and <video> do not have sufficient support for synchronized accessibility content
- [Bug 19055] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives
- [Bug 19027] Media events to indicate captions and audio descriptions
- [Bug 19018] provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec
- [Bug 19046] Add default button option/attribute for forms
- [Bug 19015] Enhancement: Set only single component for each pixel
- [Bug 19044] Extend accesskey="" to accept key names (e.g. accesskey="home")
- [Bug 19072] New: Allow placeholder for color and date+ types
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 19055] New: HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives
- [Bug 19049] New: Provide access to global accessibility settings
- [Bug 19046] New: Add default button option/attribute for forms
- [Bug 19044] New: Extend accesskey="" to accept key names (e.g. accesskey="home")
- [Bug 19027] New: Media events to indicate captions and audio descriptions
- [Bug 19020] New: <audio> and <video> do not have sufficient support for synchronized accessibility content
- [Bug 19018] New: provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 19015] New: Enhancement: Set only single component for each pixel
- [Bug 18915] Encouraged cite attribute behavior is unlikely to be implemented and so should be dropped
- [Bug 18915] Encouraged cite attribute behavior is unlikely to be implemented and so should be dropped
- Re: Getting HTML5 to Recommendation in 2014
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Fwd: additional sentence for 204
- Text Subteam Minutes for 25 September
- The outlinemask attribute - An HTML5 extension specification
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: Longdesc extension specification
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: Longdesc extension specification
- Re: Longdesc extension specification (was: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [text] HTML-A11Y Text, Tues 25 September 2012, 17:00 Z, (1PM Eastern), 90 min
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 9213] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives
- [Bug 13619] Provide access to global accessibility settings
- [Bug 9280] Add default button option/attribute for forms
- [Bug 13576] Extend accesskey="" to accept key names (e.g. accesskey="home")
- [Bug 12868] Allow placeholder for color and date+ types
- [Bug 8659] Media events to indicate captions and audio descriptions
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content
- [Bug 10464] provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec
- [Bug 13096] Enhancement: Set only single component for each pixel
- [Bug 13096] Enhancement: Set only single component for each pixel
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: Destructive threading (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- [Bug 16005] Media elements: I would suggest that Subtitle support be implemented for Audio Media elements for the hearing impaired users. It should also include an api that would allow custom presentation of the subtitles.
- [Bug 16005] Media elements: I would suggest that Subtitle support be implemented for Audio Media elements for the hearing impaired users. It should also include an api that would allow custom presentation of the subtitles.
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Destructive threading (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
Monday, 24 September 2012
- Re: What does "works" mean here? Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: A longer description feature that vendors could accept (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: A longer description feature that vendors could accept (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- subline element - HTML5 extension specification
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: What does "works" mean here? Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Longdesc extension specification (was: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- @fullsize (was: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
Sunday, 23 September 2012
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- What does "works" mean here? Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: longdesc quality statistics
- Re: longdesc quality statistics
- Re: longdesc quality statistics
- Re: longdesc quality statistics
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: longdesc quality statistics
- Re: longdesc quality statistics
Saturday, 22 September 2012
- RE: longdesc quality statistics
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
Friday, 21 September 2012
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: additional sentence for 204
- Re: longdesc document for the record
- Re: longdesc document for the record
- Re: additional sentence for 204
- Re: longdesc document for the record
- Re: Fwd: longdesc document for the record
- Re: longdesc quality statistics
- Re: Long descriptions spec - a basic idea
- Re: Long descriptions spec - a basic idea
- Re: longdesc quality statistics
- RE: Long descriptions spec - a basic idea
- Re: longdesc quality statistics
- Re: longdesc quality statistics
- Re: additional sentence for 204
- Re: Long descriptions spec - a basic idea
- Re: Fwd: longdesc document for the record
- Re: Fwd: longdesc document for the record
- longdesc quality statistics
- Implementing longdesc ... Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Fwd: longdesc document for the record
- [Bug 18010] @hidden sections should be excluded from the outline (or a note should be added, that hidden sections are included). The same goes for hidden headings of sections that are not hidden.
- Re: Long descriptions spec - a basic idea
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Long descriptions spec - a basic idea
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Issue 30 (Was: RE: Getting HTML5 to Recommendation in 2014)
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
Thursday, 20 September 2012
- Re: Requesting Clarification re CR Exit Stacks Criteria
- Re: Requesting Clarification re CR Exit Stacks Criteria
- FW: Issue 30 (Was: RE: Getting HTML5 to Recommendation in 2014)
- RE: Requesting Clarification re CR Exit Stacks Criteria
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Minutes HTML-A11Y Task Force 20 September
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: Requesting Clarification re CR Exit Stacks Criteria
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Requesting Clarification re CR Exit Stacks Criteria
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- FW: [HTMLWG] CR Exit Criteria redux
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- RE: Getting HTML5 to Recommendation in 2014
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: Issue 30 (Was: RE: Getting HTML5 to Recommendation in 2014)
- Re: Getting HTML5 to Recommendation in 2014
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- RE: Agenda: HTML-A11Y Task Force on 20 September at 15:00Z for 60 minutes
- Agenda: HTML-A11Y Task Force on 20 September at 15:00Z for 60 minutes
- Re: "turn the image around" UI idea
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: "turn the image around" UI idea
Wednesday, 19 September 2012
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- RE: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- RE: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: Extension spec for hgroup (Was: Re: Getting HTML5 to Recommendation in 2014)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: "turn the image around" UI idea
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: Getting HTML5 to Recommendation in 2014
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: "turn the image around" UI idea
- Re: Getting HTML5 to Recommendation in 2014
- Getting HTML5 to Recommendation in 2014
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: How to obsolete @longdesc
- Data collection and analysis (was RE: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: "turn the image around" UI idea
- Re: "turn the image around" UI idea
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 18915] Encouraged cite attribute behavior is unlikely to be implemented and so should be dropped
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: "turn the image around" UI idea
- Re: How to obsolete @longdesc
- Re: How to obsolete @longdesc
- Re: How to obsolete @longdesc
- Re: How to obsolete @longdesc
- Re: How to obsolete @longdesc
- Re: How to obsolete @longdesc
- How to obsolete @longdesc
- Re: What's in a name?
- Re: What's in a name?
- Water under the bridge
- Re: A longer description feature that vendors could accept (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: What's in a name?
- Re: What's in a name?
- Re: A longer description feature that vendors could accept (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: A longer description feature that vendors could accept (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: What's in a name?
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: A longer description feature that vendors could accept (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- What's in a name?
- A longer description feature that vendors could accept (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: "turn the image around" UI idea
- Re: "turn the image around" UI idea
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: "turn the image around" UI idea
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: "turn the image around" UI idea
- Re: "turn the image around" UI idea
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: additional sentence for 204
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- Re: The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- The latest InstateLongDesc CP effectively contains MUST-level UA conformance criteria
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
Tuesday, 18 September 2012
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: "turn the image around" UI idea
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- "turn the image around" UI idea
- Re: additional sentence for 204
- Re: Swapped in new approved CP overlay text (was Re: Text Subteam Minutes for 18 September)
- Swapped in new approved CP overlay text (was Re: Text Subteam Minutes for 18 September)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Text Subteam Minutes for 18 September
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 15193] draggable and dropzone regions require labels
- [Bug 17438] the term "hand authored" is undefined and ambiguous
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 17438] the term "hand authored" is undefined and ambiguous
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 17438] the term "hand authored" is undefined and ambiguous
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- [text] HTML-A11Y Text, Tues 18 September 2012, 17:00 Z, (1PM Eastern), 90 min
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- AAPI meeting agenda for 9/18
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
Monday, 17 September 2012
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Map element clarification (Was: additional sentence for 204)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: additional sentence for 204
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- In defence of iCab as an example...
- RE: 48-Hour Consensus Call: InstateLongdesc CP Update
Sunday, 16 September 2012
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
Saturday, 15 September 2012
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- RE: additional sentence for 204
- HTML5: Techniques for providing useful text alternatives
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- Re: My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
- [Bug 13958] Authors should be able to request specific modifiers for accesskeys
- [Bug 13958] Authors should be able to request specific modifiers for accesskeys
- My case for the obsoletion of longdesc (Was: 48-Hour Consensus Call: InstateLongdesc CP Update)
Friday, 14 September 2012
- RE: additional sentence for 204
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 13958] Authors should be able to request specific modifiers for accesskeys
- [Bug 18166] srcset is wrong and hard to read
- RE: additional sentence for 204
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- Re: additional sentence for 204
- ISSUE 204
- RE: additional sentence for 204
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 17117] definition of meta keyword "generator" should mention effect on validation
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level
- [Bug 17117] definition of meta keyword "generator" should mention effect on validation
- Re: additional sentence for 204
- Re: additional sentence for 204
- Re: additional sentence for 204
- Re: additional sentence for 204
- Re: additional sentence for 204
Thursday, 13 September 2012
- Re: additional sentence for 204
- Re: additional sentence for 204
- Re: additional sentence for 204
- Re: additional sentence for 204
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- Re: 48-Hour Consensus Call: InstateLongdesc CP Update
- additional sentence for 204
Wednesday, 12 September 2012
Thursday, 13 September 2012
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- 48-Hour Consensus Call: InstateLongdesc CP Update
- [Bug 18859] Update spec to match latest ISSUE-204 wording
- [Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
- Minutes HTML-A11Y Task Force 13 September 2012
- Re: Agenda: HTML-A11Y Task Force on 13 September at 15:00Z for 60 minutes
- Re: [updated] proposed rewording of ISSUE-204 text
- Agenda: HTML-A11Y Task Force on 13 September at 15:00Z for 60 minutes
Wednesday, 12 September 2012
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18793] Remove Sentence as requested by Formal Objection on HTML Issue-204 Decision
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- Re: 48-hour Consensus Call - Expedited Formal Objection on HTML Issue-204 Decision
- Please put in interim text for the ISSUE-204 statement about exposing semantics of hidden content
- Issue-204 -- New proposal on HTML list
Tuesday, 11 September 2012
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level
- [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
- [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
- [text] No HTML-A11Y Text Subteam meeting Tues 11 September
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- Re: Proposed rewording of ISSUE-204 text to address outstanding technical issues
- internet explorer and UI automation
- RE: Proposed rewording of ISSUE-204 text to address outstanding technical issues
- Re: Proposed rewording of ISSUE-204 text to address outstanding technical issues
- RE: Proposed rewording of ISSUE-204 text to address outstanding technical issues
- RE: ISSUE-30: longdesc "InstateLongdesc" - outlook
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
Monday, 10 September 2012
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
- [Bug 17117] definition of meta keyword "generator" should mention effect on validation
- [Bug 17117] definition of meta keyword "generator" should mention effect on validation
- RE: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: Apology (was RE: [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204)
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- RE: ISSUE-30: longdesc "InstateLongdesc" - outlook
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- Apology (was RE: [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204)
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
Sunday, 9 September 2012
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
Saturday, 8 September 2012
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
Friday, 7 September 2012
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- [Bug 18438] The Table summary attribute
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [aapi] Sept 8 agenda for HTML to AAPI mapping
- [Bug 17117] definition of meta keyword "generator" should mention effect on validation
- [Bug 18438] The Table summary attribute
- RE: ISSUE-30: longdesc "InstateLongdesc" - outlook
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18438] The Table summary attribute
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
- [Bug 18438] The Table summary attribute
- [Bug 18450] Consider adding a screen capture example
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
Thursday, 6 September 2012
- [Bug 18010] @hidden sections should be excluded from the outline (or a note should be added, that hidden sections are included). The same goes for hidden headings of sections that are not hidden.
- Re: new long description attribute (was Re: {minutes}} HTML WG telecon 2012-09-06)
- Re: new long description attribute (was Re: {minutes}} HTML WG telecon 2012-09-06)
- [Bug 18384] Consider adding an adaptive image element
- new long description attribute (was Re: {minutes}} HTML WG telecon 2012-09-06)
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18793] Remove Sentence as requested by Formal Objection on HTML Issue-204 Decision
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18793] Remove Sentence as requested by Formal Objection on HTML Issue-204 Decision
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18793] Remove Sentence as requested by Formal Objection on HTML Issue-204 Decision
- [Bug 14150] I am a photographer as well as a hand-coding web designer. One thing that frustrates me is the duplicity between alt="" and title="" for photographs and photographers. For instance: <img class="thumbnail" alt="David Kyles" title="David Kyles Shock and Awe
- [Bug 14150] I am a photographer as well as a hand-coding web designer. One thing that frustrates me is the duplicity between alt="" and title="" for photographs and photographers. For instance: <img class="thumbnail" alt="David Kyles" title="David Kyles Shock and Awe
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18793] Remove Sentence as requested by Formal Objection on HTML Issue-204 Decision
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Regrets for today's accessibility task force meeting
- Regrets for this week/next
Tuesday, 4 September 2012
- Re: ISSUE-30: longdesc "InstateLongdesc" - outlook
- Text subteam minutes for 4 September 2012
- [Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204
- [Bug 18745] Reword text adopted by ISSUE-204 to avoid certain implications
- Re: [text] HTML-A11Y Text, Tues 4 September 2012, 17:00 Z, (1PM Eastern), 60 min
- Re: [text] HTML-A11Y Text, Tues 4 September 2012, 17:00 Z, (1PM Eastern), 60 min
- Re: [text] HTML-A11Y Text, Tues 4 September 2012, 17:00 Z, (1PM Eastern), 60 min
- [text] HTML-A11Y Text, Tues 4 September 2012, 17:00 Z, (1PM Eastern), 60 min
Sunday, 2 September 2012
- [Bug 13176] The bounds of canvas fallback content, as rendered on the canvas, are not provided by the user agent to an assistive technology.
- [Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives
- [Bug 9212] Change the Generator Mechanism for img from Document Level to Element Level