Quick answer: Review the path a customer must complete: understand the service, reach the contact page and send an enquiry. Check it with a keyboard, enlarged text and the form’s errors. Record each barrier with its page and owner. A quick review helps you find obvious problems; it does not certify that the site meets an accessibility standard.
For: owners and lean service teams checking a live site before a launch or after a redesign. The example below is illustrative, not a report of testing this site or a client site.
Start with one real visitor task
Choose a service page that matters to the business, its contact route and the confirmation shown after sending a request. Write the task in one sentence: “Find the repair service, learn the coverage area and request a visit.” Use the same task on desktop and a narrow phone screen. This gives your review a finish line rather than a list of disconnected scores.
W3C’s Easy Checks covers page title, text alternatives, headings, contrast, resizing, keyboard access, focus, forms and more. W3C also explains that these checks are only a first review. A page can pass them and still have significant barriers.
Run five checks in the order a visitor meets them
- Understand the page: Can you tell what the service is from the title and main heading? Do the headings describe sections in an order that makes sense? If a diagram carries a decision, is that decision available in text? Decorative imagery need not repeat the whole article.
- Read comfortably: Enlarge the page and use a narrow viewport. Look for text hidden behind menus, clipped buttons and horizontal page scrolling. Check important text against its background; visual preference alone is a weak contrast test.
- Move without a mouse: Start at the address bar and use Tab, Shift+Tab, Enter and Escape. Can you reach the menu, service links and form in a sensible order? Can you see where focus is? Can you leave any opened menu or dialog?
- Complete the form: Check that each control has a visible, useful label. Submit an empty or deliberately incomplete request without sending real customer data. Are required fields clear, and does the error explain what to fix? W3C’s form label guidance explains why a programmatic label matters beyond placeholder text.
- Know what happened: After a valid test submission, confirm the visitor sees a useful success state and the team receives the message. Use a clearly marked internal test, then remove it from the operating queue. If the form fails, offer a working alternative contact route while fixing it.
Record barriers so someone can fix them
For each issue, capture the page URL, the task step, what you did, what happened, what you expected and who owns the fix. “Contact button cannot be reached by Tab on the service page” is actionable. “Accessibility score is low” is not enough to reproduce a problem.
Illustrative case: A visitor reading a local plumbing page can reach the enquiry form, but the required postcode control has only a placeholder. When the visitor submits an incomplete request, a red border appears with no text instruction. The owner first adds a visible associated label and a specific error message, then retests by keyboard. This is an example of a repair sequence, not a measured conversion result.
Decide what to fix first
Prioritise barriers that block the main enquiry path, hide essential service information or prevent a user from recovering after an error. Then work through repeated components such as navigation and form patterns; one component fix may improve several pages. Give visual polish issues a separate queue so they do not bury access blockers.
Do not call an automated scan a complete audit. W3C states that tools alone cannot determine accessibility; knowledgeable human evaluation is needed. If you need a formal conformance claim, a complex application review or legal advice, commission qualified help for that scope.
Repeat the path after the fix
Ask someone other than the editor to repeat the original task using only the keyboard, then check at mobile width. Record pass, remaining barrier and the next owner. Recheck after theme, form or navigation changes because those can reopen a problem.
Next step: If the enquiry itself is unclear, refine the questions with our enquiry form field guide. If submissions are not reaching your team, follow the contact form delivery checks. These are separate from the accessibility review.
Sources and scope: W3C Easy Checks, W3C Forms Tutorial and W3C Evaluation Overview; reviewed October 2, 2026. No formal audit or user testing was performed for this article.
Useful detail: Name what an image button does
W3C’s functional-image guidance says a text alternative should describe the link or button’s purpose.
A picture of an envelope can look obvious and still leave the action unclear to a reader who cannot see it. Make the meaning agree with the destination.
Try this:
- Identify every image that is itself a button or link.
- For an icon-only enquiry link, describe the action rather than only the icon.
- Check its announced label and destination; a decorative image beside an already named button may need different handling.
Source: W3C WAI: functional images. Checked October 3, 2026. The practical check is a PSL suggestion.
