Web Accessibility Part 1: Why Should You Care, and What Does the EAA Change?
The opening article of our two-part series explains what digital accessibility is, why it is important, and which changes businesses and institutions will face once the European Accessibility Act (EAA) takes effect.
Digital accessibility has stopped being merely “nice to have” – across the European Union it is turning into a legal obligation. The opening article of our two-part series explains what digital accessibility is, why it is important (not only from an ethical standpoint, but also a legal and strategic one), and which changes businesses and institutions will face once the European Accessibility Act (EAA) takes effect.
You’ll find out who gains from accessible design, which obligations come into play, and how putting money into accessibility results in better digital products for all users.
What is the European Accessibility Act?
The European Accessibility Act (EAA) took effect on June 28, 2025. This law is likely to considerably change how digital products are designed and built in the European Union. Both companies and public institutions will have to adjust their services, digital ones included, to new accessibility standards.
For businesses active in the EU, this means making sure their physical and digital products satisfy the EAA requirements. Companies from outside the EU that sell services or products in the EU also have to follow these rules if they want to keep doing business in this market. The only exception is micro-enterprises (companies employing fewer than 10 people with annual revenues below $2 million).
Two key deadlines set the pace for putting the regulations into practice:
- Starting June 28, 2025, every newly created product and service has to meet the EAA requirements.
- The makers of existing solutions have until June 28, 2030, to bring services and applications already in operation up to the new standards.
Not meeting the requirements of the European Accessibility Act can have serious consequences: fines ranging from several thousand up to several hundred thousand euros (depending on the Member State), bans on selling products in the EU, and lost reputation and customers who move to more accessible competitors.
For front-end developers, UX/UI designers, business owners and app developers, this sends a clear message: accessibility has to be treated seriously, not only as good practice but as a legal obligation.
It is a good moment to take a look at web accessibility, why it matters so much, and what can be done to make websites and web applications usable by as many people as possible, including people with disabilities, seniors and users with limited access to technology.
Who is covered by the European Accessibility Act?
The European Accessibility Act applies to many products and services that affect users’ everyday lives. The regulations cover:
- Companies providing digital services and products, such as online stores, banking platforms, video services and mobile applications. The obligations apply both to companies registered in the EU and to organizations from outside the European Union (e.g., from the US) whose offerings are aimed at EU customers.
- Makers of digital and physical equipment, for example general-purpose computers, self-service terminals, ATMs and smartphones. The requirements apply to every company that puts its products on the EU market, wherever it is based.
- Public institutions that provide digital services, such as government offices, government portals and e-government systems. Every public administration body in the EU member states has to make sure its websites and applications are accessible in line with the EAA.
What is digital accessibility, and who is it for?
Digital accessibility means designing websites and applications so that as many people as possible can use them, whatever their abilities, limitations, devices or way of interacting with the interface.
The core elements of accessibility are clear, plain-language content, interactive components that work intuitively, and full compatibility with assistive technologies such as keyboards, screen readers and voice control.
Many people wrongly assume that accessibility concerns only blind users of screen readers. In fact, it helps a wide range of people, including those with temporary, situational or long-term impairments, for example:
- People with low vision – who do not always use a screen reader, but may, for instance, increase the font size or zoom the page,
- Users with dyslexia – who read more easily when content uses a simple font, wider line spacing and a predictable page layout,
- Users with color vision deficiencies – who may miss color-coded system signals unless they are also marked with text or icons,
- Users with motor impairments – who struggle to move the cursor precisely and frequently rely on a keyboard or voice control,
- Users with photo- or motion sensitivity may find blinking elements or intense animations unpleasant, and these can even trigger neurological reactions.
Designing with accessibility in mind not only helps people with permanent disabilities, but also makes experiences easier to use for everyone.
WCAG and accessibility levels
Under the European Accessibility Act, digital service providers have to meet particular accessibility standards. In practice, this means implementing solutions that conform to the Web Content Accessibility Guidelines (WCAG).
WCAG is an internationally recognized set of standards describing how to make digital content accessible to people with disabilities. It is created and maintained by the Web Accessibility Initiative (WAI), a working group of the World Wide Web Consortium (W3C), an international organization established in Switzerland whose mission is to make the web work better for everyone.
WCAG has been developing since 1999 and underpins many national and international accessibility laws, the European Accessibility Act among them. The guidelines specify three conformance levels:
- A (minimum requirements),
- AA (the recommended standard for most websites),
- AAA (advanced accessibility, typically reserved for specialized content).
Level A
A website or application that conforms to Level A satisfies the minimum criteria that remove the most obvious barriers. They include:
- Providing alternative text for graphics (e.g., the alt attribute on images),
- Making sure every function can be used with a keyboard,
- Steering clear of content that could trigger epileptic seizures (e.g., flashing ),
- A consistent navigation structure,
- Clear labels on form fields.
Level A is the absolute minimum, but it does not guarantee a comfortable experience for every user.
Level AA
This is the target most often recommended and the most realistic one for the majority of organizations. It includes every Level A requirement and adds elements that genuinely improve usability:
- Enough contrast between text and background,
- Captions for video content with sound,
- The option to enlarge content without any loss of functionality,
- Multiple ways to find information (e.g., a search engine, a site map),
- A logical, clear heading hierarchy.
Conforming to Level AA offers a good balance between accessibility and what is technically achievable.
Level AAA
This is the most advanced and most demanding accessibility level. Implementing it fully is hard, but it is worth aiming for at least some of its guidelines. Among other things, it covers:
- Sign language interpretation of films,
- Very high contrast between text and background,
- Audio descriptions for video content,
- No time limits on interactions (e.g., during shopping or booking),
- Context-sensitive help for complex features (e.g., long forms).
Even if implementing the AAA level in full is not always feasible, every part that is adapted makes the digital service friendlier to users.
Keep in mind that WCAG levels build on each other, so meeting the AA level also satisfies the requirements of the A level. For most public and commercial websites, WCAG 2.1 level AA is the standard needed to fulfill legal obligations, including those imposed by the European Accessibility Act (EAA).
That said, accessibility is about more than ticking items on a compliance checklist. Real accessibility means designing and building with empathy, so that everyone can use digital products comfortably, efficiently and without obstacles, whatever their limitations or situation.
How does the EAA affect websites and digital platforms?
Beyond the conformance levels, WCAG requires websites to follow four core accessibility principles:
- Perceivable – content has to be accessible by sight and by sound to people with different disabilities, including visual, hearing or cognitive impairments.
- Operable – the whole website should be usable with a keyboard and work with assistive technologies (e.g., screen readers).
- Understandable – interfaces and content should use simple, logical language and be clearly organized.
- Robust – the website code has to be built so that it works with current and future accessibility support tools (e.g., semantic HTML, ARIA roles).
Why invest in accessible websites and applications?
1. Why digital accessibility matters
Building accessible websites and web applications is today one of the main challenges in designing digital services. Applying accessibility principles shows social responsibility, and it is also a practice that improves the usability, reception and long-term success of any online project.
2. Reaching more people
People with different kinds of limitations, whether visual, hearing, motor or cognitive, make up a growing share of Internet users. This group includes not only people with permanent disabilities, but also those whose limitations are temporary or situational. As the population ages, accessibility needs naturally grow.
Sadly, these users are still frequently ignored during design and development. By building solutions that include them and are accessible to them, we make our services available to a wider and more varied audience and improve the experience for all users.
3. Making things more comfortable for everyone
Accessible interface design principles – like a clear structure, readable fonts, sufficient contrast and the option to use applications and websites without a mouse – make applications and websites more intuitive for all users. Not only people with disabilities gain from this, but also seniors, mobile users and people less comfortable with technology.
4. Building a good image
Accessible websites and applications come across as friendlier and more attentive to what users need. Caring about accessibility becomes part of a brand’s identity – it shows empathy, inclusiveness and social responsibility. These days, this matters more and more when building relationships with users.
5. Better online visibility
Following accessibility rules frequently goes together with better search engine rankings. A correct header structure, logical element markup and alternative text for graphics all help SEO, making a website or application more visible in search results.
Practical steps to get ready for EAA compliance
Meeting the requirements of the European Accessibility Act calls for technical changes as well as an organizational approach. The steps below are the foundation for preparing websites, applications and digital products to comply with the applicable regulations.
1. Digital accessibility audit
The first step towards an accessible website or application is assessing how well it currently conforms to the WCAG guidelines. The key is to find errors involving, among other things, color contrast, a wrong header structure, missing alternative text for graphics, and components that cannot be used with the keyboard alone.
Several free tools can help with an audit:
- Lighthouse (built into Google Chrome) – quickly spots basic accessibility problems on a single page,
- axe DevTools, Accessibility Insights, Accessibility Checker – browser extensions that run detailed WCAG conformance scans and give practical advice on fixing the errors found,
- WAVE – a tool that checks a page for contrast, alternative descriptions and semantic structure,
- WebAIM Contrast Checker – for checking, one by one, how readable text is against its background.
To show the audit tools in action, here are some screenshots from tests run on a demo application I built:
1. Lighthouse:
The Lighthouse audit points out typical problems:
Once the accessibility fixes are in place, the audit confirms full compliance and finds no remaining problems:
2. axe DevTools:
The first audit result lists accessibility problems - caused by missing discernible text, alt attributes or labels:
The repeated audit shows every problem fixed - accessibility best practices applied and confirmed by automated tools:
3. Accessibility Checker:
A score of 95 means strong accessibility results according to automated checks. Still, as the audit suggestions point out, full compliance and a perfect score require manual testing to find subtle problems that tools cannot detect on their own – such as keyboard focus, screen reader behavior or dynamic content updates.
The screenshots illustrate how these tools find problems (or confirm there are none) with contrast, header structure, form accessibility and semantic correctness.
These visual examples make it easier to see how the audit process works in practice and how much simple tools can help in designing accessible interfaces.
2. Manual audit
Automated tools make a good first step, but they miss some things. Manual tests that imitate how real users (particularly those who depend on assistive technologies) experience the site are needed to complete the audit.
Manual checks worth doing include:
- Using only the keyboard to navigate (Tab, Shift+Tab, Enter, Esc) to make sure every interactive element can be reached and follows a logical order,
- Using screen readers (e.g., NVDA, VoiceOver) to check that content is read out in the intended order, labels are properly linked, and error messages get announced,
- Testing in a text-based browser such as Lynx, which removes all visual styling and depends entirely on semantic structure and clear links. If your interface works in Lynx, that is a good sign its accessibility foundations are solid.
For more complex systems – particularly those with multi-step forms, dynamic interfaces or views built from many components – it pays to bring in accessibility specialists for a thorough audit, ideally one that involves real users with disabilities.
3. Finding and fixing the most important problems
Drawing up a list of non-conformities and setting priorities, focusing on the elements that affect usability the most. Improving contrast, adding readable form labels, making navigation possible without a mouse, and adjusting the interface to work with assistive technologies.
4. Adapting key digital functions
Addressing EAA requirements in particular areas of digital activity: making the ordering process accessible in shopping services, making transactions easier to reach in online banking, and adding subtitles and alternative content formats on video platforms.
5. Preparing technical documentation and declarations of conformity
Under the EAA requirements, organizations should prepare an EU Declaration of Conformity for every product or service the directive covers. The document should state clearly how accessibility has been handled – including which standards (e.g., WCAG 2.1 AA) were applied and which concrete solutions were put in place to address user needs.
This declaration is more than a formality. It should ideally be published, for instance next to the Privacy Policy or Terms of Use, so that users with disabilities can find it easily and know what level of accessibility to expect from the product or service.
6. Making accessibility part of team processes
Training the people who build digital products, including developers, designers, content editors and SEO specialists. Making sure accessibility principles are built into the design cycle and considered at every step of the work.
7. Long-term planning and monitoring
Setting up a schedule of regular accessibility audits and putting internal procedures in place keeps the website compliant as standards change. Accessibility should be seen as an ongoing process, particularly as the product grows and gains new features, which can accidentally create new barriers.
To keep accessibility high over time, it is worth building accessibility checks into the development workflow. Some basic accessibility rules (such as the presence of alt attributes or keyboard focusability) can be verified by automated unit or integration tests, which helps catch regressions early.
Conclusion
Digital accessibility is no longer something you can skip – it is a core part of high-quality digital services.
Now that the European Accessibility Act is in force, designing with inclusivity in mind is a social responsibility and a legal obligation at the same time.
By learning who gains from accessibility, what the WCAG standards demand and why it all matters, we take the first key step towards a better web that works for everyone.