Website Accessibility Ireland 2026: What Businesses Need to Know

Website accessibility in Ireland is no longer a subject that online businesses can leave in a future roadmap. Since 28 June 2025, the European Accessibility Act has applied in Ireland to specified products and consumer services—including e-commerce services. In 2026, accessibility belongs alongside privacy, security and consumer rights in the planning of any serious digital project.

The business case is just as practical. An accessible website removes obstacles for people with visual, hearing, mobility, speech, cognitive and neurological disabilities. It can also make a site easier to use for older customers, people with temporary injuries, anyone using a keyboard instead of a mouse, and customers trying to complete a task on a small screen or in a noisy place.

This guide explains the Irish position in plain language and gives businesses an actionable way to improve. It is general information, not a legal opinion. The rules depend on the service, organisation and circumstances, so obtain independent legal advice where compliance is uncertain.

The short answer: what changed in Ireland?

Ireland implemented the European Accessibility Act through the European Union (Accessibility Requirements of Products and Services) Regulations 2023, commonly cited as S.I. No. 636/2023. The main provisions came into operation on 28 June 2025.

The legislation covers defined products and services rather than every website in exactly the same way. Services within its scope include consumer banking, certain transport information and ticketing services, e-books, electronic communications and e-commerce services. For online retailers and other businesses enabling consumers to conclude contracts online, that e-commerce category is especially important.

The Competition and Consumer Protection Commission is the Irish compliance authority for areas including e-commerce services and e-books. Other authorities are responsible for other sectors.

Does the European Accessibility Act apply to every Irish business website?

No. It is inaccurate to say that every private business website automatically falls within the same obligations. Scope depends on what the business provides, who receives it and whether an exemption or transitional provision applies.

An informational business-to-business brochure website is not the same as a consumer e-commerce service. An online shop that allows a consumer to select products, enter details and conclude a purchase is much more clearly connected with the e-commerce provisions. Booking, subscription and marketplace journeys can also require careful analysis.

The Irish regulations define a microenterprise as an enterprise employing fewer than 10 people and having either annual turnover not exceeding €2 million or an annual balance-sheet total not exceeding €2 million. A microenterprise providing a service is exempt from the service accessibility requirements in the regulations. The position for a microenterprise dealing with in-scope products is different, and the definition should not be confused with the broader term “small business”.

The CCPC has published specific European Accessibility Act guidance for microenterprises. Even where an exemption applies, the CCPC encourages accessibility: it expands the potential market, reduces friction and makes future growth less disruptive.

Do not decide that the business is exempt based on an impression of its size. Confirm employee and financial criteria, linked-business implications, the exact service being offered and any other relevant provisions with an appropriate adviser.

Public-sector websites follow a separate framework

Public bodies already have web and mobile accessibility duties under a different legal framework: the EU Web Accessibility Directive, implemented in Ireland by S.I. No. 358/2020. The National Disability Authority explains the public-sector requirements, including accessibility statements and monitoring.

That framework should not be collapsed into the private-sector e-commerce rules. A public body, a private online retailer and a microenterprise brochure site can have different legal positions, even though the practical design techniques often overlap.

What does an accessible website actually allow people to do?

An accessible website lets people perceive the information, operate the interface, understand what is happening and use it with current and future technologies. Those ideas form the four principles of the Web Content Accessibility Guidelines: perceivable, operable, understandable and robust.

In practice, a customer should be able to:

• Navigate menus, dialogs, forms and checkout using a keyboard.
• See where keyboard focus is at every step.
• Understand headings, labels, instructions and error messages.
• Read text against its background with adequate contrast.
• Zoom or reflow content without losing actions or information.
• Use a screen reader to identify structure, controls and meaningful images.
• Pause movement that distracts or creates a barrier.
• Access captions or alternatives for important audio and video.
• Complete authentication and payment without an unnecessary cognitive test.

Accessibility is not a special version of the website. It is the quality of the main experience.

Where WCAG 2.2 fits—and where it does not

The Web Content Accessibility Guidelines are the internationally recognised technical standard for web accessibility. WCAG 2.2 is the latest WCAG 2 version, and W3C encourages organisations to use it. It adds criteria addressing matters such as visible focus, dragging alternatives, target sizes, consistent help, redundant entry and accessible authentication.

For organisations working on European Accessibility Act requirements, W3C notes that most use WCAG together with the European standard EN 301 549. At the time of writing, the current EN 301 549 references WCAG 2.1, while a future revision is expected to use WCAG 2.2.

This distinction matters: “we installed an accessibility plugin” is not a compliance strategy, and “the homepage scores 100 in one scanner” is not proof that the whole service meets its legal obligations. WCAG is an essential technical reference, but the law may include service information, support processes, documentation and sector-specific requirements beyond individual web pages.

The website problems Irish businesses should fix first

1. Keyboard traps and invisible focus

Unplug the mouse and work through the site using Tab, Shift+Tab, Enter, Space and Escape. Every interactive element should be reachable in a logical order. The current position needs a visible focus indicator. Menus, cookie controls, calendars, filters and pop-up dialogs must not trap the user.

2. Weak headings and page structure

Headings are not merely large text. They give a page an understandable outline and help screen-reader users move between sections. Use one descriptive main heading, then nest subsections logically. Do not select heading levels based on visual size.

3. Images without useful alternatives

An informative image needs alternative text that communicates its purpose in context. A decorative flourish normally needs an empty alternative so assistive technology can ignore it. Product images may need specific descriptions; a link containing only an image needs an accessible name. Repeating a filename or stuffing keywords into alt text helps nobody.

4. Forms that rely on placeholders

