A service business website should help people understand an offer, evaluate fit, and take the next step without unnecessary barriers. Accessibility makes that journey more usable for people with visual, hearing, mobility, speech, and cognitive disabilities, while often improving clarity and resilience for everyone.
This checklist gives service-business teams a practical way to find and prioritize common accessibility issues. It uses the Web Content Accessibility Guidelines (WCAG) 2.2 as a reference point, but it is not a complete conformance audit or legal opinion. Requirements vary by jurisdiction and context. Use qualified review when you need to make or validate a formal conformance claim.
1. Define the scope, standard, and owner
Accessibility work becomes inconsistent when nobody owns it. Start by documenting which sites, landing pages, forms, portals, documents, and third-party tools are in scope. Identify the standard and target level your organization intends to use, then assign responsibility for design, code, content, testing, and issue tracking.
WCAG 2.2 organizes accessibility under four principles: content should be perceivable, operable, understandable, and robust. Those principles are more useful as ongoing quality criteria than as a one-time launch gate.
Your initial scope should include the pages that matter most to customer journeys:
- homepage and primary service pages;
- contact, quote, booking, and lead-generation forms;
- navigation, search, and account access;
- pricing, location, and resource pages;
- downloadable documents and embedded media;
- cookie, chat, scheduling, payment, and other third-party interfaces.
Record the owner, severity, affected template, and remediation status for every issue. This turns scattered observations into a manageable backlog.
2. Make every core task work with a keyboard
Many people navigate with a keyboard or a device that produces keyboard-like input. Test the site without a mouse. Use Tab to move forward, Shift+Tab to move backward, Enter or Space to activate controls, and Escape to close overlays where appropriate.
Confirm that:
- every link, button, menu, form field, modal, and interactive widget is reachable;
- focus follows a logical order that matches the visual and reading order;
- the focused element has a clear, persistent indicator;
- focus is not trapped inside a component unless that component is intentionally modal;
- opening and closing a modal returns focus to a sensible location;
- dropdown menus and accordions can be operated predictably;
- skip links let users bypass repeated navigation when needed.
Keyboard testing often exposes structural problems that also affect screen readers and power users. A custom component that cannot be operated without a pointer should be treated as a functional defect, not a cosmetic issue.
3. Use meaningful page structure
Headings, landmarks, lists, and other semantic elements communicate relationships that visual styling alone cannot provide. Each page should have a descriptive title and one clear primary heading. Headings should describe the content that follows and descend in a logical hierarchy.
Use real lists for grouped items, real buttons for actions, and real links for navigation. Identify major areas such as the header, navigation, main content, and footer with appropriate HTML elements. Do not rely on font size, colour, or positioning to create structure.
This is also where UI/UX design and development decisions meet. A design system should define accessible patterns for navigation, cards, accordions, forms, alerts, tables, and dialogs so teams do not solve the same problem differently on every page.
4. Give images and media useful alternatives
Informative images need alternative text that communicates their purpose in context. Decorative images should usually have empty alternative text so assistive technology can ignore them. Avoid repeating nearby captions or stuffing keywords into descriptions.
For video, provide accurate captions for spoken content and meaningful sounds. Add a transcript when it helps people consume or reference the material. Audio-only content should have an equivalent text alternative. If important visual information is not conveyed in the audio, consider audio description or an equivalent presentation.
Check icons as well. An icon-only control needs an accessible name that communicates its action. Do not assume the shape of an icon will be obvious to every visitor.
5. Check colour, contrast, and text resizing
Text and interface controls need sufficient contrast against their backgrounds. Test normal text, large text, links, form borders, focus indicators, icons, disabled states, charts, and validation messages. Brand colours that work in a logo may not work for body text or controls.
Never use colour as the only way to convey status. Pair colour with text, an icon, a pattern, or another cue. A red border alone does not tell every user that a form field contains an error.
Zoom pages to 200% and increase text size. Content should remain readable and operable without horizontal scrolling for typical page content. Watch for clipped labels, overlapping navigation, hidden buttons, fixed-height containers, and controls that lose their accessible name when layouts collapse.
6. Make forms clear and recoverable
Forms are often the most commercially important interface on a service business website. Every field needs a persistent label, not just placeholder text. Instructions should appear before they are needed, and required fields should be identified in more than one way.
When validation fails:
- identify the field with the problem;
- explain the problem in specific language;
- connect the error message to the field programmatically;
- preserve valid information already entered;
- move focus or provide a summary so the error can be found quickly;
- suggest a correction when the expected format is known.
Review contact forms, quote forms, newsletter signup, checkout, account creation, and embedded booking tools. A third-party form still affects the customer experience even when your team does not control its code. If lead capture is a priority, pair this work with a broader website conversion review so accessibility and conversion improvements support the same journey.
7. Write links, buttons, and instructions that make sense
Link text should describe the destination or purpose. Repeated phrases such as “click here” and “learn more” create ambiguity when links are read out of context. Buttons should use action-oriented labels such as “Request a consultation” or “Download the guide.”
Keep instructions independent of sensory characteristics. “Choose the green button on the right” may fail for someone who cannot perceive colour or whose screen rearranges the layout. Refer to the control by its visible name instead.
Touch targets should be large enough and separated enough to activate reliably. Pay special attention to mobile navigation, close buttons, carousel controls, pagination, filter chips, and small inline links.
8. Review responsive behaviour and motion
Accessibility does not stop at desktop. Test common pages at narrow widths, high zoom, portrait and landscape orientation, and with browser text settings increased. Make sure content reflows, controls remain available, and sticky elements do not obscure essential information.
Animation should respect a visitor's reduced-motion preference. Avoid flashing content, unexpected movement, and auto-advancing interfaces that cannot be paused. If a task has a time limit, confirm that users can extend or disable it where the underlying requirement allows.
Carousels, animated counters, video backgrounds, and scroll effects deserve extra scrutiny. If an effect does not help someone complete a task, removing it may be the most reliable improvement.
9. Keep language and interaction predictable
Use concise headings, short paragraphs, descriptive labels, and familiar terminology. Explain specialized terms when the intended audience may not know them. Keep navigation and repeated components consistent across pages.
Changes of context should not happen unexpectedly when a field receives focus or a selection changes. Warn users before opening a new window, downloading a file, or starting a process with consequences. Status messages such as “form submitted” or “results updated” should be available to assistive technology without forcing focus to move unpredictably.
Clear content is part of accessible design. A website design process should account for content hierarchy and interaction states before visual polish is finalized.
10. Test code and assistive-technology support
Automated scanners are useful for repeatable checks such as missing alternative text, duplicate IDs, certain label problems, and some contrast failures. They cannot determine whether every description is meaningful, whether the reading order makes sense, or whether a workflow is understandable.
Use several layers of testing:
- Run automated checks across representative templates.
- Complete keyboard-only testing for each critical journey.
- Inspect headings, landmarks, names, roles, and states.
- Test zoom, reflow, contrast, and reduced motion.
- Review key flows with screen readers and other relevant assistive technologies.
- Include people with disabilities in usability testing when possible.
W3C's Easy Checks explicitly notes that a page can pass quick checks and still contain significant barriers. Formal conformance evaluation therefore requires broader coverage and experienced judgment. Document the browsers, devices, assistive technologies, pages, and test dates so future reviews can be compared consistently.
11. Prioritize remediation by customer impact
Do not let a long issue list obscure the most important barriers. Start with defects that prevent people from completing high-value tasks, then fix repeated component issues that affect many pages.
A practical order is:
- Blockers in navigation, forms, booking, account access, or purchasing.
- Missing names, labels, focus states, or keyboard operation in shared components.
- Content alternatives, heading structure, contrast, and error handling.
- Template-level improvements that prevent recurrence.
- Lower-impact enhancements and longer-term process changes.
Fix the underlying component when possible instead of patching every page. Your website development standards should include accessible acceptance criteria for new templates and interactive features.
12. Build accessibility into ongoing website management
Websites change after launch. New landing pages, campaign forms, plugins, videos, documents, and third-party tools can introduce barriers even when the original build was reviewed carefully.
Add accessibility checks to content publishing, design review, code review, release testing, vendor procurement, and periodic audits. Train content editors to use headings, link text, image alternatives, captions, and document structure correctly. Maintain a way for visitors to report problems and define how those reports will be acknowledged and resolved.
W3C recommends integrating accessibility across planning, implementation, and ongoing monitoring. That approach is more reliable than treating accessibility as a one-time technical project. A structured website management plan can keep ownership, testing, and remediation from being displaced by urgent campaign work.
Turn the checklist into a working improvement plan
Begin with three representative journeys: finding a service, evaluating fit, and contacting the business. Test them with a keyboard, at high zoom, on mobile, and with appropriate assistive technology. Record each issue, its impact, the affected component, the owner, and the target release.
The goal is not to produce a passing badge from a single scanner. It is to make important customer journeys perceivable, operable, understandable, and robust, then maintain that quality as the website evolves.
If your team needs help assessing templates, prioritizing fixes, or building accessibility into a redesign or management process, contact Agency Immersive to plan the next practical step.
