Aim for WCAG 2.2 Level AA, the most widely used accessibility target. For a small business site that means readable color contrast, text alternatives on images, full keyboard use, labeled form fields, a clean heading order and captions on video. Most fixes are small, and you can check ten of them yourself in an afternoon.
Key takeaways
- WCAG 2.2 is the current W3C Recommendation (published October 2023, updated December 2024), and Level AA is the usual goal for business sites.
- Most real-world barriers are basic: low contrast, missing alt text, forms without labels, and pages that cannot be used without a mouse.
- You can test several items yourself with nothing but a keyboard and a browser.
- Accessibility is not a one-time badge. New photos, pages and apps can reintroduce problems, so recheck after changes.
- This guide is practical information, not legal advice. If you have a specific legal concern, talk to an attorney.
What does WCAG 2.2 AA actually mean for a small business site?
WCAG stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium (W3C). It is a long technical standard, but it is built on four ideas: people must be able to perceive your content, operate your site, understand it, and rely on it working with different browsers and assistive tools.
Each rule, called a success criterion, has a level: A, AA or AAA. Level A covers the most basic barriers, AA adds the requirements most organizations aim for, and AAA is stricter and not expected for every page. WCAG 2.2 builds on 2.1 and 2.0, so a site that meets 2.2 also meets the earlier versions. As of October 2026, WCAG 3.0 is still an early draft, so 2.2 remains the practical target.
Why does this matter to a shop, salon or contractor? Partly because people who use screen readers, keyboards, magnification or captions are customers. Partly because clear contrast, readable text and simple forms help everyone, including someone squinting at a phone in Fort Myers sunlight. And partly because accessibility claims about business websites have been brought in the United States under the Americans with Disabilities Act. We are not lawyers and will not quote numbers we have not verified, so treat that as a reason to take the basics seriously, not as legal guidance.
Which accessibility problems show up most on small business sites?
These six areas cause most of the trouble we see on small sites, and each maps to a specific WCAG criterion.
Color contrast
Success criterion 1.4.3 asks for a contrast ratio of at least 4.5:1 between text and its background, or 3:1 for large text (18 point, or 14 point bold). Light gray text on white and white text on a pastel button are the classic failures. Free checkers such as the WebAIM contrast checker will give you the ratio when you paste in two color codes.
Text alternatives for images
Criterion 1.1.1 asks that meaningful images have a text alternative. Informative images get a short description, decorative images get an empty alt attribute so screen readers skip them, and images that work as links or buttons should describe where the link goes. The W3C alt decision tree walks through each case.
Keyboard use and visible focus
Criterion 2.1.1 says everything must work from a keyboard, and 2.4.7 says you must be able to see where the focus is. If you cannot open the menu, reach the booking button or close a pop-up with the Tab, Enter and Escape keys, a lot of visitors cannot either.
Form labels
Criterion 3.3.2 asks for labels or instructions whenever a form needs input. A placeholder that vanishes when someone types is not a label. Every contact, quote and booking field needs a visible label tied to the field.
Headings and structure
Screen reader users often jump from heading to heading. One H1, then H2s, with H3s nested under them and no skipped levels, gives them a usable outline. It also happens to be good SEO.
Captions and small targets
Criterion 1.2.2 asks for captions on prerecorded video with sound. WCAG 2.2 added 2.5.8, which asks for touch and click targets of at least 24 by 24 CSS pixels, with some exceptions such as links inside a sentence. Tiny icon buttons crammed together on a mobile menu are the usual offender.
How do I run a 10-item accessibility self-check?
This is a starting screen, not an audit or a certification. Work through it on your homepage, your most important service page and your contact or booking page.
- Put your mouse away. Use Tab, Shift+Tab, Enter and Escape to move through the page. Can you reach and use every link, button, menu and form?
- Look for the focus outline. As you tab, can you always see which item is selected?
- Check text contrast. Test body text, buttons, footer links and text over images against the 4.5:1 ratio (3:1 for large text).
- Zoom to 200 percent. Is the text still readable without sideways scrolling or overlapping content?
- Check every image. Does each meaningful image have an accurate alt description, and do decorative ones have an empty alt?
- Read your heading outline. Is there a single H1, with H2 and H3 headings in order and no skipped levels?
- Test every form. Does each field have a visible label, and do error messages say what went wrong and how to fix it?
- Check links. Does each link make sense out of context? Replace "click here" and "read more" with descriptive text.
- Check video and audio. Do videos with speech have captions, and is anything auto-playing with sound?
- Tap on a phone. Are buttons and menu items large enough to hit without accidentally tapping a neighbor?
Write down every failure with its page address. That list is the best thing to hand a web designer.
Which fixes should I do first?
Fix in this order, because the first items block people completely.
| Priority | Problem | Typical fix | Who can do it |
|---|---|---|---|
| 1 | Cannot use the site by keyboard | Fix menus, pop-ups and focus order in the theme | Designer or developer |
| 2 | Forms without labels | Add visible labels and clear error text | Designer, or you in many themes |
| 3 | Missing or poor alt text | Describe each meaningful image; leave decorative ones empty | You |
| 4 | Low contrast | Darken text or lighten backgrounds to pass the ratio | Designer, or you via theme colors |
| 5 | Heading order and link text | Reorder headings, rewrite vague links | You |
| 6 | Captions on video | Add or correct captions | You or a captioning tool |
If your site was built on Shopify, the theme you chose and any apps you added matter a lot. A pop-up, chat widget or booking app can undo good work by trapping keyboard focus or loading unlabeled fields, so test with each one switched on.
Can automatic tools make my site accessible?
Automated checkers are useful for finding missing alt text, low contrast and unlabeled fields, but they cannot judge everything. They cannot tell you whether your alt text is accurate, whether the reading order makes sense or whether a menu is pleasant to use with a screen reader. A clean automated report is a good sign, not proof.
Be careful with overlay widgets that promise a one-line fix. They do not replace fixing the underlying page.
How does this fit with the rest of my website?
Accessibility work overlaps with things you may already be doing. Clean headings, descriptive link text and good alt text help search engines as well as screen readers, and fast, simple pages help everyone, as our guide on how fast a website should load explains. If you are deciding whether to patch or rebuild an older site, our guide on whether a website redesign is worth it in 2026 covers the trade-offs. If you are starting fresh, our Basic Website is built with semantic headings, descriptive alt text and a labeled contact form from the start, and a human checks every page. We cannot certify legal compliance, and we say so plainly.
Frequently asked questions
Is my small business legally required to have an accessible website?
It depends on your situation, and we are not lawyers. In the United States, accessibility claims about business websites have been brought under the Americans with Disabilities Act, and courts have not all agreed on how it applies. Rules for government sites differ from rules for private businesses. If you are worried about a specific legal risk, ask an attorney who handles ADA matters. Meeting WCAG 2.2 Level AA is the common technical benchmark, and it is good practice either way.
What is the difference between WCAG A, AA and AAA?
They are three conformance levels. Level A covers the most basic barriers, such as missing text alternatives and keyboard traps. Level AA adds requirements such as 4.5:1 text contrast and visible focus, and it is the level most organizations and policies target. Level AAA is the strictest, and the W3C does not recommend requiring it for entire sites because some criteria cannot be met for all content. For a small business, aim for AA on your key pages first.
What color contrast ratio do I need?
Under WCAG success criterion 1.4.3, normal text needs a contrast ratio of at least 4.5:1 against its background. Large text, meaning at least 18 point or 14 point bold, needs at least 3:1. Logos and purely decorative text have no requirement. You can check a pair of colors with a free contrast checker by pasting in the two color codes, then adjust the text or background until the ratio passes.
Do I need alt text on every image?
Every image needs an alt attribute, but not every image needs a description. Meaningful images get a short, accurate description of what they show or do. Purely decorative images, such as a background flourish, should have an empty alt attribute so screen readers skip them. Images that act as links or buttons should describe the destination or action. Avoid stuffing keywords into alt text, because it makes the page worse for the people it is meant to help.
Will an accessibility overlay or plugin fix my site?
Not on its own. Overlays and widgets can add useful controls, but they do not repair missing labels, broken keyboard navigation or low contrast in the underlying page, and they should not be treated as a way to claim compliance. The reliable approach is fixing the page itself: the theme, the content and any apps. Use automated tools to find problems, then correct them at the source and test again by hand.
How often should I recheck my website for accessibility?
Recheck after any meaningful change: a new theme, a redesign, a new booking or chat app, or a batch of new pages and photos. Even without changes, a quick pass on your top pages every few months catches drift, such as images added without alt text. Keep your list of failures and fixes so you can see what changed, and rerun the ten-item self-check each time.
Sources
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation
- W3C Web Accessibility Initiative: Images decision tree
- W3C WAI: WCAG overview and versions
If you would rather have someone else do the checking, our UI/UX Design Upgrade includes an accessibility review covering contrast ratios, focus states, readable type sizes and screen-reader labels. It is a design review and fix pass, not a legal compliance certificate, and the result depends on your theme and apps. For a new site, see the Basic Website and our web design in Fort Myers page.
