What keyboard accessibility means on a municipal website
Try municipal website tasks without a mouse to identify blocked menus, hidden focus and unusable form controls, then give the provider clear findings.
On this page
Keyboard accessibility means people can use website functions through a keyboard interface without being forced to operate a mouse. On a municipal website, that includes opening menus, finding meeting records and submitting a form. Staff can perform a first check, then ask the provider to investigate barriers.
Some residents use a standard keyboard. Others use assistive input methods that depend on keyboard-compatible controls. The important question is whether the task remains available.
What does the accessibility standard say?
WCAG's keyboard criterion (opens in a new tab) requires functionality to be operable through a keyboard interface, with a limited exception for functions whose underlying purpose depends on the path of movement. Ordinary website navigation and form completion should not require mouse-only operation.
This is a technical accessibility requirement. A quick staff check can identify obvious problems, but it does not establish full WCAG conformance or settle an organization's legal obligations.
Muniway's accessibility service addresses website design and testing. Keyboard use should be part of the review of real pages and functions, not only a claim attached to the homepage.
How can staff begin a keyboard check?
Open a public service page and set the mouse aside. Use Tab to move through interactive controls and Shift+Tab to move backward. Activate links with Enter and use the appropriate keyboard interaction for buttons and menus.
Watch the visible focus indicator: the outline or other cue showing which control currently has keyboard focus. If you cannot tell where you are, record the point where the indicator disappears.
Try a complete task. Open a menu, reach a service, follow its link and return. Check whether a popup or menu traps focus so that you cannot continue or close it using the expected controls.
Which municipal website functions deserve attention?
Prioritize the things residents must operate. Search, calendar filters, form fields and document links all need review. Third-party embeds can introduce a barrier even when the surrounding page works.
A useful finding includes the page address, the control, the keys used and what happened. Describe the observable problem rather than diagnosing the code. "The calendar filter cannot be reached with Tab" gives the provider a concrete starting point.
The mobile task guide describes a related whole-task approach. Different access methods can reveal different failures in the same service.
How should fixes be verified?
Repeat the original steps after the provider makes a correction. Check that the control can be reached, understood and operated, and that the task can continue afterward. A new visible outline does not help if the button still fails to activate.
Have the provider include appropriate assistive-technology testing and review the component wherever it appears. A shared menu correction may affect many pages, while a problem in one embedded form may need a separate owner.
Keep the findings with the website's maintenance record. Test important interactions again after significant changes. Keyboard accessibility is practical: a resident should be able to reach the service and complete the action using the input method available to them.
Frequently asked questions
Is keyboard testing the same as screen-reader testing?
No. The tests overlap, but they examine different parts of the experience. A control can be reachable by keyboard while having an unclear accessible name or status. Include appropriate screen-reader testing as well as basic keyboard checks.
What if the problem is in an outside payment or forms service?
Record the exact step and involve the provider responsible for that service. The municipal website should provide a clear assistance route while the barrier is addressed. Check the whole resident task rather than excluding the external step from review.
Can staff certify accessibility after tabbing through the homepage?
No. That check can reveal some obvious barriers, but it covers only a small part of the website and the standard. Use it as an initial review and request broader testing of representative pages, functions and assistive technologies.
Make the website easier to use.
See how Muniway handles website accessibility for local government staff and residents.