Accessibility Statement

Poool is committed to ensuring the accessibility of its web components in accordance with applicable international standards. This accessibility statement applies to the Access SDK (Web) and Engage SDK (Web), which are integrated into client websites via an iframe.

Responsible entity

Poool — 2 rue Marc Sangnier, 33130 Bègles, France.

Scope of this statement

• Access SDK (Web) and Engage SDK (Web), latest versions
• User interface components embedded via iframe
• Excludes: audio/video content (not provided within the iframe), host-site navigation (menus, sitemaps, breadcrumbs), and all client editorial content outside the iframe

Reference standard

The SDKs have been evaluated against WCAG 2.1 Level AA, as reflected in the French RGAA 4.1 framework.

Compliance Status

Within the defined scope (Poool-provided components only), no known non-conformities were identified during internal testing, and all applicable WCAG 2.1 AA requirements are met.

This compliance status applies exclusively to Poool’s own components. Any accessibility issues arising from client-configured content (text, images, labels, contrast choices, headings, error messages, or custom CSS) are outside the scope of this declaration.

Audit Results & Methodology

• Type of audit: Internal accessibility audit (October 2025)
• Scope: Full coverage of all interactive components, states, and templates of Access & Engage
• Sample: All components available in the latest product versions
• Test environments: macOS & Windows 11 (latest versions as of 19/01/2026), Google Chrome & Firefox
• Tools: WAVE, Lighthouse
• Assistive technologies checked: Basic compatibility tests with NVDA, VoiceOver macOS/iOS
• Technologies used in the product: HTML, CSS, JavaScript

Supported browsers:

Responsibilities and Embedded Content

When the Poool iframe displays text, images, colours, or styling configured by the client:

• The client is responsible for ensuring the accessibility of these custom contents.
• Poool provides configuration capabilities (text fields, style options, ARIA states, announcements), but does not control the editorial choices or the final contrast/structure supplied by the client.

Non-applicable items: audio/video content (not provided), host-site navigation.

Feedback and Contact

If you encounter an accessibility issue or require an accessible alternative, please contact us:

📩 [email protected]

Enforcement and Recourse Mechanisms

If you are unable to obtain a satisfactory response, you may contact the relevant national authority in your country responsible for digital accessibility (e.g. in France: the Défenseur des droits via official channels).

Authorities and procedures differ by jurisdiction; please refer to your national guidelines.

Screens & Components Tested

• Access modals, paywall screens, forms, status messages
• Engage templates (text variants, buttons, embedded states)
• Keyboard navigation, focus visibility, and announcement states where applicable

Continuous Improvement

A multi-year accessibility roadmap is currently being drafted (as of January 2026).

Accessibility improvements will be communicated through updates to this statement.