Website Accessibility Report (RGAA)

1. Compliance status


Champagne Bollinger is committed to making its website accessible in accordance with Article 47 of French Law No. 2005-102 of 11 February 2005.

The website https://www.champagne-bollinger.com/ is non-compliant with the French General Accessibility Improvement Guidelines (RGAA 4.1.2).

Compliance rate: 39%

RGAA 4.1.2 audit result — 30 compliant criteria out of 77 applicable criteria (39%).

2. Non-accessible content

2.1 Non-compliances 


The main non-compliances identified are as follows:

  • Images (1.1, 1.2, 1.3) — The mobile logo and the B Corp SVGs in the footer have no text alternative. The desktop logo, which is decorative in context (the parent link has a title attribute), is not hidden from assistive technologies. The text alternatives for content images use the CMS filename instead of describing the visual content.

  • Frames (2.1) — Two Google Marketing Platform (DoubleClick) analytics tracking iframes are present on every page without a title attribute.

  • Colours (3.2, 3.3) — CTA buttons display white text on a gold #B4A168 background (a ratio of 2.54:1 instead of 4.5:1). The button backgrounds and form-field borders do not meet the 3:1 ratio required for user interface components.

  • Multimedia (4.1) — The YouTube video on the Article page does not have a text transcript.

  • Tables (5.4, 5.5, 5.6, 5.7) — On the Environmental characteristics page, tabular data is built with <div> elements instead of <table> elements. On the Find us page, the keyboard-shortcuts table has neither headers nor a title.

  • Links (6.2) — Six links in the header and footer have no accessible name (empty CSS icons and SVGs without alternatives). On some pages, eight links to /durabilite are completely empty <a> elements.

  • Scripts (7.1, 7.2, 7.3, 7.4, 7.5) — Interactive components (hamburger menu, accordions, age gate and carousels) do not communicate their state to assistive technologies. The <noscript> element is empty. The hamburger menu does not trap focus within the open panel. Status messages are not announced on the Login, Search and Find us pages.

  • Mandatory elements (8.7) — English-language passages (aria-labels on vue-select components) are not marked with the lang="en" attribute.

  • Structure (9.1) — The heading hierarchy is inconsistent: four pages have no H1, while two pages have two H1 headings simultaneously.

  • Presentation (10.3, 10.6, 10.7) — The header appears twice when CSS is disabled. Text links within editorial content are distinguished only by colour. Keyboard focus is invisible on the language selector, CTA buttons and News-page filters.

  • Forms (11.1, 11.2, 11.5, 11.9, 11.10) — The search field and age-gate selectors have no labels. The aria-labels on vue-select components are in English and are not relevant. The filter radio buttons on the News page are not grouped. The show/hide password button has no accessible name. Login-form error messages are not announced.

  • Navigation (12.6, 12.7) — The website's two <nav> elements have no aria-label. There is no skip link to the main content.


2.2 Exemptions


No exemption on the grounds of disproportionate burden has been declared.

2.3 Content not subject to the accessibility requirement


Embedded third-party content (YouTube video player, interactive Google Maps, OneTrust cookie banner) is not directly controlled by Champagne Bollinger and is not subject to accessibility requirements in accordance with Article 3 of Decree No. 2019-768.

3. Preparation of this accessibility statement


Statement date: This statement was prepared on 02/06/2026.

Technology used: Nuxt.js (single-page application with server-side rendering).

Tools used for the assessment:

  • axe-core 4.9.1

  • Lighthouse 13.2

  • Browser inspector (navigation, DOM inspection, dynamic testing)

  • W3C Nu HTML Checker

  • Colour Contrast Analyser 3.x /

  • HeadingsMap (browser extension)

  • VoiceOver (macOS)

Sample of pages audited (15 pages): 

P01 : Home page - https://www.champagne-bollinger.com/en/

P02 : 1829 Login - https://www.champagne-bollinger.com/en/1829/login/

P03 : Article (News) - https://www.champagne-bollinger.com/en/news/recette-accord-b16/

P04 : News listing - https://www.champagne-bollinger.com/en/news/

P05 : Storage and serving - https://www.champagne-bollinger.com/en/conservation-service/

P06 : Sustainability - https://www.champagne-bollinger.com/en/sustainability/

P07 : The House - https://www.champagne-bollinger.com/en/the-house/

P08 : Visits and events - https://www.champagne-bollinger.com/en/events/

P09 : Environmental characteristics - https://www.champagne-bollinger.com/en/product-sheet-environmental-qualities-and-characteristics/

P10 : Personal data - https://www.champagne-bollinger.com/en/data-protection/

P11 : Search - https://www.champagne-bollinger.com/en/search/

P12 : Find us - https://www.champagne-bollinger.com/en/find-us/

P13 : Collection (PLP) - https://www.champagne-bollinger.com/en/champagne/

P14 : Product page (PDP) - https://www.champagne-bollinger.com/en/wine/special-cuvee/

P15 : Legal notices - https://www.champagne-bollinger.com/en/legal-notice/



4. Feedback and accessibility contact


If you encounter an accessibility issue that prevents you from accessing any content or feature of the website, you may contact Maison Champagne Bollinger:

We undertake to respond within two business days and, where necessary, to offer an alternative way to access the content.

5. Remedies


If you do not receive a prompt response to your report, or if the response provided is unsatisfactory, you may lodge a complaint with the French Defender of Rights.

You may:

  • Send a letter (free of charge, no postage required): Défenseur des droits — Libre réponse 71120 — 75342 Paris CEDEX 07

