The Contact

CAPTCHAs provide a task that the interviewee has to solve, in a form that is (relatively) easily solvable for people, however, very difficult for computers. An example of this is a text that has been distorted by an image filter (graphical CAPTCHAs). These CAPTCHAs are so used to decide whether the other party is a person or a machine, say, whether a computer program that fills out the contact form (with unsolicited advertising or simply nonsense) or a person. However, CAPTCHAs are also problematic from a Bedienbarkeits perspective, as they represent barriers which lead to a significant overhead for the user in the achievement of the target part (such as hard-to-decipherable CAPTCHAs). This most image-based CAPTCHAs are not accessible.

You cannot be resolved by sensory disabled people with the result that these people can not submit the form. Barrier arms solutions barrier arm would be, for example, the use of a simple math question in Writing (3 plus 4 equals “”). Such a task could be opening up through a screen reader (screen reading program for blind or severely visually impaired Internet users). The content of the contact form is sent only after the entry of the correct result. Without comment the purpose of CAPTCHAs opens up many users not intuitive, which leads to irritation over a seemingly pointless function. Who here briefly as a footer that explains why such a task before submitting the form to resolve, reap understanding from its users. Otherwise use crashes, error messages, and dissatisfaction among the users of the sources of these problems often result.

According to a current study (source: Wikipedia) Internet users spend worldwide a total 150,000 hours per day with solving CAPTCHAs. One moves so the thin line between usability and spam prevention conclusion when deciding on the use of CAPTCHAs. It is important to consider whether a CAPTCHA is actually is required or the Internet user (customer) is unnecessary barriers in the way.