Website Accessibility: A Quick Guide for Small Businesses

Website accessibility isn't just something that big corporations need to worry about. If you run a small business with a website — and in 2026, that's virtually every small business — accessibility is your responsibility. It's a legal requirement in many jurisdictions, it's good for business, and frankly, it's the right thing to do. The good news is that most accessibility improvements are straightforward and don't require a complete redesign.

What Is Web Accessibility?

Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with your website. Disabilities that affect web use include visual impairments (blindness, low vision, color blindness), hearing impairments (deafness, hard of hearing), motor impairments (inability to use a mouse, limited fine motor control), and cognitive impairments (dyslexia, ADHD, memory difficulties).

That sounds like a small audience, but the numbers are staggering. Over 1.3 billion people worldwide — about 16% of the global population — live with some form of disability. In the US alone, 61 million adults have a disability. These are your potential customers, and if your website isn't accessible, you're turning them away.

It's also worth noting that accessibility benefits go beyond people with permanent disabilities. Temporary impairments (broken arm, eye surgery recovery), situational limitations (bright sunlight, noisy environment, holding a baby), and aging-related changes (declining vision, reduced motor control) all make accessibility features valuable to the broader population.

The Legal Landscape in 2026

Web accessibility lawsuits have increased dramatically over the past few years. In the US, the Americans with Disabilities Act (ADA) has been consistently interpreted by courts to apply to websites. The Department of Justice has made it clear that websites are considered places of public accommodation.

In Europe, the European Accessibility Act requires websites and mobile applications of businesses selling products or services in the EU to be accessible. Similar laws exist in Canada (Accessible Canada Act), the UK (Equality Act), Australia (Disability Discrimination Act), and many other countries.

For small businesses, this means: if your website is inaccessible and someone files a complaint, you could face legal action. The average settlement for a web accessibility lawsuit in the US ranges from $5,000 to $25,000 for small businesses, and that doesn't include the cost of then making your site accessible. Prevention is dramatically cheaper than remediation.

WCAG: The Standard You Need to Know

The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility. The current version is WCAG 2.2, and it organizes requirements into three levels:

Level A — the minimum. These are basic requirements that every website must meet. Failure to meet Level A means some users literally cannot use your site at all.

Level AA — the standard target. Most laws and regulations reference WCAG 2.2 Level AA as the required standard. This is what you should aim for.

Level AAA — the ideal. This level is aspirational and may not be achievable for all content types, but it represents the best possible accessibility.

The guidelines are organized around four principles, known as POUR: Perceivable (users can see or hear content), Operable (users can navigate and interact), Understandable (users can comprehend content), and Robust (content works with various assistive technologies).

Quick Wins: Fixes You Can Make Today

You don't need to hire an accessibility consultant to start improving. These fixes address the most common accessibility issues and can be implemented immediately.

Add alt text to all images. Every meaningful image on your site needs descriptive alt text that conveys the same information as the image. If the image is purely decorative, use an empty alt attribute (alt="") so screen readers skip it. For a product photo, write "Red leather messenger bag with brass buckle, front view" not "image1" or "bag."

Ensure sufficient color contrast. Text must have a contrast ratio of at least 4.5:1 against its background for normal text, and 3:1 for large text (18px bold or 24px regular). Use the WebAIM Contrast Checker tool to verify your color combinations. Common offenders: light gray text on white backgrounds, colored text on colored backgrounds, and text overlaid on images without a sufficient overlay.

Make all interactive elements keyboard accessible. Every button, link, form field, dropdown, and interactive widget must be usable with the keyboard alone. Users should be able to tab to it, see a visible focus indicator, and activate it with Enter or Space. Test by unplugging your mouse and trying to use your entire site with just the keyboard.

Use semantic HTML. Use heading tags (h1-h6) in proper order to create a document outline. Use button elements for buttons and anchor tags for links. Use nav, main, article, and footer elements to define page structure. Semantic HTML gives assistive technologies the information they need to help users navigate your content.

Add form labels. Every form input needs a visible label element associated with it via the for attribute. Placeholder text is not a substitute for labels — it disappears when users start typing and is often too low contrast to read.

Don't rely on color alone. If you use color to convey information (red for errors, green for success), also include a text label or icon. Color-blind users, who represent about 8% of men and 0.5% of women, may not be able to distinguish the colors.

Navigation Accessibility

Navigation is often the biggest accessibility barrier on websites. If users can't navigate to your content, nothing else matters.

Provide a skip navigation link. This is a hidden link at the top of every page that becomes visible on focus and allows keyboard users to skip directly to the main content. Without it, keyboard users must tab through every navigation item on every page before reaching the content they came for.

Make sure your navigation is consistent. Navigation should appear in the same location on every page and contain the same items in the same order. Consistency reduces cognitive load for everyone, but it's especially important for users with cognitive disabilities who rely on predictable patterns.

Ensure dropdown menus are keyboard accessible. Many dropdown menus only work with mouse hover, which excludes keyboard and mobile users. Dropdowns should open and close with keyboard interactions and clearly indicate their expanded or collapsed state.

Use ARIA landmarks when semantic HTML isn't enough. ARIA (Accessible Rich Internet Applications) attributes like role="navigation", aria-label, and aria-expanded provide additional information to assistive technologies. But follow the first rule of ARIA: don't use ARIA if you can use a native HTML element instead.

Implement a logical focus order. When users tab through your page, the focus should move in a logical order that follows the visual layout. This usually happens naturally when your HTML source order matches the visual order. Avoid using CSS to dramatically reorder elements because the tab order follows the HTML, not the visual presentation.

Content Accessibility

How you write and structure your content significantly affects accessibility.

Use plain language. Write at a reading level appropriate for your audience. Avoid jargon, complex sentence structures, and unnecessary technical terms. If you must use specialized vocabulary, provide definitions. Clear writing benefits everyone, not just users with cognitive disabilities.

Structure content with headings. Use headings to create a logical outline of your content. Screen reader users often navigate by jumping between headings, so a good heading structure is like a table of contents for your page. Don't skip heading levels (going from h2 to h4) and don't use headings just for visual styling.

Provide captions and transcripts for media. Videos need captions for deaf and hard-of-hearing users. Podcasts and audio content need transcripts. These aren't just accessibility features — they also benefit users in noisy environments, non-native speakers, and people who prefer reading to watching.

Write descriptive link text. "Click here" and "Read more" tell screen reader users nothing about where the link goes. Instead, use descriptive text like "Read our complete guide to email marketing" or "View pricing plans." The link text should make sense even when removed from the surrounding context.

Ensure sufficient text spacing. Users with dyslexia or low vision may need to increase text spacing. Your design should not break when letter spacing is increased to 0.12em, word spacing to 0.16em, or line height to 1.5. Avoid fixed-height containers for text that prevent expansion.

Common Accessibility Mistakes Small Businesses Make

Relying on automated tools alone. Automated accessibility testing tools catch about 30-40% of WCAG issues. The rest require manual testing. Tools like WAVE, axe, and Lighthouse are excellent starting points, but they can't evaluate whether your alt text is descriptive enough, whether your color scheme makes sense, or whether your interactions are intuitive.

Treating accessibility as a one-time project. Accessibility isn't something you fix once and forget. Every new page, feature, and content update needs to maintain accessibility standards. Build accessibility into your content creation workflow and design process.

Using accessibility overlays. Third-party accessibility widgets that add a toolbar to your site (typically with icons for increasing font size, changing contrast, etc.) are widely criticized by the disability community. They often don't fix underlying accessibility issues, they can interfere with users' own assistive technologies, and they create a false sense of compliance. Fix the actual HTML and design instead.

Ignoring mobile accessibility. Mobile accessibility involves all the same principles as desktop accessibility, plus touch-specific considerations. Touch targets must be at least 44x44 pixels. Elements shouldn't be so close together that they're easy to accidentally tap. Gestures should have alternative ways to accomplish the same action.

CAPTCHAs that block users. Traditional image CAPTCHAs are inaccessible to blind users and often difficult for users with cognitive disabilities. Use alternatives like reCAPTCHA v3 (invisible), hCaptcha accessibility features, or honeypot techniques that don't require user interaction at all.

Testing Your Accessibility

You don't need expensive tools to start testing.

Keyboard testing. Navigate your entire website using only the keyboard. Can you reach every interactive element? Can you see where the focus is at all times? Can you operate all functionality? This single test reveals a surprising number of accessibility issues.

Screen reader testing. VoiceOver (built into macOS and iOS) and NVDA (free for Windows) are screen readers you can use to experience your site as a blind user would. You don't need to become an expert — even 15 minutes of screen reader testing will reveal issues that no automated tool catches.

Browser extensions. axe DevTools and WAVE are free browser extensions that analyze your page for accessibility issues. Run them on every page of your site and address all errors. Warnings and best practices are worth reviewing too.

Zoom testing. Zoom your browser to 200% and verify that all content is still usable. Users with low vision often zoom significantly, and layouts that break at higher zoom levels fail WCAG 1.4.10.

Color contrast testing. Use the WebAIM Contrast Checker or the Chrome DevTools contrast inspector to verify all text meets minimum contrast ratios. Check text on backgrounds, text on images, and interactive element states (hover, focus).

Building an Accessible Culture

The most important accessibility improvement you can make isn't technical — it's cultural.

Include accessibility in your design brief. When you commission a new website or feature, specify WCAG 2.2 Level AA compliance as a requirement. If your designer or developer doesn't know what that means, that's a red flag.

Test with real users. If possible, include people with disabilities in your user testing. Their feedback will reveal issues that no automated tool or manual audit can catch, and their perspective will change how you think about design.

Maintain an accessible content creation process. Create a simple checklist for your content creators: add alt text to images, use heading structure, write descriptive link text, ensure video captions exist. These habits, once established, add minimal time to the content creation process.

Budget for ongoing accessibility. Treat accessibility like any other aspect of website maintenance. Regular audits, prompt fixes, and continuous improvement should be part of your operating budget, not a one-time capital expense.

Accessibility isn't about perfection — it's about progress. Start with the quick wins, build good habits, and continuously improve. Your website will be better for everyone, your legal risk will decrease, and you'll reach an audience that many of your competitors are inadvertently excluding.

Want to know your website's score? Get a free AI roast at roastsite.site