What an accessible website means in 2026
Europe updated its web accessibility standard in September 2026, and lawsuits against ordinary shop and service websites in the US continue. Most of what accessibility asks for is a well-built site.
The short version
An accessible website is mostly a well-built website: text that enlarges, enough contrast, a description on every image, forms that work from a keyboard, and buttons big enough to tap. In Europe the standard behind the law, EN 301 549, was updated on 2 Sept 2026 to point at WCAG 2.2 (AccessibleEU, 7 Sept 2026), though most local businesses are microenterprises and exempt from the European Accessibility Act’s service rules (CCPC). In the US, lawsuits against small business sites continue (UsableNet’s lawsuit tracker). Ask your web designer which WCAG level your site meets.
Accessibility means a website that works for people who see less, hear less, cannot use a mouse, or are simply reading on a small phone in bright sun. It sounds like a specialist subject. For a small business site it is mostly a list of ordinary things done properly.
Two things happened this year that make it worth an hour of your attention. In Europe, the technical standard behind the accessibility laws was updated on 2 Sept 2026. In the United States, lawsuits over inaccessible websites continue at a steady pace, and many name ordinary shop and service sites.
This article says which of those applies to you, what the standard actually asks for, and what to check on your own site. If you have never looked at your homepage critically, the homepage check is the place to start, and this follows on from it.
The standard asks for ordinary things, done properly.
WCAG, the Web Content Accessibility Guidelines, is the list that most accessibility laws point to. It comes in versions and levels, and the level that matters for a business site is AA. The updated European standard points at WCAG 2.2 (AccessibleEU, 7 Sept 2026). In plain terms, it asks for the following.
| The guideline | Who it helps | How to check on your own site |
|---|---|---|
| Text you can enlarge | Older customers, anyone on a phone | Pinch to zoom on your phone. Everything should still be readable and nothing cut off. |
| Enough contrast between text and background | People in bright sunlight, tired eyes | Pale grey text on white is the usual failure. Read your site outdoors. |
| A text description on every image | Screen reader users, and search engines | Ask your designer to show you the alt text on three photos. |
| Forms that work with a keyboard | People who cannot use a mouse | Press Tab through your booking form. Every field and the button should get a turn. |
| A visible focus outline | Keyboard users | While pressing Tab, you should always see which field is active. |
| Captions on video | Deaf and hard-of-hearing people, anyone with the sound off | Any video on the site has captions on the video itself. |
| No information carried by colour alone | Colour-blind people | A red asterisk is not enough. The word required should be there too. |
| Buttons large enough to tap | Everyone with a thumb | Tap the Call and Book buttons on your phone without zooming first. |
Read that list again and notice that none of it is about disability in particular. It is about the customer who finds you on a phone at a bus stop, the one who has left their glasses at home, and the one browsing with the sound off in a waiting room. An accessible site is a site that works in worse conditions than the designer’s desk.
In Ireland and the euro area, the standard changed in September.
The technical standard behind Europe’s accessibility laws is called EN 301 549, and ETSI published an updated version, 4.1.1, on 2 Sept 2026 (AccessibleEU, 7 Sept 2026). This section applies to Ireland and the euro area. US readers can skip to the section on lawsuits.
The update “adds six new accessibility requirements from WCAG 2.2, removes the obsolete 4.1.1 Parsing criterion, and requires websites and documents to better respect users’ accessibility preferences”. It is also “the first version of EN 301 549 developed specifically with the European Accessibility Act in mind” and “includes a new annex that links the standard’s requirements directly to the EAA”.
Nothing has changed in law yet. “Until the European Commission formally cites EN 301 549 v4.1.1 in the Official Journal of the European Union, the current reference remains EN 301 549 v3.2.1 (2021), which is based on WCAG 2.1 Level AA”. Once it is cited, meeting the new version “will give organisations a presumption of conformity with both the European Accessibility Act and the Web Accessibility Directive”.
For a small business the practical reading is simple. If your site is being built or rebuilt now, ask for WCAG 2.2 AA, because that is where the standard is heading. If it was built to 2.1 AA, it is not suddenly out of date. The difference between the two is a handful of requirements, and a site that meets the older level is most of the way to the newer one.
Most local businesses are microenterprises, and most are exempt.
In Ireland and the euro area, most local businesses are microenterprises, and the European Accessibility Act exempts microenterprises from its service requirements, subject to conditions. Ireland’s Competition and Consumer Protection Commission puts the definition this way: “If your business employs fewer than 10 persons and has an annual turnover not exceeding €2 million or an annual balance sheet total not exceeding €2 million, it is a microenterprise” (CCPC).
That covers the café, the plumber, the salon and the two-person estate agency. The exemption does not automatically cover a guesthouse taking bookings online with more staff than that, or a shop selling online with a payroll above the limit. Those are the kinds of business the Act is aimed at. The exemption has conditions, and the CCPC page is the place to check them, not this article.
A café with a few staff and a booking form
A guesthouse above the staff limit taking bookings online
A one-van plumber with a contact page
A shop above the staff or turnover limit selling online
A salon with a small team and an online diary
A dental group with several branches and online booking
Exempt does not mean irrelevant. The customers who need an accessible site do not check your headcount first, and a microenterprise that grows past the limit will find it cheaper to have built properly from the start than to rebuild later.
In the US, the risk is a lawsuit, not a regulator.
In the United States there is no regulator routinely checking your site. There are lawyers. Suits under the Americans with Disabilities Act over inaccessible websites continue at a steady pace in 2026, and many of them name ordinary shop and service sites rather than big brands, according to a tracker kept by UsableNet, a company that sells accessibility services (UsableNet’s lawsuit tracker). This section applies to US readers; the European sections above do not.
The things a screen reader trips on are the ones in the table above: images with no description, a menu that cannot be opened from the keyboard, a booking form with unlabelled fields. They are also the cheap fixes. A site missing the basics is the easy target, and a site that has them is a much less attractive one.
Be wary of anyone selling an overlay: a widget added with one line of code that promises to make the site compliant. These are widely criticised in the accessibility field, and they do not stop lawsuits. They sit on top of the page and change how it behaves for some visitors, but the missing descriptions and unlabelled fields are still missing underneath. The fix is in the site itself.
Try this now
Turn on the screen reader built into your phone (VoiceOver on an iPhone, TalkBack on Android) and open your own homepage. Swipe through it with your eyes closed. Every image should announce something useful, and every button should say what it does. If you hear “image, image, button”, you have found the first job.
What to ask whoever built your site.
Ask whoever built your site which WCAG level it meets. A straight answer is 2.1 AA or 2.2 AA. A blank look tells you something too. Then ask for the cheap things first: image descriptions, contrast, focus outlines and form labels. Those four cover a large part of what the guidelines ask for and cost the least to put right.
- Pinch-zoom on a phone works and nothing is cut off.
- Body text is dark on light, or light on dark, with no pale grey.
- Every photo and logo has a description that says what it shows.
- Tab moves through every form field and button, in order, with a visible outline.
- Every form field has a written label, not just placeholder text inside it.
- Any video has captions.
- Required fields say required in words, not only in red.
- Call, Book and Menu buttons are big enough to tap without zooming.
- If the site takes bookings or payments, the booking flow passes all of the above.
- Whoever built the site has said, in writing, which WCAG level it meets.
0 of 10 checked
If you are planning a new site, put the WCAG level in the brief before anyone starts; the planning article has the other questions to settle at the same time. And if the site takes bookings, the form is the part most worth testing, because it is where a customer who cannot get through simply leaves. The bookings article covers what a booking flow should do.
A few common questions.
Does the European Accessibility Act apply to my small business?
Probably not directly. Most local businesses are microenterprises, meaning fewer than 10 staff and turnover or balance sheet not over €2 million, and microenterprises are exempt from the Act’s service requirements, subject to conditions. Check the CCPC’s guidance for microenterprises to be sure, and ask a lawyer if you are close to the limits.
Is WCAG 2.2 now required in Europe?
Not yet. The updated standard, EN 301 549 version 4.1.1, points at WCAG 2.2, but until the European Commission cites it in the Official Journal the legal reference is still the 2021 version, based on WCAG 2.1 Level AA. If you are building now, aim at 2.2 AA anyway.
Can I be sued in the US over my website?
Yes. Lawsuits under the Americans with Disabilities Act over inaccessible websites continue at a steady pace, and many name ordinary shop and service sites. The things worth fixing first are missing image descriptions, menus and forms that do not work from a keyboard, and unlabelled fields. They are also the cheapest to fix.
Will an accessibility widget make my site compliant?
No. Overlay widgets that promise compliance with one line of code are widely criticised and do not stop lawsuits. They sit on top of the page, and the missing descriptions and labels are still missing underneath. Fix the site itself.
What is the cheapest thing I can do today?
Add a text description to every image, and check that your body text is dark enough to read outdoors. Both are quick in most site builders and cover a good part of what the guidelines ask for.
Will accessibility make my site look worse?
No. Contrast, readable text, clear labels and visible buttons are the same things that make a site easy for everyone. An accessible site usually looks cleaner, not plainer.
