Re: Comments on Use cases 1.0

On 05/21/2015 06:34 AM, Léonie Watson wrote:
> Responses inline...

Thanks Léonie, further responses inline...

>> Mobile:
>> 
> Hmm, "tap to pay" in this case means...
> 
> Ah. Ok, I hadn't understood the interaction. The problem remains the 
> same though - how does someone who is unable to see the screen know 
> how much they're paying? If the amount also appears on the payer's 
> device, that's a good solution. If it doesn't/wouldn't, then there 
> needs to be some way for that to happen.

The amount appears on the payer's device. The payer's accessibility
technology would kick in at that point and let them know exactly how
much they're paying and provide a preferred interface to continue the
payment.

I've updated the language to remove the "tap to pay" terminology and
tried to make it more clear about what's actually going on:

Daniel takes a taxi from the airport to his hotel. The taxi driver
displays the total with his mobile device. Daniel and the taxi driver
touch their mobile devices to each other. The total appears on Daniel's
mobile device.

https://github.com/w3c/webpayments-ig/commit/c9905e2289a6c74698ca785355cbe3f3a4167da9

>> If work will be done to identify common design patterns within 
>> digital wallet interfaces, it may be worth putting together some 
>> guidance on how best to make those things accessible?
> 
> Yes, absolutely, and we look forward to working w/ you to put that 
> document together. :)
> 
> No problem, would be happy to help :) How can we best approach doing 
> this?

I think a liaison activity between this group and WAI might be a good
first step. Reviews like the one you did, and Katie continues to do, are
very helpful. Could we add a "Web Payment Accessibility Best Practices"
document to WAI's charter? Or whatever group you think is best?

The timeline for this is probably well into the future - starting
early-to-mid 2016. Thoughts from you? Thoughts from the WPIG group?

> Let us know if these changes have addressed the concerns you had
> with the document.
> 
> With perhaps a little more thinking about the tap to pay use case, 
> they do. Thank you.

I think I covered all of them, let me know if I missed anything. :)

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Web Payments: The Architect, the Sage, and the Moral Voice
https://manu.sporny.org/2015/payments-collaboration/

Received on Saturday, 23 May 2015 01:48:25 UTC