
Expanded digital accessibility rules have applied since June 2025. They affect many businesses that operate online and make the WCAG 2.2 guidelines and the European Accessibility Act (EAA) particularly relevant.
Many organisations are deciding whether to do the accessibility work in-house or hire a specialist. Here’s what each option requires.
Can you implement WCAG yourself?
Technically
YES
In practice
In most cases, it takes considerable time and expertise.
To bring a website or app into line with WCAG 2.2 in-house, your team needs:
- up-to-date knowledge of WCAG 2.2
- advanced front-end skills, including HTML, CSS, ARIA and semantic markup
- experience with assistive technology and alternative navigation, including screen readers and keyboard navigation
- practical experience designing accessible user journeys
- the ability to test for issues that affect different groups of users
- knowledge of EAA requirements and exemptions.
The European Commission estimates that more than 80 million people in the EU live with a disability. Accessibility guidelines and rules help make digital services easier for them to use.
Source: European Commission, 2023.
When is it worth hiring a specialist?
An experienced accessibility team can be especially useful when:
your organisation has no dedicated accessibility specialists
your website or store has a complex structure or custom features
the service handles many forms, orders or online payments
you run a mobile website or app and need to account for how people use it on small screens
you want to check compliance with the EAA and be ready for an inspection.
Want to check whether your website meets the requirements?
Explore our accessibility audit for WCAG 2.2 and the EAA

Common WCAG implementation mistakes
Digital accessibility takes knowledge of the regulations, web technology and user experience, along with practical experience using assistive tools.
The most common errors are:
- incorrect heading structure (H1–H6)
- missing ARIA labels on form controls
- error messages that are difficult to read
- insufficient colour contrast, particularly in interface controls
- incomplete support for keyboard navigation
- screen reader problems in tools such as NVDA, JAWS and VoiceOver
- missing alternative text for graphics and icons
- missing video captions or audio transcripts
- incorrect button labels, especially in dynamic JavaScript interfaces.
It can be difficult to achieve full WCAG 2.2 compliance in-house.
Many problems arise in the technical details and only become apparent when you test with real assistive technology.
Piotr Rompca
Owner of Evostudio
How much does it cost to implement WCAG?
An early assessment can help keep implementation costs down.
The cost of making a site or app accessible depends on the scope and complexity of the work. There’s no standard price for every project.
The main factors are:
the size and complexity of the site, from a simple business website to a large online store
the number and severity of issues the audit uncovers
the technology involved, such as a CMS, a custom backend or a mobile app
whether existing media need captions, transcripts or audio description
the condition of the existing code and front end.
For example:
a simple project may take a team a few weeks
a large or complex service can take specialists several months.
Need help making your whole site accessible?
See how we can help you implement WCAG

Summary
Meeting WCAG 2.2 requirements takes technical, legal and user experience expertise. It’s possible to do the work in-house, but teams need to account for the risk of missing requirements and the legal consequences that can follow.
Evostudio helps businesses assess, implement and audit digital accessibility against WCAG 2.2 and EAA requirements.
Authors
-
Milena Konieczna
Get in touch and tell us how we can help.
Join the businesses that trust us with their projects.





