W3C home > Mailing lists > Public > public-apa@w3.org > August 2016

Agenda: APA Web Payments Telecon; Thursday 18 August at 14:00Z -- NEW TIME

From: Janina Sajka <janina@rednote.net>
Date: Wed, 17 Aug 2016 14:33:33 -0400
To: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Message-ID: <20160817183333.GD1717@opera.rednote.net>
What:	APA Web Payments Teleconference
When:	Thursday 18 August
	10:00 AM        San Francisco -- U.S. Pacific  Time	(PDT: UTC -7)
	12:00 PM        Austin -- U.S. Central  Time		(CDT: UTC -5)
	 1:00 PM        Boston -- U.S. Eastern  Time		(EDT: UTC -4)
	 6:00 PM        London -- British  Time			(BST: UTC +1)
	 7:00 PM        Vienna -- Central European Time		(CEST: UTC +2)
	 8:00 PM        Tel Aviv -- Israel  Time		(IDT: UTC +3)
Where:	Webex Teleconference Code: 648 942 488; [See Below]

* 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+Web Payments Teleconference&iso=20160818T10&p1=43&ah=1

** Preliminary Agenda for APA Web Payments Telecon Thursday 18 August 2016

Meeting: APA Web Payments telecon
Chair:	Janina
agenda: this
agenda+ preview agenda with items from two minutes
agenda+	Draft A11y Statement Discussion
agenda+	PAUR Recruiting
agenda+ Other Business
agenda+ next and future meetings
agenda+ be done

Resource: Subteam Minutes

Resource: Thread on draft a11y statement

Resource: PAUR Relevant email threads

Resource: Documents to Review
1.)	Payment Request API
	This specification describes a web API to allow merchants (i.e.,
	web sites selling physical or digital goods) to easily accept
	payments from different payment methods with minimal
	integration.  User agents (e.g. browsers) will facilitate the
	payment flow between merchant and user.
2.)	Payment Method Identifiers
	This document defines payment method identifier strings so that
	components in the payment ecosystem can determine which parties
	support which payment methods.
3.)	Basic Card Payment
	http://www.w3.org/TR/payment-method-basic-card/ This specification
	describes the data formats used by the Payment Request API to
	support payment by payment cards such as credit or debit cards.

Resource: Other Relevant W3C Documents
PAUR Draft:	http://rawgit.com/w3c/apa/master/payment-accessibility-reqs/index.html
Payments FAQ:	https://github.com/w3c/webpayments/wiki/PaymentRequestFAQ
Payments Arch:	https://w3c.github.io/browser-payment-api/
COGA Report:	https://w3c.github.io/coga/issue-papers/payments.html
WCAG Mobile:	https://w3c.github.io/Mobile-A11y-Extension/
RDWG Mobile WD:	https://www.w3.org/WAI/RD/2012/mobile/note/ED-mobile

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

Resource: Webex Teleconference Logistics
Webex Best Practices: https://www.w3.org/2006/tools/wiki/WebExBestPractices

Webex Teleconference Code: 648 942 488; Password: [Please request in IRC] 
Meeting Webex Page: https://mit.webex.com/mit/j.php?MTID=m3743222ea76f5b2cf1ae411ab006f40c

PSTN --------------------------------------------------------
U.S. Toll: +1.617.324.0000

Or, request a dial-out from  your Webex app or via:

VoIP --------------------------------------------------------
Install the Webex plugin for your browser and use it to connect

Or, obtain and use the Webex client app for your mobile--Android,
Iphone, or Windows mobile.

Or, use SIP ...
SIP:6173240000@mit.edu (IPv4 only)
NOTE: SIP Reinvite may need to be disabled.

*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

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:

- For Zakim, the IRC interface to the bridge manager, that will maintain
  speaker and agenda queues:

- For a Web gateway to IRC you can use if your network administrators
  forbid IRC, see:

- For more on W3C use of IRC see:


Janina Sajka,	Phone:	+1.443.300.2200
		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
Received on Wednesday, 17 August 2016 18:33:58 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:01 UTC