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

Re: 48-Hour Call for Consensus (CfC): Web Payments API Review

From: John Foliot <john.foliot@deque.com>
Date: Fri, 19 Aug 2016 12:15:18 -0500
Message-ID: <CAKdCpxzyyWJw1bhetJmk3xiskYHJ4sSEZJ8ahJ_sLU=4H2B+Lw@mail.gmail.com>
To: Janina Sajka <janina@rednote.net>
Cc: Accessible Platform Architectures Administration <public-apa-admin@w3.org>
+1 I support this CfC

JF

On Fri, Aug 19, 2016 at 8:55 AM, Janina Sajka <janina@rednote.net> wrote:

> +1
>
> Janina Sajka writes:
> > Colleagues:
> >
> > This is a Call for Consensus (CfC) to the Accessible Platform
> > Architectures (APA) Working Group on our review of three Web Payments
> > API specifications.
> >
> > *     Background Information
> >
> > APA's review of the following three API specifications relating to
> > payment transactions via the web was requested by the Web Payments
> > Working Group at:
> >
> > http://lists.w3.org/Archives/Public/public-apa/2016Apr/0050.html
> >
> > 1.)   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.
> > 2.)   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.
> > 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.
> >
> > Review of these three specifications was referred to APA's Web Payments
> > Subteam, whose deliberations on these specifications are available in
> > recent teleconference minutes and publically archived email threads:
> >
> > 1.) Subteam Minutes
> > https://www.w3.org/2016/08/04-apa-minutes.html
> > https://www.w3.org/2016/08/18-apa-minutes.html
> >
> > 2.) Email Threads
> > http://lists.w3.org/Archives/Public/public-apa/2016Aug/0015.html
> > http://lists.w3.org/Archives/Public/public-apa/2016Aug/0067.html
> >
> > *     Proposed 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.
> >
> > *     ACTION TO TAKE
> >
> > This CfC is now open for objection, comment, as well as statements of
> > support via email. Silence will be interpreted as support, though
> > messages of support are certainly welcome.
> >
> > If you object to this proposed action, or have comments concerning this
> > proposal, please respond by replying on list to this message no later
> > than 23:59 (Midnight) Boston Time, Tuesday 26 August.
> >
> > Janina
> >
> > --
> >
> > 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
> >
>
> --
>
> 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
>
>
>


-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion
Received on Friday, 19 August 2016 17:15:50 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:22:53 UTC