Mobile App Accessibility Report (RAAM)

1. Compliance status

Champagne Bollinger is committed to making its 1829 by Bollinger mobile application (iOS / Android) accessible in accordance with Article 47 of French Law No. 2005-102 of 11 February 2005.

The 1829 by Bollinger mobile application is non-compliant with the Mobile Application Accessibility Assessment Framework (RAAM 1.1), based on European standard EN 301 549 v3.2.1.

Compliance rate: 35%

RAAM 1.1 audit result — 18 compliant criteria out of 52 applicable criteria (35%), calculated based on the overall status of each criterion.

2. Inaccessible content

2.1 Non-compliances

The main non-compliances identified are as follows:

Graphic elements (1.1, 1.2, 1.3) — Application images do not have text alternatives accessible to assistive technologies. Decorative images can receive screen-reader focus without being marked as decorative (1.1). Informative images do not have text alternatives that convey their content (1.2). Where an alternative exists, it is not always relevant (1.3).

Colours (2.2, 2.3) — The contrast ratio between text and its background is insufficient on several screens, particularly in the header and navigation bar (2.2). The contrast ratio of interactive components (buttons, icons) against their background is insufficient (2.3).

Multimedia (3.5, 3.9) — The YouTube presentation video embedded in the tutorial has no text transcript or accessible alternative (3.5). The video has no synchronized audio description (3.9).

Interactive components (5.1, 5.2) — Several icon buttons (back, profile, messages, scanner, basket) have no accessible name. The screen reader announces only “Button” without specifying its function (5.1). Some interactive components cannot be operated using an external keyboard (5.2).

Structure (7.1, 7.2) — No heading is semantically structured in the application. Text visually presented as headings does not have the “header” trait, making heading navigation impossible with VoiceOver or TalkBack (7.1). Lists of items are not structured with list traits (7.2).

Presentation (8.2, 8.6) — On Android, enlarging text to 200% causes truncation and overflow (8.2). Header buttons communicate their function only through the icon shape, without an accessible name (8.6).

Forms (9.1, 9.2, 9.5, 9.9) — Form fields (login, registration, address, payment) do not all have a compliant visible label (9.1). On Android, some labels are not exposed to assistive technologies (9.2). Some form buttons have no accessible label (9.5). Input error messages are not conveyed by assistive technologies (9.9).

Navigation (10.1, 10.2) — On Android, the tab order is inconsistent: focus moves from header elements directly to out-of-context elements (10.1). The order in which content is announced by the screen reader does not always match the visual order (10.2).

Content access (11.9) — On Android, the application forces portrait orientation through the AndroidManifest.xml file. Users cannot use landscape orientation. This issue does not affect the iOS version (11.9).

Accessibility documentation and features (12.1, 12.2, 12.4) — No documentation for accessibility features is available within the application (12.1). No mechanism is provided to activate application-specific accessibility features (12.2). No documentation compliant with accessibility requirements was identified on the distribution platforms (12.4).

2.2 Exemptions

No exemption due to disproportionate burden is declared.

2.3 Content not subject to accessibility requirements

The following content is not subject to accessibility requirements and was not audited:

  • Native Stripe component (PaymentSheet): integrated payment module provided by

    the third-party supplier Stripe. Its accessibility is the responsibility of the third-party

    supplier.

  • OneTrust component (cookie consent, Android): cookie consent banner provided by

    the third-party supplier OneTrust. Its accessibility is the responsibility of the

    third-party supplier.

3. Preparation of this accessibility statement


Statement date: This statement was prepared on 30/06/2026.

Technology used: Flutter (cross-platform mobile development framework).

Tools used for the evaluation:

  • VoiceOver (iOS) — manual testing

  • TalkBack (Android) — manual testing

  • External Bluetooth keyboard

  • Accessibility tree inspection

  • Automated contrast analysis

  • Static analysis of the Flutter code

Test environment:

iOS:

  • iPhone 15 Pro (simulator, iOS 17.5) — VoiceOver

  • iPhone 17 (IOS 26.5.1) — VoiceOver

  • External Bluetooth keyboard

Android :

  • Samsung Galaxy S23 (Android 14) — TalkBack

  • Pixel 10a (Android 16) — TalkBack

  • Pixel 6 (emulator, Android 14) — TalkBack

  • External Bluetooth keyboard

Audited screen sample (20 screens):

S01 : Tutorial

S02 : Cookie consent

S03 : Age verification

S04 : Pre-home

S05 : Login

S06 : Registration

S07 : Navigation menu

S08 : Post-login home

S09 : Product list

S10 : Product details

S11 : Event list

S12 : Event details

S13 : News list

S14 : Article details

S15 : Settings

S16 : Form error

S17 : Basket

S18 : Delivery

S19 : Address

S20 : Payment

Each screen was audited on both platforms (iOS and Android). Cross-cutting components (header, navigation bar) were covered by a consolidated audit (T00).

4. Feedback and accessibility contact


If you encounter an accessibility issue preventing you from accessing any content or feature on the site, you can contact Maison Champagne Bollinger:

We undertake to reply within 2 business days and, if necessary, provide an alternative means of accessing the content.

5. Enforcement procedure


If you do not receive a prompt response to your report, or if the response provided is not satisfactory, you may submit a complaint to the Défenseur des droits (French Rights Defender).

You can:

 

Gain exclusive access to the Maison

Attend exclusive events, buy rare cuvées and discover numerous other features through the 1829 App.

Join 1829