A practical guide for business owners and marketing leads who want more enquiries from the traffic they already have. Which accessibility errors show up on almost every website, what WCAG 2.2 added for forms, buttons, and sticky elements, and how to fix them in the order that protects leads first.
Most websites lose customers to accessibility errors that are cheap to fix: faint text, unlabelled form fields, icon buttons with no name, and tap targets too small to hit. These are not edge cases for a small group of users. They slow down anyone on a phone in sunlight, anyone with tired eyes, and anyone filling in your contact form one-handed, and they block people who rely on a keyboard or screen reader entirely. Six error types account for almost all detected problems on the web. Fix those on your enquiry, booking, and checkout paths first, then build the fixes into your page templates so new pages do not reintroduce them.
Why accessibility is a lead problem, not a compliance chore
The World Health Organization estimates that 1.3 billion people, about 16% of the world’s population, experience significant disability. Add older buyers, people on small screens, and anyone with a temporary injury, and a large share of your visitors depend on the same basics: readable text, labelled fields, buttons that say what they do, and a page that works without a mouse.
Most sites do not meet those basics. WebAIM’s 2026 Million report, which tested the home pages of the top one million websites in February 2026, found:
- 95.9% of home pages had detected WCAG 2 failures, up from 94.8% in 2025.
- An average of 56.1 detected errors per page, up 10.1% in a year.
- Because automated tools only catch part of the picture, full WCAG 2 A/AA conformance was certainly lower than 4.1% of pages.
Every one of those errors sits between a visitor and an action you paid to bring them to. An unlabelled phone field or a “Submit” button a screen reader announces as just “button” is a lost enquiry you will never see in your analytics.
“Barely 4% of popular home pages clear even the automated accessibility checks. Getting the basics right is still a way to stand out.”
The six errors behind almost every failed check
WebAIM reports that 96% of all detected errors fall into six categories, and they have been the same six for seven years. Here is how often each appeared in 2026, what it costs you, and the usual fix:
- Low contrast text (83.9% of home pages) — Grey text on white, white text on a light photo, pale placeholder text in forms. WCAG AA asks for a contrast ratio of at least 4.5:1 for body text and 3:1 for large text. Fix it once in your global colours and typography rather than page by page.
- Missing alternative text (53.1%) — Images with no alt attribute. When the image is a link or a button, the link has no name at all. Describe what the image shows or does; leave purely decorative images with empty alt text.
- Missing form input labels (51%) — Fields that rely on placeholder text that disappears once you type. WebAIM found one in three form inputs was not properly labelled. Every field needs a visible label tied to it.
- Empty links (46.3%) — Icon-only links, such as social icons or a logo with no text, that a screen reader cannot name.
- Empty buttons (30.6%) — Hamburger menus, close icons, carousel arrows, and floating chat buttons with no accessible name.
- Missing document language (13.5%) — A one-line setting that tells assistive technology which language to read the page in.
None of these needs a redesign. On a WordPress site built with Elementor, most are fixed in global settings, image alt fields, form field settings, and button labels.
What WCAG 2.2 added that business websites trip over
WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added nine success criteria. Several land directly on the parts of a site that produce leads:
- Focus Not Obscured (2.4.11, AA) — When someone tabs to a link or field, it must not be completely hidden by your own content. Sticky headers, cookie banners, and floating WhatsApp or chat buttons are the usual culprits.
- Target Size (Minimum) (2.5.8, AA) — Tap targets need to be at least 24 by 24 CSS pixels, or spaced so a 24-pixel circle around each does not overlap its neighbour. Tiny close icons and tightly packed footer links fail this.
- Dragging Movements (2.5.7, AA) — Anything that needs dragging, such as a price slider or a before-and-after image, needs a simple click or tap alternative.
- Consistent Help (3.2.6, A) — If you offer contact details, a chat, a WhatsApp link, or an FAQ on several pages, keep it in the same relative place on each.
- Redundant Entry (3.3.7, A) — Do not ask for the same information twice in one process. A booking or checkout flow that asks for name and phone again on step three fails it; auto-fill or let the user select what they entered.
- Accessible Authentication (Minimum) (3.3.8, AA) — Logins for customer or dealer portals should not depend on memorising or retyping something. Allowing password managers and paste, or offering an email login link, meets the requirement.
WCAG 2.2 also removed one older criterion, 4.1.1 Parsing, as obsolete. Everything else from 2.0 and 2.1 still applies.
Why plugins, sliders, and extra code make it worse
The 2026 data points to a clear cause. Home pages are getting heavier, and heavier pages carry more errors:
- The average home page grew to 1,437 elements, up 14.3% in a single year.
- Pages using ARIA code averaged 59.1 errors, against 42 for pages without it. ARIA is meant to help, but added carelessly it creates new barriers.
- Carousel libraries such as Slick and OWL Carousel were linked with roughly 26% more errors than average, and pages with reCAPTCHA had 7.7 more.
- WebAIM’s own conclusion names heavier reliance on third-party libraries and AI-assisted coding as likely drivers.
The practical lesson for a business site is restraint. A hero slider nobody waits for, three popups, and a stack of add-on widgets each add places for a visitor to get stuck. Accessibility overlay widgets do not fix the underlying code either; the errors are still in the page they sit on.
“Every slider, popup, and plugin you add is another place for a customer to get stuck. Simpler pages are easier to make accessible and easier to keep that way.”
A 30-minute test you can run today
You do not need a specialist to find the worst problems. Run these checks on your home page, your main service page, and your contact or booking page:
- Keyboard only — Put the mouse aside and press Tab through the page. Can you see where you are at every step? Can you open the menu, fill in the form, and submit it?
- Zoom to 200% — Text should get bigger without overlapping, cutting off, or forcing sideways scrolling on a normal desktop window.
- One thumb on a phone — Try to hit every button, menu item, and form field. Note anything you mis-tap.
- Run a free checker — WebAIM’s WAVE tool or the accessibility audit in Chrome Lighthouse will flag contrast, labels, alt text, and empty links in minutes.
- Submit the form wrong — Leave a required field empty. Does the error message say which field and how to fix it, in text rather than colour alone?
- Listen once — Turn on VoiceOver on a Mac or iPhone, or NVDA on Windows, and listen to your main call to action and form. If it says “button” or “link” with no name, a customer using it hears the same.
Automated tools find a useful share of problems, not all of them. WebAIM states plainly that a page with no detected errors is not proof it is accessible, which is why the manual checks matter.
Fix in the order that protects leads first
A full audit can wait. Start where a barrier costs you money:
- Enquiry, booking, and checkout forms — Visible labels, clear error messages, no repeated fields, large enough buttons, and a submit button with a real name.
- Navigation and calls to action — Named menu and close buttons, visible keyboard focus, and sticky bars or floating buttons that never cover the focused item.
- Global colours and type — Fix contrast in your site-wide settings so every page inherits it.
- Images and icons — Alt text on meaningful images and names on icon links, starting with logos, social icons, and product photos.
- Templates — Bake the fixes into your page, post, and product templates so new content starts accessible.
If you sell online to customers in the European Union, there is a legal reason too: the European Accessibility Act lists e-commerce among the services it covers. For everyone else, the business case is the same as for any conversion fix: more of the visitors you already have can complete the action you want.
Build accessibility into the template, not a one-off audit
Accessibility drifts every time someone adds a page, a plugin, or a new popup. The durable fix is to make the basics part of how the site is built: accessible global colours and typography, labelled form patterns, named buttons and icons, focus that stays visible, and help that sits in the same place on every page. Then recheck your key paths whenever you change the design or add a tool.
TechyXen builds and maintains websites with these basics in the template from day one, and we can audit an existing site, fix the forms and pages that carry your enquiries, and set up the checks that keep it clean. If you want to know what your contact or booking path sounds like to a screen reader, we can test it with you.
Web development · Automation & AI · Digital marketing · Contact · WhatsApp · Call
1 Comment
[…] Fix the accessibility errors that block real customers — a WCAG 2.2 checklist for business website… […]