Gotcha. When talking about accessibility, things are always couched in conditionals (e.g., when the payment app presents a user interface that allows for the selection from a list of one or more payment methods, that list must be exposed in such a way that assistive technologies can ensure the list is selectable by users with visual and/or motor skill challenges). So I don't think we are disagreeing on that point. I agree about internal processing... I think. It might be nice to suggest messaging structures that would improve their interoperability and ease of use in the case of push payments, for example. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/110#issuecomment-210127667Received on Thursday, 14 April 2016 20:10:16 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:15 UTC