Surveys13 min read

Form Accessibility Checklist (WCAG) for Better User Experience

Use this form accessibility checklist to make online forms easier for everyone to use. Learn how to follow WCAG 2.2 guidelines for accessible form fields, keyboard navigation, screen readers, colour contrast, error messages, mobile usability, and accessibility testing.

Nikhil Dogra

November 18, 2026

Form Accessibility Checklist (WCAG) for Better User Experience

Introduction

Forms may appear very usable with a mouse, however they may be difficult to use with different methods. For example, the user may get ‘stuck’ within a dropdown using keyboard navigation, or may not be able to understand which information is requested in a form field due to it being announced as ‘edit text’ in a screen reader. Alternatively, low contrast text may cause difficulties in understanding instructions.

These issues may be easy to overlook in a design review, but can mean users cannot complete sign ups, applications, payments or get in touch with a business.

Designing accessible forms allows people with varying abilities and interactions to perform the same tasks. Consider screen reader support, keyboard navigation, clear labelling, readable text, clear guidance, useful error messages and mobile support.

This checklist covers best practice for making accessible forms in line with the Web Content Accessibility Guidelines (WCAG) 2.2. It gives you some things to consider, why they matter, and how designers and developers can ensure accessibility of online forms before publishing.

Why it Matters

Forms are often used by websites to prompt actions from users. If they are inaccessible, users may not be able to complete sign-ups, applications, support requests or purchases.

It is important to consider accessibility in forms for people with low vision, colour blindness, poor motor control, hearing or cognitive impairments, people with temporary injuries, or simply people using a device in difficult conditions.

To increase digital accessibility, the World Wide Web Consortium (W3C) have provided a set of guidelines to follow (WCAG). In comparison to previous iterations, WCAG 2.2 includes guidance relevant to forms in order to increase accessibility including duplicate entry, accessible login systems and minimum size targets.

According to a February 2026 analysis of 1 million home pages by WebAIM, 95.9% of home pages contained some detectable WCAG issues. 51% were missing labels on input fields, and 83.9% had text with low contrast. (Note: This was an automated analysis of accessibility issues and does not constitute full accessibility audits). Therefore it is clear that even basic accessibility issues are common.

Implementing accessibility in forms can help businesses by:

  • Making crucial tasks accessible to more people.

  • Reducing confusion for users.

  • Avoiding avoidable errors and incomplete submissions.

  • Improving usability across different devices and input methods.

  • Meeting accessibility policies and any legal requirements.

Find out more about creating usable forms by exploring some of the features available in online form builders here.

10 Things to Check for Accessibility in Forms

Below is a list of things to consider to make forms accessible. While the WCAG references show relevant success criteria, completing these checks does not necessarily mean a form meets WCAG requirements.

1. Label all inputs

WCAG Success Criteria: 1.3.1, 2.4.6, 3.3.2, 4.1.2

Each input should have a clear label.

Placeholders should not be used alone as they may not be consistently announced by screen readers and are typically hidden when a user begins to type.

To make forms accessible, label all input fields. Ensure labels are associated with the input and provide concise information. Clearly mark required fields and provide guidance for any special formatting requirements.

For example, instead of using the generic label ‘Email’, use ‘Work Email’. If a date is requested, use ‘Date of Birth (DD/MM/YYYY)’.

Group radio buttons or checkboxes together in a fieldset with a legend so that users with assistive technologies can understand the question and all choices.

2. Make it keyboard accessible

WCAG Success Criteria: 2.1.1, 2.1.2, 2.4.3, 2.4.7, 2.4.11

Not everyone will complete a form using a mouse or touch screen. Users may complete forms using a keyboard, alternative devices, or other assistive technology.

To make a form keyboard accessible, the user should be able to:

  • Navigate through the form using Tab/Shift+Tab keys.

  • Make choices with appropriate keyboard controls.

  • Activate buttons with Enter/Space.

  • Interact with dropdown menus and date pickers without using a mouse.

  • Leave interactive components (such as dialog boxes).

Navigation through a keyboard accessible form should follow visual order, and users should not be taken between sections of a form unexpectedly.

