- From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
- Date: Mon, 2 May 2016 13:25:38 -0400
- To: <public-apa@w3.org>
- Message-ID: <53c801d1a497$a5b16b60$f1144220$@gmail.com>
This is the email for Manu last week that I missed because it went to my Knowbility account….. * katie * Katie Haritos-Shea Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA) Cell: 703-371-5545 | <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA | <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 ---------- Forwarded message ---------- From: Manu Sporny <msporny@digitalbazaar.com <mailto:msporny@digitalbazaar.com> > Date: Fri, Apr 29, 2016 at 11:06 AM Subject: Call for reviews of Web Payments HTTP API spec To: John Foliot <john.foliot@deque.com <mailto:john.foliot@deque.com> >, Katie Haritos-Shea <katie@knowbility.org <mailto:katie@knowbility.org> > Hey John and Katie, Just a heads-up that the call for review/support of the Web Payments Core Messages and HTTP API spec is out: https://lists.w3.org/Archives/Public/public-payments-wg/2016Apr/0213.html The group is going to make a decision on it next Thursday during the telecon. Integrating the HTTP API spec into the Web Payments WG failed last week because not enough people read the spec and made comments on it. I need your help - this stuff is important for the Web Payments ecosystem and, I assert, is important for accessibility. The Web Payments HTTP API would enable people with accessibility needs to "bring their own app or device" to a payment interaction. That is, the HTTP API would enable people to have non-interactive payment apps (or interactive ones w/ very specific accessibility features) without having to operate in a browser environment. Imagine an app on a personal device (not a browser) that had an audio interface for payments "Your total is $114.34 for groceries. Would you like to pay?"... "Yes". I'm sure both of you could think of more compelling accessibility use cases for Web Payments (and if you do, please tell me!), but the one above feels compelling enough to support the adoption of the Web Payments HTTP API into the Web Payments Working Group. Please respond to the call for support before close of business next Tuesday so people have the chance to read your thoughts before the call. If you'd like to schedule a call and go through both docs together, I'd be happy to do that too. My availability (all times ET): Mon 1pm-5pm Tue 3pm-5pm Wed 10am-4pm skype: msporny / phone: 540-641-1942 <tel:540-641-1942> -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: The Web Browser API Incubation Anti-Pattern http://manu.sporny.org/2016/browser-api-incubation-antipattern/ -- John Foliot Principal Accessibility Consultant Deque Systems Inc. <mailto:john.foliot@deque.com> john.foliot@deque.com Advancing the mission of digital accessibility and inclusion -- * katie * Katie Haritos-Shea Principal ICT Accessibility Architect (WCAG 2/Section 508/ADA/AODA/QA/FinServ/FinTech/Privacy) <http://www.deque.com/> Deque | Cell: <tel:703-371-5545> 703-371-5545 | <mailto:Katie.Haritos-Shea@Deque.com> Katie.Haritos-Shea@Deque.com | Herndon, VA | <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile Deque | 2121 Cooperative Way | Suite 210 | Herndon, VA | 20171-5344 | Office: 703-225-0380 <https://docs.google.com/a/deque.com/uc?id=0B5reybhGDw0GTExGUjZXbGdJQnc&export=download>
Received on Monday, 2 May 2016 17:26:09 UTC