Using WCAG to Improve Usability For Everyone​ — Register

EN 301 549 Compliance

  • EN 301 549 is the European accessibility standard for information and communication technology (ICT)
  • It applies across websites, software, documents, hardware, and digital services
  • It is used to meet accessibility requirements under the European Accessibility Act (EAA)
  • Compliance requires accessible, usable experiences and compatibility with assistive technologies across real-world use

On This Page

Accessible Kiosk RFPs: EAA & EN 301 549 Compliance

Learn how to write kiosk RFPs that meet European Accessibility Act and EN 301 549 standards to ensure compliant self-service solutions.

What is EN 301 549?

EN 301 549 is the European accessibility standard that defines how information and communication technology (ICT) must be designed and delivered to be accessible to people with disabilities. This EN 301 549 standard applies to a wide range of digital products and services, including websites, applications, software, documents, and hardware.

Developed to support accessibility expectations across the European Union, EN 301 549 provides a consistent framework for evaluating digital accessibility across both public and private sector services. It establishes how organizations should meet EN 301 549 accessibility requirements across the full digital ecosystem.

Meeting these requirements is the foundation of EN 301 549 compliance.

What is EN 301 549 compliance?

At a high level, EN 301 549 compliance means ensuring a product or service meets applicable accessibility requirements defined in the EN 301 549 standard across information and communication technology (ICT). In practice, this requires organizations to ensure that their websites, applications, software, documents, and digital systems are accessible, usable, and compatible with assistive technologies.

Unlike standards that focus only on web content, EN 301 549 accessibility requirements apply across the full range of ICT, including software, hardware, and documents. Compliance is demonstrated by meeting technical criteria and ensuring products and services can be used by users with disabilities in real-world scenarios.

EN 301 549 is a voluntary standard. However, because EN 301 549 is used to support regulatory frameworks such as the European Accessibility Act, achieving EN 301 549 compliance is an important step for organizations delivering digital products and services in the European Union. EN 301 549 has also been adopted as a standard in other countries, like Australia, Kenya, and Canada, and is emerging as a globally significant standard for ICT accessibility.

What does EN 301 549 cover?

To meet EN 301 549 compliance, organizations must ensure that the information and communication technology (ICT) they deliver is accessible across a wide range of digital and physical experiences. The EN 301 549 standard defines accessibility requirements across a wide range of ICT systems and digital experiences. EN 301 549 compliance applies across a wide range of technologies and digital experiences, requiring accessibility to be built into both the technologies organizations provide and the digital experiences delivered through them.

EN 301 549 and the European Accessibility Act (EAA)

To meet EN 301 549 compliance, organizations must ensure that the information and communication technology (ICT) they deliver is accessible to people with a range of disabilities. The EN 301 549 standard defines accessibility requirements for a wide range of digital technologies and products.

EN 301 549’s requirements include:

  • Functional performance criteria, high-level requirements for user needs of disability groups that underpin more detailed requirements for all ICTs.
  • General requirements for digital products
  • Specific requirements for:
    • Websites
    • Digital documents
    • Software
    • Hardware
    • ICT providing communication services, including emergency service access
    • ICT with video-playing capabilities
    • Instructions and product information

In practice, EN 301 549 compliance applies across a wide range of technologies and digital experiences, requiring accessibility to be built into both the hardware organizations provide and the digital experiences delivered through them.

EN 301 549 and WCAG

EN 301 549 and WCAG are closely related but serve different roles in digital accessibility. WCAG guidelines help organizations understand what’s needed to ensure web content is accessible to people with disabilities. EN 301 549 standard incorporates WCAG as part of a broader set of accessibility requirements for information and communication technology (ICT).

In practice, WCAG applies primarily to web applications and content, while EN 301 549 compliance extends those requirements across the full digital ecosystem, including software, documents, hardware, and communication technologies.

Learn more about how WCAG guidelines define accessibility on our WCAG topic page.

What are EN 301 549 accessibility requirements?

EN 301 549 accessibility requirements define the accessibility functionality and features that information and communication technology (ICT) must provide to be accessible to people with disabilities. In practice, EN 301 549 compliance is based on a combination of technical accessibility, real-world usability, and compatibility with assistive technologies.

Technical accessibility

For websites, software interfaces, and documents, EN 301 549 incorporates WCAG guidelines to define how digital content should be structured, presented, and interacted with. Version 3 of EN 301 549 references WCAG 2.1 Level AA, while Version 4 references WCAG 2.2 Level AA.

For specific ICTs, including hardware and closed functionality systems like kiosks, EN 301 549 provides additional requirements beyond WCAG.

Usability in real-world scenarios

Meeting technical requirements alone is not sufficient. Digital products and services must support users in navigating content, understanding information, and completing tasks independently across real-world conditions.

Assistive technology compatibility

ICT must work with assistive technologies such as screen readers, magnifiers, and alternative input methods. For systems with closed functionality, accessibility must be built directly into the experience.

Together, these elements define how organizations achieve EN 301 549 compliance in a consistent and meaningful way across a wide range of ICT systems and user experiences.

EN 301 549 open vs. closed functionality

The EN 301 549 accessibility standard distinguishes between open functionality and closed functionality to define how accessibility must be supported across different types of ICT.

Open functionality