Visibility of focus is very important. If you hide the default focus styles from browsers, provide an equally clear focus indicator. Ensure that fixed elements such as headers, banners or floating chat widgets do not obscure the focussed element.

3. Use good contrast

WCAG Success Criteria: 1.4.1, 1.4.3, 1.4.10, 1.4.11

Even if a form includes nice colours, the colours may not be easy to read. People with low vision or colour blindness may struggle to read the form if there is poor contrast.

As a general rule, text should have a minimum contrast ratio of 4.5:1, large text 3:1. Main UI elements and visual cues should generally have a contrast ratio of 3:1 with surrounding colours.

Avoid using only colour to convey information. For example, if an error occurs, adding a red box around the field is inadequate. Provide a text explanation, such as "Enter a valid email address, such as name@example.com."

Check text, labels, buttons, borders, focus indicators and error messages. Ensure it is easy to read under various light conditions and when zoomed in on the browser.

4. Provide clear error messages and guidance

WCAG Success Criteria: 3.3.1, 3.3.3, 3.3.4, 4.1.3

Users should know why they have an error in their form submission.

Any error in a form should be clear to the user with guidance on how to correct the error. A generic message such as ‘Invalid input’ should not be used.

Instead, include messages such as:

  • ‘Please enter a valid email address (example@domain.co.uk).’

  • ‘Password must be 8 characters or more.’

  • ‘Please choose an option.’

Error messages should be placed close to the relevant field. Link errors to the field in code with aria-describedby. Where a field contains invalid data, include aria-invalid="true".

If errors are shown dynamically, ensure they are announced by assistive technologies. Including a summary of errors and linking to relevant fields after a failed submission will make it easier for users to locate and resolve issues.

If the form relates to an important action (such as payments or legal actions), include an option for the user to review and amend information before proceeding.

5. Optimise for mobile

WCAG Success Criteria: 1.3.4, 1.3.5, 2.5.8

In addition to fitting on a smaller screen, it is important to consider mobile accessibility in forms.

Ensure the form can be used easily on mobile by:

  • Providing input fields of a large enough size.

  • Ensuring text is readable without excessive zooming.

  • Providing enough spacing between buttons and controls.

  • Appearing correctly in portrait and landscape orientation.

  • Allowing users to complete forms without horizontal scrolling at the reflow width.

  • Using input types which provide appropriate keyboards on mobile.

WCAG 2.2 requires that all pointer targets are a minimum of 24x24px (CSS pixels) in size (some exceptions apply). However, providing a larger size (for example 44x44px) will be easier to use for touch screen users. To meet enhanced AAA standards, this is recommended.

Include suitable autocomplete options for things such as names, emails and phone numbers. This will make it easier to fill in forms and reduce typing for mobile users and users with assistive technologies.

6. Avoid repetition

WCAG Success Criteria: 3.3.7, 3.3.8

Long forms can be tedious, and repeating information may become frustrating for users.

Review each piece of information requested and ask if it is really necessary. Avoid asking users to enter information that can be known or safely retrieved by the system.

For example, during checkout processes, provide an option for users to apply the same address as the billing address.

To make log in forms accessible:

  • Allow pasting of passwords.

  • Support password managers.

  • Avoid unnecessary memory or puzzle based authentification.

  • Provide an accessible alternative if authentification is creating a barrier.

If the form has multiple sections, split them into sensible steps. Including a progress indicator and allowing users to edit previous answers can make longer forms more accessible.

7. Allow plenty of time to complete

WCAG Success Criteria: 2.2.1

Sometimes forms will have time limits due to security and session requirements. However, users may take longer to understand instructions, answer questions, and input information with assistive technologies.

If it is not essential to include time limits, allow users to turn them off, change them, or extend them. If sessions will end, provide warnings to users and let them know what will happen to their information.

Not everyone will be able to complete a form at the same speed. Giving users a little flexibility can help avoid them losing their work.

8. Provide clear instructions and consistent design

WCAG Success Criteria: 3.2.3, 3.2.4, 3.3.2

Users should understand what is required of them in the form.

