FW: [Web Payments] Call for reviews of HTTP API and Core Messages proposals

Below I responded to the 'Call for reviews of HTTP API and Core Messages proposals' work to be included in the W3C Web Payments WG task to build the web Payments architecture. 

​​​​​I beleive the web payments HTTP API proposal will allow users with disabilities (whether or not they are using AT), to utilize the W3C Web Payments specs to complete transactions by using their preferred UI/wallet/system. 

Ian had asked for me to elaborate on my response for the list and I did:

"Ian,

If a user is mobility impaired and needs their preferred voice-only UI wallet/agent/system (that uses this HTTP API) to complete a payment using our architecture, they can.

If a user is blind and uses a screen reader, and they need to use a specific UI wallet/agent/system (that uses this HTTP API) that they have chosen because it works best with their screen reader, to complete a payment using our architecture, they can.

If a user has cognitive limitations and need a simplified UI wallet/agent/system (that uses this HTTP API) that they have chosen because it works best for them, to complete a payment using our architecture, they can.

Does that help?"

This is one area of the W3C web payments where we may be able to get some traction and have the greatest impact. Making specificc suggestion for this proposal may help us and Manu get this taken up by the Working Group. I will forward Manu's email to this list next - as this measure failed to pass last week in the WG meeting.....



* katie *
 
Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
 
Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545


-----Original Message-----
From: Katie Haritos-Shea GMAIL [mailto:ryladog@gmail.com] 
Sent: Monday, May 2, 2016 10:31 AM
To: 'Manu Sporny' <msporny@digitalbazaar.com>; 'Web Payments Working Group' <public-payments-wg@w3.org>
Cc: ryladog@gmail.com
Subject: RE: Call for reviews of HTTP API and Core Messages proposals

1. Intergrrating the HTTP API into the Web Payments architecture is one of the most important immediate ways that Accessibility can be incorporated into payments by allowing users with disabilities to utilize their own preferred UI/device (that may or may not use assistive technologies), that uses this HTTP API. Meaning they can use the interaction model (auditory, simplified UI, text only, etc.) that they need to complete the payment.

2. This work is vital to the Accessibility of the W3C web payments work.

3. Knowbility considers the accessibility of the core Web Payments the highest priority, of course!


-----Original Message-----
From: Manu Sporny [mailto:msporny@digitalbazaar.com] 
Sent: Wednesday, April 27, 2016 9:05 PM
To: Web Payments Working Group <public-payments-wg@w3.org>
Subject: Call for reviews of HTTP API and Core Messages proposals

Hi all,

This is a friendly reminder to make sure you review the Core Messages and HTTP API proposals found here before next Thursday and send your thoughts back to the mailing list:

http://w3c.github.io/webpayments/proposals/core-messages/  

http://w3c.github.io/webpayments/proposals/web-payments-http-api/ 

When you review them, please:

1. Email any review comments you have back to the mailing list.
   An example of review comments can be found here:

https://lists.w3.org/Archives/Public/public-webpayments-ig/2016Apr/0048.html

   Note: Your review doesn't have to be anywhere as thorough as the one
         above, but it should demonstrate that you've read the document
         closely.

2. Let us know if you think the work should be taken up by the
   Working Group.

3. Note how important the work is to your organization and mention what
   you think its priority should be.

-- manu

--
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc.
JSON-LD Best Practice: Context Caching
https://manu.sporny.org/2016/json-ld-context-caching/

Received on Monday, 2 May 2016 17:23:16 UTC