The European Accessibility Act Is One Year Old. Most Irish Business Websites Are Still Not Compliant.

This Saturday, 28 June, marks the one-year anniversary of the European Accessibility Act coming into force in Ireland. For most Irish businesses, that date passed without anyone noticing.

That is about to change.

The European Accessibility Act (EAA) introduced legally binding accessibility requirements for digital services sold in the EU. If your website takes orders, accepts bookings, processes payments, or delivers services online, there is a good chance it falls within scope. Research conducted before the deadline by Recite Me found that roughly half of Irish businesses were unaware the regulations were even coming ^[5]. In the year since, enforcement has been quiet. That does not mean the obligation has gone away.

Here is what you actually need to know, and where to start.

What the EAA Actually Covers

The EAA does not apply to every website in existence. It targets specific service categories where digital barriers cause the biggest practical harm to people with disabilities. In practice, that means businesses providing any of the following online:

• E-commerce (selling products or services online)
• Online booking systems
• Digital payment services
• Electronic communications services
• Banking and financial services
• Passenger transport ticketing and information

If your website takes a card payment, books an appointment, or processes a subscription, you are almost certainly providing an e-commerce service under the Act. The regulation applies to any business offering these services to consumers in the EU, regardless of where the business is based ^[2].

Pure information websites, strictly speaking, may sit outside the immediate scope. A website that publishes your opening hours and phone number, with no transactional element, has a different position to one with a checkout. But most businesses we talk to are not running brochure sites. They have booking buttons, payment links, and enquiry forms that feed directly into their sales process. If you are in any doubt about where your site sits, that is a question for your solicitor, not a guess you should make yourself.

The safe working assumption for any business that generates revenue through its website is to aim for compliance. This also connects to a broader point: poor website decisions compound over time, and common website mistakes cost businesses customers every day. Accessibility is one more dimension where the gap between well-built and hastily-built sites becomes commercially visible.

The Timeline: New Sites vs. Existing Services

This is the part that matters most, and the part most coverage has got slightly wrong.

If you launched a new digital service or added new e-commerce capability after 28 June 2025, it must comply with the accessibility standard now. There is no grace period for new services.

If your website and its core transactional functionality existed before 28 June 2025, you have until 28 June 2030 to achieve full compliance. That is four years. It sounds generous. But accessibility is not a toggle you switch on overnight, and most businesses have a long list of things they have been meaning to address for four years. Start now and it is a manageable project. Leave it to 2029 and it becomes an emergency.

The technical standard you need to meet is WCAG 2.1 Level AA (the Web Content Accessibility Guidelines published by the World Wide Web Consortium). Ireland's implementation of the EAA requires compliance with EN 301 549, which incorporates WCAG 2.1 Level AA in full ^[3].

The penalties for non-compliance in Ireland are not small. A summary conviction can result in a fine of up to €5,000. On indictment, that rises to €60,000, with the possibility of imprisonment in more serious cases ^[1].

Who Is Actually Exempt

Not every business is caught by this.

Micro-enterprises are partly exempt. The definition is specific: businesses with fewer than 10 employees AND annual turnover or balance sheet total below €2 million. If you meet both criteria, you have limited exemptions for services you provide. Notably, the exemption does not extend to products you place on the market.

That threshold is narrower than most business owners assume. If you have more than 10 people working for you, even part-time, or your revenue runs above €2 million, you are not a micro-enterprise under the EU definition and the exemption does not apply to you.

Worth noting for growing businesses: you are building something to scale. An accessible digital service costs less to build correctly from the start than to retrofit under deadline pressure. Most of the businesses I speak to who took accessibility seriously early on found it made their sites better for everyone, not just users with disabilities. Clearer form labels, better colour contrast, keyboard-navigable layouts. These improvements benefit every customer.

What WCAG 2.1 AA Actually Means for a Small Business Website

Most business owners hear "WCAG 2.1 Level AA" and imagine a total rebuild. In practice, many of the requirements are specific, testable, and fixable without touching your theme or hiring a developer.

Here is what the standard actually asks for, in plain terms:

Alternative text on images. Every meaningful image needs a text description so that screen readers can convey it to visually impaired users. A product photo without alt text is invisible to someone using assistive technology. Consider what that means at the moment of purchase: a customer who cannot read your product images cannot make a confident buying decision. They leave, find a competitor whose site works for them, and do not come back.

Colour contrast. Text must have sufficient contrast against its background. The minimum ratio for standard body text under WCAG 2.1 AA is 4.5:1. A soft grey font on a white background might look refined on a high-resolution screen and be effectively unreadable for users with low vision or colour blindness.

Keyboard navigation. Every function on your website, including your menu, checkout, booking form, and filters, must be usable by someone who cannot use a mouse. This covers people using screen readers, switch access devices, and keyboard-only navigation. If your checkout requires a mouse click to proceed, a significant proportion of users with motor impairments simply cannot complete a purchase from you.

Clear form labels. Every field in your contact form, booking flow, or checkout needs a visible, associated label. Placeholder text inside the input field does not count as a label. When the placeholder disappears as a user starts typing, the context is gone. Screen readers announce the field as "edit text" with no indication of what should go there.

Descriptive link text. The phrase "click here" as a link anchor tells nobody where they are going. A screen reader user navigating by links alone hears a list of "click here, click here, click here." Fixable in minutes and clearer for every visitor.

Your website content also plays a role in this. Content with clear headings, plain language, and logical reading order is both more accessible and more likely to meet the quality signals Google now evaluates under E-E-A-T standards. Accessibility and search quality are not competing priorities. They typically reinforce each other.