Give clear instructions close to any relevant fields. Include explanations for why sensitive information is requested, any formatting requirements, and what will happen after submission.

Ensure a consistent design for labels, required fields, buttons and validation messages.

For example, if the first section of your form includes clear labelled fields, don’t switch to unlabeled placeholder fields in the middle of the form.

If the form has multiple sections, make sure heading titles make sense and let users know where they are and what information is required.

9. Make dynamic content accessible

Including dynamic content like conditional questions, drop down menus, collapsible sections and interactive widgets can make forms more usable. However, this content may create accessibility issues.

If new content is shown depending on the user’s choices, ensure that it is announced correctly and is accessible via keyboard.

Ensure:

  • New input fields have meaningful labels.

  • Fields which are hidden are not accidentally keyboard accessible.

  • Dropdowns can be navigated without a mouse.

  • Expanded/collapsed sections inform the user of their current state.

  • Focus doesn’t unexpectedly move with changing content.

If conditional logic has been used, make sure to test all possible paths through the form, not just the default option.

10. Keep user information safe & explain what will happen next

Users should know why information is being requested from them, and what will happen once they have completed the form.

This is particularly important if sensitive information is requested, including personal, financial and employment information.

Inform users of:

  • What information is requested and why.

  • What will happen with the information.

  • If users can save and return to the form later.

  • What will happen after submission.

  • How to get in touch with the organisation for help.

After a successful submission, make sure the confirmation is clear. Don’t just change the colour or add a subtle animation.

Making sure forms are accessible before publishing

While this checklist is very useful, it is also important to conduct actual testing. Whilst automated tests can highlight many technical issues, we cannot be 100% sure that a form is accessible and easy to understand for all users.

A practical approach to testing could be:

Conduct automated testing

Tools like WAVE and axe can help to identify issues like missing labels, contrast issues and accessibility errors.

Conduct automated testing on the live form. Even if no issues are picked up, it is important to look at each issue to be sure the form is accessible.

Keyboard navigation

Try to complete the form with only keyboard navigation.

Check that all fields can be reached, focus navigation makes sense, selections can be made, errors can be corrected, and that the form can be submitted. If you get stuck, investigate what is causing the issue with that particular control/interaction.

Screen reader testing

Using screen readers (NVDA on Windows, or Voiceover on apple devices) will help you understand what is being announced.

Note what is being said for labels, instructions, required fields, errors and confirmations. Make sure that the purpose of each field is clear, even without visual context.

Zoom and mobile testing

Zoom in on the form and check it is usable without excessive horizontal scrolls. Also test on a real mobile device, as well as in device mode in the browsers dev tools.

Be aware of small buttons, overlapping content, cut off instructions and hard to select fields.

Testing with users with disabilities

If possible, get people with disabilities to test the form. They may highlight issues that aren’t picked up by automated testing or internal reviews.

Take note of the issues they face, and fix them. Re-test the form to make sure the issues have been resolved.

Common Accessibility issues in forms

Even if a form is well designed, there may be small issues which create large accessibility barriers. Be wary of:

  • Missing labels in favour of placeholders.

  • Removing keyboard focus styling.

  • Using only colours to show errors.

  • Vague labels such as ‘Details’ or ‘Other’ without explanations.

  • Creating custom controls without keyboard accessibility.

  • Adding ARIA attributes in places where native HTML would be more appropriate.

  • If new conditional questions are shown, ensuring focus is managed and the questions are announced.

  • Testing with desktop and mouse only.

  • Considering accessibility only once and not regularly.

Native HTML controls should be used wherever possible. If ARIA is used, it should be correctly implemented to improve accessibility. Using incorrect or unecessary ARIA can create further issues.

Examples of Accessible Form Design

Understanding accessibility in forms becomes much easier through real World Examples.

SaaS Sign Up Form

On a software site, placeholder text has been replaced with labels. Password managers are supported, users can paste in passwords and clear instruction on password requirements are included.

This makes the sign up process easier to understand and complete across different devices and assistive technologies.

Checkout Form

An online shop previously showed errors using only red borders. Error messages have been added, error messages link to relevant fields, and a review step has been added before payment.

