A website can look polished and still be difficult to use. A customer might be unable to open the navigation without a mouse, read text after enlarging it, or finish a contact form using a keyboard. Those problems affect real people and can interrupt an otherwise promising inquiry.
Small businesses do not need to become accessibility specialists to notice some of the most obvious barriers. They do need to recognize that a quick check is only a starting point, not proof that a site meets accessibility standards.
Here is a practical 15-minute website accessibility check focused on a customer’s most important journey: finding a service, understanding it, and making contact.
What does website accessibility mean for a small business?
Website accessibility means designing and maintaining digital content so people with different abilities and assistive technologies can perceive, navigate, understand, and use it. That includes customers who navigate by keyboard, enlarge text, use screen readers, or need clear instructions.
The W3C Web Accessibility Initiative’s Easy Checks recommends checking basics such as headings, image alternatives, contrast, keyboard access, and form labels. It also makes an important distinction: a page can pass a few simple checks and still contain significant accessibility barriers.
Think of the exercise below as a first-pass diagnostic, not a compliance audit or legal certification.
The 15-minute accessibility check: follow one customer journey
Choose a page that matters to your business: a service page, appointment page, or contact page. Open it in a desktop browser. Then work through these five short checks, noting what you can and cannot complete.
Minutes 0–3: Put the mouse aside
Press Tab to move through links, buttons, menus, and form fields. Use Shift + Tab to go backward. Try opening the service menu and reaching the contact action.
Look for: A visible focus indicator; a logical sequence; controls that actually work; and no point where focus becomes trapped.
Record a problem if: You can see a button but cannot reach or activate it with the keyboard. Keyboard operation is particularly important for people who cannot use a mouse.
Minutes 3–6: Enlarge the page
Increase browser zoom to 200%. Read the service description, open the navigation, and locate the next step.
Look for: Readable text, usable controls, and content that does not overlap, disappear, or become impossible to reach.
Record a problem if: The main call-to-action is cut off or text overlaps another element. Then repeat a quick visual check on a phone; desktop zoom and mobile layout reveal different issues.
Minutes 6–9: Read the page without relying on its pictures
Look at the headings and links first. Can you understand what the service is, who it is for, and where to go next? Inspect important images for meaningful alternative text when you have access to the editor.
Look for: Descriptive headings, links that make sense in context, and alt text that communicates information carried by an image. Decorative images generally need empty alt text rather than a redundant description.
Record a problem if: An image contains essential service information that is not available as text, or several buttons simply say “Click here.”
Minutes 9–12: Try the contact form
Use only the keyboard to move through the form. Check whether each field has a clear label, whether required fields are identified, and whether an error explains what needs correction.
Look for: Instructions before they are needed, visible labels, clear error messages, and a usable submit button.
Record a problem if: The form relies only on placeholder text for instructions, marks errors only in red, or does not explain a rejected submission.
If delivery is also unreliable, see our separate guide to contact forms that do not send email. Accessibility and delivery are different checks; both matter.
Minutes 12–15: Rank the barriers by customer impact
Write down the exact page, control, device, and action that failed. Put barriers that prevent a customer from contacting you ahead of minor cosmetic issues.
Look for: A reproducible problem, not a vague note such as “site isn’t accessible.”
Record a useful issue as: “On the services page, keyboard focus skips the Request Estimate button after the pricing section.” That gives a developer something specific to investigate.
How to decide what to fix first
Use a simple three-level priority system. It is a practical workflow, not an official WCAG severity scale.
Priority 1: The customer cannot complete the task
Examples: an inaccessible navigation menu, a submit button that cannot be activated, or an error that prevents form completion. Investigate promptly.
Priority 2: The task works, but important information is hard to understand
Examples: weak contrast, unclear labels, confusing link text, or a meaningful diagram without a text equivalent. Plan a focused correction.
Priority 3: Improvements that support consistency
Examples: clearer heading structure, better button wording, and consistent instructions across forms. Include these in ongoing website maintenance.
Do not use the priority labels to dismiss a standards failure. A complete evaluation may identify issues that a brief business-focused review misses.
A realistic example: the estimate button nobody can reach
Imagine a local home-services company with a well-designed service page. A visitor reads the page and sees a prominent “Request an Estimate” button. When navigating by keyboard, however, focus never reaches that button because the clickable element was built incorrectly.
The page may still look fine on a phone and receive traffic from search. But for a customer who depends on keyboard navigation, the conversion path is broken. The immediate fix is not a new advertising campaign. It is to make the control operable, verify its visible focus state, and test the complete request process again.
This is a hypothetical example, not a claim about an actual client or a measured conversion outcome. It illustrates why task completion is a useful way to prioritize accessibility work.
Can an accessibility plugin fix everything?
No single plugin or toolbar can reliably establish that an entire website is accessible. Automated tools can flag certain problems, but they cannot fully judge whether instructions make sense, whether a keyboard journey works naturally, or whether a form is understandable to real users.
The W3C’s Web Content Accessibility Guidelines (WCAG) 2.2 provide a formal framework for evaluating accessibility. A complete assessment requires more than this short test, and may involve manual testing, assistive technologies, and specialist review. Avoid treating a plugin score or an accessibility statement as a substitute for actual usability.
For WordPress businesses, accessibility should be considered when selecting themes, adding page-builder components, updating forms, and publishing new content. Our guide to website redesign versus refresh can help distinguish focused fixes from a larger rebuild.
What should you do after the first check?
Repeat the same journey on the site’s other high-value pages, including the homepage and any booking or intake flow. Test across devices and, when possible, involve people who use assistive technology. Keep a small issue log with the page URL, steps to reproduce, business impact, owner, and retest result.
Make accessibility part of regular updates rather than a one-time project. A new form, popup, menu, or content block can introduce barriers even after earlier issues were fixed. For a related usability check, read our guide to investigating a slow WordPress website on mobile; speed and accessibility are different concerns, but both affect the experience of using the site.
If your website is hard for customers to navigate or your contact process is unclear, Grassroots can help assess the underlying design and WordPress workflow. Explore our website design services or start a conversation about the specific problem.
Built in collaboration with ChatGPT.
