Interactive elements should be reachable and operable through a keyboard where the interface requires interaction. A visually obvious control can still be unavailable to someone using another input method. For this service-area page, the practical test is whether the customer knows who serves the area without being directed to a fictitious office.
Can the page be used without a mouse?
Start with a customer checking whether work is available in a particular area. The keyboard access check concerns actual coverage, the operating base and exceptions. Repeating city names is not evidence of a local branch. A service-area page should distinguish coverage from a storefront and preserve the real business identity.
A city served is not automatically a storefront. Location markup and directions should identify real premises, with coverage described separately.
Check it on this page
Select a covered area and an edge case, then check whether the page explains who serves each and any limits that apply.
- Tab through the controls in a meaningful order.
- Open menus and operate links with the keyboard.
- Check the return from any expanded or modal state in an approved preview.
A shared link treatment underlined an entire content block
One reviewed page applied hover underlining to a large linked area, making the whole block look like linked text. The repair needed to address the scope of the style rather than rewriting the content.
For this service-area page, the check focuses on actual coverage, the operating base and exceptions. Style the action label deliberately and check the pointer and keyboard states after changing a shared rule.
Repair the source, then check the published result
Repair inaccessible controls and preserve suitable native behavior. Retest entry, interaction and recovery instead of checking only the first focusable element.
Record the keyboard access result for this destination, then repeat the customer route until the customer knows who serves the area without being directed to a fictitious office. If the repair changed a shared component, compare another destination with different approved facts to detect unintended copying.
Explore a relevant example
The linked Benchmark page helps you inspect actual coverage, the operating base and exceptions. It is a current example to explore, not evidence that every business has the same problem.
Further reading
Platform guidance can change. Consult the current official documentation before making platform-specific changes.
Have a question about this?
Ask Benchmark about your situation. Your inquiry will include this article's topic, and any paid work starts with an agreed scope.
Ask an Expert