Customers can now understand what to correct in the form, without relying on colour.

Job Application

An employer has a long application form with many fields. To make it more accessible, the form has been divided into sections, a progress bar has been added, and clear instructions for required documents have been included. Users can also save their progress.

Applicants can complete each section at a time.

Quick Accessibility Checklist for Forms

Before publishing a form, consider:

  • Fields have visible and linked labels

  • Required fields are clearly indicated.

  • Guidance and examples appear before inputs.

  • All controls can be used with a keyboard.

  • Focus indicators are visible and not obstructed.

  • Text and UI elements have good contrast.

  • Error messages help user understand the problem and how to fix it.

  • Labels, error messages and confirmations are announced using screen readers.

  • The form is usable on mobile devices, with suitable sized touch controls.

  • Conditional questions and dynamic content are accessible.

  • A suitable time frame is given for users to complete the form.

  • Requesting personal information is explained clearly.

  • The form has been tested with automated and manual methods.

If you have multiple forms on a website, consider keeping a record of issues found, who needs to fix them, and when they should be reviewed next. This can help to make accessibility easier to maintain as the form changes.

Final Thoughts

Accessible forms go beyond increasing font sizes and adding more labels. They take into consideration how people of varying abilities can read, navigate, understand and interact with forms.

A good accessibility checklist for forms should include labelling, keyboard navigation, contrast, error messages, mobile usability, dynamic content and testing. WCAG 2.2 provides a good framework for considering these points in a form. However, to make forms accessible to users, it is important to test with users to find and fix barriers.

Try completing an important form on your website without a mouse. Try using a screen reader to understand how each field is announced. See what happens when incorrect data is entered. Fix any issues found, and repeat this with other forms.

If you are looking to create or update forms, Ovoform can help. Explore templates and integrations to suit your form. Regardless of what tool you are using, be sure to run a final check to ensure the published form meets accessibility requirements.

Frequently Asked Questions

What is form accessibility?
Form accessibility refers to designing online forms so that people with varying abilities can understand, navigate and complete them. This can be achieved by having clear labelling, keyboard navigation, screen reader compatibility, good contrast and clear error messages.
What WCAG level should forms meet?
Many websites and forms aim to meet level AA of WCAG. This includes important requirements for contrast in text, keyboard accessibility, labelling and interactivity. The legal requirements depend on the organisation and country.
Are placeholders enough to make form fields accessible?
No. Placeholders should not replace visible labels. They disappear when users type and may not provide a reliable accessible name. Use a visible label that is programmatically associated with the input.
How do I test whether a form is screen reader accessible?
Use a screen reader such as NVDA or VoiceOver to navigate the form. Check that each field has a meaningful name, instructions are announced, errors are communicated, and users can complete and submit the form.
Can automated tools check form accessibility?
Automated tools such as WAVE and axe can detect many common issues, including missing labels and some contrast problems. However, they cannot identify every accessibility barrier. Manual keyboard, screen reader, and user testing are also important.
What is the minimum button size for WCAG 2.2?
WCAG 2.2 Success Criterion 2.5.8 (Level AA) generally requires pointer targets to be at least 24 × 24 CSS pixels, with specific exceptions. The 44 × 44 CSS pixel target is covered by Success Criterion 2.5.5 at Level AAA.
How often should forms be checked for accessibility?
Review forms before publishing and whenever their design, fields, validation, or interactive behaviour changes. High-traffic and important forms should also be checked regularly as part of ongoing website maintenance.
Form AccessibilityAccessible FormsForm Accessibility ChecklistWCAG 2.2WCAG ComplianceAccessible Form DesignWeb Form AccessibilityAccessible Online FormsScreen Reader AccessibilityKeyboard NavigationAccessible Form FieldsForm ValidationMobile AccessibilityWebsite AccessibilityAccessibility TestingForm Usability

Ready to build forms that convert?

Create surveys, FAQs, and feedback forms in minutes with Ovoform — no code required.

Get started free

Ready to create better forms?

Start building with Ovoform today — free forever, no credit card required.

Get Started For Free