Website accessibility for small businesses: a practical guide

When owners think about their website, they picture a typical visitor: someone with a laptop or phone, good eyesight, a steady hand and a quiet room. But real customers are more varied. Some are colour blind. Some have low vision and enlarge the text. Some cannot use a mouse and navigate by keyboard. Some are deaf or hard of hearing, some use screen readers, and many people are simply using a phone in bright sun with one thumb while holding a coffee.

Web accessibility is the practice of building sites that work for all of these people. It is the right thing to do, and it is also good business: it widens your audience, improves usability for everyone and tends to produce cleaner, better-structured pages that search engines understand. This guide explains the essentials in plain language and gives you a practical path to improve your own site.

Why accessibility matters

It is about real people

A significant portion of the population lives with some form of disability, and many more experience temporary or situational limitations: a broken wrist, a noisy environment, a glare on the screen. When your site is hard to use, those customers leave, often without telling you why.

It is good for business

Accessible sites reach more people, reduce friction and tend to convert better. Clear structure, good contrast, readable text and well-labelled forms help every visitor. Older customers, who are a large and loyal market for many local businesses, often benefit most.

It overlaps with SEO

Many accessibility practices, such as descriptive headings, meaningful link text, alternative text for images and logical structure, also help search engines understand your content.

It reduces legal and reputational risk

Accessibility laws and standards are evolving in Canada and elsewhere. Several provinces have accessibility legislation, and federal rules apply to certain organizations. Requirements vary by jurisdiction, size and sector, so it is worth checking what applies to you, but regardless of legal obligations, taking reasonable steps protects your reputation and shows care for customers.

The standard to aim for

The most widely used benchmark is the Web Content Accessibility Guidelines, or WCAG, published by the World Wide Web Consortium. Most organizations target level AA of the current version. The guidelines are organized around four principles, often summarized as POUR:

• Perceivable. Information must be presented in ways users can perceive, such as through text alternatives, captions and sufficient contrast.
• Operable. Interface components must be usable by different input methods, including keyboard, and give people enough time and clear navigation.
• Understandable. Content and operation must be clear and predictable.
• Robust. Content must work with a wide range of browsers and assistive technologies.

You do not need to memorize the criteria to make progress. The sections below translate them into practical actions.

Text and colour

Contrast

Text needs enough contrast against its background to be readable. For normal text, WCAG AA requires a contrast ratio of at least 4.5 to 1; for large text, 3 to 1. Light grey text on white, or pale text over a photo, often fails. Free contrast checkers let you test colour pairs. Pay attention to buttons, links, placeholder text in forms and text overlaid on images.

Do not rely on colour alone

If information is conveyed only by colour, such as red for errors or green for success, people who cannot distinguish those colours will miss it. Add text, icons or patterns. For example, an error message should say what went wrong, not just turn a field red.

Readable size and spacing

Use a comfortable base text size, generally 16 pixels or larger, with generous line spacing and short lines. Let users enlarge text up to 200 percent without breaking the layout. Avoid long blocks of justified or all-caps text, which are harder to read.

Choose fonts thoughtfully

Pick clear, legible typefaces. Decorative fonts may suit a logo but make body text difficult, especially for people with dyslexia or low vision.

Images, video and audio

Alternative text

Every meaningful image needs alt text describing its content or purpose, so screen reader users understand it. Write what the image communicates, concisely: “Technician installing a furnace in a basement,” not “image123.jpg.” Decorative images that add no information should have empty alt text so assistive technology skips them. Images that function as links or buttons should describe the destination or action.

Images of text

Avoid putting important text inside images, such as a banner with your phone number as part of the picture. It cannot be resized properly, searched or read by assistive technology. Use real text styled with CSS.

Captions and transcripts

Provide captions for videos with speech, so deaf and hard-of-hearing users, and people watching without sound, can follow. Provide transcripts for audio content. Avoid autoplaying media with sound, and give users control over playback.

Structure and navigation

Headings

Use headings in a logical order to outline the page: one main heading, then subheadings that nest sensibly. Screen reader users often navigate by headings, so they act as a table of contents. Do not choose heading levels based on how large they look; use styling for appearance.

Landmarks and layout

Use semantic page regions such as header, navigation, main content and footer, so assistive technology can jump between them. Offer a “skip to main content” link at the top so keyboard users can bypass repeated navigation.

Links

Link text should make sense out of context. “Read our accessibility statement” is clear; “click here” is not. Make links visually distinguishable from surrounding text, not by colour alone. Avoid opening new windows unexpectedly without warning.

Consistent, predictable navigation

Keep menus in the same place and order across pages. Provide more than one way to find content, such as navigation, search and a sitemap, where appropriate. Use clear page titles that describe each page’s purpose.

