How to Check Website Accessibility Before a Small Business Site Launch

A website can look polished and still be difficult to use. A visitor might be unable to reach the menu with a keyboard, read a low-contrast button, or understand a form error. Those problems are easy to overlook when a site is reviewed only with a mouse on a large desktop monitor.

A practical website accessibility check does not require you to become a specialist overnight. It does require testing how real people can navigate, read, and complete important tasks. Use this guide before launch, after a redesign, or whenever you change a major page.

Start with the tasks visitors actually need to finish

Choose three important journeys: finding a service, contacting the business, and reading an article or answer. Open each on a desktop and a phone. Note where the next step becomes unclear, a control disappears, or instructions depend entirely on color or visual position.

Do not treat a passing automated score as proof that the experience works. Automated scanners identify some technical issues; they cannot reliably judge whether instructions make sense or a whole journey is usable.

Test keyboard navigation before checking decorative details

Put the mouse aside. Press Tab to move through links, buttons, form controls, and menus; use Shift+Tab to move backward. Use Enter or Space where appropriate to activate controls.

  • Can you see which element currently has keyboard focus?
  • Does the focus order follow the page’s reading order?
  • Can you open and close the mobile or desktop navigation without getting trapped?
  • Can you reach the form, submit it, and read any validation messages?
  • Are popups and dialogs dismissible without a mouse?

A missing focus indicator or a menu that works only on hover deserves attention before cosmetic polish.

Check readability and contrast in the actual design

Read the page on a small screen in ordinary lighting. Look closely at text placed over photographs, pale gray captions, thin fonts, and button labels. A link should be recognizable as a link without requiring visitors to distinguish subtle shades of color.

For typical text, WCAG 2.2 Level AA uses a contrast ratio of at least 4.5:1; large text generally needs 3:1. Some interface elements and meaningful graphical objects also have contrast requirements. Use a contrast checker rather than guessing from the screen.

Zoom the page to 200%, then test a narrow viewport. Content should reflow without forcing horizontal scrolling for ordinary reading, although some complex content has legitimate exceptions. Check that no labels, buttons, or error messages are cut off.

Give images and controls useful names

Images that communicate information need text alternatives that explain their purpose in context. Decorative images usually need an empty alt attribute so they do not add noise for screen-reader users. A photograph does not need a list of every visible object if that detail is irrelevant to the article.

Buttons and links also need descriptive names. “View maintenance options” tells visitors more than a repeated “Click here.” Icon-only buttons, including search and menu toggles, should have an accessible name.

Make forms understandable when something goes wrong

Every form field should have a persistent label. Explain required fields, identify errors in text, and tell visitors how to correct them. Placeholder text alone is not a reliable replacement for a label.

Submit a test entry with missing information and another with valid information. Confirm that the errors are associated with the right fields, the success message is clear, and the submission reaches the intended destination. For delivery-specific troubleshooting, see why website contact forms stop working.

Review headings, links, and page structure

A page should have one clear primary heading followed by sections in a meaningful hierarchy. Headings are navigation landmarks, not merely a way to make text larger. Avoid skipping levels just to achieve a visual effect.

Link text should describe the destination, especially when read out of context. The same wording should not point to unrelated destinations. If you are reorganizing a site’s information, the guide to simplifying website navigation provides a useful companion check.

Use automated checks as a second opinion

Run a reputable accessibility checker on representative page templates, including the homepage, a service page, an article, and the contact page. Review flagged problems manually. Common findings include missing form labels, empty buttons, insufficient contrast, and incorrectly structured headings.

Compare results with the official WCAG 2.2 guidelines. A quick checklist can reveal obvious barriers, but it is not a full accessibility audit or a legal-compliance certification. More complex sites may benefit from specialist review and testing with assistive technology users.

A simple pre-launch accessibility review

  1. Complete your top three visitor tasks using only a keyboard.
  2. Check text, buttons, and link contrast on desktop and mobile.
  3. Zoom in and verify that the layout still works.
  4. Review meaningful image alt text and icon button names.
  5. Submit each important form with both valid and invalid information.
  6. Inspect the heading order and descriptive link labels.
  7. Run an automated scan, then manually confirm its findings.
  8. Record issues, fix the most obstructive ones, and retest.

Accessibility belongs in the launch process, not at the end of a long list of optional improvements. If you are preparing a new site or rebuilding an old one, begin with the 651 Web Design website design overview and build usability checks into the project from the start.