By Rakibul Hasan, Moonlab
An accessible website can be used by people with disabilities, such as someone using a screen reader, a keyboard only or who has low vision. The standard most often used is WCAG, the Web Content Accessibility Guidelines. Good accessibility also helps everyone, including people on phones and in bright sun.
This guide covers WCAG basics, quick checks you can do today and what the European Accessibility Act and the ADA in the US mean in general terms. This is not legal advice. Whether a law applies to you depends on your business, your products and your country, so check with a qualified professional.
What WCAG is
WCAG is a set of guidelines published by the W3C. It is organized around four ideas: content must be perceivable, operable, understandable and robust. Each guideline has success criteria at levels A, AA and AAA. Level AA is the usual target.
WCAG 2.1 and 2.2 are the versions in common use. The European standard EN 301 549, used for the European Accessibility Act, refers to WCAG. Check which version your market expects.
Quick checks you can do today
You do not need to be a developer to find the most common problems. Try these on your home page and your key service pages.
- Tab through the page with only your keyboard. Can you reach and use every link, button and form? Is the focus visible?
- Zoom the page to 200 percent. Does it still work without sideways scrolling?
- Check text contrast. Light grey text on white is a common failure.
- Check that all meaningful images have alt text.
- Check that forms have labels, not only placeholder text.
- Check headings are in order and links say where they go, not click here.
- Play any video with captions on.
Free tools
Automated tools such as WAVE, Lighthouse in Chrome and axe browser extensions find many issues. They catch only a portion of problems, so use them as a start. Try a screen reader such as NVDA on Windows or VoiceOver on Mac and iPhone on one key page.
Manual testing with real assistive technology and, ideally, disabled users gives the best picture.
The European Accessibility Act
The European Accessibility Act (EAA) is an EU directive. Its requirements apply from 28 June 2025 to certain products and services, including e-commerce services, consumer banking, e-books, and passenger transport services. Each EU country has its own national law, and enforcement differs.
Microenterprises providing services are exempt, with a microenterprise generally defined as fewer than 10 staff and turnover or balance sheet under 2 million euros. The exemption is for services, not for products. If you sell into the EU, check whether you are in scope and whether the exemption applies. Ask a professional.
ADA and the US
In the US, the Americans with Disabilities Act is used in lawsuits over inaccessible websites, and courts have taken different views on its reach. There is no single technical standard written into the law for private websites, but WCAG 2.1 AA is widely used as the benchmark. Public sector sites have specific rules.
Demand letters and lawsuits against small businesses do occur. Reducing risk comes from actually making the site accessible and keeping a record of your efforts. Talk to an attorney if you receive a claim.
UK position
In the UK, the Equality Act 2010 requires service providers to make reasonable adjustments for disabled people, which can include websites. Public sector bodies have specific accessibility regulations. There is no equivalent of the EAA in UK law, though UK businesses selling into the EU may be affected.
A practical plan for a small business
Fix the basics first, because they help the most people and are cheap. Pick the pages that matter, such as your home, contact, booking and checkout pages.
Write an accessibility statement saying what you have done and how to get help. Add a contact route for users with problems. Ask your web provider to build to WCAG 2.2 AA, and add checks to your launch list. See moonlab.space/guides/website-audit-checklist-small-business.
A worked example and common mistakes
Here is a made-up example. A small online homeware shop in Cork sells to Ireland, the UK and other EU countries, and wants to know where it stands. The owner starts with a one hour test of the home page, a product page and the checkout.
She tabs through each page with the keyboard and finds that the menu cannot be opened without a mouse and the focus outline is hidden. She zooms to 200 percent and finds the checkout button runs off the screen. A contrast check shows grey product prices on white are hard to read. She runs WAVE and finds missing alt text on product images and unlabeled form fields. A short test with a screen reader shows the Add to basket buttons are all announced as button.
She sends the list to her developer, ordered by how many people each problem affects: keyboard menu and focus first, then form labels, button names, contrast and alt text. She asks for a fix of the checkout before the others. After the fixes she repeats the tests, writes a short accessibility statement with a contact email, and adds the checks to her launch list for new pages. She asks an adviser whether the European Accessibility Act applies to her shop.
Avoid these mistakes.
- Relying on an overlay widget to fix everything.
- Testing only with automated tools.
- Using color alone to show errors.
- Placeholder text instead of form labels.
- Videos with no captions.
- Links that say click here.
- Treating accessibility as a one time project.
How to decide and what to do this week
To decide what to fix first, rank problems by how many people they stop and how cheap they are to repair. Use this order as a starting point.
- Keyboard access and visible focus on menus, forms and checkout.
- Form labels and clear error messages.
- Color contrast of text and buttons.
- Alt text for meaningful images and names for icon buttons.
- Captions for video and a transcript for audio.
- A page structure with headings in a sensible order.
How Moonlab can help
We build with accessibility in mind and can review an existing site. See moonlab.space/services/web-development and moonlab.space/services/ui-ux-design.
A free 30-minute automation audit at moonlab.space/contact can include a quick accessibility check of your key pages.
