How to Maintain Accessible Website Forms After an Update

Maintain accessible website forms by checking the visible wording, keyboard use, labels, instructions, error messages and successful submission after every meaningful form or website update. A form that still looks familiar can become harder to use when a field, plugin or layout changes.

The check should cover both accessibility and the real business outcome. A technically tidy form is still failing if enquiries do not arrive, confirmation is unclear or the visitor is asked for information the organisation does not need.

Start with the purpose and required information

Write down what the form is for and the minimum information needed to respond. Remove fields that no longer support that purpose. Shorter forms reduce effort for everyone and lower the chance of collecting unnecessary personal information.

Check that the heading and opening instruction explain what will happen next. If a visitor is requesting a call, say what details are required and give a realistic indication of the response process. Optional fields should be clearly optional. Do not rely on colour, asterisks without explanation or placeholder text alone to communicate essential instructions.

Check labels and instructions in the page

Every field needs a clear label that remains available while the person types. The label should describe the expected information in ordinary language, and it should be connected to the field in the underlying code. Grouped choices also need a meaningful group description.

The W3C Web Accessibility Initiative’s forms tutorial covers labels, instructions, validation and user notifications. Use it as a practical reference when reviewing a new form or explaining a defect to a developer. A visual check alone cannot confirm that labels and controls are correctly associated.

Use the keyboard and trigger every error

Move through the form using the Tab key and confirm that the focus order follows the visible layout. Each control and the submit button should be reachable, the current focus should be visible, and there should be no keyboard trap. Test on a narrow screen as well as a desktop.

Submit an empty form, enter an invalid email address and test any special formats. Errors should identify the affected field, explain how to fix the problem and remain available to assistive technology. After correcting one error, make sure the person’s other valid answers are retained rather than erased.

If possible, include people with different access needs in a proportionate usability check. Automated tools can identify some code problems, but they cannot tell you whether instructions make sense, an error is easy to recover from or the form asks for information in a confusing order. Record their feedback without collecting more personal detail than the test needs.

Confirm privacy information and delivery

Review any privacy message or link beside the form so it matches the information collected and the way it will be used. If a newsletter choice or marketing consent is separate from the enquiry, present it as a separate, unambiguous decision rather than bundling it into submission.

Complete a real test using an address the organisation can monitor. Confirm that the visitor sees a useful success message, the notification reaches the correct inbox and replies go to the expected address. Check spam handling carefully, because an aggressive filter can make a working form appear quiet.

Make form checks part of website maintenance

Repeat the test after plugin updates, field changes, design work or changes to email delivery. Keep a short record of the date, device, result and any defect found. This makes it easier to distinguish a new failure from a longstanding issue and ensures repairs are retested.

JigiWeb provides website maintenance and practical support across common platforms. If an update has disrupted a form, ask for the complete journey to be checked, including accessibility, submission, notifications and the response route.

Keep a simple form register containing the page URL, purpose, destination inbox, responsible person and last successful test. When a staff role or email address changes, the register shows which forms need attention. It also helps prevent an old campaign form from remaining online after nobody is watching its responses. Include embedded forms supplied by external services in the same record. Retest them after supplier changes.

Read all our blogs here View All Blogs
Back
Share this article