Minutes from TF call of 01-31-13
Possible WCAG techniques
[Bug 12228] All Media Elements should have the ability to have both short and longer textual descriptions associated to the element.
[Bug 13624] <video> The pause-on-exit flag should lead to the paused for user interaction state
[Bug 13546] <video> make positioning of caption cues more flexible
[Bug 12546] <video> MEDIA CONTROLLER requires autoplay attribute for grouped multitrack
[Bug 13333] audio, video (and source) elements require param children or equivalent
UAWG Feedback / FYI
Dealing with cues that come out of order
HTML-A11Y Task Force Agenda for 31 January at 16:00Z for 60 minutes
Bug 11342 - Needs review
[Bug 19020] <audio> and <video> do not have sufficient support for synchronized accessibility content
[Bug 19072] Allow placeholder for color and date+ types
[Bug 12868] Allow placeholder for color and date+ types
Agenda: HTML-A11y bug triage telecon, 30th January 2013
Heartbeat publication for HTML to Platform Accessibility APIs Implementation Guide
Fwd: 4.13.1 Bread crumb navigation - use of right angle brackets
[Bug 18384] Add an adaptive image mechanism
ACTION-138 jquery on W3C site
Minutes: HTML-A11y TF telecon, 24th January 2013
Regrets for today
[Bug 19020] <audio> and <video> do not have sufficient support for synchronized accessibility content
[Bug 13096] Enhancement: Set only single component for each pixel
[Bug 10464] provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec
[Bug 10464] provide clear user friendly links to WAI-ARIA documents in the ARIA section of the spec
[Bug 5758] <audio> and <video> do not have sufficient support for synchronized accessibility content
[Bug 19027] Media events to indicate captions and audio descriptions
[Bug 8659] Media events to indicate captions and audio descriptions
[Bug 13576] Extend accesskey="" to accept key names (e.g. accesskey="home")
[Bug 9280] Add default button option/attribute for forms
[Bug 13619] Provide access to global accessibility settings
[Bug 9213] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives
Agenda - thursday 24 jan
CfC: to publish Encrypted Media Extensions specification as a First Public Working Draft (FPWD)
[Bug 13639] CSS2 System Colors Should Be Recognized
[Bug 13639] CSS2 System Colors Should Be Recognized
[Bug 13639] CSS2 System Colors Should Be Recognized
[Bug 13639] CSS2 System Colors Should Be Recognized
[Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 13639] CSS2 System Colors Should Be Recognized
[Bug 10618] Use "no ARIA-defined role" rather than "no role" in the weak/strong ARIA tables
[Bug 13428] Remove 4.8.1.1 Requirements for providing text to act as an alternative for images
[Bug 13571] user agent MUST allow user to activate the button
[Bug 13666] Improve handling of footnotes and endnotes
[Bug 13460] Show more use cases for details/summary elements
[Bug 13514] Support different resolutions for command elements and images
[Bug 13508] Fully support tri-state and indeterminate controls
[Bug 13572] 4.10.19 aborting autofocus based on user choice not optional
[Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
[Bug 14870] autosubmit attribute for form elements
[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 13548] size, width and height attributes on input should be conforming but obsolete
[Bug 14697] Harmonize roles with ARIA
[Bug 15401] metadata in image files
[Bug 18438] The Table summary attribute
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
[Bug 13666] Improve handling of footnotes and endnotes
[Bug 13460] Show more use cases for details/summary elements
[Bug 13514] Support different resolutions for command elements and images
[Bug 13508] Fully support tri-state and indeterminate controls
[Bug 13572] 4.10.19 aborting autofocus based on user choice not optional
[Bug 18245] Conveying state of an Active tab in tabbed panels to Assistive Technologies like screen readers
[Bug 14870] autosubmit attribute for form elements
[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 13548] size, width and height attributes on input should be conforming but obsolete
[Bug 14697] Harmonize roles with ARIA
[Bug 18438] The Table summary attribute
[Bug 15401] metadata in image files
[Bug 18385] Programmatic association of a page element to a 'description' text in a different uri
[Bug 8738] Role-based navigation
[Bug 10438] math should be changed changed from no role to "math" role
[Bug 10903] provide an introduction to wai-aria in the wai aria section of the spec
[Bug 10914] Allow multiple space separated values for the ARIA role attribute
[Bug 10452] Consider documenting attributes that map to ARIA properties in a separate table
[Bug 10449] Consider allowing various command-like ARIA roles for h1-h6
[Bug 10448] Consider broadening the set of allowed roles for command elements
[Bug 10451] Consider restricting the roles allowed for the label element
[Bug 10462] merge ARIA mapping tables and list
[Bug 10484] default roles for figcaption and caption: Make it simple to achieve accessibility
[Bug 10592] "h1 to h6 element that does have an hgroup ancestor" not listed in ARIA section
[Bug 10444] ARIA section does not list elements that have no default role or role restrictions
[Bug 10905] clarify how assigning an accesskey to an element affects the elements default role
[Bug 10482] Specify how @usemap affects role (of <img> and <object>)
[Bug 8738] Role-based navigation
[Bug 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes
[Bug 11893] define lexical processing rules for ARIA attributes
Agenda: HTML-A11y bug triage telecon, 23rd January 2013
HTML-A11y bugs (ARIA team)
HTML-A11y bugs (Media team)
HTML-A11y bugs (Text Alt team)
RE: Call for Consensus on resolutions to Objections to Publish an FPWD for long textual descriptions on images
[Bug 10618] Use "no ARIA-defined role" rather than "no role" in the weak/strong ARIA tables
[Bug 18384] Add an adaptive image mechanism
Minutes: HTML-A11y TF telecon, 17th January 2013
[Bug 13639] CSS2 System Colors Should Be Recognized
[Bug 13657] exact number not imporant in range doesn't make sense.
[Bug 10618] Use "no ARIA-defined role" rather than "no role" in the weak/strong ARIA tables
[Bug 10618] Use "no ARIA-defined role" rather than "no role" in the weak/strong ARIA tables
[Bug 10618] Use "not an ARIA-defined role" rather than "no role" in the weak/strong ARIA tables
[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)
[Bug 13541] Incomplete accessibility API exposure rules for svg element
Re: HTML-A11Y Task Force Agenda for 17 January at 16:00Z for 60 minutes
Re: Call for Consensus on resolutions to Objections to Publish an FPWD for long textual descriptions on images - due Friday 20th December, 23:59 EST
HTML-A11y bugs (Chaals)
RE: HTML-A11y bugs for review
HTML-A11Y Task Force Agenda for 17 January at 16:00Z for 60 minutes
Bug 16186 HTML 5 missing explicit directives for support full keyboard access (FKA) when navigating to a fragment identifier
[Bug 13572] 4.10.19 aborting autofocus based on user choice not optional
[Bug 13566] use of input type image to send coordinates should be phased out
[Bug 13553] 4.10.6 confusing, seemlingly contradictory text
[Bug 13549] 4.10.18 associating form elements with forms that do not contain them can cause navigation problems for AT and keyboard users
[Bug 13460] Show more use cases for details/summary elements
[Bug 13390] Readonly attribute on input.{color|range|checkbox|radio}
[Bug 10709] @title should be a required attribute for FRAME and IFRAME in HTML5
[Bug 8885] Fallback mechanism for embedded content
[Bug 10873] Provide a method of explicitly setting a tooltip for an element
[Bug 8753] Undo for drag and drop
[Bug 13574] Accessibility API support for dropzone
[Bug 10713] Drag and Drop: Add guidance for keyboard-only interaction
[Bug 14906] consider to add event "dragActivate" to the spec
[Bug 7721] Drag and Drop is not keyboard accessible
[Bug 13574] Accessibility API support for dropzone
[Bug 14906] consider to add event "dragActivate" to the spec
[Bug 8753] Undo for drag and drop
[Bug 10713] Drag and Drop: Add guidance for keyboard-only interaction
[Bug 7721] Drag and Drop is not keyboard accessible
Old action items...
[Bug 18384] Add an adaptive image mechanism
[Bug 13571] user agent MUST allow user to activate the button
[Bug 13428] Remove 4.8.1.1 Requirements for providing text to act as an alternative for images
[Bug 18450] Consider adding a screen capture example
[Bug 13548] size, width and height attributes on input should be conforming but obsolete
[Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 15213] Drag-and-drop processing model
Agenda: HTML-A11y bug triage telecon, 16th January 2013
[Bug 12933] Other tags should be allowed inside an img tag
Minutes from Jan 10 meeting of A11Y TF
HTML-A11Y Task Force Agenda for 9 January at 16:00Z for 60 minutes
[Bug 15213] Drag-and-drop processing model
regrets for two weeks
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9215] Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives
[Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
[Bug 9216] Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives"
Minutes: HTML-A11y bug triage telecon, 9th January 2013
[Bug 13429] Section 7.5 contenteditable and designMode must make navigation consistent platform conventions
[Bug 14107] Non-conformance of the summary attribute for the table element makes WCAG 1.0 compliance impossible
[Bug 13668] Generated content must be accessible
[Bug 13655] Support for viewports and positions
[Bug 13638] Consider referencing User Agent Guidelines in section 4.10.22.2 Implicit submissions
[Bug 13575] Retrieving keybindings in automation-friendly format
[Bug 13573] Moving the caret with the keyboard
FW: CfC: to publish Media Source Extensions specification as a First Public Working Draft (FPWD)
Agenda: HTML-A11y bug triage telecon, 9th January 2013
RE: CFC to publish Using ARIA in HTML as a First public working draft (reply by Wednesday Dec 19)
- Re: CFC to publish Using ARIA in HTML as a First public working draft (reply by Wednesday Dec 19)
- Re: CFC to publish Using ARIA in HTML as a First public working draft (reply by Wednesday Dec 19)