The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,979 other subscribers

Archive for the ‘Usability’ Category

Public traffic ticked vending machines can have good user experience.

Posted by jpluimers on 2021/06/29

At the bottom a few examples on on how not do do user experience.

Most of them are related to public traffic ticket vending machines, which seem to have a common pattern of having very low usability.

Good UX is possible

There is one example I know that has quite a good user experience, because taking usability into account aspart of the design was done at the start of the project.

This is contrary to most machines: they are built by engineers just taking into account their needs and challenges: build from existing parts, allowing for easier serviceability, aiming for ease of manufacturing.

Dutch GVB did it differently: they hired Dutch design agency [WayBack] Fabrique to design and test the user experience before the whole machine went into production.

This resulted in a machine that combines easy usability, good servicing, and straightforward manufacturing process. In addition, an “extended” version that allows for non-electronic payment was designed and manufactured in the same go.

[WayBack] Fabrique

Fabrique is a strategic design agency, specialised in service design, app development, e-commerce and website design. Discover Fabrique!

(Note I am not affiliated, nor endorsed by Fabrique. I just think they did a very good job)

Here are some pictures of the designed and manufactured machines; the vertical stripes light up the place where the next user interaction takes place:

Read the rest of this entry »

Posted in Development, Software Development, Usability, User Experience (ux) | Leave a Comment »

Thread by BiancaPrins: 8 simple steps to improve your site accessibility

Posted by jpluimers on 2021/06/03

[WayBack] Thread by @BiancaPrins: “@jpluimers @rulesbyrosita in begint met simpele dingen: 1) plaats alternatieve tekst bij foto’s (of duidelijke omschri […]” #toegankelijkheid #IT #a11y.

I need to translate it:

#toegankelijkheid in #IT begint met simpele dingen:

1) plaats alternatieve tekst bij foto’s (of duidelijke omschrijving eronder)
2) Voorzie filmpjes van ondertiteling en audiodiscriptie
3) gebruik standaard headers altijd in de juiste volgorde

#a11y 1/2

4) bij laag contrast ‘merk kleuren’ groter lettertype en bold font
5) bij voorkeur geen Italic font gebruiken
6) zorg dat alleen links underlined zijn en hyperlink met ‘weer te geven tekst’
7) duidelijke structuur
8) ‘knoppen’ voorzien van label

Via: [WayBack] Jeroen Pluimers on Twitter: “Wat kan ik beter doen op ? Hoewel eigenlijk bedoeld voor mezelf als offline geheugen, trekt het dagelijks een berg bezoekers, dus het kan vast beter toegankelijk worden…”



Posted in accessibility (a11y), Development, Software Development, Usability, User Experience (ux) | Leave a Comment »

Common UX ant-pattern: “you have Tea and No Tea”

Posted by jpluimers on 2021/03/03

I see this pattern in a lot of user interfaces, especially on web-sites: “you have Tea and No Tea”.

For instance the example from the web site on the right: it indicates in Dutch you are getting a postal package. In the body text it says “because we send it as a letter, you do not get a tracking code” followed by a headed section containing a link to an invalid tracking code.

There was only one historic case where the condition “you have Tea and No Tea” opened doors.

Nowadays you should just put a user story on your front-end team back-log that prevents displaying a tracking code when there is none.

Maybe file an issue for the back-end team as well, to distinguish the cases where you can or cannot track shipments.

If you fix it, then an important to remember that often multiple front-ends share the same code.

In the case of the screen shot on the right, the email system showed the same issue; a strong indication either part of the code, or the design steps have been shared.

For such cases, it helps tracking back where the root of the shared design or code came started, then ensure everything stemming from that root is re-checked to ensure altered copies are inspected for the need of modification.


[WayBack] Thread by @jpluimers: “Er gaat iets mis met @KPNwebcare PostNL tracking codes voor prepaid SIM kaarten vanaf : de “PostNL Track & Trace […]”

Er gaat iets mis met @KPNwebcare PostNL tracking codes voor prepaid SIM kaarten vanaf : de “PostNL Track & Trace code” link mist de 3S en ziet er nu uit als!/track-en-tr… waarbij op * 20 cijfers staan zonder 3S erin.

Hoe krijg ik de goede code?

Ah, een typisch geval van “you have Tea and No Tea” waarbij “Tea” de aandacht trekt, maar “No Tea” niet.

Mooie user story voor een backlog item van jullie front-end scrum teams (;

Applaus als jullie trouwens laten zien deze klassieker te kennen (;

and [WayBack] Thread by @jpluimers: “@KPNwebcare Doe ik. Zowel site als email hebben hetzelfde probleem. @KPNwebcare Daar zitten deze twee zinnen in: “Handig om te weten: omdat […]”

Doe ik. Zowel site als email hebben hetzelfde probleem.
mentions Daar zitten deze twee zinnen in:

“Handig om te weten: omdat uw bestelling via post wordt verstuurd, is het niet mogelijk om deze via een Track & Trace code te volgen”


“Track & Trace code
Dit is uw persoonlijke PostNL Track & Trace code”

Met daarin dezelfde foutieve link.


Read the rest of this entry »

Posted in Development, Software Development, Usability, User Experience (ux) | Leave a Comment »

Why a study with only 7 respondents can be good – from Dutch paper “De Volkskrant”

Posted by jpluimers on 2021/01/07

[] Waarom een onderzoek met maar 7 respondenten toch goed kan zijn | De Volkskrant: Denkfouten in het hedendaags ontwerp gefileerd door innovatie-expert (en cabaretier) Jasper van Kuijk. Deze week: gebruikstest.

Google translated in English.


Quantitative studies often require large numbers of respondents, but quantitative studies can be done with a very small group.

While quantitative studies often will get you just one result (I rate this application a 7 out of 10, or with this A/B change, click through increases by 5%), qualitative studies will get you much more specific comments like “the main menu is cluttered”, or “the design is slick” (translated from the Image in the article).

Extensive research was done for a 2003 published paper [] Beyond the five-user assumption: Benefits of increased sample sizes in usability testing which you can read as PDF [WayBack].


[WayBack] Jasper van Kuijk on Twitter: “Mijn ‘Hoe moeilijk kan het zijn?’ van vandaag. Waarom voor gebruiksgemak een gebruikstest met 7 participanten nuttiger is dan een enquête met 1500 respondenten. #HMKHZ via de @volkskrant”


[WayBack] Ionica Smeets on Twitter: “Hear, hear! Aldus een wiskundige die heel wat jaren nodig had om waarde van kwalitatief onderzoek in te zien…”




Read the rest of this entry »

Posted in Development, Software Development, Testing, Usability, User Experience (ux) | Leave a Comment »

960 Grid System

Posted by jpluimers on 2020/11/19

Would this be the reason that so many web-sites still use less than half of my screen width?

The 960 Grid System is an effort to streamline web development workflow.

Source: [WayBack] 960 Grid System

Via: [WayBack] windows – What minimum screen size should I assume? – Stack Overflow (where in 2010 for some types of software you had to go for 640×480, many things were still 800×600, but 1024×768 for desktop users was the norm; on the one hand times have changed, but on the other hand not a lot).

Code: [WayBack] GitHub – nathansmith/960-Grid-System: The 960 Grid System is an effort to streamline web development workflow.



Posted in Development, Software Development, Usability, User Experience (ux), Web Development | Leave a Comment »

%d bloggers like this: