Web accessibility practices for small business websites have moved from “nice to have” to “increasingly required” in 2026, as ADA lawsuits against small businesses crossed 4,000 cases annually and EAA compliance became enforceable across the EU. The good news: 80% of accessibility wins come from a dozen specific practices that are cheap to implement during a redesign and modest to retrofit on existing sites. Here’s the practical playbook.
Table of Contents
Alt Text For Every Meaningful Image
Alt text is the single most under-implemented accessibility feature on small business sites. Every image conveying information needs descriptive alt text; decorative images need empty alt (alt=””) so screen readers skip them. The pattern most sites get wrong: alt=”image1.jpg” or alt=”picture of our team” when descriptive context is needed.
Per W3C’s image accessibility decision tree, the alt text should convey what the image communicates in context, not what it visually shows. A photo of the founder shaking a customer’s hand might be alt=”Founder Maria Chen meeting with longtime customer at the 2026 grand opening” — context matters.
Keyboard Navigation Must Work Everywhere
Every interactive element on the page must be operable by keyboard alone — Tab to navigate, Enter/Space to activate, arrow keys for menus and carousels. Focus indicators must be visible (don’t remove the default outline without replacing it). Skip-to-main-content links should appear at the top of every page.
Test by unplugging your mouse and trying to complete every primary task on your site. Most small business sites fail within 30 seconds. The fixes are usually small CSS and ARIA additions, not architectural rewrites. For broader UX framing, our ux design principles that convert covers principles that align cleanly with accessibility wins.
Color Contrast And Color-Independent Information
Text needs minimum 4.5:1 contrast ratio against background (3:1 for large text). Many small business sites use brand colors that fail contrast at common sizes — a quick check with WebAIM’s contrast checker reveals issues fast.
Never convey information by color alone. “Required fields are red” fails for color-blind users. Add text labels, icons, or patterns alongside color. Same for charts, status indicators, and form validation messages.
Form Labels And Error Messages
Every form input needs a programmatically associated label (label element with for attribute matching input id, or aria-label as fallback). Placeholder text is not a label substitute — it disappears on input and fails for screen readers.
Error messages need to be clearly associated with the relevant field, announced to screen readers via aria-live or aria-describedby, and explain how to fix the error. “Invalid input” is useless; “Email must contain @ symbol” is actionable. WCAG 2.2 form guidelines have the complete pattern documentation.
Headings In Hierarchical Order
H1 through H6 should reflect content hierarchy, not visual styling. One H1 per page (usually the main page heading), H2s for major sections, H3s for subsections, etc. Skipping levels (H1 then H4) breaks screen reader navigation.
This sounds pedantic but is the single most-used navigation pattern for screen reader users. They jump heading-to-heading the way sighted users skim. Bad hierarchy makes the site genuinely unusable, not just slower.
Captions And Transcripts For Video
Every video on a small business site should have captions (synchronized) and ideally a transcript (full text equivalent). YouTube’s auto-captions are usable but frequently wrong on technical or proper-noun-heavy content — review and edit before publishing.
Transcripts help SEO too, providing crawlable content from video assets that’s otherwise invisible. For broader content marketing thinking, our small business website mistakes post covers content patterns that pair with accessibility work.
Mobile Accessibility Is Distinct
Web accessibility practices that work on desktop sometimes fail on mobile — touch targets too small, hover-only interactions, fixed-position elements that block content when zoomed. Apple and Google both have mobile-specific accessibility guidelines worth reviewing.
Touch targets should be at least 44x44px (Apple) or 48x48dp (Google). Test mobile sites with VoiceOver (iOS) or TalkBack (Android) for 30 minutes — the issues that surface are usually fixable in an afternoon.
Wrap Up
Web accessibility practices for small business are mostly small, well-documented changes that compound into legally protective and ethically sound websites. Alt text, keyboard navigation, color contrast, form labels, heading hierarchy, video captions, and mobile-specific testing cover 80% of compliance and the vast majority of real user benefit. Don’t wait for a lawsuit to start the work — retrofitting accessibility under legal pressure is dramatically more expensive than building it in.
Frequently Asked Questions
Is my small business website legally required to be accessible?
In the US, ADA Title III applies to most public-facing businesses. EU EAA applies to many product/service sites starting 2025. Healthcare and government have additional requirements. Most lawsuits target accessibility failures at the WCAG 2.1 AA level.
How much does an accessibility audit cost?
$1,500-10,000 for a thorough manual audit of a small business site. Free automated scans (WAVE, axe DevTools) catch maybe 30% of issues but miss many real-world barriers. Manual + automated combined is the right approach.
What’s the WCAG conformance level I should target?
WCAG 2.2 AA is the practical and legal standard for most small business sites. AAA is aspirational and rarely required. AA conformance prevents the vast majority of lawsuits and meaningfully improves user experience.
Do accessibility tools like overlays work?
Largely no. Tools like AccessiBe and UserWay are widely criticized by accessibility experts and disability advocacy groups for failing to actually fix accessibility issues. They can also create new barriers. Real accessibility comes from underlying code, not bolted-on widgets.
How do I test screen reader compatibility?
Free options: VoiceOver on Mac (built-in), NVDA on Windows (free download). Spend 30 minutes navigating your site with the screen reader and eyes closed. The friction you experience reveals issues real users hit daily.