One important thing to know upfront: no accessibility plugin on its own guarantees compliance. Automated tools typically catch somewhere between 30% and 40% of accessibility issues, depending on the complexity of your site. The remainder requires human review. Plugins are a starting point and a useful ongoing monitoring tool. They are not a finish line.

How Full WordPress Helps You Get There

This is one of the practical advantages of building on full WordPress rather than a proprietary platform.

WordPress has a long-standing internal commitment to accessibility. The block editor has been developed with accessibility standards in mind, and core WordPress components meet many WCAG requirements by default. Accessibility-ready themes in the WordPress repository must pass defined accessibility criteria before they are listed. That does not mean every theme is compliant out of the box, but the baseline is substantially better than most closed builders.

Beyond core, the plugin ecosystem gives you access to dedicated accessibility tools at a depth that platforms like Wix or Squarespace cannot match. WP Accessibility, Accessibility Checker by Equalize Digital, and All in One Accessibility are among the options available. These tools scan your content for issues, fix common problems in bulk, and help you generate the Accessibility Statement that the EAA also requires you to publish.

Web60's all-inclusive €60/year platform gives you complete access to this ecosystem from day one. No restrictions on which plugins you can install, no requirement to upgrade to a higher tier, no waiting for the platform to add an accessibility feature to its product roadmap. You have full WordPress, which means you have the tools to genuinely address this. That is a meaningful difference when you are facing a compliance requirement rather than a nice-to-have improvement.

Where to Start This Month

Rather than treat accessibility as a project to schedule for some future quarter, here is a straightforward process to make real progress now.

Scan. Run an automated assessment using Google Lighthouse (available in Chrome DevTools under the Lighthouse tab) or the free WAVE tool from WebAIM. Both are free, take under ten minutes, and give you a prioritised list of issues. You do not need a developer to run either of them.

Fix. Address the issues that automated tools can resolve directly. Alt text on images, form label associations, and basic colour contrast failures are often identifiable and fixable without touching any code. An accessibility plugin on your WordPress site will surface many of these and offer guided remediation.

Test. Close your mouse, open your homepage, and try to navigate using only the Tab key. Try to reach your contact form, your booking button, or your checkout. If you cannot get there without a mouse, neither can a keyboard user. This test costs nothing and reveals problems that automated scans often miss.

Publish. Write your Accessibility Statement. The EAA requires it. It does not need to be long. It should state your current compliance level, note any areas you are still working on, and give users a way to report issues they encounter. Add it as a standard page on your site and link to it from your footer.

Schedule. Set a recurring calendar reminder to run another automated scan every six months. Content changes, plugins update, and new pages get added. Accessibility is not a one-time project.

This is a pattern that plays out well when businesses approach it methodically. Consider a typical example: a gift shop in Killarney with an online checkout added ahead of tourist season goes through this process over a few evenings, working through the scan results one issue at a time. The result is not a perfect site (few are) but a measurably better one, with an honest Accessibility Statement that sets realistic expectations. That is a reasonable position to be in one year on.

Conclusion

The EAA has enforcement mechanisms with real financial consequences. But the more straightforward reason to deal with this is commercial.

Roughly 15% of the population lives with some form of disability. An inaccessible checkout, booking form, or product page is turning away real customers who intended to buy from you. That is not a regulatory problem first. It is a revenue problem.

If your site is on full WordPress, you are on the platform best equipped to handle this, with the tools, themes, and plugins to make genuine progress without a developer on retainer. Start with the automated scan this week. Fix the obvious issues. Publish your Accessibility Statement. Commission an independent review before the end of the year if compliance genuinely matters for your business.

June 2030 will arrive faster than most people expect.

Frequently Asked Questions

Does the European Accessibility Act apply to my small business website?

It depends on what your website does. The EAA applies to businesses providing e-commerce services, online bookings, and digital payments to consumers in the EU. Pure information websites without these transactional functions may not be directly in scope, though the answer depends on how your services are structured. Micro-enterprises (fewer than 10 employees AND under €2 million annual turnover) have limited exemptions for services, though not for products they sell. If you are unsure, that question belongs to your solicitor.

What is the compliance deadline for Irish businesses?

If you launched a new digital service or e-commerce capability after 28 June 2025, it must comply now. If your website was live and providing services before that date, you have until 28 June 2030. Building accessibility in now is significantly cheaper than retrofitting it under deadline pressure in a few years.

What standard do I need to meet for EAA compliance?

The EAA requires compliance with EN 301 549, which incorporates WCAG 2.1 Level AA. In practical terms, this covers alternative text on images, sufficient colour contrast for text, keyboard navigation throughout your site, clearly labelled form fields, and descriptive link text. It is more specific and more achievable than the acronyms suggest.

What are the fines for non-compliance in Ireland?

Under the Irish regulations, a summary conviction can result in a fine of up to €5,000. On indictment, that rises to €60,000, with the possibility of imprisonment in serious cases. Enforcement against small businesses has been limited in the first year, but the legal framework is in place.

Can a WordPress plugin make my site fully compliant with the EAA?

Plugins help but do not guarantee compliance on their own. Automated accessibility tools typically identify between 30% and 40% of issues on a given site. Meeting the EAA standard properly requires accessible design, accessible code, and accessible content working together. Use a plugin as your starting point and ongoing monitoring tool, then consider an independent human accessibility audit if compliance is business-critical.

Do I need to publish an Accessibility Statement?

Yes. The EAA requires businesses in scope to publish an Accessibility Statement on their website. It should state your current compliance level, identify any known gaps you are still addressing, and provide a mechanism for users to report issues. This is a standard page on your WordPress site, linked from the footer.

Sources