RE: Call for reviews of HTTP API and Core Messages proposals

That is the point, they have a choice.

​​​​​



* 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: Ian Jacobs [mailto:ij@w3.org] 
Sent: Monday, May 2, 2016 10:56 AM
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Cc: Manu Sporny <msporny@digitalbazaar.com>; Web Payments Working Group <public-payments-wg@w3.org>
Subject: Re: Call for reviews of HTTP API and Core Messages proposals


> On May 2, 2016, at 9:48 AM, Katie Haritos-Shea GMAIL <ryladog@gmail.com> wrote:
> 
> 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?

Am I understanding that the user is not using a browser with assistive technology in these scenarios?

Ian

--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447

Received on Monday, 2 May 2016 15:01:24 UTC