Layout & accessibility

Audit pricing page: Can the page be used without a mouse?

By Benchmark Enterprise Systems, LLC · Published

Editorial review assigned to Ryan Schober · Review pending

Ask an Expert →

The direct answer

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 audit pricing page, the practical test is whether the chosen audit’s scope matches the request made at the next step.

Can the page be used without a mouse?

Start with an owner choosing between local-presence and website reviews. The keyboard access check concerns the named scope, price, coverage and deliverable. Different audits can overlap without being identical. A pricing table should explain the distinction and avoid presenting all findings as verified measurements.

A corporate site and a location network need an explicit coverage count. A single-location price should not imply all branches are checked.

Check it on this page

Match a known problem to the review that addresses it, then compare the selected scope with the inquiry destination.

  • 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 audit pricing page, the check focuses on the named scope, price, coverage and deliverable. 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 chosen audit’s scope matches the request made at the next step. 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 the named scope, price, coverage and deliverable. 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.

Benchmark Local Boost

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