Accessibility Conformance Report

42min booking pages · Based on VPAT® Version 2.5Rev (WCAG edition) · October 15, 2026

VPAT® is a registered service mark of the Information Technology Industry Council (ITI). To keep a copy of this report, print the page or save it as a PDF from your browser.

Name of Product/Version

42min booking pages, the pages invitees use. Release b43a7c77, on 42min.us since October 15, 2026.

Report Date

October 15, 2026, the date of the evaluation.

Product Description

42min is an online meeting scheduling service. This report covers the pages a person uses to book, change and cancel a meeting with an organization that uses 42min: a host's and a team's landing pages, the booking page (calendar, times and details form), the confirmation page, routing forms, meeting polls (Roundtable), single-use booking links, and the cancel and reschedule pages. Event types that take payment are outside this report (see the notes).

Contact Information

Kikinda LLC (42min): plus@42min.us.

Notes

  • Scope. The invitee-facing pages listed above. The host and administration area is not covered by this report. A separate report for it is due by December 31, 2026 (see the roadmap in the accessibility statement).
  • Evaluated configuration. WCAG conformance is for complete pages. This report covers the pages in the configuration that was evaluated, in English and in Arabic: the shipped page themes with their default colors, the default settings, and the settings that change the invitee's page:
    • single and split name fields;
    • one question of each type;
    • guests and SMS opt-in;
    • recurring meetings and approval;
    • a fixed timezone;
    • a routing form without its header.
    Event types that take payment are not part of it.
  • Customer themes. An organization that edits a theme's HTML, CSS or colors makes its own page, and such pages are outside this report. The theme editor names every text color pair under 4.5:1 with its measured ratio.
  • Embedding. Customers can embed these pages in their own websites: inline, in a frame titled with the event or form name, or in 42min's popup. The popup is a modal dialog named by the link that opens it, with a close button; it keeps focus inside, returns it to the link, and closes on Escape from inside the page as well. The 42min pages and the popup are covered. The website around them belongs to its owner and is outside this report.
  • Paid event types. Event types that take payment are outside this report. Their payment step happens on the payment platform's hosted checkout page, which 42min does not control, and WCAG counts every page of a process toward the conformance of the whole.

Evaluation Methods Used

  • Automated: axe-core 4.10.3 on every page and state in scope, at desktop and phone widths, and on every shipped theme through the booking form, with checks of our own for landmarks, headings, accessible names, focus movement, Tab order, reflow at 320 CSS pixels, text spacing, non-text contrast and forced colors; and Lighthouse 13.5 accessibility audits of every page type, at desktop and phone widths.
  • Code review against each WCAG 2.1 success criterion.
  • Manual testing, on October 15, 2026: the keyboard alone (Microsoft Edge 154 on Windows 11); NVDA 2026.2 with Microsoft Edge 154 on Windows 11; VoiceOver with Safari on macOS and on iOS; the booking flow in Arabic with a screen reader; 200% and 400% zoom; a Windows contrast theme; the WCAG text spacing override; and the colors of the dark-theme and florida themes.

Applicable Standards/Guidelines

Standards and guidelines this report covers
Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0Level A (Yes), Level AA (Yes), Level AAA (No)
Web Content Accessibility Guidelines 2.1Level A (Yes), Level AA (Yes), Level AAA (No)
Web Content Accessibility Guidelines 2.2Not claimed in this report

Terms

  • Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: some functionality of the product does not meet the criterion.
  • Does Not Support: the majority of product functionality does not meet the criterion.
  • Not Applicable: the criterion is not relevant to the product.
  • Not Evaluated: the product has not been evaluated against the criterion. Used only for Level AAA.

WCAG 2.x Report

