Accessible municipal forms that help residents finish without assistance
Check municipal online forms for clear labels, usable errors, keyboard access and confirmation so residents can complete applications more independently.
On this page
Accessible municipal online forms make fields understandable, allow people to complete the task with different input methods and explain how to correct mistakes. Test the entire submission, including attachments and confirmation. A form that looks tidy can still block a resident at the final step.
Good form design also helps staff. Clear requirements and usable error messages give residents a better chance to send the information the office needs without a follow-up call.
Can residents identify every field?
Use a persistent label that explains the information requested. Instructions inside an empty field can disappear when typing begins, so they should not be the only explanation. Identify required fields consistently and explain any unusual format beside the field.
W3C's form instructions guidance (opens in a new tab) recommends information that helps users understand what to enter. For a municipal application, that means explaining an unfamiliar account or parcel reference where the resident encounters it.
Keep the form limited to necessary information. Ask the responsible department to review fields that nobody uses. Each unnecessary question adds work and can introduce another point of confusion.
What happens when someone makes a mistake?
An error should name the problem and help the resident correct it. Color alone should not carry the message. Keep entered information where possible so one missing item does not force the person to start again.
W3C's validation guidance (opens in a new tab) explains identifying errors and providing useful correction suggestions. Test the actual messages rather than assuming the form builder's defaults are understandable.
Check an empty required field, an invalid date and an unsupported attachment. Make sure the resident can reach the problem field and understand which part needs attention. A message at the top of a long form is not enough if the person cannot locate the error.
Can the whole task be completed with a keyboard?
Move through the form without a mouse. Check that the current control is visibly indicated, the order makes sense and the resident can reach uploads, date controls and submit buttons. An on-screen signature method needs particular review if it relies on drawing.
Ask the provider to test with appropriate assistive technology as well. A basic keyboard check can find barriers, but it is not a complete accessibility evaluation. The keyboard guide explains what staff can observe and report.
Muniway's Forms tool is built to meet WCAG 2.1 AA and includes labels and text error messages. The actual service configuration and uploaded material still deserve review.
Does the final step explain the outcome?
After a successful test, check the confirmation. It should tell the resident what was received and what happens next. If staff review is still pending, the wording should say so.
Test on a phone and verify the staff destination. Accessibility and service completion meet here: residents need to know the form worked, and employees need a usable record.
Keep these checks in the process whenever a form changes. Adding a field, altering an upload requirement or connecting a payment step can create a new barrier. A form stays useful through continued review, not just a successful launch-day demonstration.
Frequently asked questions
Does an automated scan prove a form is accessible?
No. Automated checks catch only some issues. Complete the form manually, test keyboard use and error recovery, and include suitable assistive-technology testing. Review any external payment or upload step as part of the same resident task.
Are placeholder words inside a field enough?
Use a visible label that remains available while the resident types. Placeholder text can disappear and may not provide the same information to every user. Keep instructions and format examples near the field where they are needed.
Should a required signature always use a drawing box?
A drawing-only interaction can create barriers. Confirm the accepted signature method for the service and have the provider evaluate accessible alternatives. The department's procedural requirements and the form's usability both need to be addressed before launch.
Put a working form on the website.
See how Muniway handles online forms for local government staff and residents.