- From: Ian Jacobs <ij@w3.org>
- Date: Wed, 24 Aug 2016 23:13:52 -0500
- To: Janina Sajka <janina@rednote.net>
- Cc: public-apa@w3.org, Michael Cooper <cooper@w3.org>, Adrian Hope-Bailie <adrian@ripple.com>, "Telford-Reed, Nick" <Nick.Telford-Reed@worldpay.com>, "Michael [tm] Smith" <mike@w3.org>
- Message-Id: <B869AF43-23D7-43EA-8949-24DD69EED682@w3.org>
> On Aug 24, 2016, at 10:22 PM, Janina Sajka <janina@rednote.net> wrote: > > Dear Ian and Web Payments WG: > > APA has concluded our review of the three Web Payments specification > FPWDs as requested in your email below. Our apologies for taking > somewhat longer than we had anticipated to reach our consensus on these > documents. Hi Janina and APA, Thank you for the review. I will bring the request to the attention of the Working Group (e.g., at an upcoming teleconference). All the best, Ian > > Our consensus decision on this comment is logged at: > > http://lists.w3.org/Archives/Public/public-apa/2016Aug/0080.html > > APA Comment > > The Accessible Platform Architectures (APA) Working Group has found no > specific problem in these three API specifications themselves. However, > we do request addition of the following section to each specification: > > Accessibility Impact Statement > > This specification has no defined user interface. In addition, there are > no specific accessibility requirements on implementations. However, to > the extent that an implementation provides user interactions in support > of this specification, the implementation must ensure that the interface > for those interactions is exposed to the platform accessibility API. > Moreover, implementors should take into consideration the needs of their > users with varying abilities when designing solutions that implement > this specification. As an example, the use of biometric authentication > techniques should provide for enough variation to allow for people with > widely differing physical abilities. See the W3C Accessibility > Guidelines documents for more information. > > Janina > > > Ian Jacobs writes: >> Janina, >> >> Today we announced FPWDs of the Web Payments Working Group: >> >> First Public Working Draft of Payment Request API Specifications >> https://www.w3.org/blog/news/archives/5371 >> >> On behalf of the Web Payments Working Group, and per our charter [1]), >> I’d like to ask for WAI APA WG review of these early drafts: >> >> * Payment Request API >> http://www.w3.org/TR/payment-request/ >> >> 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. >> >> * Payment Method Identifiers >> http://www.w3.org/TR/payment-method-id/ >> >> This document defines payment method identifier strings so that >> components in the payment ecosystem can determine which parties >> support which payment methods. >> >> * 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. >> >> We also announced a FAQ to go with the specs: >> https://github.com/w3c/webpayments/wiki/PaymentRequestFAQ >> >> Thank you, >> >> Ian >> >> [1] https://www.w3.org/Payments/WG/charter-201510.html#coordination >> -- >> Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs >> Tel: +1 718 260 9447 >> >> >> > > > > -- > > 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 > -- Ian Jacobs <ij@w3.org> http://www.w3.org/People/Jacobs Tel: +1 718 260 9447
Received on Thursday, 25 August 2016 04:14:09 UTC