W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2010

Re: HEADS UP--For Thursday's TF Agenda

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 27 Jan 2010 01:30:12 -0800
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <F4258E06-2482-4319-9830-96D7B267BBAC@apple.com>
To: Janina Sajka <janina@rednote.net>

Regrets this week.

 - Maciej

On Jan 26, 2010, at 4:13 PM, Janina Sajka wrote:

> The attached email proposal from Michael Cooper will be on our agenda at our
> upcoming teleconference on Thursday, 28 September.
> Please come prepared to approve this proposal, or to make alternative
> suggestions.
> Please note, if there are bugs Michael has proposed we defer that you
> believe should NOT be deferred, please be prepared with the relevant bug
> number.
> Also, if you, or someone you know, wishes to take on one of these bugs,
> especially one that is proposed for deferral, please be prepared to
> identify it and your commitment to it.
> Additional bug analysis which contributes to Michael's proposal can be
> found at:
> http://www.w3.org/mid/4B58779C.5030100@w3.org
> -- 
> Janina Sajka,	Phone:	+1.443.300.2200
> 		sip:janina@rednote.net
> Chair, Open Accessibility	janina@a11y.org	
> Linux Foundation		http://a11y.org
> Chair, Protocols & Formats
> Web Accessibility Initiative	http://www.w3.org/wai/pf
> World Wide Web Consortium (W3C)
> Resent-From: public-html-a11y@w3.org
> From: Michael Cooper <cooper@w3.org>
> Date: January 21, 2010 7:56:37 AM PST
> To: HTML Accessibility Task Force <public-html-a11y@w3.org>
> Subject: Proposal on categories for bugs
> Going through the bugs the task force should take on (http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html), I was able to put nearly all of them into a category. I think it will be most useful for us to look at them by category, address general issues for that category, and then address the specific filed bugs for that category. Here are the categories I arrived at:
> text alternatives - mechanisms to define text alternatives images and other types of objects
> summary - table summary
> media - direct accessibility of included media (audio, video, etc)
> canvas - direct accessibility of canvas
> aria - aria integration or harmonization issues
> drag and drop - accessibility of drag and drop
> display - display rules and quirks for features
> focus - management and reaction to keyboard focus
> labels - how to label elements (distinct from text alternatives)
> semantics - full set of required semantics don't appear to be defined
> Looked at this way, there are only 10 major topics (at present) for the task force to consider. As we close on a given topic, we should be able to close on a number of bugs all at once.
> This is just a proposal to help give something to react to and serve as a springboard for organizing the task force work.
> Michael
> -- 
> Michael Cooper
> Web Accessibility Specialist
> World Wide Web Consortium, Web Accessibility Initiative
> E-mail cooper@w3.org
> Information Page
Received on Wednesday, 27 January 2010 09:30:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:07 UTC