FW: Agenda: Special HTML-A11Y Task Force on 1 August at 15:00Z for 240 minutes

Hello,

For anyone who attended Thursday's session or is interested in the second part, here is the meeting request.  Note this is entirely an optional item for UAAG and no specific actions are requested of UAAG members from this mail unless you are interested.  We have done a good job of looking at the HTML 5 spec and our concerns have made it into the larger process that is filing bugs.  If you are interested in attending this session, I'm told we are welcome by the task force and I know they can always use the help.

Mail archives for the task force mailing list can be found at http://lists.w3.org/Archives/Public/public-html-a11y/. Minutes from Thursday's session are at http://lists.w3.org/Archives/Public/public-html-a11y/2011Jul/0169.html.

The basic process that is going on at this point is:

1. The HTML5 accessibility task force is reviewing comments from the various accessibility reviews that have happened on the HTML5 spec.  This includes the reviews done by members of UAAG.
A. The wiki where review comments have been compiled is at http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review.
B. A single page version of this review wiki is at http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/All.
2. The task force looks at the comments and assesses if there is enough detail and justification for the task force to file a task force supported bug.
A. If the review determines that a bug is appropriate, someone from these meetings is assigned to file the bug and update the wiki with the bug number.
B. The task force has a triage group that is watching for these bugs and helping to move them through the bug process.  This does not mean that this group will do all the bug work but they are monitoring and helping ensure task force issues do not get lost.
C. The wiki is updated to indicate by and large what the task force has done with comments e.g. bug or feels the issue needs more discussion.
3. Bugs from this process that the task force has determined to file and support are tagged with the keyword of a11ytf.
4. Note, this does not stop anyone from filing bugs outside this process on the HTML 5 spec around accessibility or any other areas of concern.  The a11ytf designation is an indication that the task force has reviewed the issue and that this group believes it is important and that they are tracking it specifically.
5. For any bugs filed on the HTML 5 spec at this point, the more complete the text being proposed is the better.

Thanks,

Kelly

-----Original Message-----
From: Janina Sajka [mailto:janina@rednote.net] 
Sent: Thursday, July 28, 2011 1:40 PM
To: HTML Accessibility Task Force
Cc: Jim Allan; Kelly Ford
Subject: Agenda: Special HTML-A11Y Task Force on 1 August at 15:00Z for 240 minutes

Colleagues:

We will continue (and hopefully finish) processing bugs against the Last Call Working Drafts in a special meeting this coming Monday. Thanks to all for your perseverance and outstanding work so far.

* Time of day conversions

You can check for the correct time of this meeting in your time zone using the Fixed Time Clock at:

http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=1&year=2011&hour=11&min=0&sec=0&p1=43
 
** preliminary agenda for HTML-A11Y Task Force Telecon 1 August 2011 at 15:00Z for 240 minutes

Meeting: HTML-A11Y telecon
Chair: Janina_Sajka
agenda: this
agenda+	Last Call Bug Review http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review
agenda+	Other Business
agenda+ Actions Review http://www.w3.org/WAI/PF/HTML/track/actions/open
agenda+ Identify Scribe for 4 August 
agenda+http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List
agenda+ be done

** Resource: Previous Teleconference Minutes
HTML TF:        http://www.w3.org/2011/07/28-html-a11y-minutes.html
Canvas Subteam: http://www.w3.org/2011/04/04-html-a11y-minutes.html
Media Subteam:  http://www.w3.org/2011/07/27-html-a11y-minutes.html
Text Subteam:  http://www.w3.org/2011/07/18-text-minutes.html

** Resource: Key Task Force URIs
Task Force Wiki:	http://www.w3.org/WAI/PF/HTML/wiki/Main_Page
Consensus Procedures:	http://www.w3.org/WAI/PF/HTML/consensus-procedures
Work Statement:		http://www.w3.org/WAI/PF/html-task-force.html
HTML LC Time Line: http://lists.w3.org/Archives/Public/public-html/2011May/0162.html
HTML Decision Policy:	http://dev.w3.org/html5/decision-policy/decision-policy-v2.html 

** conference infrastructure access information a.k.a. dial-in  instructions

Reference: http://www.w3.org/Guide/1998/08/teleconference-calendar.html#s_273

2011-08-01, 15:00Z (for 240 minutes)
Dial the Zakim bridge using either SIP or the PSTN.
PSTN: +1.617.761.6200 (This is a U.S. number).
SIP: zakim@voip.w3.org
You should be prompted for a pass code,
This is
2119#
(a11y#)

Alternatively, bypass the Zakim prompts and SIP directly into our teleconference.
SIP: 002119@voip.w3.org

> Instructions for how to connect using SIP:
http://www.w3.org/2006/tools/wiki/Zakim-SIP
Place for users to contribute additional VoIP tips.
http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips
 
IRC: server: irc.w3.org, port: 6665, channel: #html-a11y.

During the conference you can manage your participation with Zakim commands as follows:
   61# to mute yourself
   60# to unMute yourself
   41# to raise your hand (enter speaking queue)
   40# to lower your hand (exit speaking queue)

The system acknowledges these commands with a rapid, three-tone confirmation.  Mobile phone users especially should use the mute function if they don't have a mute function in their phone.  But the hand-raising function is a good idea for anyone not using IRC.

* IRC access

     There will also be an IRC channel available. The server is irc.w3.org,
     the port number is 6665 (note this is not the normal default) and the channel is #html-a11y.

* Gregory Rosmaita's scribing and participation tips http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet

For more on the IRC setup and the robots we use for agenda and speaker queuing and for posting the log to the web, see:

- for RRSAgent, that captures and posts the log with special attention to action items:
http://www.w3.org/2002/03/RRSAgent

- for Zakim, the IRC interface to the bridge manager, that will maintain speaker and agenda queues:
http://www.w3.org/2001/12/zakim-irc-bot

- for a Web gateway to IRC you can use if your network administrators forbid IRC, see:
http://www.w3.org/2001/01/cgi-irc

- for more on W3C use of IRC see:
http://www.w3.org/Project/IRC/

-- 

Janina Sajka,	Phone:	+1.202.595.7777;
		sip:janina@CapitalAccessibility.Com
Partner, Capital Accessibility LLC	http://CapitalAccessibility.Com

Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada Learn more at http://ScreenlessPhone.Com

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)

Received on Friday, 29 July 2011 22:18:04 UTC