public-html-a11y@w3.org from January 2011 by subject

[Bug 10066] replace section 3.2.6 with the alternative spec text provided (ARIA)

[Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference

[Bug 10480] add role="presentation" on the ASCII fish image

[Bug 10481] Default role of <IMG> should be "img"

[Bug 10482] Should @usemap affect the default role of an IMG element?

[Bug 10482] Specify how @usemap affects role (of <img> and <object>)

[Bug 10483] <figcaption> should be considered the caption of <figure> _itself_

[Bug 10484] default roles for figcaption and caption: Make it simple to achieve accessibility

[Bug 10485] The img element with non-empty alt should default to the img aria role

[Bug 10486] References to "image" ARIA role should be "img"

[Bug 10494] modify aria example and fix spelling

[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 10693] Need a means for navigating between related timed tracks of media elements

[Bug 10773] accesskey should chosen from document's declared charset

[Bug 10775] how is user to decide which set of access keys to use?

[Bug 10781] are accesskeys case sensitive?

[Bug 10839] Providing visible indication that descriptions and captions are available.

[Bug 10840] Allow the user to independently adjust the volumes of the audio description and original soundtracks.

[Bug 10888] Access Command Requirements for HTML5

[Bug 10915] clarify why a command element that is not in a menu is conforming

[Bug 10916] Add a new <control> element to convey the common semantics of a script enabled UI control

[Bug 10917] modify user agent requirement for details element

[Bug 10918] provide better examples

[Bug 10921] put back direct link to the W3C version of the canvas 2d context spec

[Bug 10927] collection of all interactive (actionable, focusable) elements

[Bug 10963] Table prohibited from being used as a layout aid

[Bug 11140] Subject: Physical Keys and Gestures for "accesskey" attribute The use of ASCII/Unicode code points for key binding has numerous well-known drawbacks. There are vital physical keyboard keys with no Unicode representation. Even for the main alphabet keys sp

[Bug 11207] Make track element additions technology neutral

[Bug 11238] Enable canvas to support accessible rich text editing

[Bug 11239] Canvas support accessible caret tracking independent of Focus Ring tracking

[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 11391] Provide examples of actual <track> usage, user agent implications

[Bug 11395] Use media queries to select appropriate <track> elements

[Bug 11441] "The img must not be used as a layout tool." Missing "element"?

[Bug 11466] Reword 4.4.7 The hgroup element

[Bug 11473] Clarify proper tabindex usage

[Bug 11533] clarify if specially focusable elements mean "all elements with defined valid tabindex" or "elements with a tabindex that allows sequential focusing."

[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 11557] Authors should not be allowed to specify roles on elements that they already have by default

[Bug 11593] the <track> @kind attribute should include the all of the identified accessibility content types

[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 11892] explicitly state that ARIA states and properties are formal/normative HTML attributes

[Bug 11893] define lexical processing rules for ARIA attributes

[Bug 8000] ARIA roles added to the a element should be conforming in HTML5

[Bug 8673] Restriction on command element as part of a menu

[Bug 8716] Replace img Guidance for Conformance Checkers with Suggested Text for Short Text Alternatives

[Bug 8800] Cut/copy/paste should use dedicated events instead of overloading drag and drop

[Bug 9218] Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives

[Bug 9241] Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0

[Bug 9326] HTML elements mapping to ARIA and A11y APIs

[Bug 9452] Handling of additional tracks of a multitrack audio/video resource

[Bug 9485] Mandate all conformance checkers and validators must refer to WCAG

[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.

[media] Following up on Media Bugs

A11Y-ISSUE-1 (setCustomValidity): Forms validation using setCustomValidity [ARIA mapping]

Accessibility Taskforce ARIA mapping subteam meeting tuesday 18th, January

Accessibility Taskforce ARIA mapping subteam meeting tuesday 25th, January

addition of ARIA related specification text to HTML5

Agenda: HTML-A11Y Media Subteam on 12 January at 22:00Z for 90 Minutes

Agenda: HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes

Agenda: HTML-A11Y Media Subteam on 26 January at 22:00Z for 90 Minutes

Agenda: HTML-A11Y Media Subteam on 5 January at 22:00Z for 90 Minutes

Agenda: HTML-A11Y Task Force on 06 January at 16:00Z for 60 minutes

Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes

Agenda: HTML-A11Y Task Force on 20 January at 16:00Z for 60 minutes

Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes

Agenda: Januarry 11: HTML Accessibility Bug Triage Sub-Team

Agenda: Januarry 18: HTML Accessibility Bug Triage Sub-Team

Agenda: Januarry 25: HTML Accessibility Bug Triage Sub-Team

Agenda: January 10, 2011 Canvas Accessibility Working Group

Agenda: January 17, 2011 Canvas Accessibility Working Group

Agenda: January 24, 2011 Canvas Accessibility Working Group

blog post by ann van kesteren: My Formal Objection to WAI-ARIA

Call for Consensus - Draft statement to be delivered to WAI / WCAG WG

Canvas and access to remote desktop environments [Was: HTML 5 Canvas Accessibility Call on January 10]

Change proposal: Title attribute is not a substitute for alternative text.

Confirmed Face to Face meeting of HTML Accessibility Task Force

counter proposal for ISSUE-129 ARIA in HTML5

default roles of elements with accesskey set

Focusability of text span [Was: minutes: Canvas Subteam Call 2011-01-24 [draft]]

Fwd: Google Feedback on the HTML5 media a11y specifications

HGROUP revisited

HTML 5 (sic) and A11y

HTML 5 Canvas Accessibility Call on January 10

HTML A11y TF Weekly telecon minutes

HTML-A11Y Media Subteam - Action

HTML-A11Y Media Subteam Minutes for 12 January

HTML-A11Y Telecon Begins on the Hour!

HTML-ISSUE-31

html5 editor has a change of tack on ARIA conformance requirements in HTML5

IMPORTANT: The HTML-A11Y Task Force Starts 1 Hour Early This Week

Issue 142: Video Poster (or, what's in a name?)

Issue 142: Video Poster [Was: Reminder: January Change Proposal Deadlines]

Issue 30 - longdesc

Issue 9: Video Accessibilty [was Issue 142: Video Poster]

ISSUE-129 CCP - copied for review and comment

ISSUE-142 (poster-alt): Chairs Solicit Proposals

January/February 2011 HTML 5 Accessibility Browser Support Update

longdesc implementation info (was Re: minutes: HTML A11y TF Telecon 2011-01-06 [draft])

longdesc use cases

Media TextFormats Accessibility Comparison Summary Released

Media: Question about autoplay (video in browsers)

Minutes Bug Triage sub-team 18 January 2011

Minutes from Media Telecon on 26 January

Minutes of HTML-A11Y Media Subteam on 19 January at 22:00Z for 90 Minutes

Minutes: 11 January HTML Accessibility Bug-Triage

minutes: Canvas Accessibility Subteam meeting, 2011-01-31 [draft]

minutes: Canvas Subteam Call 2011-01-24 [draft]

minutes: CANVAS subteam of HTML5 A11y TF telecon 2011-01-10 [draft]

minutes: HTML A11y TF Telecon 2011-01-06 [draft]

minutes: HTML Accessibility Task Force telecon 2011-01-20 [draft]

Minutes: Januarry 25: HTML Accessibility Bug Triage Sub-Team

Minutes: January 17, 2011 HTML Canvas Accessibility subteam meeting

MODIFIED: Call for Consensus - Draft statement to be delivered to WAI / WCAG WG

regrets RE: Agenda: HTML-A11Y Task Force on 13 January at 15:00Z for 120 minutes

regrets RE: Agenda: HTML-A11Y Task Force on 27 January at 16:00Z for 60 minutes

Reminder: January Change Proposal Deadlines

Request input on the potential usefulness of HTML to Platform Accessibility APIs Implementation Guide

request to re-open issue 133 due to submission of a change prposal.

Review of caret and selection proposal in current canvas API draft

Solution to grammar, spelling, and

Status on reopening longdesc Issue 30 (was Re: longdesc use cases)

Survey on Face to Face possibilities

Survey on text alternatives

Test Case: Option Role - Canvas Accessibility Working Group

UltraViolet and captions

updated Drag and Drop spec in HTML5 draft

Use Case: setCaretSelectionRect - Canvas Accessibility Working Group

Weekly Resolved & Rejected Bugs Report

Last message date: Monday, 31 January 2011 23:29:56 UTC