Accessibility Act and WCAG 2.2: How to Make Your Website and Online Store Accessible
Digital accessibility has become a key focus area for businesses, organizations, and public institutions. With the EU Accessibility Act (EAA), which came into effect on June 28, 2025, there is increased emphasis on ensuring that digital products and services can be used by everyone—including people with disabilities or impairments.
For many businesses, this means that websites, online stores, apps, and digital self-service solutions must be reviewed and improved. At the same time, more and more organizations are choosing to work in accordance with WCAG 2.2, the latest version of the international web accessibility guidelines.
What Is the Accessibility Act?
The Accessibility Act is Denmark’s implementation of the EU’s European Accessibility Act (EAA). Its purpose is to ensure that a range of digital products and services can be used by people with various types of disabilities and impairments.
The legislation covers, among others, many private companies that provide digital services to consumers. This includes:
- Online stores and e-commerce solutions
- Online booking and reservation systems
- Ticketing systems for culture, attractions, and transportation
- Banking and payment services
- Digital self-service solutions
- Mobile apps and digital platforms
For businesses in the experience and attractions industry, the requirements can be particularly relevant because ticket purchases, bookings, and event information are often handled digitally. If a user cannot complete a ticket purchase using a keyboard, screen reader, or assistive technology, this may constitute a significant accessibility barrier.
Learn more about the EU’s accessibility regulations on the European Commission website
What Is WCAG 2.2?
WCAG stands for Web Content Accessibility Guidelines and is published by the World Wide Web Consortium (W3C). The guidelines describe how digital solutions can be made accessible to the widest possible range of users.
WCAG 2.2 was published in October 2023 and builds on WCAG 2.1. Version 2.2 introduces new requirements focusing on users with cognitive disabilities, people with low vision, and mobile device users.
Although the harmonized European standard still primarily references WCAG 2.1 through EN 301 549, many organizations are already adopting WCAG 2.2 to future-proof their solutions and achieve a higher level of accessibility.
Learn more about WCAG 2.2 on W3C
The Four Core Principles of WCAG
All WCAG requirements are based on four fundamental principles. If a website does not comply with these principles, many users will encounter accessibility barriers.
1. Perceivable
Content must be presented in ways that users can perceive, regardless of how they access the site.
- Images must have alternative text
- Videos should include captions
- Color must not be the only means of conveying information
- Text must have sufficient contrast
2. Operable
All functionality must be usable by different types of users.
- Navigation must work with a keyboard
- Links and buttons must be easy to activate
- Users must not become trapped within page elements
- Focus indicators must be clearly visible
3. Understandable
Users must be able to understand both the content and the functionality.
- Forms must have clear field labels
- Error messages must be easy to understand
- Navigation must be consistent
- Language must be clear and logical
4. Robust
Content must function across browsers, screen readers, and other assistive technologies.
- Correct HTML structure
- Semantic headings
- Accessible form fields
- Compatibility with assistive technologies
Is WCAG 2.2 a Legal Requirement?
The short answer is: not directly.
Many organizations are currently working toward WCAG 2.2 compliance, but it is important to understand the relationship between the Accessibility Act and WCAG standards.
The European Accessibility Act (EAA) requires digital products and services to be accessible to people with disabilities and impairments. However, the legislation does not directly reference WCAG 2.2.
The harmonized European standard EN 301 549, which serves as the technical reference for digital accessibility in the EU, is still primarily based on WCAG 2.1 Level AA. As a result, WCAG 2.1 AA is often referred to as the formal basis for compliance.
That does not mean organizations should stop at WCAG 2.1. WCAG 2.2 builds upon the existing requirements and introduces several improvements that make digital solutions more user-friendly and accessible—particularly for people with cognitive disabilities, low vision, or limited motor skills.
For most organizations, WCAG 2.2 is therefore the natural target standard. It not only provides a higher level of accessibility but also helps future-proof websites, online stores, ticketing systems, and digital services as standards and regulatory requirements continue to evolve.
If you would like a more detailed overview of the legislation itself, who is affected, and which products and services the regulations apply to, you can read our guide to the EU’s new Accessibility Act.
In Summary
- The Accessibility Act is the legal requirement.
- EN 301 549 is the European standard used as the technical reference.
- EN 301 549 is currently based primarily on WCAG 2.1 AA.
- WCAG 2.2 is the latest recommended standard and the best way to future-proof your solution.
WCAG 2.2 Made Simple: What Should You Focus On?
The official guidelines contain many details, but for most organizations there are a handful of areas that deliver the greatest impact.
Alternative Text for Images
All meaningful images should have descriptive alt text. A screen reader must be able to communicate the image’s purpose or message to the user.
Keyboard Navigation
The entire website must be usable without a mouse. Users should be able to navigate menus, links, form fields, and buttons using only a keyboard.
Clear Heading Structure
Headings should be structured correctly using H1, H2, H3, and so on. This makes content easier to understand for both screen reader users and other visitors.
Sufficient Color Contrast
Text must be easy to read. Light gray text on a white background often creates accessibility issues for users with low vision.
Clear Forms
All fields should have labels, and errors should be explained in a way that helps users complete the process.
Visible Focus Indicators
When users navigate with a keyboard, it must be clear which element is currently selected.
The Most Important New Areas in WCAG 2.2
WCAG 2.2 introduces several new success criteria that particularly improve the user experience for people with cognitive disabilities and motor impairments.
Larger Click Targets
Buttons, links, and interactive elements must be easier to activate on both mobile devices and tablets.
Improved Focus Visibility
Users navigating with a keyboard should be able to more easily identify where focus is located on the page.
Reduced Repetition of Information
If users have already provided information earlier in a process, the system should avoid requiring the same information again.
Accessible Login Solutions
Login processes must not rely on complex memory tasks, puzzles, or visual challenges that create unnecessary barriers.
Accessibility in E-Commerce
Online stores are among the areas that most frequently face accessibility challenges. Problems often occur in product displays, filtering systems, shopping carts, and checkout processes.
An accessible online store should ensure, among other things:
- Product images have relevant descriptions
- Filters can be operated with a keyboard
- The cart and checkout work with screen readers
- Payment errors are explained clearly
- All actions can be completed without a mouse
The more complex the purchasing process, the more important accessibility becomes.
Accessibility in Ticketing Systems and the Experience Industry
Museums, attractions, concert venues, festivals, theaters, and experience centers are increasingly dependent on digital ticketing systems.
Many of the same accessibility challenges found in e-commerce occur here as well, often with additional complexity involving seat selection, dates, time slots, and interactive maps.
For ticketing systems, it is particularly important that:
- Calendars can be used with a keyboard
- Seat selection has accessible alternatives
- Prices and ticket types are communicated clearly
- The entire booking flow works with screen readers
- Users can complete purchases without time-related barriers
If a user cannot purchase a ticket digitally because of inaccessible design, the organization may risk both lost revenue and non-compliance with legal requirements.
How to Get Started with Compliance
- Conduct an accessibility audit of your website or online store.
- Test the site using only a keyboard.
- Review contrast ratios and readability.
- Evaluate forms and checkout flows.
- Test with screen readers.
- Prioritize issues that have the greatest user impact.
- Integrate accessibility into future development projects.
Accessibility Is About More Than Compliance
Although legislation has increased focus on accessibility, digital accessibility is ultimately about creating solutions that can be used by as many people as possible.
Good accessibility often improves the overall user experience, reduces friction in purchasing and booking processes, and makes digital solutions more robust across devices and technologies.
For organizations with websites, online stores, ticketing systems, or digital services, WCAG 2.2 is therefore not just a matter of compliance. It is also an investment in better user experiences, broader reach, and more inclusive digital solutions.
Questions and Answers About the Accessibility Act and WCAG 2.2
What is the difference between the Accessibility Act and WCAG 2.2?
The Accessibility Act is the legislation, while WCAG 2.2 is a set of technical guidelines that help organizations create accessible digital solutions.
Does the Accessibility Act apply to online stores?
Yes. Many online stores and consumer-facing e-commerce solutions are covered by the regulations and must ensure that the purchasing process is accessible.
Is WCAG 2.2 a legal requirement?
WCAG 2.2 is the latest version of the guidelines. Many organizations use it as best practice, while the current harmonized EU standards continue to be based on WCAG 2.1 through EN 301 549.
How do you test a website’s accessibility?
Accessibility is typically tested using automated tools, manual reviews, keyboard navigation testing, and screen reader testing.
Why is keyboard navigation important?
Many users cannot use a mouse and rely on keyboards or assistive technologies. Therefore, all key functions must be accessible without a mouse.
What does WCAG Level AA mean?
AA is the level most commonly referenced in legislation and standards. It includes both fundamental and enhanced requirements for digital accessibility.
Should my website comply with WCAG 2.1 or WCAG 2.2?
WCAG 2.1 AA remains the primary basis of the harmonized European standard EN 301 549. However, many organizations choose to work toward WCAG 2.2 because it builds on WCAG 2.1 and introduces new requirements that improve accessibility for a wider range of users.
Why is WCAG 2.2 recommended if it is not a direct legal requirement?
WCAG 2.2 is the latest version of the international web accessibility guidelines. By following WCAG 2.2, organizations achieve a higher level of accessibility and future-proof their digital solutions as standards and expectations continue to evolve.
