Sooner or later, most business owners hear that their website should be accessible. Then the offers arrive: a plugin that promises to fix everything in minutes, an audit report with a long list of issues, or a suggestion to rebuild the design. They all sound like the same service. They are not, and choosing the wrong one means spending money while real visitors still struggle to book, buy or ask a question.

This article compares the three main approaches, what each realistically delivers, and how to choose based on your situation rather than on whichever pitch is loudest.

What accessibility means on a business website

Accessibility means people can use your site regardless of how they see, hear, move or process information. That includes someone using a screen reader, someone who navigates with a keyboard because of a motor impairment, and someone with colour blindness. It also includes people in everyday situations: a visitor on a phone in bright sunlight, someone with a broken wrist using one hand, or an older customer who needs larger text.

In practice, the basics are concrete:

  • Text has enough contrast against its background to be read comfortably.
  • Every action can be completed with a keyboard, and you can always see where you are on the page.
  • Images that carry meaning have text descriptions.
  • Form fields have clear, visible labels, and errors explain what to fix.
  • Headings follow a logical order so the page can be scanned and navigated.
  • Buttons and links are large enough to tap and say what they do.

Many of these improve the experience for everyone, which is why accessibility is better treated as part of good design than as a separate compliance chore. Legal and sector requirements differ, so if you operate in a regulated field, check what applies to you with a qualified adviser.

Option 1: An accessibility overlay or widget

An overlay is a script you add to your site. It usually displays a small icon that opens a panel where visitors can enlarge text, increase contrast or pause animations. Some products also claim to detect and fix problems automatically.

Where it helps

  • It is quick to install and needs little involvement from your team.
  • The display controls can be a convenient extra for some visitors.

Where it falls short

An overlay sits on top of your pages. It cannot reliably repair problems in how the page is built underneath: a form field with no real label, a menu that cannot be reached with a keyboard, a button described only as an icon, or a heading structure that makes no sense. Automated fixes can guess at these, but guesses are often wrong. People who rely on assistive technology also usually have their own settings and tools, and an extra layer can conflict with them.

The larger risk is false confidence. Once the icon is on the site, it is easy to believe the work is done and never check whether a real person can complete an inquiry. We would treat an overlay as, at most, a small supplement to fixing the underlying site, never as the fix itself.

Option 2: A one-off audit and fix

Here, someone reviews your key pages and templates against recognised guidelines (the common reference is WCAG), using both automated tools and manual checks such as keyboard-only navigation and a screen reader. You receive a prioritised list of issues, and a developer and designer work through it.

Where it helps

  • It addresses real problems on the site you already have, without a redesign.
  • You can focus on the pages that matter most, such as the homepage, service pages and your inquiry or booking path.
  • The report gives you a clear record of what was found and what was changed.

Where it falls short

  • It is a snapshot. New pages, new images and new plugins can reintroduce issues within months.
  • If the site was built in a way that fights accessibility, some fixes are awkward and a few may be better handled by rebuilding that component.
  • Automated tools alone catch only part of the problems, so an audit without manual testing can look cleaner than reality.

Option 3: Build accessibility into design and development

This approach treats accessibility as a requirement from the first wireframe. Colour palettes are chosen with contrast in mind, button and form patterns are designed once with visible focus states and clear labels, and developers use proper page structure instead of styling generic elements to look like headings and buttons.

Where it helps

  • Problems are prevented rather than repaired, which usually means less rework.
  • Reusable components carry good behaviour to every page. If you maintain a design system, accessibility rules can live inside it so each new page inherits them.
  • It fits naturally into UI/UX design work instead of arriving as a separate checklist at the end.

Where it falls short

  • It only applies when you are building or redesigning, so it does nothing for a live site you are not ready to touch.
  • It still needs testing with real tools and, ideally, real users.
  • Day-to-day content can undo it. A staff member who uploads an image with no description, or writes a link that just says "click here", creates a new gap.

The three options side by side

The table below summarises who each approach suits and its main limitation.

ApproachBest forMain limitation
Overlay or widgetOptional extra display controlsCannot fix how pages are built
Audit and fixLive sites with no redesign plannedIssues return without ongoing habits
Built-in from designNew builds and redesignsNeeds testing and content discipline

The pattern is that the further down the table you go, the more the work addresses causes rather than symptoms. The overlay is quickest but shallowest. Building it in is the most thorough but is only available when you are already making design decisions. The audit is the practical middle path for most existing sites.

How to choose for your situation

Consider a few hypothetical cases. A clinic with a five-year-old site and no plans to redesign could audit just its booking path and service pages, fix the findings, and revisit once a year. A company about to commission a new website should write accessibility into the brief so it shapes the design from the start. A small shop with a very limited budget could skip the formal audit and fix the highest-impact basics itself: text contrast, form labels, image descriptions and tappable buttons.

Tip: Before paying for anything, unplug your mouse and press the Tab key to move through your inquiry or booking form. If you lose track of where you are, cannot reach a button, or cannot submit the form, you have found your first and most important fix.

That two-minute test tells you more about your priorities than any badge on a plugin. If your form fails it, start there. Our form design checklist covers labels and error handling that help both accessibility and completion rates.

Takeaways

  • Do not rely on an overlay as your accessibility plan. If you use one, treat it as an optional extra, and fix the underlying pages as well.
  • For a live site, start with an audit that includes manual testing, and limit it to your most valuable pages first.
  • For a new build or redesign, put accessibility requirements in the brief so they are designed in rather than retrofitted.
  • Test your inquiry or booking path with a keyboard and on a phone in bright light before anything else.
  • Train the people who add content: image descriptions, meaningful link text and sensible headings are everyday habits, not one-time fixes.
  • Plan to re-check periodically, especially after adding new plugins, pages or design changes.

Accessibility is rarely finished. It is a standard you maintain, and the realistic goal is that more visitors can complete what they came to do, a little more each time you review the site. If you would like help deciding which approach fits your website, you are welcome to get in touch with the Digital Revo team.

Frequently asked questions

Do we need to be fully accessible before we launch or update our site?

Perfection is not a realistic starting point. Begin with the pages and journeys that matter most, such as your inquiry form, booking path and key service pages, and make those work well for keyboard and screen reader users. Then expand to the rest of the site over time.

Can a plugin make our WordPress site accessible?

Some plugins help with specific tasks, such as adding skip links or improving form labels, but none can make a whole site accessible on their own. The theme, page builder, content and forms all affect the result. A review of your theme and templates, followed by fixes, is more dependable than a single plugin.

Who is responsible for keeping the site accessible after launch?

It is shared. The designer and developer are responsible for the structure and components, while the people who publish content are responsible for things like image descriptions, link wording and heading use. It helps to write a short content guideline for your team and to re-test key pages whenever something significant changes.