Search
  • Stores
Menu

Accessibility Statement

Drawn up on 27/06/2025 and updated on 06/02/2026 following an accessibility audit.

Palais des Thés is committed to ensuring that its websites are accessible, in accordance with Decree No. 2023-931 of 9 October 2023 relating to the accessibility of products and services for persons with disabilities.

To this end, Palais des Thés implements the following strategy and actions:

  • Collaborative work with an external agency specialised in accessibility: Tanaguru
  • Awareness-raising initiatives for internal teams delivered by Tanaguru
  • Training programmes for teams delivered by Tanaguru
  • Remediation of existing content that does not meet accessibility requirements
  • Integration of accessibility requirements into ongoing and future web developments

This accessibility statement applies to the Palais des Thés website.

Compliance status

The website www.palaisdesthes.com is currently not compliant with the requirements of the General Accessibility Improvement Framework (RGAA 4.1). This non-compliance is due to a number of technical criteria that have not yet been met (see details below).

Test results

The compliance audit conducted by Tanaguru on 27 July 2025 indicates a compliance rate of 29% against RGAA 4.1 criteria and 30% against RAWeb criteria, based on a representative sample of 25 pages.

Non-accessible content

Certain criteria remain non-compliant to date and will be addressed through progressive remediation.

The following is a list of the main non-compliant criteria identified during the audit:

  • Criterion 1.2: Is each decorative image correctly ignored by assistive technologies?
  • Criterion 1.3: For each informative image with a text alternative, is that alternative relevant (excluding special cases)?
  • Criterion 2.1: Does each frame have a frame title?
  • Criterion 2.2: For each frame with a frame title, is that title relevant?
  • Criterion 3.1: On each web page, information must not be conveyed by colour alone. Is this requirement met?
  • Criterion 3.2: On each web page, is the contrast between text colour and background colour sufficiently high (excluding special cases)?
  • Criterion 3.3: On each web page, are the colours used in interface components or graphical elements conveying information sufficiently contrasted (excluding special cases)?
  • Criterion 4.1: Does each pre-recorded time-based media have, where required, a text transcript or audio description (excluding special cases)?
  • Criterion 4.4: For each pre-recorded synchronised time-based media with subtitles, are those subtitles relevant?
  • Criterion 4.5: Does each pre-recorded time-based media have, where required, a synchronised audio description (excluding special cases)?
  • Criterion 4.7: Is each time-based media clearly identifiable (excluding special cases)?
  • Criterion 4.8: Does each non-time-based media have, where required, an alternative (excluding special cases)?
  • Criterion 4.9: For each non-time-based media with an alternative, is that alternative relevant?
  • Criterion 4.11: Is playback of each time-based media, where required, controllable using the keyboard and any pointing device?
  • Criterion 4.12: Is consultation of each non-time-based media controllable using the keyboard and any pointing device?
  • Criterion 5.3: For each layout table, does the linearised content remain understandable?
  • Criterion 5.8: Each layout table must not use elements intended for data tables. Is this requirement met?
  • Criterion 6.1: Is each link clearly identifiable (excluding special cases)?
  • Criterion 6.2: On each web page, does each link have an accessible label?
  • Criterion 7.1: Is each script, where required, compatible with assistive technologies?
  • Criterion 7.3: Is each script operable using the keyboard and any pointing device (excluding special cases)?
  • Criterion 7.4: For each script that initiates a change of context, is the user informed or given control?
  • Criterion 7.5: On each web page, are status messages correctly exposed to assistive technologies?
  • Criterion 8.6: For each web page with a page title, is that title relevant?
  • Criterion 8.7: On each web page, is any change of language correctly indicated in the source code (excluding special cases)?
  • Criterion 8.9: On each web page, HTML elements must not be used solely for presentation purposes. Is this requirement met?
  • Criterion 9.1: On each web page, is information structured through the appropriate use of headings?
  • Criterion 9.2: On each web page, is the document structure consistent (excluding special cases)?
  • Criterion 9.3: On each web page, is each list correctly structured?
  • Criterion 9.4: On each web page, is each quotation correctly identified?
  • Criterion 10.1: Are style sheets used to control the presentation of information across the website?
  • Criterion 10.2: On each web page, does information-bearing visible content remain available when style sheets are disabled?
  • Criterion 10.3: On each web page, does information remain understandable when style sheets are disabled?
  • Criterion 10.4: On each web page, does text remain readable when text size is increased up to at least 200% (excluding special cases)?
  • Criterion 10.6: On each web page, is any link whose purpose is not obvious distinguishable from surrounding text?
  • Criterion 10.7: On each web page, is visible focus provided for each element that receives focus?
  • Criterion 10.8: For each web page, are hidden contents intended to be ignored by assistive technologies?
  • Criterion 10.9: On each web page, information must not be conveyed solely by shape, size, or position. Is this requirement met?
  • Criterion 10.11: For each web page, can content be presented without requiring vertical scrolling for a viewport height of 256px or horizontal scrolling for a viewport width of 320px (excluding special cases)?
  • Criterion 10.12: On each web page, can text spacing properties be adjusted by the user without loss of content or functionality (excluding special cases)?
  • Criterion 11.1: Does each form field have an associated label?
  • Criterion 11.2: Is each form field label relevant (excluding special cases)?
  • Criterion 11.5: Within each form, are fields of the same nature grouped together where appropriate?
  • Criterion 11.6: Within each form, does each grouping of fields of the same nature have an associated legend?
  • Criterion 11.7: Is each legend associated with a grouping of fields of the same nature relevant?
  • Criterion 11.9: Within each form, is the label of each button relevant (excluding special cases)?
  • Criterion 11.10: Within each form, is input validation used appropriately (excluding special cases)?
  • Criterion 11.11: Within each form, is input validation, where required, accompanied by suggestions to assist users in correcting input errors?
  • Criterion 11.13: Can the purpose of an input field be programmatically determined to facilitate automatic completion using user data?
  • Criterion 12.3: Is the “site map” page relevant?
  • Criterion 12.8: On each web page, is the tab order logical and consistent?
  • Criterion 12.11: On each web page, are additional contents displayed on hover, focus, or activation of an interface component, where required, accessible via the keyboard?
  • Criterion 13.9: On each web page, is the content accessible regardless of screen orientation (portrait or landscape) (excluding special cases)?

