vibrance
Book a call

Contact forms that work: design based on research and data protection under the GDPR

For many businesses, the contact form is the most important route to new work and at the same time one of the most common sources of errors on a website. This article summarises empirical findings on form design, explains the relevant accessibility criteria and clarifies the data protection questions, from the legal basis to spam protection.

by Kilian Dickmann, Founder and ownerPublished on 6 min read

A contact form looks simple: a few fields and a button. Yet enquiries regularly fail because fields are unclear, error messages are not understood or the form is barely usable on a smartphone. At the same time, it is the place where a website collects the most personal data. Here, design and data protection are closely connected.

What studies show about forms

Twenty guidelines and how they were tested

In 2010, Javier Bargas-Avila and colleagues compiled twenty guidelines for usable web forms from the research available at the time [2]. Four years later, Mirjam Seckler and colleagues tested whether these guidelines work in practice. They took existing forms from large news websites, improved them according to the guidelines and compared both versions in a laboratory experiment with eye tracking and 65 participants [1].

The improved forms were completed faster, led to fewer failed submission attempts, required fewer eye movements and were rated more satisfying [1] [9]. Three points mattered most to participants:

  • Clearly distinguish required and optional fields.
  • State format requirements in advance, not only in the error message, for example how a phone number or a date should be entered.
  • Show error messages directly at the field concerned, not only collected at the top or bottom.

Further proven rules

Practice-oriented summaries by Luke Wroblewski and the Nielsen Norman Group reach similar conclusions [3] [4]:

Rule Reason
As few fields as possible Every additional field costs time and effort. Whatever is not needed for the first reply can be asked later.
Single-column layout The eye follows one line; multi-column forms make it easier to miss fields.
Labels outside the fields Placeholder text disappears when typing and often has low contrast; it does not replace a label.
Suitable input types On a smartphone, an email or phone field opens the matching keyboard.
Understandable error messages Say what is wrong and how to fix it, politely and without jargon.
Validation when leaving a field Errors appear when they are relevant, not after the first letter.
Input is kept Nothing may be lost after an error or a server problem.
Clear confirmation After sending, the page says that the message has arrived and what happens next.

Accessibility

Forms are a focus of WCAG. For a typical contact form, these criteria are particularly relevant [5]:

  • 3.3.2 Labels or Instructions: every field has a label; required fields and formats are explained.
  • 3.3.1 Error Identification and 3.3.3 Error Suggestion: errors are described in text, not only by colour, and where possible with a suggestion for correction.
  • 1.3.5 Identify Input Purpose: fields for name, email or phone are marked up so that browsers can fill them automatically.
  • 3.3.7 Redundant Entry: information already given does not have to be entered again.
  • 3.3.8 Accessible Authentication: cognitive tests such as picture puzzles must not be the only hurdle. This affects many CAPTCHAs.

On top of this come the general requirements for contrast, keyboard operation and visible focus. A form that can be completed and submitted entirely by keyboard, and whose error messages a screen reader reads out, is easier for everyone to use.

Data protection

Anyone who sends an enquiry through a form wants a reply. Under the GDPR, processing the details for that purpose can usually be based on Art. 6(1)(b) where the enquiry is aimed at a contract, and otherwise on the legitimate interest in answering under Art. 6(1)(f) [6].

A checkbox “I consent to the processing of my data” is not required for this and can even create problems. Consent must be freely given; if sending the form is made conditional on it although the processing is necessary for the reply anyway, Art. 7(4) GDPR speaks against it being freely given [6]. In addition, consent can be withdrawn at any time, which leads to unclear situations during an ongoing enquiry. A notice at the form with a link to the privacy policy, which provides the information required by Art. 13 GDPR on purpose, legal basis, recipients and storage period, is sufficient and common.

Data minimisation

Under Art. 5(1)(c) GDPR, only data necessary for the purpose may be collected [6]. For a first enquiry, name, email address and message are usually enough. Phone number, company or budget can be offered as optional fields if they are clearly marked as such. This matches the design rule of using as few fields as possible.

Technical and organisational measures

  • Encrypted transmission via HTTPS is state of the art and required under Art. 32 GDPR [6].
  • Service providers for hosting or sending email process the enquiries on the business’s behalf; a contract under Art. 28 GDPR must be concluded with them.
  • Define the storage period: enquiries that do not lead to a contract are deleted; for contracts, the statutory retention periods apply.

Spam protection without data leaving the site

