Friday, 30 December 2011
- [Bug 13572] 4.10.19 aborting autofocus based on user choice not optional
- [Bug 13572] 4.10.19 aborting autofocus based on user choice not optional
Thursday, 29 December 2011
Friday, 23 December 2011
- [Bug 13570] why does input type=color support autocomplete?
- RE: more bugs
- [Bug 13572] 4.10.19 aborting autofocus based on user choice not optional
- [Bug 13558] input type=email should support friendly names
- [Bug 13571] user agent MUST allow user to activate the button
- [Bug 13570] why does input type=color support autocomplete?
- [Bug 13569] Allow user agents to override autocomplete
- [Bug 13568] use of "accessible" to refer to placement of UI controls is confusing
- [Bug 13567] Fix typos in definition of <input type=image alt="">
- [Bug 13563] radio and checkbox elements should not be valid without an associated label
- [Bug 13558] input type=email should support friendly names
- should bug 8000 be closed as fixed?
- bug 13570
- Add bug 13560 to next agenda
- more bugs
- [Bug 8673] Restriction on command element as part of a menu
- [Bug 9326] HTML elements mapping to ARIA and A11y APIs
Thursday, 22 December 2011
Wednesday, 21 December 2011
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
Tuesday, 20 December 2011
- Re: [text] HTML-A11Y Text, Tues 20 Dec, 2011, 17:00 Z, (1PM Eastern), 60 min
- Re: [text] HTML-A11Y Text, Tues 20 Dec, 2011, 17:00 Z, (1PM Eastern), 60 min
- [Bug 13461] Commentary on Issue #30 (longdesc) from the Association of American Publishers
- [Bug 13428] Remove 4.8.1.1 Requirements for providing text to act as an alternative for images
- Re: [text] HTML-A11Y Text, Tues 20 Dec, 2011, 17:00 Z, (1PM Eastern), 60 min
- RE: Clarification on process for bugs marked resolved won't fix
- Clarification on process for bugs marked resolved won't fix
- Minutes HTML-A11y Bug triage telecon 20th December, at 16:00UTC
- [Bug 13291] it doesn't make sense for <button> to be exposed as a link or radio button; it would just confuse users told to "click the button"
- [Bug 13142] Typo: "even when the response do include a recognized challenge" "do" -> "does"
- [Bug 9623] <details> and <summary> are missing from the "strong aria semantics" table
- [Bug 9113] re: "axis on td and th elements" text could say "Use the scope attribute on the relevant th"
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- [Bug 10774] fallback for accesskey insufficiently defined
- [Bug 13570] why does input type=color support autocomplete?
- [Bug 10249] Canvas requires a content selection method
- RE: Agenda: HTML-A11y Bug triage telecon 20th December, at 16:00UTC
- [Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
- [Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
- Re: [text] HTML-A11Y Text, Tues 20 Dec, 2011, 17:00 Z, (1PM Eastern), 60 min
- [Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
- [Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
- [Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
- Re: Fw: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- [Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
- Re: Request to re-open issue 131
- [text] HTML-A11Y Text, Tues 20 Dec, 2011, 17:00 Z, (1PM Eastern), 60 min
Monday, 19 December 2011
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Fw: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- [Bug 13651] Missing alt should not be considered conforming in the presence of figcaptions over 50 words in length.
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- RE: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: HTML Canvas 2D Context Extensions - for review
- Re: Request to re-open issue 131
- [Bug 12834] Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements
- RE: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Hit testing use cases Re: Request to re-open issue 131
- Re: HTML Canvas 2D Context Extensions - for review
Sunday, 18 December 2011
- Re: Request to re-open issue 131
- Re: HTML Canvas 2D Context Extensions - for review
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- @alt and @title in WebKit
- Re: Request to re-open issue 131
- Re: Request to re-open issue 131
- Re: HTML Canvas 2D Context Extensions - for review
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: HTML Canvas 2D Context Extensions - for review
- Hit testing use cases Re: Request to re-open issue 131
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Request to re-open issue 131
- Re: HTML5 implementor feedback requested - title attribute recommendations and requirements
Saturday, 17 December 2011
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- RE: HTML5 implementor feedback requested - title attribute accessibility mapping
- RE: HTML5 implementor feedback requested - title attribute recommendations and requirements
- [Bug 13657] exact number not imporant in range doesn't make sense.
- [Bug 13554] 4.10.7 please specify all cases where readonly attribute makes the input immutable
Friday, 16 December 2011
- [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 13549] 4.10.18 associating form elements with forms that do not contain them can cause navigation problems for AT and keyboard users
- [Bug 13528] Many examples in the forms section to do not exemplify best practice
- [Bug 13547] overloading of input element is confusing
- Re: HTML Canvas 2D Context Extensions - for review
- [Bug 13664] what events are fired when iframe seemless attribute is changed dynamically?
- [Bug 13661] 4.8.2 Will iframe loading events break existing AT?
- [Bug 13654] 3.5.1 does unregistering event listeners include AT?
- [Bug 13511] document parsing should discuss setting up accessibility APIs
- [Bug 13657] exact number not imporant in range doesn't make sense.
- [Bug 13665] Need to define model for focus order and how to keyboard out of frame
- [Bug 13550] type table in 4.10.7 should indicate control type changes based on list attribute
- [Bug 13551] clarify definition of "value sanitization algorithm"
- Agenda: HTML-A11y Bug triage telecon 20th December, at 16:00UTC
- Re: Request to re-open issue 131
- [Bug 15213] Drag-and-drop processing model
Thursday, 15 December 2011
- [Bug 15213] Drag-and-drop processing model
- Re: Request to re-open issue 131
- [Bug 15213] Drag-and-drop processing model
- [Bug 13432] <video> In the description of accessibility features, call out those with reduced faculties separately from those with disabilities, to avoid offending the elderly
- [Bug 11240] Canvas support accessible selection position tracking independent of Focus Ring tracking
- [Bug 10853] HTML5 lacks a verbose description mechanism
- [Bug 10774] fallback for accesskey insufficiently defined
- [Bug 13727] regarding "phrase or paragraph with an alternative graphical representation"
- [Bug 14419] when canvas isn't supported, or for blind users, the canvas element's content should be displayed, so excluding input types like text and select is discriminatory
- [Bug 15213] Drag-and-drop processing model
- [Bug 15212] If a text selection is identified for a drag operation
- RE: agenda: HTML-A11Y Task Force, 15 December at 16:00Z
- [Bug 15193] draggable and dropzone regions require labels
- Re: agenda: HTML-A11Y Task Force, 15 December at 16:00Z
- [Bug 12984] Contributions to HTML5: Techniques for providing useful text alternatives
- agenda: HTML-A11Y Task Force, 15 December at 16:00Z
- Re: wontfix bug assignments
- [Bug 15193] draggable and dropzone regions require labels
- RE: HTML Canvas 2D Context Extensions - for review
- [Bug 13591] Keyboard-only drag and drop must be fully supported
- Re: Request to re-open issue 131
- [Bug 10713] Drag and Drop: Add guidance for keyboard-only interaction
Wednesday, 14 December 2011
- Re: Request to re-open issue 131
- [Bug 12874] question on use of image maps
- [Bug 12877] remove section 3.11
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- Re: Request to re-open issue 131
- Re: wontfix bug assignments
- [Bug 13651] Missing alt should not be considered conforming in the presence of figcaptions over 50 words in length.
- HTML Canvas 2D Context Extensions - for review
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- Media Requirements from the ITU
Tuesday, 13 December 2011
- [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
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- Re: Minutes from HTML-A11y Bug triage telecon, 22nd November at 16:00UTC
- [Bug 14740] title attribute definition does not match reality
- Re: Cancelled: HTML-A11y Bug triage telecon on 6th December, at 16:00UTC
- [Bug 13728] on guidance for conformance checkers about text alternatives
- [Bug 13667] Title attribute is overloaded
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- [Bug 13665] Need to define model for focus order and how to keyboard out of frame
- [Bug 13641] Please provide a Glossary of Terms
- [Bug 13635] Feedback on Various Input Types and Attributes
- [Bug 13616] Allow specifying categories/keywords for commands
- [Bug 13630] Better method for user-friendly help or hints
- [Bug 13594] Handling of duplicate keyboard shortcuts
- New bugs
- [Bug 13539] Specify reading and navigation order
- [Bug 13579] Clarify behavior of accesskey on static content elements
- [Bug 13555] Fixing keyboard shortcuts and commands
- [Bug 13514] Support different resolutions for command elements and images
- [Bug 12228] All Media Elements should have the ability to have both short and longer textual descriptions associated to the element.
- Re: HTML5 implementor feedback requested - title attribute accessibility mapping
- Re: Request to re-open issue 131
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- Re: Request to re-open issue 131
- [Bug 14937] Replace poor coding example for figure with multiple images
- [Bug 13176] The bounds of canvas fallback content, as rendered on the canvas, are not provided by the user agent to an assistive technology.
Monday, 12 December 2011
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- HTML5 implementor feedback requested - title attribute accessibility mapping
- HTML5 implementor feedback requested - title attribute recommendations and requirements
- Agenda: HTML-A11y Bug triage telecone on 13th December, at 16:00UTC
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [Bug 12794] <video> Add a non-normative note on how to provide text alternatives for media elements
- [Bug 12964] <video>: Declarative linking of full-text transcripts to video and audio elements
Sunday, 11 December 2011
- [Bug 14107] Non-conformance of the summary attribute for the table element makes WCAG 1.0 compliance impossible
- [Bug 12834] Allow LEGEND element to be wrapped in DIV
Saturday, 10 December 2011
- [Bug 14107] Non-conformance of the summary attribute for the table element makes WCAG 1.0 compliance impossible
- [Bug 14740] title attribute definition does not match reality
- RE: Request to re-open issue 131
- Re: Request to re-open issue 131
- Re: Request to re-open issue 131
Friday, 9 December 2011
- [Bug 12834] Allow LEGEND element to be wrapped in DIV
- [Bug 14740] title attribute definition does not match reality
- [Bug 14107] Non-conformance of the summary attribute for the table element makes WCAG 1.0 compliance impossible
- [Bug 14073] Define role of @title in <a title="Expansion"><abbr>abbrevitation</abbr></a>
- [Bug 13942] Allow @autofocus on any element with @tabindex
- [Bug 13614] Define <th abbr=""> as a way to provide a name for a row/column that is used when describing cells for which that cell is a header
- [Bug 13181] Canvas does not allow mouse events to be directed to keyboard accessible objects in fallback content
- [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 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 13578] Argument for the approval of adding setElementPath to the Canvas 2d 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 13732] canvas accessibility
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- Re: 7.6 Drag and drop (accessibility)
- Re: Request to re-open issue 131
- [Bug 14906] consider to add event "dragActivate" to the spec
- [Bug 13578] Argument for the approval of adding setElementPath to the Canvas 2d 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 13732] canvas accessibility
- [Bug 10645] <dialog> Add support for in-page dialogs
- [Bug 10645] <dialog> Add support for in-page dialogs
- [Bug 10645] Add a modal attribute to html5 to indicate a modal segment of the DOM (modal dialog)
- [Bug 10645] Add a modal attribute to html5 to indicate a modal segment of the DOM (modal dialog)
- Re: Request to re-open issue 131
Thursday, 8 December 2011
- Minutes HTML A11Y TF 8 December 2011
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [Bug 12964] <video>: Declarative linking of full-text transcripts to video and audio elements
- [Bug 12794] <video> Add a non-normative note on how to provide text alternatives for media elements
- [Bug 10919] Allow role="presentation" to override the default role of any element
- [Bug 11956] restrict use of role=presentation
- Request to re-open issue 131
- [Bug 15080] Hi I was wondering if / when some sort of implementation of a "capture" tag would be introduced. Removing the need to add extra third party code or writing your own "capture" system. Surely this would be a good addition to the spec, it would mean less spa
- Re: agenda: HTML-A11Y Task Force, 08 December at 16:00Z
- Re: Agenda: HTML-A11Y Task Force on 8 December at 16:00Z for 60 minutes
- agenda: HTML-A11Y Task Force, 08 December at 16:00Z
- [Bug 14937] Replace poor coding example for figure with multiple images
- [Bug 14937] Replace poor coding example for figure with multiple images
- [Bug 14937] Replace poor coding example for figure with multiple images
- [Bug 14937] Replace poor coding example for figure with multiple images
- [Bug 13614] Define <th abbr=""> as a way to provide a name for a row/column that is used when describing cells for which that cell is a header
- [Bug 14937] Replace poor coding example for figure with multiple images
- [Bug 13614] Define <th abbr=""> as a way to provide a name for a row/column that is used when describing cells for which that cell is a header
- [Bug 13614] Define <th abbr=""> as a way to provide a name for a row/column that is used when describing cells for which that cell is a header
Wednesday, 7 December 2011
- [Bug 14937] Replace poor coding example for figure with multiple images
- [Bug 12834] Allow LEGEND element to be wrapped in DIV
- [Bug 14906] consider to add event "dragActivate" to the spec
- [Bug 14906] consider to add event "dragActivate" to the spec
- [Bug 14870] autosubmit attribute for form elements
- [Bug 13614] Define <th abbr=""> as a way to provide a name for a row/column that is used when describing cells for which that cell is a header
- [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 13176] The bounds of canvas fallback content, as rendered on the canvas, are not provided by the user agent to an assistive technology.
- [Bug 13567] Fix typos in definition of <input type=image alt="">
- [Bug 13359] <track> A way is needed to identify the type of data in a track element
- [Bug 12834] Provide a way for authors to have their fieldset legends not straddle the fieldset border
- [Bug 13532] Clarify that UAs should make user-accessible all elements that take focus or react to user input, regardless of the input method
- [Bug 13359] A way is needed to identify the type of data in a track element
- [Bug 12834] Provide a way for authors to have their fieldset legends not straddle the fieldset border
- [Bug 12834] Provide a way for authors to have their fieldset legends not straddle the fieldset border
- [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 13614] Define <th abbr=""> as a way to provide a name for a row/column that is used when describing cells for which that cell is a header
- [Bug 13614] Define <th abbr=""> as a way to provide a name for a row/column that is used when describing cells for which that cell is a header
- [Bug 12834] Provide a way for authors to have their fieldset legends not straddle the fieldset border
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13728] on guidance for conformance checkers about text alternatives
- [Bug 13668] Generated content must be accessible
- Agenda: HTML-A11Y Task Force on 8 December at 16:00Z for 60 minutes
- [Bug 13614] Do not obsolete abbr on TH and TD
- FW: ISSUE-186: role-presentation-override - Chairs Solicit Proposals
- [Bug 13574] Accessibility API support for dropzone
- [Bug 13357] <video>: Additional AudioTrack.kind categories are needed to identify tracks where audio descriptions are premixed with main dialogue.
- [Bug 12544] <video> MEDIA CONTROLLER requires track kind for in-band tracks
- [Bug 13428] Remove 4.8.1.1 Requirements for providing text to act as an alternative for images
- [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 13461] Commentary on Issue #30 (longdesc) from the Association of American Publishers
- [Bug 13551] clarify definition of "value sanitization algorithm"
- [Bug 13567] definition of @alt on input type image needs a rewrite
- [Bug 12547] <video> Expose the /most recently reported readiness state/ as MediaController.readyState
- RE: Change proposal for reopening issue 131 to address chairs clarification on text baseline
Tuesday, 6 December 2011
- Cancelled: HTML-A11y Bug triage telecon on 6th December, at 16:00UTC
- Re: Agenda: HTML-A11y Bug triage telecon on 6th December, at 16:00UTC
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- Agenda: HTML-A11y Bug triage telecon on 6th December, at 16:00UTC
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
Monday, 5 December 2011
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 13359] A way is needed to identify the type of data in a track element
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- RE: Change proposal for reopening issue 131 to address chairs clarification on text baseline
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
Sunday, 4 December 2011
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- Change proposal for reopening issue 131 to address chairs clarification on text baseline
- Issue-131
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
Saturday, 3 December 2011
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 13096] Enhancement: Set only single component for each pixel
- [Bug 9213] HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives
- [Bug 13520] Drag and Drop without a pointing device
- [Bug 13550] type table in 4.10.7 should indicate control type changes based on list attribute
Friday, 2 December 2011
- [Bug 13728] on guidance for conformance checkers about text alternatives
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13737] the menu element and accessibility
- [Bug 13635] Feedback on Various Input Types and Attributes
- [Bug 13638] Consider referencing User Agent Guidelines in section 4.10.22.2 Implicit submissions
- [Bug 13626] Facilitate grouping of menu items
- [Bug 13096] Enhancement: Set only single component for each pixel
- [Bug 10249] Canvas requires a content selection method
- [Bug 8722] focus behaviour should be same for canvas regions as for elements
- [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 13655] Support for viewports and positions
- [Bug 13728] on guidance for conformance checkers about text alternatives
- [Bug 13727] regarding "phrase or paragraph with an alternative graphical representation"
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13590] VHA Comments on HTML5 Draft Specification
- [Bug 13731] need simple visual alternatives to indicate that audio is playing to let a deaf user know
- [Bug 13732] canvas accessibility
- [Bug 13614] Do not obsolete abbr on TH and TD
- [Bug 13096] Enhancement: Set only single component for each pixel
- [Bug 13616] Allow specifying categories/keywords for commands
- [Bug 13614] Do not obsolete abbr on TH and TD
- [Bug 13578] Argument for the approval of adding setElementPath to the Canvas 2d specification.
- [Bug 13578] Argument for the approval of adding setElementPath to the Canvas 2d specification.
- [Bug 13532] Sequential navigation to all elements that take focus or input
- [Bug 13432] <video> In the description of accessibility features, call out those with reduced faculties separately from those with disabilities, to avoid offending the elderly
- [Bug 14906] consider to add event "dragActivate" to the spec
- [Bug 13181] Canvas does not allow mouse events to be directed to keyboard accessible objects in fallback content
- [Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)
- [Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)
- [Bug 12590] @role=presentation for IMG should also require that @title is empty
- [Bug 12306] "When authors use the canvas element, they must also provide content that, when presented to the user, conveys essentially the same function or purpose as the bitmap canvas." While everyone can probably agree that alternative content is a good idea when f
- [Bug 11557] Authors should not be allowed to specify roles on elements that they already have by default
- [Bug 13447] SVG content model VENN diagram needs to be made accessible [3.2.5.1 Kinds of content/content-venn.svg].
- [Bug 13436] Editorial changes to The Video element (4 of 5)
- [Bug 13096] Enhancement: Set single component for pixel
- [Bug 12964] <video>: Declarative linking of full-text transcripts to video and audio elements
- [Bug 13096] Enhancement: Set single component for pixel
- [Bug 13429] Section 7.5 contenteditable and designMode must make navigation consistent platform conventions
- [Bug 12708] @accesskey: Clarify what it needs in order to have effect
- [Bug 13548] size, width and height attributes on input should be conforming but obsolete
- [Bug 12794] <video> Add a non-normative note on how to provide text alternatives for media elements
Thursday, 1 December 2011
- [Bug 13096] Enhancement: Set single component for pixel
- [Bug 13594] Handling of duplicate keyboard shortcuts
- [Bug 12710] @accesskey: Authoring conformance - reliance on @tabindex et cetera
- [Bug 13614] Do not obsolete abbr on TH and TD
- [Minutes] HTML-A11Y TF (text-team) Teleconference on 1 December
- [Bug 10919] Allow role="presentation" to override the default role of any element
- [Bug 13129] Accessible Tables examples in HTML 5 spec
- [Bug 13137] HTML 5 table spec tables samples contain no ARIA markup example.
- [Bug 13129] Accessible Tables examples in HTML 5 spec
- [Bug 13137] HTML 5 table spec tables samples contain no ARIA markup example.
- [Bug 12243] Conformance of aria-describedby="" and aria-labelledby="" attributes pointing to interactive content