Triptease Messages render as web components inside an iframe on your website, and they are built to meet WCAG 2.2 (Web Content Accessibility Guidelines) at conformance Level AA. WCAG 2.2 AA is the technical standard most accessibility regulations reference, including the European Accessibility Act. Triptease maintains a VPAT (Voluntary Product Accessibility Template) that documents, criterion by criterion, how the guest-facing message components conform.

This article describes the platform's built-in conformance. How accessible any individual message is also depends on the content you configure — see the related article on designing accessible messages.

The guest-facing parts of every Triptease Message — buttons, links, forms, expandable panels, dismissible modals, countdown timers, and price comparisons — are built so that assistive technology and keyboard users can operate them.

Keyboard operability is built in. Every interactive element uses a native HTML control (button, link, input, select, or checkbox), so it works with the keyboard by default and shows the browser's standard focus outline. That focus outline is protected in two ways: the styling system does not allow injected styles to remove focus outlines, and the components are isolated from your site's own CSS, so a style reset on your page cannot strip focus indicators from inside a message.

Focus is managed automatically for modal-style messages. When a dismissible (modal) message opens, focus is trapped inside it: pressing Tab and Shift+Tab cycles through the message's controls and does not escape to the page behind it. When the guest dismisses the message using the close button, focus is automatically returned to the element that triggered it. This focus handling is automatic — you do not need to configure it. Collapsible and inline (non-modal) messages do not trap focus, which is the expected behaviour for non-modal content.

Screen reader support is built into the components. Icon-only buttons carry accessible labels, form fields are programmatically tied to their labels, validation errors are announced when they appear, and the countdown timer exposes a readable time summary. The message's language is set on the document so screen readers pronounce content correctly, and the iframe carries a translated title in 25 languages.

Colour and contrast meet the standard for system-controlled elements. System text and icons meet or exceed the WCAG 2.2 AA contrast ratios. Contrast within your message also depends on the colours you choose, so testing your own combinations is still recommended.

Q: Is the Triptease Messages widget WCAG 2.2 AA compliant?

A: Yes. The guest-facing Triptease Messages components conform to WCAG 2.2 at Level AA, and Triptease maintains a VPAT documenting conformance against each success criterion. The accessibility of a specific message also depends on the content and colours you configure.

Q: Does keyboard focus stay trapped within the modal until it is closed?

A: Yes, for dismissible (modal) messages. While a dismissible message is open, Tab and Shift+Tab cycle through its controls and focus cannot move to the page behind it. When the message is closed, focus is automatically returned to the element that opened it. Collapsible and inline messages are not modal and do not trap focus.

Q: Are there accessibility settings, callbacks, or APIs to manage focus when a message opens and closes?

A: Focus management is handled automatically — the focus trap engages when a dismissible message opens and focus is restored to the triggering element when it closes, with no configuration required. If you need developer-facing focus callbacks or programmatic control beyond this automatic behaviour, contact your Triptease account team so the request can be checked against the current platform capabilities.

Q: Is accessibility documentation or a VPAT available for review?

A: Yes. Triptease maintains a VPAT for the Triptease Messages platform covering WCAG 2.2 Level A and AA. Request a copy through your Triptease account team or Support.

Q: Does the VPAT cover everything in a message? A: The VPAT covers the rendered guest-facing message components. It does not cover content you author yourself — such as image alt text or custom colour choices — or the surrounding hotel page, which is outside Triptease's control.