Systems with open functionality allow users to install and use their own assistive technologies, such as screen readers or magnifiers. In these cases, EN 301 549 accessibility requirements focus on ensuring compatibility with those tools.

Closed functionality

Systems with closed functionality do not allow users to install assistive technologies. Instead, accessibility must be built directly into the system. This is common for public access devices such as kiosks, payment terminals, and other self-service technologies, where users rely on built-in accessibility features.

Understanding the difference between open and closed functionality is important for achieving EN 301 549 compliance, as it determines how accessibility must be implemented across different types of ICT.

How to achieve EN 301 549 compliance

Achieving EN 301 549 compliance requires a structured approach that ensures accessibility is built into information and communication technology (ICT) from the start and maintained over time.

Identify in-scope systems

Determine which websites, applications, software, documents, and devices fall under EN 301 549 accessibility requirements across your digital ecosystem.

Conduct an accessibility audit

Evaluate ICT against the EN 301 549 standard to identify gaps and establish a baseline for compliance.

Remediate accessibility issues

Prioritize and address barriers that prevent users from accessing content or completing key tasks across digital experiences.

Test and validate accessibility

Use a combination of automated tools and manual testing, including assistive technologies, to confirm alignment with EN 301 549 compliance requirements.

Maintain accessibility over time

Integrate accessibility into design, development, and content processes to sustain EN 301 549 compliance as systems evolve.

Each of these steps can be explored in more detail to support a scalable, long-term approach to accessibility.

EN 301 549 compliance checklist

Most organizations start with these core steps to meet EN 301 549 compliance requirements and establish a strong foundation for accessibility:

  • Identify scope
    Determine which websites, applications, software, documents, and devices fall under EN 301 549 accessibility requirements across your ICT environment.
  • Audit accessibility
    Evaluate systems against the EN 301 549 standard to identify gaps and establish a baseline for EN 301 549 compliance.
  • Fix accessibility issues
    Prioritize and remediate barriers that impact usability, focusing on issues that prevent users from accessing content or completing key tasks.
  • Test for accessibility
    Validate improvements using automated tools and manual testing, including assistive technologies, to ensure alignment with EN 301 549 compliance requirements.
  • Document conformance
    Maintain clear documentation of how systems meet EN 301 549 accessibility requirements, including evaluation methods and remediation efforts.
  • Monitor and maintain
    Establish ongoing processes for testing, tracking, and improving accessibility to sustain EN 301 549 compliance over time.

This EN 301 549 compliance checklist provides a starting point, but long-term success depends on integrating accessibility into how digital products and services are designed, developed, and maintained.

EN 301 549 compliance requires ongoing processes

EN 301 549 compliance is not a one-time effort. Organizations must establish processes to ensure accessibility is maintained as digital products and services evolve.

This includes maintaining documentation that demonstrates how systems meet EN 301 549 accessibility requirements, implementing ongoing monitoring to identify new issues, providing clear channels for users to report accessibility barriers, and tracking remediation efforts to ensure issues are resolved effectively.

Sustaining EN 301 549 compliance requires accessibility to be integrated into everyday workflows, from design and development to testing and maintenance.

Need help with EN 301 549 compliance?

Understanding your current level of EN 301 549 compliance is the first step toward delivering accessible, usable digital experiences across your ICT environment. An accessibility audit can help identify gaps across websites, applications, software, and documents, while a structured evaluation supports ongoing alignment with EN 301 549 accessibility requirements.

If you’re assessing your accessibility baseline or looking to strengthen how you meet the EN 301 549 standard, Vispero’s Digital Accessibility Services experts can help you maintain EN 301 549 compliance through expert audits, assistive technology-informed testing, and structured accessibility evaluation.

EN 301 549 FAQ

EN 301 549 is the European accessibility standard that defines how information and communication technology (ICT) must be designed and delivered to be accessible to people with disabilities. It applies to websites, applications, software, documents, and hardware.
EN 301 549 compliance means meeting the accessibility requirements defined in the standard across ICT. In practice, this includes ensuring digital products and services are accessible, usable, and compatible with assistive technologies in real-world scenarios.
EN 301 549 is the technical standard used to meet accessibility requirements under the European Accessibility Act (EAA). While the EAA defines the legal obligation, EN 301 549 provides the framework used to evaluate and implement accessibility.
EN 301 549 incorporates WCAG guidelines as part of its requirements. WCAG focuses on web accessibility, while EN 301 549 extends those principles across a broader range of ICT, including software, hardware, and documents.
The EN 301 549 standard covers a wide range of ICT, including websites, web applications, software, mobile apps, digital documents, hardware, self-service technologies, and communication services.
EN 301 549 itself is not a law, but it is used as a harmonized standard to meet legal accessibility requirements under the EAA and other EU regulations. Organizations subject to these laws are typically required to follow EN 301 549 to demonstrate compliance.
ICT stands for information and communication technology. In the context of EN 301 549, it refers to digital systems such as websites, software, hardware, telecommunications, and digital content that must meet accessibility requirements.
Open functionality refers to systems that allow users to install and use their own assistive technologies. Closed functionality refers to systems that do not allow this, requiring accessibility features to be built directly into the product, such as in kiosks or terminals.
Yes. Vispero helps organizations meet EN 301 549 requirements through accessibility audits, assistive technology–informed testing, remediation guidance, and ongoing support aligned with EAA and WCAG.