Table 1: Success Criteria, Level A
CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text ContentSupportsLogos carry the organization's name and photos the person's name. Initials are named by the person. Decorative emoji and arrows are hidden from assistive technology. The month arrows are named "Previous month" and "Next month".
1.2.1 Audio-only and Video-only (Prerecorded)Not ApplicableNo audio or video content.
1.2.2 Captions (Prerecorded)Not ApplicableNo audio or video content.
1.2.3 Audio Description or Media Alternative (Prerecorded)Not ApplicableNo audio or video content.
1.3.1 Info and RelationshipsSupportsEvery page has a main landmark and headings that follow the visual structure: the page title at level one, steps and dates below it. Form fields have programmatic labels. Radio and checkbox questions are grouped under a legend, required groups are marked, and errors are tied to their fields. The timezone list groups zones by region.
1.3.2 Meaningful SequenceSupportsReading order follows the visual order, on right-to-left pages too.
1.3.3 Sensory CharacteristicsSupportsInstructions do not rely on shape, size, position or sound.
1.4.1 Use of ColorSupportsLinks in text are underlined. The chosen day and time are also exposed as pressed and, on light accents, ringed. Errors are stated in text.
1.4.2 Audio ControlNot ApplicableNo audio.
2.1.1 KeyboardSupportsEvery control is a native button, link or form field. The phone country list and the timezone list work with the arrow keys, Enter and Escape.
2.1.2 No Keyboard TrapSupportsLists and popups close on Escape and when focus leaves them. At phone width the timezone list is a modal dialog: focus stays inside it until it closes, on Escape or with its close button.
2.1.4 Character Key ShortcutsNot ApplicableNo single-character shortcuts.
2.2.1 Timing AdjustableSupportsNo page in the evaluated configuration sets a time limit on what the visitor is doing. The 42-minute payment hold applies only to event types that take payment, which are outside this report.
2.2.2 Pause, Stop, HideSupportsNo moving or automatically updating content. Loading indicators stop when loading ends.
2.3.1 Three Flashes or Below ThresholdSupportsNo flashing content.
2.4.1 Bypass BlocksSupportsNo blocks repeat across pages. Every page has a main landmark and headings.
2.4.2 Page TitledSupportsEach page's title names its purpose and the meeting or person it concerns, in the page's language; a page that does not exist says so, in the visitor's language.
2.4.3 Focus OrderSupportsTab order follows the visual order. When a step replaces the page in place, focus moves to where the new step starts: the form's heading after a time is chosen, the chosen day after Back, the heading of a canceled meeting, and the notice when a time was taken meanwhile.
2.4.4 Link Purpose (In Context)SupportsLink text names its destination. A landing page's event rows are single links with no links inside them.
2.5.1 Pointer GesturesSupportsNo multipoint or path-based gestures.
2.5.2 Pointer CancellationSupportsActions run on click, when the pointer is released.
2.5.3 Label in NameSupportsAccessible names contain the text the control shows, in the same order, for example "Timezone: Eastern Time 2:15 PM", "10:00 AM, 2 votes" and "Country code: United States +1".
2.5.4 Motion ActuationNot ApplicableNo motion input.
3.1.1 Language of PageSupportsThe page language follows the content language, on the 404 page too. Ukrainian is declared as uk.
3.2.1 On FocusSupportsFocus never changes the context by itself.
3.2.2 On InputSupportsChoosing a value does not change the context unexpectedly. Steps advance on an explicit choice.
3.3.1 Error IdentificationSupportsErrors are described in text next to their field and announced, and the first invalid field takes focus.
3.3.2 Labels or InstructionsSupportsEvery field has a visible label. Required fields and required groups say so.
4.1.1 ParsingSupportsAlways supported for WCAG 2.0 and 2.1, per ITI's instructions: the criterion is obsolete in WCAG 2.2.
4.1.2 Name, Role, ValueSupportsCustom controls expose their names, roles and states: the day and time buttons (pressed, current date), the timezone button and its dialog with a search field and a list grouped by region, the phone country list, and poll votes.
Table 2: Success Criteria, Level AA
CriteriaConformance LevelRemarks and Explanations
1.2.4 Captions (Live)Not ApplicableNo live audio or video.
1.2.5 Audio Description (Prerecorded)Not ApplicableNo video.
1.3.4 OrientationSupportsPages work in both orientations.
1.3.5 Identify Input PurposeSupportsName, email and phone fields declare their autocomplete purpose, on routing forms too.
1.4.3 Contrast (Minimum)SupportsText clears 4.5:1 on every surface of the shipped themes, measured in the browser for every state of the booking flow, including errors, links, the chosen time and the "Powered by 42min" line. Customized themes are outside the evaluated configuration.
1.4.4 Resize TextSupportsPages work at 200% zoom without loss of content or function.
1.4.5 Images of TextSupportsNo images of text except logos.
1.4.10 ReflowSupportsNo horizontal scrolling of the page and no text cut off at 320 CSS pixels.
1.4.11 Non-text ContrastSupportsField borders, the chosen day and time, focus indicators and the keyboard cursor in lists clear 3:1, and stay visible in Windows contrast themes.
1.4.12 Text SpacingSupportsNo content is cut off with the WCAG text spacing override applied.
1.4.13 Content on Hover or FocusSupportsNo content appears on hover or focus.
2.4.5 Multiple WaysNot ApplicableThe pages are steps in a process.
2.4.6 Headings and LabelsSupportsHeadings and labels describe their topic or purpose.
2.4.7 Focus VisibleSupportsEvery focusable element shows focus, text fields in Windows contrast themes included.
3.1.2 Language of PartsSupportsThe page language is the event type's language, and 42min's own text is in that language. Text a host writes in another language is the host's content.
3.2.3 Consistent NavigationSupportsNo repeated navigation. The footer is the same on every page.
3.2.4 Consistent IdentificationSupportsControls with the same function have the same name on every page.
3.3.3 Error SuggestionSupportsErrors say what to enter, and a likely typo in an email address is offered as a correction.
3.3.4 Error Prevention (Legal, Financial, Data)SupportsNo legal commitment or financial transaction happens in the evaluated configuration. A booking is made only when the invitee submits the details form, with the chosen time in view, and it can be canceled from the confirmation page and email. Canceling and rescheduling happen on their own pages: the meeting is shown, and nothing changes until the invitee presses Cancel Meeting or Confirm Reschedule.
4.1.3 Status MessagesSupportsLoading, saving, the chosen time, availability problems and results are announced through status regions, and errors through alerts.

Table 3: Success Criteria, Level AAA

Not evaluated: this report does not claim Level AAA.

Legal Disclaimer (Company)

This report describes the accessibility of the 42min booking pages on the report date, in the configuration described above, as evaluated by Kikinda LLC. It is provided for information. We update it when a release changes these pages.