Re: HTML accessibility task force meeting agenda 07-02-2013

yes

On 7 February 2013 15:44, Paul Cotton <Paul.Cotton@microsoft.com> wrote:

>  >agenda+ Longdesc Extension Update
> http://dvcs.w3.org/hg/html-proposals/raw-file/b63325998cc1/longdesc1/longdesc.html
> >agenda+ Status of "alt" text in HTML (specification and usage in the
> document)
>
> ****
>
> Can we please put these items first on the agenda ahead of any bug
> discussion?****
>
> ** **
>
> /paulc****
>
> ** **
>
> Paul Cotton, Microsoft Canada****
>
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3****
>
> Tel: (425) 705-9596 Fax: (425) 936-7329****
>
> ** **
>
> *From:* Steve Faulkner [mailto:faulkner.steve@gmail.com]
> *Sent:* Wednesday, February 06, 2013 4:17 PM
> *To:* HTML Accessibility Task Force
> *Subject:* HTML accessibility task force meeting agenda 07-02-2013****
>
> ** **
>
> Hi all, agenda below, see you there!
>
> * 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://timeanddate.com/worldclock/fixedtime.html?iso=20130131T11&p1=43
>
> ** preliminary agenda for HTML-A11Y Task Force Teleconference 07-02-2013
> at 16:00Z for 60 minutes
>
> Meeting: HTML-A11Y Task Force Teleconference
> Chair: SteveF
> agenda+ Identify Scribe
> http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List
> agenda+ Media Bugs (Continued)
> http://lists.w3.org/Archives/Public/public-html-a11y/2012Nov/0040.html
> agenda+ Text Bugs
> agenda+ Subteam Reports: Bug Triage; AAPI Mapping;
> agenda+ Longdesc Extension Update
> http://dvcs.w3.org/hg/html-proposals/raw-file/b63325998cc1/longdesc1/longdesc.html
> agenda+ Status of "alt" text in HTML (specification and usage in the
> document)
> agenda+ Actions Review http://www.w3.org/WAI/PF/HTML/track/actions/open
> agenda+ Other Business
> agenda+ Identify Scribe for the next TF teleconference
> http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List
> agenda+ be done
>
> Resource: Draft Alt Report
> http://www.davidmacd.com/WCAG/WAI/buggy.html
>
> ** Resource: Previous Teleconference Minutes
> HTML-A11Y TF:   http://www.w3.org/2013/01/24-html-a11y-minutes.html
> Text Subteam:   http://www.w3.org/2012/12/11-text-minutes.html
> AAPI Mapping:   http://www.w3.org/2012/12/04-html-aapi-minutes.html
> Media Subteam:  http://www.w3.org/2012/06/29-media-minutes.html
>
> ** Resource: Key Task Force URIs
> Task Force Wiki:        http://www.w3.org/WAI/PF/HTML/wiki/Main_Page
> Scribing History:
> http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List
> Consensus Procedures:   http://www.w3.org/WAI/PF/HTML/consensus-procedures
> Work Statement:         http://www.w3.org/WAI/PF/html-task-force.html
> HTML Plan 2014:
> http://dev.w3.org/html5/decision-policy/html5-2014-plan.html#other-changes
> HTML-WG<http://dev.w3.org/html5/decision-policy/html5-2014-plan.html#other-changesHTML-WG>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
>
> 2013-01-31, 16:00Z (for 60 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, 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,
> Channel: #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/****
>
> ****
>
>
> --
> with regards
>
> Steve ****
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html