Accessibility Statement

People book meetings with organizations that use 42min on pages those organizations share with them. We want everyone to be able to use those pages, whatever device or assistive technology they use. This statement says how far that holds today and where to tell us when it does not.

1. Conformance Status

The pages people use to book, reschedule and cancel a meeting conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, for event types without payment, in the configuration described in section 2, as evaluated on October 15, 2026.

Our conformance report, based on the VPAT® 2.5Rev template (WCAG edition), gives the rating and the reasoning for each criterion: Accessibility Conformance Report.

2. What This Statement Covers

• The pages a person uses to book, change and cancel a meeting on an event type without payment: a host's and a team's landing pages, the booking page, the confirmation page, routing forms, meeting polls, single-use booking links, and the cancel and reschedule pages.
• The page themes 42min ships, with their default colors. They were evaluated in English and in Arabic, which reads right to left.
• The popup that opens these pages from a link on another website (42min's popup embed): its dialog, its close button and its keyboard behavior.

3. Known Limitations

• Customized themes. An organization can edit its booking page theme. A page with edited colors or markup is that organization's own design and is outside this statement. When an edit makes text hard to read, the theme editor shows the measured contrast.
• Websites that embed 42min. An organization can embed these pages in its own website, in the page itself or in 42min's popup. The 42min pages and the popup are covered. The website around them belongs to that organization and is outside this statement.
• Event types that take payment. They are outside this statement. Their payment step happens on the payment platform's checkout page, which the platform runs and 42min does not control.
• The host and administration area. The pages hosts and administrators use to run 42min are not covered yet. Section 6 gives the date of their report.

4. How We Test

Before a release that changes these pages, we check them in Chromium with axe-core and with checks of our own for focus, page titles, layout at 320 CSS pixels, text spacing and contrast, on every shipped theme, at desktop and phone widths.

On October 15, 2026, a person also checked the pages by hand:

• with the keyboard alone;
• with NVDA and Microsoft Edge on Windows, and with VoiceOver and Safari on macOS and iOS, in English and in Arabic;
• at 200% and 400% zoom, and with the WCAG text spacing settings;
• in a Windows contrast theme.

5. Feedback

If something on a 42min page gets in your way, email plus@42min.us. Tell us the page address and what happened. We answer within 2 business days.

6. Roadmap