Improve website buttons with accurate labels, suitable activation areas, and keyboard access. Measure completed inquiries alongside clicks and input errors.
Make the action clear and operable by pointer and keyboard. For inquiries, measure clicks and completed submissions as separate stages. More clicks alone leave the inquiry outcome unresolved.
Opening a pricing page and submitting an inquiry have different roles. Establish the operation before choosing its appearance.
Use links for page navigation and buttons for actions such as submitting a form. W3C's button pattern distinguishes these roles. A button-shaped link to a pricing page can still say View pricing. (W3C button pattern)
A form that only requests a conversation needs wording consistent with that action, such as Send inquiry. See Microcopy for examples.
Statements such as free or takes one minute need support from the actual charge and input process. Add accurate explanations of what follows the action.
Distinguish label size from the clickable area. Where padding forms part of the activation area, measure the full region.
WCAG 2.2 Level AA generally specifies a 24-by-24 CSS-pixel target, with exceptions including spacing, inline links, and equivalent controls. CSS pixels are layout units. Use the minimum alongside an assessment of actual operation. (W3C target size)
Make keyboard focus visible. Check standard button activation with Enter and Space, keeping its behavior distinct from a navigation link.
After changing wording, placement, or supporting copy, check rendering, activation, and the submission result. Repeated click events and people who complete an inquiry are different counts.
State whether the click-rate denominator represents exposed people or sessions. Define the completion-rate unit as well. See A/B test design for a comparison over the same period.
If clicks rise while completions fall, investigate input errors, pricing, and receipt instructions. Correct the affected field or explanation, then verify inquiry delivery after publication.
SpreadSite is a no-code website builder that lets you create, publish, and update a website from Google Sheets using ready-made templates.
To build a website while checking the path from service information to an inquiry, give SpreadSite a try!
A: Choose a readable combination that identifies the action within the page. Evaluate adoption through operation and measured outcomes.
A: For an inquiry goal, evaluate completed submissions and input errors as well. Click counts and people completing a submission are different metrics.
A: 24 by 24 CSS pixels is the general WCAG minimum. Design the area with spacing, users, and operating context in mind.
A: Use a link when navigating to a pricing page. Match the element role to the operation, whatever its visual shape.
A takeaway meal website should connect signature dishes with ordering details
Converse across Generations by Asking about Actual Experiences
Task Ownership: Define the Output, Owner, and Supporting Roles
Decide website page count from visitor tasks and content
Critical and Constructive Thinking: Examine Evidence and Develop a Testable Option