Many forms use a third-party CAPTCHA to protect against spam. Such services load scripts from other servers, often analyse device and behavioural characteristics and can set cookies; this may require consent under § 25 TDDDG and trigger information obligations [7]. On top of that come the accessibility hurdles mentioned above.

For small websites, simpler methods that work without third parties are often enough:

  • a field invisible to people (a “honeypot”) that automated programs fill in,
  • a time check that discards extremely fast submissions,
  • a server-side limit on the number of enquiries per sender within a short period.

These measures process hardly any additional data, do not burden visitors and are easy to describe in the privacy policy.

No newsletter through the back door

Sending an enquiry is not consent to advertising. Under § 7(2) no. 2 of the German UWG, advertising by email generally requires prior express consent [8]. A newsletter subscription must therefore not happen automatically through the contact form; if it is offered, then as a separate, unticked option, usually with confirmation by email.

Checklist

  1. Does the form contain only the fields needed for a first reply, and are optional fields marked?
  2. Does every field have a visible label that does not disappear when typing?
  3. Are error messages shown at the field, as text, in understandable language?
  4. Can the form be completed and submitted entirely by keyboard?
  5. Is input kept after an error?
  6. Is there a notice referring to the privacy policy at the form, rather than mandatory consent?
  7. Does spam protection work without a third party, or is such a service integrated in a legally sound way?
  8. Does the page confirm receipt and the next step after sending?

Conclusion

A good contact form is short, clearly labelled, forgiving of errors and economical with data. These properties are empirically supported, largely match the requirements of accessibility and at the same time simplify data protection. Doing without consent checkboxes and third-party CAPTCHAs where they are not needed results in a form that lets more enquiries through and offers less legal exposure.

Frequently asked questions

Does a contact form need a consent checkbox?
No. Processing to answer an enquiry is usually based on Art. 6(1)(b) or (f) GDPR. A notice with a link to the privacy policy is sufficient.
Which fields should a contact form have?
For a first enquiry, usually name, email address and message. Further fields only as clearly marked optional details.
How do I protect a form against spam without a CAPTCHA?
With a field invisible to people, a time check and a server-side limit on enquiries per sender.

Sources

The numbers in square brackets in the text refer to this list. Online sources last checked in November 2026.

  1. [1]Seckler, M., Heinz, S., Bargas-Avila, J. A., Opwis, K. & Tuch, A. N. (2014). Designing usable web forms: Empirical evaluation of web form improvement guidelines. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI '14), 1275–1284. research.google/pubs/pub42513/
  2. [2]Bargas-Avila, J. A., Brenzikofer, O., Roth, S. P., Tuch, A. N., Orsini, S. & Opwis, K. (2010). Simple but crucial user interfaces in the World Wide Web: Introducing 20 guidelines for usable web form design. In R. Matrai (Ed.), User Interfaces (pp. 1–10). InTech.
  3. [3]Wroblewski, L. (2008). Web Form Design: Filling in the Blanks. Rosenfeld Media.
  4. [4]Whitenton, K. (2016). Website Forms Usability: Top 10 Recommendations. Nielsen Norman Group. www.nngroup.com/articles/web-form-design/
  5. [5]W3C, Web Content Accessibility Guidelines (WCAG) 2.2, in particular Success Criteria 1.3.5, 3.3.1, 3.3.2, 3.3.3, 3.3.7 and 3.3.8. www.w3.org/TR/WCAG22/
  6. [6]Regulation (EU) 2016/679 (General Data Protection Regulation, GDPR), in particular Art. 5, 6, 7, 13, 25, 28 and 32. eur-lex.europa.eu/eli/reg/2016/679/oj
  7. [7]German Data Protection Conference (DSK), Guidance for providers of digital services (OH Digitale Dienste), version 1.2, November 2024. datenschutzkonferenz-online.de/media/oh/OH_Digitale_Dienste.pdf
  8. [8]German Act against Unfair Competition (UWG), § 7 Unacceptable nuisance. www.gesetze-im-internet.de/uwg_2004/__7.html
  9. [9]Google Research Blog (2014). Simple is better – Making your web forms easy to use pays off. research.google/blog/simple-is-better-making-your-web-forms-easy-to-use-pays-off/

About the author

Kilian Dickmann, Founder and owner

Designs and builds websites for small businesses and writes here about design, technology, accessibility and data protection in practice.

More insights

Questions about your own site?

In a free thirty-minute call we look at it together.