Skip to main content

Web Accessibility

Digital accessibility aims to ensure that all users, including those with disabilities, can access a website's or application's content and features without barriers.

Updated over a week ago

At Eventmaker, we have initiated a thorough effort to make our sites and platforms more accessible, while enabling you to configure your events in compliance with international standards.


What is web accessibility?

It means enabling all audiences to access digital content, notably people affected by:

  • Hearing impairments: hard of hearing, deaf, deaf-blind.

  • Visual impairments: partially sighted, blind, color-blind...

  • Motor impairments: difficulties using a mouse or keyboard.

  • Cognitive impairments: reading, memory, attention difficulties...

The fundamental principles of accessibility are summarized in the WCAG (Web Content Accessibility Guidelines) around four pillars:

  • Perceivable: content must be visible or audible.

  • Operable: accessible via keyboard, coherent navigation.

  • Understandable: clear content, predictable behavior.

  • Robust: compatible with assistive technologies.

To make your website accessible to all users, the World Wide Web Consortium (W3C) has issued a set of recommendations called the WCAG. The criteria set by the web standards body are considered the global standard for designing accessible websites and web materials. The latest WCAG publication is version 2.1. The WCAG 2.1 criteria are organized around the following 13 topics:

  • Images

  • Frames

  • Tables

  • Colors

  • Links

  • Consultation

  • Multimedia

  • Scripts

  • Mandatory elements

  • Presentation

  • Navigation

  • Forms

  • Information structuring

They are divided into three main categories: development, editorial, and design. Thus, website accessibility depends not only on Eventmaker developments but also on the content/visual design that you customize from our platform.

Here are some best practices to adopt on your sites

⚡ Many accessibility errors are related to customization rather than our code! Here's how to avoid them:

Images & Multimédia

  • Add a descriptive alternative text ("alt")

  • Provide synchronized subtitles for videos

  • Add an audio description for videos without voice

Links & Navigation

  • All links must be explicit (no "Click here")

  • Organize pages with logical headings (h1, h2, h3...)

  • Ensure a consistent tab order

Colors & Contrast

  • Text/background contrast ≥ 4.5:1 minimum (or 3:1 for large text)

  • Do not convey information by color alone

  • Add an underline or hover effect to links

Forms

  • Associate each field with a clear label

  • Use help text to explain fields

Understanding

  • Avoid unexplained jargon

  • Define acronyms the first time they appear

  • Provide a glossary if needed

Legal reminder:


Since 28 June 2025, the European Accessibility Act (EAA) requires companies with more than 10 employees or €2M in turnover to make their websites accessible. In France, this is in addition to the RGAA, which also requires an accessibility statement and a visible legal notice.


Accordingly, our code is largely compliant, but regarding final accessibility, it largely depends on the visual and textual settings chosen by your teams.

And Eventmaker in all this?

On the Eventmaker platform and website

  • Our tech teams carry out an accessibility audit of our templates.

  • Most of the effort on your side focuses on:

    • Choosing contrasts (background, text, button colors)

    • Font sizes

    • Alternative text for images

    • Including legal notices in the footer (accessibility statement)

⚠️ Important

Les "plugins" d'accessibilité (overlays) ne suffisent pas à se conformer à la loi. Seule une vraie accessibilité native est reconnue.

Conclusion

Making a website accessible is not optional; it's a right. It's important for your events: more visitors, better understanding, increased inclusivity. With Eventmaker, you have the tools to comply with obligations while improving the user experience for everyone.

Did this answer your question?