RE: AW: APA Web Payments sub-group: ACTION-2078: Draft and send an email to the WAI-IG, asking for help with the PAUR -- DRAFT message

Thanks Chaals, Katie and All

 

I’m DeafBlind and dependent on screen-readers on laptops and mobiles (as we call them in the UK).

 

I wouldn’t use my mobile (an IPhone5) for payment as it is virtually impossible to input numbers or text without a bluetooth keyboard (screen display of characters/numbers to touch and input are poorly designed.

 

Trouble, also, via a laptop. When paying, eg. Via Amazon, the website diverts to my bank account for permission to release funds.

 

I am asked for a random selection of characters from my bank password – 1 at a time, up to 3 characters.

 

This is challenging as have to switch between screens to check password then go back to input.

 

The password entries are also *ed out. So I have to know my keyboard very well to be sure of correct entries.

 

Exgtra best,

Howard (Leicester)

Kent, England, UK.

 

 

From: Chaals McCathie Nevile [mailto:chaals@yandex-team.ru] 
Sent: 11 August 2016 11:02
To: 'WAI Interest Group' <w3c-wai-ig@w3.org>; Batusic, Mario <mario.batusic@fabasoft.com>
Subject: Re: AW: APA Web Payments sub-group: ACTION-2078: Draft and send an email to the WAI-IG, asking for help with the PAUR -- DRAFT message

 

On Fri, 05 Aug 2016 09:57:36 +0200, Batusic, Mario <mario.batusic@fabasoft.com <mailto:mario.batusic@fabasoft.com> > wrote:

Hi Katie, All,

 

Buying/paying something online works over a web site or a web application – better: something in between. So it  should suffice to make this web source accessible according to WCAG 2.0, improving all web application parts eventually with WAI-ARIA to make the paying process accessible.

 

 

 

For me as a blind person the real problem during payment processes is the sometimes activated, very short time-out time that is inpossible to prolong.

Futhermore I need a very clear statemnet about the current status of my payment: was the previous step OK and what exactly is the current one that I have to handle.

 

Both of these are problems I have faced.

 

Another is where the actual payment step means I temporarily lose the information about *what* I am paying for. This can cause pretty substantial levels of anxiety, as I suddenly can't make a last thorough check at the moment I most want to do so.

 

cheers

 

 

Ciao     Mario

 

Von: Katie Haritos-Shea GMAIL [mailto:ryladog@gmail.com] 
Gesendet: Donnerstag, 04. August 2016 21:59
An: public-apa@w3.org <mailto:public-apa@w3.org> ; 'WAI Interest Group' <w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> >
Cc: 'Janina Sajka' <janina@rednote.net <mailto:janina@rednote.net> >; ryladog@gmail.com <mailto:ryladog@gmail.com> 
Betreff: APA Web Payments sub-group: ACTION-2078: Draft and send an email to the WAI-IG, asking for help with the PAUR -- DRAFT message

 

Dear APA Web Payments sub-group,

 

Below is the message I intend to send to WAI-IG concerning the need to collect personal experiences of persons with disabilities to help us (the APA Web Payments sub-group) develop some use cases for the Payment Accessibility User Requirements (PAUR). Please send any additions or comments to me tonight, as I plan to send it out tomorrow.  Thanks!

 

 

 

Email Subject: Call for Discussion: Help with use cases for the Payment Accessibility User Requirements (PAUR) document.

 

 

Dear WAI Interest Group,

 

We, the APA Web Payments sub-group, need your help. We would love to hear about personal experiences and frustrating issues that you, as persons with disabilities, have encountered, or might expect to encounter, when making payments on the web.

 

 

HISTORY:

 

The APA Web Payments sub-group, falls under the W3C’s Accessible Platform Architectures (APA) Working Group. As many of you know APA’s mission is to ensure W3C specifications provide support for accessibility to people with disabilities.

 

 

TOPIC FOR DISCUSSION:

 

Our sub-group for Web Payments is working on Use Cases for the Payment Accessibility User Requirements (PAUR) document. This document is intended to present the accessibility requirements and needs that users with disabilities have with respect to making payments on the web.

 

We will be collecting your personal experiences and turning them into use cases for the PAUR.

 

 

HOW TO CONTRIBUTE:

 

Please respond to *this* email list at: w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org> . If you share this email with others who are not on this list, please be sure that they understand they need to subscribe to this list before they can directly post here. See HOW TO SUBSCRIBE below.

 

Please send your experiences, thoughts and feedback by September 1st.

 

We also would welcome those with technical expertise in web payment design/development, finance and accessibility to join our sub-group.

 

 

HOW TO SUBSCRIBE:

 

Users will need to subscribe before they can directly post to this list. To join/subscribe to the WAI IG list, send an email to w3c-wai-ig-request@w3.org <mailto:w3c-wai-ig-request@w3.org>  with “subscribe” as the subject line. Also, please invite your friends to join us on the WAI IG.

 

Thank you for your support!

 

 

 

 

* 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 |  <https://twitter.com/Ryladog> @ryladog

 





-- 

Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru <mailto:chaals@yandex-team.ru>  - - - Find more at http://yandex.com