Exemptions for disproportionate burden

None.

Content not subject to the accessibility obligation

None.

Ongoing improvements

We are currently working to progressively remediate the following items identified during the accessibility audit.

  • Addition of relevant text alternatives for visual content
  • Compliance remediation of dynamic components
  • Optimisation of keyboard navigation and semantic markup
  • Awareness-raising and training of internal teams on accessibility issues
  • Correction of technical non-compliances identified during the audit
  • Completion of a second accessibility audit

Preparation of this accessibility statement

This statement was drawn up on 27 June 2025 and was updated on 6 February 2026.

Technologies used in the provision of the service

  • HTML 5
  • CSS 3
  • JavaScript

User agents, assistive technologies and tools used to assess accessibility

  • Firefox and NVDA (latest version)
  • Safari and VoiceOver (latest version)
  • Firefox and JAWS (previous version)

The following tools were used during the evaluation:

  • Firefox built-in developer tools
  • Tanaguru Webext extension
  • Web Developer extension
  • Stylus extension
  • HeadingsMap extension
  • Colour Contrast Analyser
  • W3C HTML Validator

Website pages included in the compliance assessment:

  • Page 1: Home
  • Page 2: Legal notice
  • Page 3: Site map
  • Page 4: Contact
  • Page 5: Accessibility
  • Page 6: Search results
  • Page 7: Product pages
  • Page 8: Login
  • Page 9: My account
  • Page 10: Cart
  • Page 11: Delivery
  • Page 12: Payment
  • Page 13: FAQ
  • Page 14: Editorial: Our story
  • Page 15: Store locator
  • Page 16: Blog
  • Page 17: Order confirmation
  • Page 18: Order confirmation email
  • Page 19: Order history
  • Page 20: Order
  • Page 21: Category pages
  • Page 22: Blog home pages
  • Page 23: Blog recipe page
  • Page 24: Blog article page
  • Page 25: Blog category page

Feedback and contact information

If you experience any difficulty accessing content or functionality on the website, please let us know. You may contact us using the following methods:

By email: contact@palaisdesthes.com
By telephone: 01 55 28 80 40
Via our contact form

We undertake to respond as soon as possible.

Remedies

This procedure should be used in the following circumstances.

You have reported an accessibility issue to the website operator that prevents you from accessing content or a service on the website and have not received a satisfactory response.

Log In