W3C home > Mailing lists > Public > public-webpayments-ig@w3.org > March 2015

RE: Important Accessibility Requirement or Consideration for Web Payments work

From: David Ezell <David_E3@VERIFONE.com>
Date: Tue, 31 Mar 2015 13:47:22 +0000
To: "chaals@yandex-team.ru" <chaals@yandex-team.ru>, "Katie.Haritos-Shea@Chase.com" <Katie.Haritos-Shea@Chase.com>
CC: "public-webpayments-ig@w3.org" <public-webpayments-ig@w3.org>
Message-ID: <54C00E24834FCE47B11EC129A84E7F78CCB27095@VF2WDEXMB1.verifone.com>
Chaals and Katie:

I completely agree with adding the reference to the UCFPWD.   WAI is one way W3C can add value to the payments space.  This raises a bigger question about our related potential areas of contribution around UX and predictability.

In other words - this is a good start, but as we define our flows in the usecases, we need some of our IG heads thinking in terms of how to make things safe and predictable.

I'm not suggesting any of this effort to go into the FPWD, but should certainly be on our radar.

Best regards,

-----Original Message-----
From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru]
Sent: Sunday, March 29, 2015 5:29 AM
To: Manu Sporny; public-webpayments-ig@w3.org
Subject: Re: Important Accessibility Requirement or Consideration for Web Payments work

29.03.2015, 06:24, "Manu Sporny" <msporny@digitalbazaar.com>:
> On 03/28/2015 02:18 PM, Katie Haritos-Shea GMAIL wrote:
>>  While doing my review of the Web Payments Use Cases FPWD today it
>>  occurred to me that somewhere in our documentation on requirements
>>  there should be some place to include a core W2C WCAG2 accessibility
>>  requirement for financial transactions.
> Done.
> https://github.com/w3c/webpayments-ig/commit/fc8c0a2277b1fe80f9813e9be

> 26991c5fe49a7be

Note that this is tricky, since we want to reduce payment "friction".

I suspect the way this plays out is that where we do introduce something like that, we allow things like limit-setting (so many transactions, with such-and-such a cap, for a given time period…). Note that this has also been considered important in areas like harm minimisation for gambling systems, as well as being a fairly common practice in managing corporate spending where thresholds are set for reporting requirements (analagously to legal cash transaction reporting requirements as it happens).

But we should actively check what we do in this space with the relevant WAI groups - WCAG, and the Cognitive Accessibility task force.



> Note that we should probably also mention this in the Payment Agent
> spec as well.
> -- manu
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: The Marathonic Dawn of Web Payments
> http://manu.sporny.org/2014/dawn-of-web-payments/

Charles McCathie Nevile - web standards - CTO Office, Yandex chaals@yandex-team.ru - - - Find more at http://yandex.com

This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.
Received on Tuesday, 31 March 2015 13:49:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:33 UTC