RE: Agenda: APA WEEKLY Teleconference; Wednesday 24 January at 17:00Z

Regrets, will be unable to attend as I will be on training at this time.

-----Original Message-----
From: Janina Sajka [mailto:janina@rednote.net]
Sent: Tuesday, January 23, 2018 3:46 PM
To: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Subject: Agenda: APA WEEKLY Teleconference; Wednesday 24 January at 17:00Z

What:   APA Weekly Teleconference
When:   Wednesday 24 January
         9:00 AM        San Francisco -- U.S. Pacific  Time     (PST: UTC -8)
        11:00 AM        Austin -- U.S. Central  Time            (CST: UTC -6)
        12:00 PM        Boston -- U.S. Eastern  Time            (EST: UTC -5)
         5:00 PM        London -- British  Time                 (BST: UTC +0)
         6:00 PM        Vienna -- Central European Time         (CET: UTC +1)
         7:00 PM        Tel Aviv -- Israel  Time                (IDT: UTC +2)
Where:  Webex Teleconference Code: 647 449 723
        https://www.w3.org/2017/08/telecon-info_apa

* Time of day conversions

Please confirm the correct time of this meeting in your time zone using the Fixed Time Clock at:

http://timeanddate.com/worldclock/fixedtime.html?msg=APA+Teleconference&iso=20180124T12&p1=43&ah=1

** Preliminary Agenda for APA WG Telecon Wednesday 24 January 2018

Meeting: APA WG telecon
Chair:  Janina
agenda: this
agenda+ preview agenda with items from two minutes
agenda+ CSS A11y TF
agenda+ Upcoming COGA CfC--Standing permission to publish Gaps WDs
agenda+Actions Checkin (Specs)
agenda+https://www.w3.org/WAI/APA/track/products/8
agenda+ new on TR http://www.w3.org/TR/tr-status-drafts.html
agenda+ New in HTML 5.3 -- Leonie
agenda+ APA and W3C Verticals -- Leonie
agenda+ Charter Renewal
agenda+ Other Business
agenda+ be done

Resource: APA Teleconference Minutes
APA Telecon:    http://www.w3.org/2018/01/10-apa-minutes.html
COGA TF:        https://www.w3.org/2018/01/18-coga-minutes.html
RQTF:           http://www.w3.org/2017/01/11-rqtf-minutes.html

Resource: APA's Accessibility Checklist
Current:        http://w3c.github.io/pfwg/wtag/checklist.html
TPAC:           http://www.w3.org/2017/11/06-apa-minutes.html#item04

Resource: Push/Notifications
Minutes: http://lists.w3.org/Archives/Public/public-apa/2017Oct/0025.html
Issue:  https://github.com/whatwg/notifications/issues/107
Issue:  https://github.com/w3c/push-api/issues/259

Resource: Research Questions Task Force (RQTF)
Home Page:      https://www.w3.org/WAI/APA/task-forces/research-questions/
Work Statement: https://www.w3.org/WAI/APA/task-forces/research-questions/work-statement

Resource: CSS Accessibility Task Force
Work Statement: https://www.w3.org/WAI/APA/task-forces/css-a11y/work-statement
Draft Issues:   https://github.com/w3c/aria/wiki/CSS-AAM-Potential-Features
TPAC2016 Mtg:   https://www.w3.org/2016/09/20-css-minutes

Resource: COGA Task Force
Timeline:       https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Main_Page

Resource: ARIA Personalization Task Force:
https://www.w3.org/WAI/ARIA/task-forces/personalization/work-statement

Resource: Key APA Pages For Reference
Home Page: http://www.w3.org/WAI/APA/
Charter: http://www.w3.org/2015/10/apa-charter.html
Member List:    https://www.w3.org/2004/01/pp-impl/83907/status
Decision Policy: http://www.w3.org/WAI/APA/decision-policy
Tracker (Issues and Actions): http://www.w3.org/WAI/APA/track Spec Review History: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review
APA at TPAC 2017: https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017
TPAC 2017 Page: https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2017

Resource: Webex Teleconference Logistics
Teleconference Data:    https://www.w3.org/2017/08/telecon-info_apa
Webex Best Practices:   https://www.w3.org/2006/tools/wiki/WebExBestPractices

*IRC Logistics
IRC: server: irc.w3.org, channel: #APA

IMPORTANT: Upon joining IRC, please identify yourself:
present+ [your_name]
Ex: present+ Janina_Sajka

* Some helpful 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.443.300.2200
                        sip:janina@asterisk.rednote.net
                Email:  janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures        http://www.w3.org/wai/apa


Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.

Received on Tuesday, 23 January 2018 15:57:36 UTC