Tims issue paper on web Payments

I want to add some issues to the thread at http://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2014Nov/0030.html
on web Payments

1. Too many options and additional options add to the complexity. Additional options should be trivial to ignore and not require a lot of reading to understand that they are: a, additional and b, how to skip them 

2. Sometimes the interface aims to confuse the user, such as the default "quantity" being set to "2" and not one. This to me is defrauding the vulnerable. The user then needs to reset it to 1. Any attempts to trick the user into buying anything other then what they intended at the price that they intended, is, in my opinion, fraudulent when the user is in a coga group.

3. A similar scenario is included in extra costs. Estimates for all costs should be made clear at the beginning of the task. Dito for other criteria.

4. scaffolding help is important

5. I would stress the need for bread crumbs, that also show what steps are coming (faded out). It also means that if a user is unable to complete all the steps they will not start the task, avoiding frustration .
All the best

6. I would also suggest the issues of unexpected behaviors, such as opening a new window, or change of context. It needs to follow the flow of the bread crumbs.

7, sessions data should not time out without a lot of warning (so the user can get a cup of tea without lose of data or flow, and info must be save. This stuff is hard and we need to help people achive it.
Lisa Seeman

Athena ICT Accessibility Projects
LinkedIn, Twitter