Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Accessibility · 17 Nov 2026 · 6 min read

Accessible forms: labels, errors and keyboard use

Accessible forms can be completed with a keyboard, a screen reader or magnification. This guide covers labels, error messages and a simple keyboard test.

The short answer

Accessible forms have a visible label linked to every field, a logical order, instructions before the field and error messages written in words and linked to the field. Everything must work with a keyboard alone. Test by tabbing through the form, checking visible focus, and fixing deliberate errors without a mouse.

What makes a form accessible

Accessible forms can be understood and completed by people who use a keyboard instead of a mouse, a screen reader, voice control, magnification or who simply need more time and clearer wording. Most of the work is done with correct HTML and clear writing, not with special tools.

Five things decide most of it:

  • Every field has a label that is programmatically linked to it.
  • The order of fields makes sense, and the keyboard follows that order.
  • Instructions appear before the field, and not just after an error.
  • Errors are described in words, found easily and linked to the field.
  • Nothing relies on colour, hover or a mouse alone.

Forms are where the money is made on many sites: enquiries, bookings, sign-ups, checkout. A form that excludes people loses real business, and the loss is silent because nobody reports it. If your form is the main contact route, read this with our guide to website navigation and menu structure in mind, since a visitor must also be able to reach the form with a keyboard.

Labels that work

A label must be connected to its field in the page code, so that a screen reader announces "Email address, edit text" when the field gets focus, and so that clicking the label puts the cursor in the field. A visible text label sitting near the box is not enough on its own if it is not linked.

Do not use placeholder text as the label. Placeholders vanish when typing starts, are often low contrast, and are not reliably announced. Use them, if at all, for an example format, such as a sample date.

Keep labels short and specific. "Phone number" is clearer than "Contact". When several fields belong together, such as the parts of an address or a set of radio buttons, group them with a fieldset and a legend that names the group. A set of options headed "Preferred contact method" needs that heading announced with each option.

Say which fields are required, in text. An asterisk alone is not enough unless the form explains it. Mark optional fields as optional if most are required.

Help text and instructions

Put instructions where they are needed, before the field. If a password has rules, or a date needs a particular format, say so up front. The help text should be linked to the field so that assistive software reads it with the label.

Avoid timed forms where possible. If a time limit exists, warn the person and let them extend it. Do not clear what they typed if the session expires.

Use the right input type for each field: email, telephone, number or date. Mobile devices then show a suitable keyboard, and many browsers can fill saved details. Turning on the browser's autofill hints for name, email and address fields saves effort for people who find typing slow or hard.

How errors should be shown

Good error handling is the biggest difference between a form people can finish and one they abandon. Follow these points.

  1. Describe the problem in text. "Enter an email address in the format name@example.com" beats "Invalid input".
  2. Put the message next to the field it concerns, and link it to that field in the code so a screen reader announces it.
  3. Do not show an error with colour alone. Add text, and an icon if you like.
  4. When the form is submitted with errors, move focus to a summary at the top or to the first problem field, so keyboard and screen reader users know something happened.
  5. Keep everything the person has already typed.
  6. Explain how to fix it. Say what is wrong and what to enter, instead of just saying something is wrong.

Avoid validating too early. An error that appears after the first typed letter in an email field is annoying and confusing. Check when the person leaves the field or when they submit.

After a successful submission, confirm it clearly and move focus to the message. A confirmation that appears silently somewhere on the page may never be noticed by a screen reader user. Our guide to website contact forms covers what should follow submission on the business side.

How do I test a form with a keyboard?

You do not need special software for the first round of testing. Put the mouse aside and work through the form with the keyboard.

  1. Press Tab to move forward through fields, and Shift with Tab to move back. Does the order follow the visual order?
  2. Check that you can always see where focus is. A visible outline or highlight must appear on every field, button and link.
  3. Use the arrow keys inside groups of radio buttons, and the space bar to tick boxes.
  4. Open any dropdown, date picker or custom widget with the keyboard and choose an option. Custom widgets are the usual failure point.
  5. Press Enter to submit and confirm that you reach the confirmation.
  6. Submit with errors deliberately and check that you can find and fix each one without the mouse.
  7. Check that you never get stuck, for example inside a pop-up you cannot close.

Then try a screen reader on the same form, and listen. Do labels, instructions and errors make sense in spoken form? Also zoom the page in until the text is much larger, and check that the form still works and that nothing is cut off. If you are not sure how to run a screen reader, ask a developer or an accessibility specialist to demonstrate, or check the current documentation of the screen reader that comes with your computer.

Always test on a copy first, because forms handle real data. A staging site lets you test safely without sending real enquiries.

Common mistakes

These problems show up again and again on small business sites.

  • Placeholder text used as the only label.
  • Custom dropdowns and date pickers that work only with a mouse.
  • A challenge puzzle for spam protection with no accessible alternative.
  • Error messages that vanish after a few seconds.
  • Focus that disappears because the style was removed for appearance.
  • Buttons built from plain page elements that the keyboard cannot reach.
  • Required fields marked only by colour.

Many of these come from plugins and add-ons. Choose a form tool that outputs standard markup, and test it, rather than trusting a claim on its sales page. The hosting and the theme do not change the principle; a form that fails on one platform will usually fail on another. If you are unsure how your site is hosted, types of web hosting explained can help you ask the right questions.

Fonts matter too. A very thin font or tiny text on labels makes fields hard to read, as discussed in our guide to choosing and loading web fonts.

Where this fits in the wider picture

Accessible forms are one part of an accessible site. Law and regulation on accessibility differ by country and change over time, so ask a qualified lawyer what applies to you. If you collect personal data in forms, read about what a privacy policy and other legal pages are for, and make sure the form links to yours.

No form will suit every user, because needs vary, but a form built on clean markup and tested with a keyboard and assistive software is a far better starting point. If you want help with forms on your site, see our website development service.

Related guides

Questions and answers

What makes a form accessible?

Each field has a visible label linked to it in the code, the order is logical, instructions come before the field, errors are written in words and linked to the field, and everything works without a mouse. Do not rely on colour alone.

How should form errors be shown?

Describe the problem in plain text next to the field, link the message to the field in the code, never rely on colour alone and keep what the person typed. After a failed submit, move focus to an error summary or the first problem field.

How do I test a form with a keyboard?

Use Tab and Shift with Tab to move through the fields, check that focus is always visible, use arrow keys on radio groups, open any dropdown or date picker, press Enter to submit, and fix deliberate errors without a mouse.

Is placeholder text enough as a label?

No. Placeholder text disappears when typing starts, is often low contrast and is not reliably announced by assistive software. Use a real label and keep the placeholder for an example format only.

Are CAPTCHAs bad for accessibility?

They can be. Puzzles that rely on sight or fine motor control block some users. If you use one, offer an accessible alternative, or use background checks that need no puzzle, and test with a keyboard and screen reader.

Do I need an expert to make forms accessible?

Many fixes are straightforward for a developer: labels, input types, error handling and focus. For a formal review, or for legal questions, ask an accessibility specialist or a qualified lawyer in the relevant country.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote