In this article, we explain what WCAG is, the current compliance status of Momice, and what you as an organizer must do to keep your event website accessible (WCAG 2.1 AA compliant).
What is WCAG?
The Web Content Accessibility Guidelines (WCAG) are international guidelines used to assess whether a website or application is usable for people with disabilities.
This includes visitors who:
Are visually impaired or blind (and use a screen reader)
Are color blind
Have motor impairments
Are sensitive to moving elements
Have difficulty reading or concentrating
The WCAG guidelines are technically neutral. This means they are not dependent on a specific solution or technology, but are broadly applicable to event websites.
The current standard many organizations must comply with is WCAG 2.1 Level AA.
Does Momice comply with WCAG 2.1 AA?
Yes, Momice complies with WCAG 2.1 AA.
How was this tested?
In collaboration with Cardan (a partner in digital accessibility), an extensive accessibility audit was conducted on the Momice event website.
Identified issues and improvements were documented and implemented.
An annual accessibility test is conducted to maintain compliance.
Important: who is responsible for what?
At Momice, we ensure that:
The software technically and functionally complies with WCAG 2.1 AA.
All system elements (such as registration forms, validations, navigation, and structure) are properly configured.
Everything within our control is tested.
Please note: as an organizer, you have a lot of freedom regarding:
Colors
Images
Content
Text styling
Templates
Due to this flexibility, it is possible that an event website may no longer comply with WCAG guidelines. Therefore:
Momice is responsible for the technical foundation.
The organizer is responsible for the content and chosen settings.
We are happy to help you set up your event template in a WCAG-compliant way. Please contact your Momice account manager or email [email protected].
What should you check as an organizer?
Below are the most important points to review.
Color usage & contrast
Proper contrast ratios are mandatory. Please check the following:
The border color of input fields must have a minimum contrast ratio of 3.0:1 against the background.
Button color versus button text must have a minimum contrast ratio of 4.5:1.
Field borders must have sufficient contrast with the background color.
Tip: we recommend using a white background.
Some system elements (such as validation messages and error notifications) cannot be customized. These are designed based on a white background.
You can test contrast using the WebAIM Contrast Checker tool.
Please note: It is technically not possible to automatically enforce contrast compliance. Always test this manually.
Headings
Do not create a heading without content underneath it.
A heading must always introduce the content that follows.
Use heading levels logically (avoid skipping levels randomly).
Momice’s default structure is WCAG approved. We do not offer full structural freedom, as this could result in non-accessible websites.
Using text colors in the WYSIWYG editor
Do not apply custom text colors via the editor.
Why?
This may negatively impact contrast.
The color settings within your website template are safer and WCAG-validated.
Images & alternative text (alt text)
The following is mandatory:
Every photo on the photo page must have a title (this is used as alternative text).
The logo in the top bar must have alternative text.
This text must describe which company or organization the logo belongs to.
Example: “Logo of Company X”.
Alt text is crucial. Screen readers often read this as one of the first elements on the page.
Images in the image widget
Currently, it is not yet possible to add alt text to images in the image widget.
We assume these images are decorative. It is not permitted to place important information (such as the event title or date) only within an image.
Attachments
Every attachment must include a description. Without a description:
An H2 heading without content is generated.
This is not allowed under WCAG guidelines.
Contacts, speakers, and locations
The name of a speaker, contact, or location is displayed as a heading. Therefore, at least one additional field (such as title, company, or description) must be completed so that content appears underneath the heading.
Guest list
In addition to first and last name, at least one extra field must be configured.
Again, a heading without content is not permitted.
Language usage
Do not use a different language than the configured event language. Mixing languages without technically marking this correctly is not allowed under WCAG.
Special WCAG techniques in Momice
Momice includes several built-in accessibility features.
“Skip to content” shortcut
When navigating using a keyboard (Tab key), a hidden button appears:
“Skip to content”. This allows users to bypass navigation and jump directly to the main content.
Countdown timer with pause button
Moving or time-sensitive elements can be problematic for some users. The countdown timer includes a pause button so visitors can stop it.
Automatic sitemap
Every event website automatically includes a sitemap. Why?
WCAG requires at least two routes to the same content.
For example, the program page must be accessible via multiple paths.The sitemap provides a clear secondary navigation route.
Time limit in the registration system
When registering, a ticket is temporarily reserved:
10 minutes for paid tickets
30 minutes for free tickets
Normally, time limits must be extendable under WCAG guidelines. However, ticketing systems are an exception, as unlimited extensions would not be workable. Therefore, this time limit is permitted.
Frequently Asked Questions
Can I place important information (such as title + date) inside an image?
No. This is not good practice. Important information must always be available as text.
My input fields do not have sufficient contrast
This is determined by the border color compared to the background. For example, a border color such as #555555 on a light background usually meets contrast requirements.
My logo does not have alt text
This is mandatory. The alt text must describe which company or organization the logo represents.