Keyboard and focus

Many people navigate without a mouse, using a keyboard, switch device or voice control. Test your site by putting the mouse aside and using the Tab key:

• Can you reach every link, button and form field?
• Is the order logical?
• Can you see where you are? A visible focus indicator, such as an outline, is essential. Do not remove it without providing a clear alternative.
• Can you open and close menus, dialogs and carousels with the keyboard?
• Can you escape from modal windows, and does focus return sensibly?

Interactive elements built from scratch, like custom dropdowns, are common sources of keyboard traps. Use standard elements where you can.

Forms

Forms are where accessibility failures cost you leads directly.

• Label every field with visible text associated with the input. Placeholder text is not a substitute, because it disappears and is often low in contrast.
• Group related fields with clear headings, such as for address or contact preferences.
• Mark required fields clearly, in text as well as with symbols.
• Give helpful error messages that identify the field and explain how to fix the problem, and keep the user’s entered data.
• Use appropriate input types so phones present the right keyboards, and support autofill.
• Provide clear instructions for formats, such as phone number patterns.
• Be careful with captchas, which can block users with visual or cognitive disabilities. Offer accessible alternatives or invisible protections.

Motion, timing and flashing

Moving content can distract, cause discomfort or trigger vestibular reactions. Respect users who set a preference for reduced motion. Let users pause, stop or hide carousels, auto-updating content and animations. Avoid content that flashes more than three times per second, which can trigger seizures. Do not set aggressive time limits on forms or sessions without warning and the ability to extend.

Mobile and zoom

Accessible design and mobile design reinforce each other. Make touch targets large enough, support both portrait and landscape and do not disable pinch-to-zoom. Ensure content reflows when zoomed instead of forcing horizontal scrolling.

Documents and downloads

If you offer PDFs, such as menus, brochures or price lists, make them accessible too: use real text rather than scanned images, add headings and alternative text, set the reading order and tag the document. When possible, publish the same information as a web page, which is generally easier to make accessible and to read on phones.

Content and language

Write in plain language. Short sentences, clear words and defined jargon help people with cognitive disabilities, those reading in a second language and everyone in a hurry. Set the page language in the code so screen readers pronounce text correctly. Explain abbreviations on first use.

Testing your site

You can find many problems with simple checks, and use a layered approach.

Automated tools. Free tools such as Lighthouse, WAVE and axe scan for common errors, like missing alt text, low contrast and unlabelled fields. They catch only a portion of issues, but they are a quick starting point.

Manual checks.

• Navigate the whole page using only the keyboard.
• Zoom to 200 percent and check the layout.
• Turn off images and check that essential information remains.
• Check the heading structure.
• Review colour contrast on key elements.

Assistive technology. Try a screen reader such as NVDA on Windows or VoiceOver on Mac and iPhone for a few key tasks, such as finding your phone number or submitting a form. Even a short session is eye-opening.

Real users. If possible, get feedback from people with disabilities. Nothing replaces lived experience.

An accessibility statement

Consider publishing a short accessibility statement that describes your commitment, the standard you aim for, known limitations and how people can contact you for help or to report problems. It signals care and gives users a path to ask for assistance. Respond promptly and respectfully to any feedback.

A practical roadmap for small businesses

You do not have to fix everything at once. Work in order of impact.

1. Run an automated scan on your main pages to find obvious issues.
2. Fix contrast and text size across the site.
3. Add alt text to meaningful images.
4. Label every form field and improve error messages.
5. Check keyboard navigation and restore visible focus indicators.
6. Clean up headings and link text.
7. Caption or transcribe key videos.
8. Review PDFs and publish web versions of essential information.
9. Build it into your process: include accessibility in briefs for new pages, designs and content.
10. Re-test regularly, especially after redesigns and plugin updates.

If you are commissioning a new site, make accessibility a requirement from the start. It is much cheaper to build in than to retrofit.

Common myths

“Accessibility makes sites ugly.” Good accessible design is simply good design, with clarity and contrast.

“Only a few people need it.” Many users benefit, and situational limitations affect everyone at times.

“An overlay plugin will fix it.” Quick-fix widgets claiming instant compliance generally do not fix underlying problems and can introduce new ones. Real accessibility comes from the code and content.

“We are too small for this to matter.” Small businesses lose customers and reputation just like large ones, and the fixes are often simple.

Final thoughts

Accessibility is not a one-time project; it is a habit of building and writing with all your customers in mind. Start with the basics of contrast, structure, labels and keyboard use, test regularly and keep improving. The result is a website that is easier for everyone to use and a business that visibly welcomes its whole community. If you would like us to review your website’s accessibility and suggest priorities, we would be glad to help.