Small-business website accessibility is not a separate “compliance project.” It is the practical work of making your pages, forms, and content usable with a keyboard, screen reader, zoom, captions, and clear visual cues. Start with the checklist below, then have the highest-value customer journeys reviewed by a qualified accessibility professional.
Why accessibility belongs in your website plan
An accessible website lets more people understand your services and complete important actions. It also tends to improve the basics every visitor benefits from: clear headings, meaningful links, readable content, properly labeled forms, and controls that work on mobile and keyboard.
The U.S. Department of Justice explains that businesses open to the public must provide full and equal enjoyment of their goods and services, including those offered online. Its guidance does not prescribe one detailed technical standard for private businesses; WCAG 2.2 is the widely used technical framework. This article is educational, not legal advice—speak with qualified counsel about obligations that apply to your organization.
The practical WCAG 2.2 checklist
Use this as a triage list for a service-business site. It is not a certification or a substitute for a full audit.
- Give meaningful images an equivalent text alternative. A product photo, staff portrait, map, or diagram needs alt text that conveys its purpose. Decorative images can use empty alt text so screen readers skip them.
- Keep text easy to read against its background. Do not rely on faint gray copy, text placed directly on busy photos, or color alone to communicate an error, status, or required field.
- Use real headings in a logical order. One clear page topic followed by descriptive section headings helps visitors scan and helps assistive technology navigate the page.
- Make every task work with a keyboard. Tab through menus, buttons, accordions, booking widgets, and forms. The focus indicator must stay visible, and the order must make sense.
- Write links and buttons that explain the destination. “View roofing website examples” is more useful than “Click here.” A button should name the action: “Request a quote,” not “Submit.”
- Label every form field and explain errors in words. Placeholder text is not a label. If a phone number is missing, identify the field and explain what needs to change.
- Provide captions for meaningful video and transcripts when helpful. Make audio and visual information available in a form people can access without hearing the soundtrack or watching the screen.
- Test zoom and small screens. Visitors should be able to enlarge text without losing content or functionality, and important controls should not require tight, precise taps.
- Use semantic HTML before adding ARIA. Native buttons, labels, headings, lists, and links carry useful meaning by default. ARIA is helpful when needed, but it cannot repair a confusing interaction.
- Review third-party tools. Chat widgets, calendars, payment forms, appointment tools, and embedded maps are part of the customer experience. Test the specific workflows you embed.
Start where a blocked visitor costs you a lead
Inventory
List the pages where visitors call, book, buy, or request help.
Test
Use a keyboard and a scanner to identify obvious barriers.
Prioritize
Fix blockers on high-value journeys before cosmetic items.
Repeat
Re-test after design, content, plugin, or vendor changes.
Example: A contractor’s quote form might look polished but still block a keyboard user if the date picker traps focus or errors appear only in red. Improving the form means adding visible labels, clear written error messages, keyboard-operable controls, and a confirmation that can be understood without color alone.
How to test your own site in 20 minutes
1. Try a keyboard-only walkthrough
Unplug your mouse or set it aside. Use Tab, Shift+Tab, Enter, Space, and Escape to open the menu, reach the primary call to action, complete the contact form, and close any popups. If you cannot see where focus is, get stuck in a widget, or cannot use a control, record the page and step.
2. Check the core conversion pages
Review your home page, service pages, contact page, booking flow, checkout, and top landing pages. These are the highest-impact places to make sure headings, links, forms, and media are working well.
3. Run an automated scan—but treat it as a starting point
Automated tools can flag issues such as missing labels or low contrast. They cannot reliably decide whether alt text is useful, reading order is sensible, instructions are understandable, or a complex widget works well for a person using assistive technology. Combine scanning with manual testing and, when the stakes are high, human evaluation.
What “WCAG 2.2 AA” actually means
WCAG has three conformance levels: A, AA, and AAA. A common project target is Level AA, which includes Level A plus Level AA success criteria. Conformance applies to a full page, including responsive versions and components on that page—not merely a homepage mockup. W3C does not recommend using Level AAA as a general requirement for entire sites because not all content can meet every AAA criterion.
Build accessibility into your next website update
The lowest-friction time to address accessibility is while you are planning new pages, content, and features. Put requirements into the brief: keyboard behavior, focus states, label and error patterns, alt-text ownership, captioning, and testing of third-party tools. That approach is usually more efficient than trying to patch everything after launch.
QC Webworks designs and maintains websites for Quad Cities businesses with conversion, clarity, and long-term usability in mind. If you are planning a redesign or need help prioritizing issues on an existing site, explore our web design services or website maintenance options, then request a conversation.
Frequently asked questions
Do small-business websites need to be accessible?
Accessibility is good customer service and helps more people use your website. The Department of Justice has published guidance on web accessibility and the ADA for businesses open to the public. Specific legal obligations depend on the organization and situation, so obtain legal advice for legal questions.
Is WCAG 2.2 required for every private business?
WCAG 2.2 is a W3C technical standard, not a blanket statement of every private business’s legal requirement. It is a strong practical benchmark for accessibility work. The DOJ’s guidance notes that businesses have flexibility in how they meet ADA requirements; consult counsel on your circumstances.
Can an accessibility overlay or plugin make my site accessible?
No tool can guarantee an accessible experience on its own. Tools can help identify issues or provide features, but the underlying content, code, keyboard interactions, and third-party components still need testing.
What is the fastest accessibility improvement to make?
Start with the actions that create leads or revenue: contact and booking forms, primary navigation, key calls to action, and important service information. Then fix clear blockers such as missing labels, keyboard traps, and unreadable contrast.
How often should we check accessibility?
Review it when you launch a redesign, add new templates or plugins, change a form or booking flow, or publish important new content. Periodic manual checks help catch regressions that automated scans miss.