Every field needs a persistent, programmatically associated label. Instructions should appear before they are needed. If submission fails, identify the fields with errors, describe how to correct them and preserve the customer’s existing input. Colour alone should never carry the message.

5. Low contrast and colour-only meaning

Pale grey text, text placed over busy photography and subtle form borders are common design failures. Check text, controls, focus indicators and meaningful graphics. Links within body copy should be identifiable without relying only on a small colour difference.

6. Mobile layouts that do not reflow

Test zoom, landscape orientation and narrow viewports. Content should reflow rather than forcing two-direction scrolling for ordinary text. Sticky banners must not cover controls. Touch targets need enough space to avoid accidental activation. Our article on mobile-friendly websites covers the broader commercial case.

7. Video, audio, animation and motion

Provide accurate captions for meaningful speech and relevant audio. Supply transcripts or audio description where the content requires them. Avoid autoplay with sound, allow users to pause moving content and respect reduced-motion preferences. Never publish effects that create seizure risk.

8. Inaccessible PDFs and third-party tools

A polished HTML page does not solve an inaccessible menu, application form, price list or report uploaded as a PDF. Payment widgets, booking engines, maps, live chat and consent managers are part of the customer journey too. Test them and include accessibility requirements in supplier selection.

Why an automated accessibility score is not an audit

Automated tools are valuable for finding repeatable problems such as missing labels, some contrast failures and invalid relationships. They are also fast enough to include in development and publishing workflows.

But the W3C is explicit that tools cannot check every accessibility aspect automatically. Human judgement is required, and tools can return misleading results. Software cannot reliably decide whether alternative text is useful, whether a checkout is understandable, whether focus order makes sense or whether an error message helps someone recover.

A credible review combines:

• Automated tests across representative templates and states.
• Keyboard-only testing.
• Screen-reader checks on core journeys.
• Zoom, reflow, contrast, motion and orientation checks.
• Manual review against the relevant WCAG success criteria.
• Testing with disabled users where possible.
• Documentation of scope, evidence, exceptions and remediation.

Accessibility overlays are not a substitute for fixing the site

A toolbar that changes font size or colours may offer a preference to some users, but it does not repair missing semantics, broken keyboard interactions, inaccessible checkout logic or poor source content. An automated overlay cannot take responsibility for the underlying website, third-party components and business processes.

Prioritise accessible design, semantic HTML, tested components and maintainable content. Add optional user controls only where they provide genuine value.

A practical 30-day accessibility plan

Period	Action	Useful output
Days 1–5	Confirm legal scope, owners and priority user journeys.	Scope note covering services, exemptions, templates and suppliers.
Days 6–12	Test the homepage, navigation, contact, search, account and checkout paths.	Issue register with evidence, WCAG references, severity and owner.
Days 13–21	Fix blockers in templates and shared components before isolated content issues.	Keyboard-operable, labelled and reflowing core journey.
Days 22–26	Retest with multiple methods and validate third-party components.	Regression results and documented limitations.
Days 27–30	Publish support information and embed checks into normal operations.	Accessibility contact route, publishing checklist and review schedule.

Fixing the shared design system first gives the greatest return. Correcting one form component can improve every form; correcting the header can improve every page. Then work through unique templates, documents and older content.

Make accessibility an operating habit

A website can regress the day after an audit. A new campaign can introduce text inside images, a plugin update can alter focus behaviour and a content editor can skip heading levels. Sustainable accessibility needs ownership.

Add acceptance criteria to design and development tickets. Give editors rules for headings, links, media and PDFs. Keep a tested component library. Include disabled users in research. Require vendors to explain what they tested rather than simply declaring that their tool is accessible.

Maintain a clear route for customers to report a barrier. Responding well to a specific problem is both good service and a source of valuable product insight.

Accessibility, SEO and conversion: related but not identical

Accessibility is about people, not rankings. It should never be reduced to an SEO tactic. However, several good practices also improve clarity and discoverability: descriptive titles, real headings, meaningful links, useful image alternatives, captions and clean page structure.

The overlap is incomplete. A page can be technically indexable and still be impossible to use with a keyboard. It can have excellent alt text and still present an inaccessible payment dialog. Treat accessibility, SEO and conversion as distinct disciplines that share a well-built foundation.

Frequently asked questions

Is WCAG 2.2 legally required for every website in Ireland?

No single statement fits every organisation. Private services within the European Accessibility Act, public bodies under the Web Accessibility Directive and organisations governed by other duties can have different requirements. WCAG is the leading technical standard, but legal scope and the applicable European standard need to be assessed in context.

Are microenterprises exempt from website accessibility rules?

The Irish EAA regulations exempt a microenterprise providing a service from the service requirements. A microenterprise has fewer than 10 employees and turnover not above €2 million or a balance-sheet total not above €2 million. This does not mean every small organisation is exempt from every accessibility duty. Confirm the business, service and applicable law independently.

Can a WordPress website be accessible?

Yes. WordPress can support accessible websites, but the result depends on the theme, plugins, content, configuration and testing. Platform choice alone does not create conformance.

How often should a website be reviewed?

Test during design and development, before significant releases, after major component changes and on a recurring risk-based schedule. High-use journeys such as checkout and account access deserve more frequent checks.

Where should an Irish business start?

Start with the journeys that matter most: navigation, contact, sign-up, search, booking and checkout. Remove critical blockers, then improve the shared system and editorial process. For a broader build plan, use our Irish business website guide.

SEOWeb.ie builds fast, accessible-by-design WordPress experiences for Irish businesses. Explore our web design and SEO services or request a practical website review.