One of the most annoying user interface flaws, IMHO, is when a web site wants a credit or debit card number, and rejects it if you include the spaces that are shown on the card.
I just went to pay a council tax bill, and the form there went one "better": the field for your card number has a JavaScript event handler that actively rejects spaces (along with all other non-numeric characters)
FFS people, this is Usability 101: it's hard for humans to read a string of 16 digits and be sure they got them all correct and/or in the right order. This is why the card is manufactured with spaces in the number dividing it into easy-to-read four digit groups.
If your back-end system wants it without spaces, then strip the spaces on the back-end when you process the input, don't just prevent them being input at all in the user interface. Shoddy, shoddy, shoddy
And who was responsible for providing this chunk of fail? Step forward Crapita, renowned purveyors of barely-functional, badly-designed usability nightmares to the powers-that-be at our expense.
I just went to pay a council tax bill, and the form there went one "better": the field for your card number has a JavaScript event handler that actively rejects spaces (along with all other non-numeric characters)
FFS people, this is Usability 101: it's hard for humans to read a string of 16 digits and be sure they got them all correct and/or in the right order. This is why the card is manufactured with spaces in the number dividing it into easy-to-read four digit groups.
If your back-end system wants it without spaces, then strip the spaces on the back-end when you process the input, don't just prevent them being input at all in the user interface. Shoddy, shoddy, shoddy
And who was responsible for providing this chunk of fail? Step forward Crapita, renowned purveyors of barely-functional, badly-designed usability nightmares to the powers-that-be at our expense.
Comment