Wordpress Blog

Tag: Culture

  • EN 301 549: What It Is and How to Comply with the European Digital Accessibility Standard

    EN 301 549: What It Is and How to Comply with the European Digital Accessibility Standard

    Find out what EN 301 549 requires, how it relates to WCAG and the European Accessibility Act, and what steps you need to take to ensure compliance before June 2025.

    EN 301 549: The European Accessibility Standard 🌍♿

    The EN 301 549 standard sets accessibility requirements for information and communication technology (ICT) products and services — including hardware, software, documents, and mobile applications — used in Europe. Originally designed for public procurement, it is now part of the European Accessibility Act (EAA). ✅📱💻

    To comply, EU Member States must:

    • 📄 Handle and respond to accessibility-related requests concerning websites and mobile apps, in accordance with applicable national regulations.
    • 🎓 Offer targeted training programs on digital accessibility and legal obligations.
    • 📢 Actively promote awareness and commitment to accessibility at all levels of the organization.
    • 💡 Share and apply best practices to ensure websites and mobile apps are genuinely accessible.
    • 🛠️ Ensure there is an effective enforcement procedure for accessibility obligations.

    What Does EN 301 549 Cover? 🔍

    Aligned with the WCAG, this standard goes beyond web content: it also includes requirements for hardware, applications, documents, and telecommunications. As a harmonized European standard, compliance is presumed to meet legal obligations.

    Key Details of Version v3.2.1 (Harmonized in February 2022) 📅

    • 📝 Public sector must publish an accessibility statement indicating the current level of accessibility, non-accessible elements, and complaint procedures.
    • 🚫 Some content is excluded (e.g., videos published before 2020, or intranets created before 2019. Refer to the standard for more information.).
    • 🧭 There must be an explanation of inaccessible elements, and information on available alternatives.

    Expected Changes in Version v4.1.1 (March–May 2025) 🔄

    • 🆕 Adoption of WCAG 2.2, with additional criteria to support users with cognitive disabilities.
    • 🗣️ Inclusion of real-time text (RTT) in communications — helpful for people with hearing or speech disabilities.
    • 🤝 Full alignment with the EAA, effective June 2025, making legal compliance easier.

    Is Complying with EN 301 549 the Same as Following WCAG 2.2? 🤔

    Largely, yes ✅ — but there are some differences.

    For instance, EN 301 549 addresses the use of biometric data. If an organization uses biometric systems, it must follow specific rules to comply with this standard.

    Why Is EN 301 549 Important for European Organizations and Businesses? 🇪🇺🏢

    1. ⚖️ Legal compliance: As of June 2025, it is mandatory in the EU for public organizations — non-compliance may lead to penalties.
    2. 🌍 Access to new markets: An estimated 135 million people with disabilities in Europe represent a significant market opportunity.
    3. 🌟 Social responsibility and reputation: Demonstrates a commitment to inclusion and enhances corporate image.

    How to Prepare Before June 2025? 🧭📆

    • 🔍 Conduct comprehensive audits that include WCAG 2.2 and specific EN 301 549 requirements.
    • ⚙️ Update technical platforms, including PDFs, user interfaces, and telecommunications systems.
    • 👥 Train internal teams — designers, developers, content creators — on new criteria like RTT and WCAG 2.2.
    • 📊 Ongoing monitoring, as standards will continue to evolve.

    Conclusion ✅

    EN 301 549 is a cornerstone of digital accessibility in Europe. With version v4.1.1, organizations must adapt to new requirements (such as WCAG 2.2) and prepare for mandatory EAA compliance by June 2025. 🗓️♿

    At Inclusif, we help you meet EN 301 549 through technical audits, custom consulting, team training, and continuous support.

    If you need help adapting your website, app, or digital documentation, visit inclusif.life and discover how we can support your journey toward real, sustainable accessibility.

  • Why accessibility widgets are no longer enough in the Digital Kit

    Why accessibility widgets are no longer enough in the Digital Kit

    Accessibility widgets promise quick solutions, but do they really comply with WCAG and current laws?

    The problem with “magic solutions” ⚠️

    Many organizations implement accessibility widgets, hoping to quickly comply with legal regulations or improve the experience for their users with disabilities. These widgets typically promise “automatic” accessibility by simply copying and pasting code into the website. But the reality is different.

    While these tools can offer useful functions—such as contrast enhancement, font size changes, or text-to-speech—they don’t correct errors in the source code nor guarantee real compliance with WCAG 2.2. Moreover, they don’t replace an audit or structural adaptation of the site.

    During the first years of the Digital Kit, web accessibility was evaluated quite leniently. It was enough to present an Excel sheet that digital agents filled out with generic statements about WCAG guideline compliance.

    However, this has changed. And it’s an important change.

    Technical limitations of widgets 🛠️

    • They don’t detect or correct semantic errors (such as incorrect use of HTML tags).
    • They don’t improve keyboard navigation or guarantee logical heading structures.
    • They don’t resolve barriers in forms, sliders, menus, or video players.

    Legal and reputational risks ⚖️💥

    In the European context, and particularly in Spain, laws such as Royal Decree 1112/2018 require that websites of public administrations and certain private sectors comply with WCAG 2.2 level AA. Relying solely on widgets is not a legally valid solution and can expose you to sanctions or claims.

    Additionally, some entities that use only widgets have been reported for poor accessibility, which negatively affects their reputation and credibility.

    The real alternative: audit, improvement and commitment 💡✅

    For a site to be truly accessible:

    • 🔎 A complete technical evaluation is needed (ideally combining automatic tools like Inclusif’s analyzer and manual review).
    • 🛠️ Changes must be applied to the code and design that benefit all users.
    • 📜 A transparent accessibility statement must be published.
    • 👥 It’s advisable to train the team so they can maintain that level of accessibility over time.

    How Inclusif helps you 🚀🌍

    At Inclusif, we combine automatic analysis with manual audits supported by experts.

    We offer you a clear roadmap, without needing to depend on third parties: you can implement the changes yourself or count on our consulting service.

    📄 We also help you generate your accessibility statement and justify possible cases of disproportionate burden if necessary.

    ✨ The goal is not to cover up, but to transform your website into a truly accessible space.

    Conclusion 🧠

    Widgets can be a complement, but they should never be the only measure. Real accessibility requires commitment, technical verification, and concrete action.

    The next step? Make your site truly accessible. You won’t just comply with the law: you’ll also improve the experience for all your users.

    If you want to try our accessibility scanner to check some of the points where your page’s accessibility is lacking, you can try it for free here.

    Our goal is clear: to make the greatest number of websites truly accessible. Because an accessible website doesn’t just avoid sanctions or remediation: it improves the experience for all users.