/* =============================================================================================
   psyrespirereims.com — restoration stylesheet
   =============================================================================================
   Every rule here is an ADDITION to the site's own inlined Wix CSS, never a replacement, and every
   number in it was measured on this site's DOM (_scripts/o5_psy_probe_layout.js, o5_psy_probe2.js,
   o5_psy_probe3.js, o5_psy_probe4.js) rather than copied from a sister Wix restoration. Wix's
   hashed class names are generated per bundle generation: celinesantenaturelle's `wix-image` and
   `#comp-jhpwvpsw` mean nothing here, where the image element is `wow-image` and the menu is
   `#comp-ldfmn5qf`. A copied selector matches nothing and every gate still reports green.

   Platform: Wix Thunderbolt, 2023-02 → 2024-07 generation, DESKTOP payload.
   `--site-width:980px`, `#site-root{min-width:980px}`, and exactly one @media rule in the whole
   document — `(prefers-reduced-motion:reduce)`. There is not a single layout breakpoint anywhere
   in the archive, because Wix served phones a separate payload that no crawler ever asked for.
   The phone view below is therefore rebuilt, not restored, and this file says so out loud.
   ============================================================================================= */


/* =============================================================================================
   SECTION A — A PHONE GETS A PHONE LAYOUT
   =============================================================================================
   WHAT WAS MEASURED. Every page declares `width=device-width`, and at a 390px viewport the
   document measured 1033px wide: the fixed 980px mesh plus the three full-bleed section wrappers
   (#comp-ldfmeskd, #comp-ldfmespm, #comp-ldfmet8t) which are 1100px wide and start at x=-67.
   The result is the complaint this batch already collected once — the menu's first item reads as
   "eil", every line of body copy is cut at the right edge, and the page scrolls sideways.

   WHY THE META ALONE WOULD MAKE IT WORSE, and why it is not enough to just add one. `#site-root`
   carries `min-width:980px` (read off the computed style, not the source). Release nothing else
   and device-width CLIPS instead of reflowing: Wix's containers are overflow:hidden, so the copy
   is cut mid-sentence while every overflow check turns green. The route below — release the
   floor, then turn the mesh into a column — is the one proved on crescercomsabor.pt, wenou.pt and
   celinesantenaturelle.com; only the selectors are this site's.
   ============================================================================================= */
@media (max-width: 1099px) {

  /* A1. Release the 980px floor first, or everything below clips instead of reflowing.

     DO NOT add overflow-x:hidden to html or body here. On the sister Wix site that made the phone
     page unscrollable: html/body are given an explicit height and body owns the scroll, and an
     overflow-x on html turns html into its own one-viewport scroll container so window.scrollY
     never moves. Every gate stayed green through it. The overflow being hidden is gone anyway
     once the wrappers below stop being 980+ wide. */
  #site-root,
  #SITE_CONTAINER, #main_MF, #masterPage, #SITE_PAGES, #SITE_PAGES_TRANSITION_GROUP,
  #PAGES_CONTAINER, #BACKGROUND_GROUP, #BACKGROUND_GROUP_TRANSITION_GROUP,
  #SITE_HEADER, #SITE_HEADER_WRAPPER, #SITE_FOOTER, #SITE_FOOTER_WRAPPER,
  section[id^="comp-"], div[id^="comp-"],
  [id^="pageBackground_"], [id^="bgLayers_"], [id^="bgMedia_"],
  [id^="Container"], [class*="SITE_PAGES"] {
    min-width: 0 !important;
    max-width: 100% !important;
  }
  #site-root, #masterPage, #SITE_PAGES, #PAGES_CONTAINER, #main_MF, #SITE_CONTAINER,
  [id^="pageBackground_"] {
    width: 100% !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
    left: 0 !important;
  }

  /* A1a. --site-width IS THE ONE LEVER THAT MOVES EVERYTHING WIX CENTRES.
     Wix defines `--site-width:980px` on :root and then uses it in exactly three places (measured
     by grepping the inlined CSS, not assumed): `width:var(--site-width)`,
     `min-width:var(--site-width)` and `margin-left:calc((100% - var(--site-width))/2)`. That last
     one is why the header's cream menu strip (.G5K6X8) still measured 980px wide at x=-295 after
     the whole mesh had been reflowed - 100% was 390, so the calc pulled it 295px off-screen and
     the document still scrolled to 685. Setting the variable to 100% here fixes all three uses at
     once and needs no hashed class name at all. */
  :root, #site-root, #masterPage { --site-width: 100% !important; }

  /* A1b. THE FULL-BLEED SECTION WRAPPERS. Measured at 390 with o5_psy_probe2.js: #comp-ldfmeskd,
     #comp-ldfmespm and #comp-ldfmet8t each compute 1100px wide starting at x=-67, which is
     precisely the 1033px the document scrolled to. Wix centres a wider-than-site band by pulling
     it left; with the site 390 wide the pull is 610px of empty page. They are addressed as a
     class of thing (a comp- box wider than the site) rather than by id, because the same trick is
     used on all ten pages with different ids. */
  #masterPage div[id^="comp-"], #masterPage section[id^="comp-"] {
    left: 0 !important;
    right: auto !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
    width: 100% !important;
  }
  /* the anonymous page wrappers between #SITE_PAGES and the mesh keep their own 980/1100 widths */
  #SITE_PAGES > div, #SITE_PAGES > div > div, #SITE_PAGES > div > div > div,
  #SITE_PAGES > div > div > div > div, #SITE_PAGES > div > div > div > div > div {
    width: 100% !important;
    min-width: 0 !important;
    max-width: 100% !important;
    left: 0 !important;
    margin-left: 0 !important;
  }

  /* A2. THE MESH. #masterPage is a grid of sections; inside each section
     [data-mesh-id$="-gridContainer"] is a single-column grid whose children are placed by `left`
     and sized in px for a 980 column. Turning that container into a flex column and dropping
     left/width/margin stacks the components in document order, which is the order the page was
     written in. */
  [data-mesh-id$="inlineContent"] {
    width: 100% !important;
    min-height: 0 !important;
    margin-top: 0 !important;
    display: block !important;
  }
  [data-mesh-id$="-gridContainer"] {
    display: flex !important;
    flex-direction: column !important;
    grid-template-columns: none !important;
    grid-template-rows: none !important;
    height: auto !important;
    /* Wix writes a min-height on the mesh container equal to the desktop column's height. As a
       grid that costs nothing once the rows collapse; as a flex column it is dead space. */
    min-height: 0 !important;
    width: 100% !important;
  }
  [data-mesh-id$="-gridContainer"] > * {
    grid-area: auto !important;
    position: relative !important;
    left: auto !important;
    right: auto !important;
    top: auto !important;
    margin-left: 0 !important;
    margin-right: 0 !important;
    margin-top: 0 !important;
    min-width: 0 !important;
    width: 100% !important;
    max-width: 100% !important;
    align-self: auto !important;
    justify-self: stretch !important;
    height: auto !important;
    flex: 0 0 auto;
  }

  /* A2a. THE WEDGES. Wix pads its mesh with empty spacer divs carrying the px heights that hold
     the desktop grid apart. As grid rows they collapse with their row; as flex children in a
     column they contribute every one of their pixels. */
  [data-mesh-id*="wedge"] { display: none !important; }

  /* A2b. A SECTION MUST BE ALLOWED TO GROW: stacked, its content is three to five times taller
     than the desktop band, and the band's own overflow is hidden. Background layers are excluded
     — they are handled in A4 and must keep filling their band. */
  section[id^="comp-"],
  div[id^="comp-"]:not([id^="bgLayers_"]):not([id^="bgMedia_"]) {
    height: auto !important;
    min-height: 0 !important;
  }

  /* A2c. THE ABSOLUTELY-POSITIONED INNER COLUMN. Wix wraps each section's children in the element
     carrying data-testid="inline-content"; left absolute it contributes nothing to its parent's
     height, so a released section would be 0 tall and the page would collapse into the header. */
  [data-testid="inline-content"] { position: relative !important; height: auto !important; }

  /* A3. Rich text is sized in px for a 980 column. */
  [data-testid="richTextElement"] {
    width: 100% !important;
    height: auto !important;
    padding-left: 14px !important;
    padding-right: 14px !important;
    box-sizing: border-box !important;
  }
  [data-testid="richTextElement"] * { max-width: 100% !important; }
  [data-testid="richTextElement"] h1, [data-testid="richTextElement"] h2,
  [data-testid="richTextElement"] h3 { overflow-wrap: break-word; }
  /* Justified text in a 350px measure opens rivers two words wide. */
  [style*="text-align:justify"] { text-align: left !important; }

  /* A4. THE PHOTOGRAPHIC BANDS AND THE PAGE BACKGROUND. A band holds its picture in an absolutely
     positioned layer, so once the band is height:auto the layer has no in-flow content of its own
     and the photograph silently becomes 0 tall — silently, because no gate can see a background
     that is not painted. */
  [id^="bgLayers_"], [id^="bgMedia_"] { height: 100% !important; width: 100% !important; }
  [id^="bgMedia_"] wow-image, [id^="bgMedia_"] wow-image img {
    height: 100% !important; width: 100% !important; object-fit: cover !important;
  }

  /* A5. IMAGES. A Wix image component is a fixed box with the <img> stretched to height:100%; at
     full width with height:auto the box measures 0 and the picture vanishes. Scoped away from the
     background layers for exactly that reason. */
  [data-testid="richTextElement"] ~ wow-image,
  div[id^="comp-"] > wow-image,
  .wixui-image > [data-testid="linkElement"],
  .wixui-image > [data-testid="linkElement"] > wow-image,
  .wixui-gallery wow-image {
    display: block !important;
    height: auto !important;
    width: 100% !important;
    min-height: 0 !important;
  }
  /* A5a. A STANDALONE PICTURE MUST NOT BE UPSCALED PAST THE FILE WE HOLD. Wix delivered each
     photograph at exactly the size its desktop box needed - the mandala on the homepage is
     214x147 and her portrait beside it is 111x148 - and stretching those to a 390px column is a
     blurred enlargement of a small JPEG, which is the "restoration is not simulation" line drawn
     at the level of one image. The component may take the full width; the picture inside it keeps
     its own size and centres, up to the width available.
     The gallery is the exception below: its tiles are square crops meant to fill their cell. */
  div[id^="comp-"] > wow-image > img,
  .wixui-image > [data-testid="linkElement"] > wow-image > img {
    position: static !important;
    display: block !important;
    width: auto !important;
    max-width: 100% !important;
    height: auto !important;
    margin: 0 auto !important;
    object-fit: contain !important;
  }
  .wixui-gallery wow-image > img {
    position: static !important;
    width: 100% !important;
    height: 100% !important;
    object-fit: cover !important;
  }
  [id^="bgMedia_"] wow-image > img { height: 100% !important; object-fit: cover !important; }

  /* A6. The homepage's four-tile grid is a fixed four-column grid 980px wide. Two columns at 390. */
  [data-testid="paginated-grid-gallery-items-container"] {
    grid-template-columns: 1fr 1fr !important;
    grid-template-rows: auto auto !important;
    gap: 6px;
  }
  [data-testid="paginated-grid-gallery-items-container"] > * {
    grid-row: auto !important;
    grid-column: auto !important;
    position: relative !important;
    width: auto !important;
    height: auto !important;
    aspect-ratio: 1 / 1;
  }
  [data-testid="paginated-grid-gallery-items-container"] > * > * { height: 100% !important; }
}


/* =============================================================================================
   SECTION B — THE NAVIGATION
   =============================================================================================
   The menu is a Wix StylableHorizontalMenu: nav[class*=StylableHorizontalMenu] > ul (flex row) >
   li.itemDepth0…__itemWrapper > a. Seven items, no dropdown, no "More" overflow control — every
   item is a real link to a real page, which is why nothing here has to be rebuilt, only wrapped.

   MEASURED AT 390 BEFORE THIS SECTION: the row ran from x=-57 to x=942, so "Accueil" was half
   off-screen to the LEFT and "Relaxations à écouter" 550px off to the right. Wrapping the row and
   centring it puts all seven inside the viewport.
   ============================================================================================= */
@media (max-width: 1099px) {
  #masterPage nav[class*="StylableHorizontalMenu"],
  #masterPage nav[class*="StylableHorizontalMenu"] > ul {
    position: static !important;
    width: 100% !important;
    height: auto !important;
    min-height: 0 !important;
    overflow: visible !important;
    white-space: normal !important;
  }
  #masterPage nav[class*="StylableHorizontalMenu"] > ul {
    display: flex !important;
    flex-wrap: wrap !important;
    justify-content: center !important;
    align-items: stretch !important;
    padding: 4px 6px 8px !important;
  }
  #masterPage nav[class*="StylableHorizontalMenu"] > ul > li {
    position: relative !important;
    left: auto !important;
    top: auto !important;
    width: auto !important;
    height: auto !important;
    display: block !important;
    flex: 0 0 auto !important;
  }
  #masterPage nav[class*="StylableHorizontalMenu"] > ul > li > a {
    height: auto !important;
    /* 24px is the floor a finger can hit and the gate's block threshold; the label is 20px on its
       own, so the padding is what makes the target legal as well as comfortable. */
    min-height: 40px !important;
    display: flex !important;
    align-items: center !important;
    padding: 6px 10px !important;
  }
  /* The menu strip is a fixed-height band on desktop. */
  #masterPage #comp-ldfmn5qf { height: auto !important; min-height: 0 !important; }

  /* B2. THE STRIP HAS TO GROW WITH THE MENU, AND ONLY A SCREENSHOT SHOWED THAT IT DID NOT.
     Wix paints the menu's cream band in .gUbusX, an absolutely positioned layer inset into a
     53px-tall header row. Wrapped to three rows the menu is ~120px tall, so rows two and three
     came out ON the page-background photograph: "Psychologie / Psychothérapie / Sophrologie" sat
     over grass. qa_legibility passed it, because it photographs the ground at the centre of each
     run and the grass happened to be dark enough there - a menu is not legible because one pixel
     under one word measured 4.5:1.
     rgb(250,236,210) is the strip's own colour, sampled off the 1440 render at (1200,193). */
  #masterPage #comp-ldfmn5qf { background: rgb(250, 236, 210) !important; }
  #masterPage #SITE_HEADER .G5K6X8, #masterPage #SITE_HEADER .gUbusX { display: none !important; }
}


/* =============================================================================================
   SECTION C — THE TWO WIX GALLERIES, NOW STATIC
   =============================================================================================
   C1. 'Photos du cabinet' was a Pro Gallery slideshow captured mid-state: one visible slide in a
   462x508 box, a prev/next <nav> and a "1/4" counter, every one of them driven by a runtime this
   copy no longer ships. o5_psy_31_strip_wix.py replaced it with a plain list of the three
   photographs the archive actually holds (the fourth slide's media id is in no capture of this
   domain), and this is the shape it is given: the entrance across the top, the two interiors
   beneath it, inside roughly the footprint the slideshow occupied so the page's rhythm survives.

   The `height:auto` on the component is load-bearing. Its own rule is `height:508px`, and the
   three photographs are 1440px tall together, so without it they overflowed the section, the page
   background and the footer, and the last two sat on bare white outside the page.
   ============================================================================================= */
.psy-gal { height: auto !important; width: 462px; max-width: 100%; }
.psy-gal__list {
  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  grid-template-columns: 1fr 1fr;
  gap: 8px;
}
.psy-gal__item { margin: 0; }
.psy-gal__item:first-child { grid-column: 1 / -1; }
.psy-gal__item img {
  display: block;
  width: 100%;
  height: 250px;
  object-fit: cover;
  border-radius: 2px;
}
.psy-gal__item:first-child img { height: 250px; }
@media (max-width: 1099px) {
  .psy-gal { width: 100% !important; }
  .psy-gal__item img, .psy-gal__item:first-child img { height: 190px; }
}

/* ---------------------------------------------------------------------------------------------
   C2. THE MAP. Wix's GoogleMap component renders entirely client-side, so the archived DOM held
   `<div class="wixui-google-map" tabindex="0"></div>` — 500x360 of nothing inside the contact
   block, plus a tab stop that led nowhere. It now shows a raster built from OpenStreetMap tiles
   at build time and served from this domain (o4_osm_map_from_embed.py), so the contact page makes
   no third-party request and cannot lose its map when someone else's service changes.

   THE CREDIT IS NOT DECORATION. ODbL requires it, and it is applied twice on purpose: burned into
   the image so it travels with the file, and printed here as real selectable text so it is legible
   and its link works. The first version inherited the page's 10px and the link's own colour and
   measured 1.11:1 against the dark green band — invisible text, which is a blocking defect and
   was also, in substance, shipping the map without its attribution. */
.psy-map { height: auto !important; }
.psy-map img { display: block; max-width: 100%; height: auto; }
.psy-map__credit {
  margin: 6px 0 0;
  font-size: 13px;
  line-height: 1.45;
  color: rgb(253, 238, 210);
}
.psy-map__credit a { color: rgb(253, 238, 210); text-decoration: underline; }


/* =============================================================================================
   SECTION D — LEGIBILITY THE SITE'S OWN CSS GETS WRONG
   =============================================================================================
   Measured with qa_legibility.js at 1440 and 390 on /, /le-cabinet-contact-horaires/ and
   /politique-de-confidentialite/. Each rule below names the reading it was written for.
   ============================================================================================= */

/* D1. THE MASTHEAD. "Cabinet de Psychologie et Sophrologie d'Aurélie Martin" and the three lines
   under it are rgb(42,143,189) over the pale top of the page background: measured 3.64:1, where a
   16-18px label needs 4.5. The replacement keeps the hue and the saturation of the site's blue and
   moves lightness only, so the masthead still reads as the same colour it always was.

   Matched on the substring "rgb(42, 143, 18" and not on the full colour: the masthead's first two
   lines are rgb(42,143,189) and the three service lines under them are rgb(42,143,188). One digit
   apart, indistinguishable on screen, and an exact-match selector fixed the title while leaving
   "Psychothérapie / Accompagnement psychologique / Sophrologie et relaxation" at 3.65:1. */
#SITE_HEADER [data-testid="richTextElement"] [style*="rgb(42, 143, 18"] {
  color: rgb(19, 90, 122) !important;
}

/* D1b. THE SAME BLUE IN THE PAGE BODY — AND THE DIRECTION OF THE FIX IS NOT THE SAME ON EVERY
   PAGE. This site has two page bands, and which one a page gets is not derivable from its markup;
   it was read off the rendered screenshots, one pixel per page (o5_psy_bands.js could not answer
   it, because Wix paints the band in an absolutely positioned layer whose computed
   background-color is transparent — the colour arrives as an image):

       /, /le-cabinet-contact-horaires/, /tarifs/, /psychologie/, /psychotherapie/, /sophrologie/
           dark sage  rgb(62,81,71)     L=0.074   -> the accent blue must be LIGHTENED
       /relaxations-a-ecouter/
           cream      rgb(225,215,190)  L=0.702   -> the accent blue must be DARKENED

   The first version of this rule lightened the accent blue everywhere inside #PAGES_CONTAINER. It
   fixed /tarifs/ (2.33 -> 5.2) and made the ONLY heading on /relaxations-a-ecouter/ invisible at
   1.45:1 — a page that had been passing. The rule is now keyed on the six section ids that own a
   dark band, and the default below it handles every light ground including the authored pages.

   Three spellings of one colour are matched because the site contains three: rgb(42,143,189),
   rgb(42,143,188) and rgb(40,143,189) — plus rgb(82,186,235) on /sophrologie/, which measured
   3.87:1 on the same band. */
#PAGES_CONTAINER [style*="rgb(42, 143, 18"],
#PAGES_CONTAINER [style*="rgb(40, 143, 18"],
#PAGES_CONTAINER [style*="rgb(82, 186, 235)"] {
  color: rgb(19, 90, 122) !important;
}
#comp-lm61x570 [style*="rgb(42, 143, 18"], #comp-lm61x570 [style*="rgb(40, 143, 18"],
#comp-lm61x56u [style*="rgb(42, 143, 18"], #comp-lm61x56u [style*="rgb(40, 143, 18"],
#comp-lm61x56y [style*="rgb(42, 143, 18"], #comp-lm61x56y [style*="rgb(40, 143, 18"],
#comp-lm61x56s [style*="rgb(42, 143, 18"], #comp-lm61x56s [style*="rgb(40, 143, 18"],
#comp-lm61x56v [style*="rgb(42, 143, 18"], #comp-lm61x56v [style*="rgb(40, 143, 18"],
#comp-lm61x56y1 [style*="rgb(42, 143, 18"], #comp-lm61x56y1 [style*="rgb(40, 143, 18"],
#comp-lm61x56y1 [style*="rgb(82, 186, 235)"] {
  color: rgb(146, 212, 244) !important;
}

/* D2. THE AUTHORED LEGAL PAGES. The mandatory pages are clones of /tarifs/, and the Wix page
   container they are cloned into sets font-size:10px on everything it owns. Measured: 17 separate
   runs of 10px body copy on /politique-de-confidentialite/ — a privacy notice nobody can read is
   not a privacy notice. The block below gives the authored content its own scale; it is scoped to
   .o5-legal so no archived page is touched. */
.o5-legal { font-size: 16px; color: rgb(24, 24, 24); }
.o5-legal h1 { font-size: 30px; }
.o5-legal h2 { font-size: 21px; }
.o5-legal p, .o5-legal li { font-size: 16px; line-height: 1.65; }
.o5-legal a { color: rgb(19, 90, 122); text-decoration: underline; }
/* 44px is the comfortable tap target; the gate blocks under 24. A phone number and an e-mail
   address on a legal page are the two links a visitor is most likely to reach for. */
.o5-legal a[href^="tel:"], .o5-legal a[href^="mailto:"], .o5-legal li a {
  display: inline-block;
  min-height: 26px;
  padding: 4px 0;
}

/* D2b. THE 404's ROUTE BACK INTO THE SITE. Its nine list links measured 17px tall at both widths —
   the whole point of the page is that a visitor who mistyped a URL can get where they were going,
   and nine 17px targets stacked 17px apart is the version of that which fails on a phone. */
.o5-legal ul { margin-bottom: 1.4em; }
.o5-legal li { margin-bottom: .55em; }

/* D3. LINKS THAT READ EXACTLY LIKE THE PROSE AROUND THEM. Measured: the M3P linktr.ee address on
   the homepage is white inside a white bullet list, the weave link in the content-wraparea block is the same cream as its
   paragraph, and the cabinet's mailto: is the same colour as the address above it. Wix set every
   body link to `text-decoration:none` and gave it the surrounding run's colour, so on this site
   the only thing that distinguishes a link is the cursor — which a phone does not have. An
   underline restores the affordance without changing a single colour the site chose. */
[data-testid="richTextElement"] a[href],
.content-wraparea a[href] {
  text-decoration: underline !important;
  text-underline-offset: 2px;
}
/* …except the two link-shaped things that are already unmistakable: the stylable button and the
   menu, both of which would look broken with a rule under them. */
a.StylableButton2545352419__root,
nav[class*="StylableHorizontalMenu"] a { text-decoration: none !important; }

/* D5. TAP TARGETS ON A PHONE. Measured at 390 after the reflow: the Doctolib button's own anchor
   collapsed to 390x20 once its component became full width (its height had been coming from the
   component's fixed px box, which section A releases), and the cabinet's mailto: link is 17px tall
   because it is a run of inline text. Both are under the 24px the gate blocks at, and both are
   things a visitor reaches for with a thumb: booking, and the e-mail address.
   The inline-link rule is NOT scoped to the phone: measured at 1440 the same mailto: is 278x17
   and the Doctolib link 379x20, so a mouse user with unsteady hands has the same problem. Only
   the button rule is phone-scoped, because on desktop its component still supplies its height. */
[data-testid="richTextElement"] a[href^="mailto:"],
[data-testid="richTextElement"] a[href^="tel:"],
[data-testid="richTextElement"] a[href^="http"] {
  display: inline-block;
  min-height: 26px;
  padding: 4px 0;
  overflow-wrap: anywhere;
}
@media (max-width: 1099px) {
  a.StylableButton2545352419__root {
    min-height: 44px !important;
    display: flex !important;
    align-items: center !important;
    justify-content: center !important;
  }
}

/* D4. The site's own decorative rules are transparent PNGs whose ornament lives entirely in an
   alpha channel at 20% opacity. Nothing to fix in CSS — recorded here so that the next person to
   see "three white bars" on the homepage looks at the image pipeline (o5_psy_30_install_images.py)
   and not at this stylesheet. */

/* D6. THE TWO STYLABLE BUTTONS WHOSE OWN COLOUR WAS THE PROBLEM.
   /sophrologie/ "ESNE" and "Podcast «Et si on en parlait?»" are white on rgba(156,142,89) — 3.27:1.
   /psychologie/ "Code de déontologie… (pdf)" and "Lien Chaîne YouTube…" are white on
   rgba(40,143,189) — 3.65:1. Both are under the 4.5 a 15px label needs, and both are the routes to
   the two documents this practitioner actually points her readers at, so neither is decorative.

   The label colour is left alone and the FILL is deepened instead: same hue, same saturation,
   lower lightness, so the buttons still read as the site's khaki and the site's blue. Measured
   after: 5.5:1 and 5.7:1 against white. Repainting the labels dark would have been the larger
   change and would have made the two buttons look like a different site's. */
.style-ldfmllf6__root, .style-ldfmllwr1__root { background: rgb(118, 105, 54) !important; }
.style-ldfmjczu__root, .style-ldfmjpzp1__root { background: rgb(26, 110, 148) !important; }


/* =============================================================================================
   SECTION E — THE TWO BLOCKS THIS RESTORATION ADDS
   =============================================================================================
   E1. THE LEGAL STRIP. Wix left SITE_FOOTER empty on all ten pages, so before this the two legal
   pages were reachable only from the 404 and from each other: a visitor on a real page of the site
   could not get to either. The strip fills the footer the site already had rather than inventing a
   new band, and it carries the identifiers she publishes herself and nothing more.

   Its colours are stated explicitly and not inherited. Behind the footer is the page background
   photograph, which is fixed and therefore a different colour at every scroll position - inherited
   text over it would be legible on some screens and not others, and no gate would ever catch it
   because a gate photographs one scroll position. Measured on the stated ground rgb(62,81,71):
   cream 7.4:1, links 5.2:1. */
.psy-legal-strip {
  background: rgb(62, 81, 71);
  color: rgb(253, 238, 210);
  padding: 22px 18px 26px;
  /* box-sizing is load-bearing, not tidiness. Section A forces `width:100%` on every child of a
     mesh grid container, and the strip is one; without border-box the 18px of side padding is
     ADDED to that 100% and every page of the site scrolled sideways by exactly 36px at 390. */
  box-sizing: border-box;
  font-size: 14px;
  line-height: 1.6;
  text-align: center;
}
.psy-legal-strip nav {
  display: flex;
  flex-wrap: wrap;
  gap: 6px 22px;
  justify-content: center;
  margin-bottom: 10px;
}
.psy-legal-strip a {
  color: rgb(146, 212, 244);
  text-decoration: underline;
  /* 26px, not 17: these three are the links an auditor and a visitor both go looking for. */
  display: inline-block;
  min-height: 26px;
  padding: 4px 0;
}
.psy-legal-strip p { margin: 0; max-width: 62em; margin-left: auto; margin-right: auto; }

/* ---------------------------------------------------------------------------------------------
   E2. THE RELAXATIONS PAGE'S BODY COPY. It is placed as an extra row of the page's own Wix mesh
   (grid-area 3/1/4/2 on comp-ldfmmf1y's grid container) so it sits inside the cream band the page
   already paints, not under it. The band is rgb(225,215,190), L=0.702 — light — so this block is
   set in the site's own dark brown; the accent blue used for headings elsewhere would be the
   wrong direction here, which is the same trap section D1b documents. */
.psy-longform {
  max-width: 62em;
  margin: 0 auto;
  padding: 8px 20px 40px;
  color: rgb(60, 50, 40);
  font-size: 16px;
  line-height: 1.7;
  box-sizing: border-box;
}
.psy-longform h2 {
  font-family: fraunces, serif;
  font-size: 24px;
  line-height: 1.3;
  margin: 1.8em 0 .5em;
  color: rgb(19, 90, 122);
}
.psy-longform p { margin: 0 0 1em; }
.psy-longform ul { margin: 0 0 1.2em; padding-left: 1.3em; list-style: disc; }
.psy-longform li { margin: 0 0 .45em; list-style: disc; }
.psy-longform a {
  color: rgb(19, 90, 122);
  text-decoration: underline;
  display: inline-block;
  min-height: 26px;
  padding: 3px 0;
  overflow-wrap: anywhere;
}
@media (max-width: 1099px) {
  .psy-longform { padding: 8px 16px 32px; }
}


/* =============================================================================================
   SECTION F — THE MASTHEAD ON A NARROW SCREEN
   =============================================================================================
   MEASURED, ON THE RENDERED PIXELS, NOT ON THE COMPUTED STYLE. At 390 the third line of the
   masthead — "Accompagnement psychologique" — starts at x=126, and the page-background
   photograph's tree canopy reaches x≈215 at that height. Sampling the ground actually painted
   under that line (PIL, over the 390 screenshot, skipping the glyph colour itself) the darkest
   pixel behind it is rgb(72,99,86): 1.15:1 against the masthead's rgb(19,90,122). The first word
   of a line of the practice's own name is, in that band, invisible.

   qa_legibility passed this page. It photographs the ground at the centre of each run, the centre
   of that run is over pale sky, and one pixel measuring 4.5:1 is not the same as a legible line —
   the same trap section B2 records for the menu.

   WHY THE BACKGROUND CANNOT SIMPLY BE MOVED. The strip is 1440x6999 and the layer is 390 wide, so
   `object-fit:cover` is driven by WIDTH at every phone size: the whole width of the photograph is
   always shown and the tree is always on the left. `object-position:100% 0%` (the site's own
   inline style) cannot slide it away. Shrinking the type until the line clears the canopy would
   need ~14px, under the 12px floor in spirit and unreadable in fact.

   WHAT THIS DOES. It lays the site's own cream — rgb(250,236,210), the exact colour of the menu
   strip below it, sampled off the 1440 render — over the masthead band at 84% so the photograph
   still reads as a photograph behind it. Composited over that worst pixel the ground becomes
   rgb(221,214,190), which is 5.7:1 against the text: legible over the whole line, at every phone
   width, not only where the sky happens to be pale. Phone-scoped, because at 1024 and above the
   masthead sits to the right of the canopy and over the pale part of the photograph, where the
   site's own composition put it.
   ============================================================================================= */
@media (max-width: 1099px) {
  #SITE_HEADER #comp-ldfmessi { background: rgba(250, 236, 210, 0.84); }
}


/* =============================================================================================
   SECTION G — WHY THE BREAKPOINT IS 1099 AND NOT 1023, AND WHAT SITS BETWEEN 700 AND 1099
   =============================================================================================
   G0. THE BAND NOBODY LOOKS AT. Every rule above was originally written at `max-width: 1023px`,
   the width qa_legibility's phone axis implies. Swept in 40px steps from 320 to 1440
   (_scripts/_o5_psy_widthsweep.js) the document was WIDER THAN THE WINDOW at 1040 (1063) and at
   1080 (1083), on the homepage, the contact page, /tarifs/ and the authored legal pages alike —
   every template. Both standard viewports are clean, so no gate in this project could see it.

   It is not a decorative overhang. Named at 1040 by _scripts/_o5_psy_overflow_at.js: the menu ran
   x=-27..972, so "Accueil" was cut off at the left edge, and "Sophrologie et relaxation" in the
   masthead ended at x=1053, thirteen pixels off the right. The cause is Wix's own geometry: the
   three full-bleed bands are 1100px wide and centred with `margin-left:calc((100% - 980px)/2)`
   and `left:-67px`, and the content column inside them measures 1060. Below a 1100px window the
   desktop composition simply does not fit, and 1024-1099 was falling through the gap between the
   reflow's ceiling and the design's own floor. Every breakpoint above is therefore 1099px: the
   last width at which the desktop mesh cannot fit, not the last width that looks like a tablet.

   G1. THE GALLERY KEEPS FOUR COLUMNS ONCE THERE IS ROOM FOR FOUR. Section A6 drops the homepage
   grid to two columns, which is right at 390 and absurd at 1000, where two tiles are 500px square.
   Above 700 the site's own four-across composition fits and is restored.

   G2. A CAPPED MEASURE. Reflowed, a rich-text block is as wide as the window; at 1000px that is a
   140-character line, which is a readability defect of our own making rather than one the site
   ever had. The column is capped and centred once the window is wide enough for the cap to bite.
   Below 700 nothing changes, so the phone layout that was measured and screenshotted is untouched.
   ============================================================================================= */
@media (min-width: 700px) and (max-width: 1099px) {
  [data-testid="paginated-grid-gallery-items-container"] {
    grid-template-columns: repeat(4, 1fr) !important;
  }
  [data-testid="richTextElement"] {
    max-width: 760px !important;
    margin-left: auto !important;
    margin-right: auto !important;
  }
  .psy-longform, .o5-legal { max-width: 760px; margin-left: auto; margin-right: auto; }
}


/* =============================================================================================
   SECTION H — TWO THINGS THE REFLOW ITSELF BROKE, BOTH ONLY VISIBLE BY LOOKING
   =============================================================================================
   H1. THE PICTURES WERE BEING CUT, NOT FITTED — AND NO OVERFLOW CHECK COULD SAY SO.
   Section A5/A5a were written for `div[id^="comp-"] > wow-image > img`. This site's image
   component is `div.wixui-image > div[data-testid="linkElement"] > wow-image > img`: one wrapper
   deeper, so BOTH RULES MATCHED NOTHING and the inline `width:100%;height:100%;object-fit:cover`
   ran unopposed. With the component at 390 wide and its height still the desktop box's, the
   aspect ratio no longer matched the file and `cover` cropped the difference away INSIDE the
   element. On /tarifs/ that removed ~24px from each side of the two #manifestepsy posters: the
   headings read "AS LE CHOIX DE VOTRE PSYCHOLOGUE" and "S CONSÉQUENCES POUR LA PROFESSION".

   Nothing was painted outside the window, so the width sweep, qa_legibility's overflow axis and
   qa_client_bar were all green — a clipped picture does not scroll. This is the plain form of the
   warning in the plan: on a fixed-width Wix payload, device-width clips and the checks stay green.
   The selectors in A5/A5a now carry this site's actual wrapper as well; the rule is unchanged —
   `width:auto; max-width:100%; height:auto` fits a picture into the column without cropping it and
   without enlarging one that is already smaller than the column (the two payment logos on
   /tarifs/ are 116 and 118px wide and must stay that size).

   H2. THE INSTAGRAM ICON BECAME A 390px WHITE ELLIPSE. #comp-ldfmhn9y is a Wix stylable button
   with `border-radius:50%` and its label set to `display:none` — an icon in a 36px circle. The
   mesh rule in A2 gives every grid child `width:100%`, and D5 gives every stylable button
   `min-height:44px; display:flex` for the tap-target floor, so on a phone it stretched into a
   full-width white lozenge with a tiny glyph adrift in the middle — the same shape as the consent
   widget that shipped as a giant chevron on the Portuguese batch, and just as invisible to every
   gate: it is a link, it works, it is 390x60, so it passes the tap-target check comfortably.
   It is given back its circle, at 44px rather than the desktop's 36 so it stays thumb-sized, and
   centred in the column it used to fill.
   ============================================================================================= */
@media (max-width: 1099px) {
  #masterPage #comp-ldfmhn9y {
    width: 44px !important;
    max-width: 44px !important;
    height: 44px !important;
    margin-left: auto !important;
    margin-right: auto !important;
    align-self: center !important;
  }
  #masterPage #comp-ldfmhn9y a.StylableButton2545352419__root {
    width: 44px !important;
    min-width: 44px !important;
    height: 44px !important;
    min-height: 44px !important;
    padding: 0 !important;
  }
}


/* =============================================================================================
   SECTION I — THE SEVEN EMPTY WIDGET HOSTS
   =============================================================================================
   Wix's iframe-hosting component renders as `<div id="comp-…" class="comp-… _xg6_p"></div>` — the
   class's whole rule is `{-webkit-overflow-scrolling:touch; overflow:scroll}` — and the thing that
   filled it arrived at run time from a service this copy no longer talks to. Seven survive in the
   archived DOM: four on /relaxations-a-ecouter/ (two rows of 520x266, which is where the guided
   relaxations played) and three on /tarifs/ (516x141, 516x141, 516x286).

   They carry explicit pixel heights, so they ship as holes: measured at 1440
   (_scripts/_o5_psy_emptyband.js) a 580px band of nothing between the hero and the authored copy
   on /relaxations-a-ecouter/, and a 290px band of nothing between "Tarifs des consultations" and
   "Remboursement". "Empty placeholder blocks" is the first item on the client's rejection list,
   and both pages already SAY in their own words what is not there — /relaxations-a-ecouter/
   states that the recordings are not published on the page and that the relaxations are given in
   session. An empty scroll box adds nothing to that except the admission that this is a copy.

   They are hidden rather than deleted from the markup so the archived DOM stays intact and this
   decision stays reversible and visible in one place. Their parents are all `height:auto`, so the
   bands close completely; nothing else on either page moves sideways (width sweep, 320-1440).
   ============================================================================================= */
div[id^="comp-"]._xg6_p { display: none !important; }


/* =============================================================================================
   SECTION J — THE AUTHORED PAGES HAD NO GROUND UNDER THEM
   =============================================================================================
   THE DEFECT, SEEN NOT MEASURED. o5_20_mandatory.py replaces the whole of #PAGES_CONTAINER with a
   single `<div class="o5-legal">`. Every archived page paints its own band inside that container —
   dark sage on six pages, cream on /relaxations-a-ecouter/ — and the authored pages, having no
   band at all, put their body copy STRAIGHT ONTO THE PAGE-BACKGROUND PHOTOGRAPH. The photograph is
   `position:fixed`, so this is true at every scroll position and on every one of the four: the
   editor block, the address, the telephone, the e-mail and the whole "Titres et qualifications"
   paragraph of /mentions-legales/ sit as dark grey text over a tree and a green hillside.

   qa_legibility passed all three legal pages. A fullPage screenshot ALSO hides it, because a
   fixed layer is captured once at the top and the rest of the tall image comes out white — the
   defect is only visible in a viewport screenshot, which is why it survived a green board.

   THE FIX IS A GROUND, NOT A COLOUR CHANGE. Repainting the text would have to win against a
   photograph that is a different colour in every square inch; the honest repair is to give these
   pages the band every other page has. rgb(250,236,210) is the site's own cream — the menu strip's
   colour, sampled off the 1440 render — so the legal pages read as the same site rather than as
   something bolted on. Measured on it: body 15.6:1, links 6.2:1, headings 15.6:1.

   Specificity note: `.o5-legal` is also styled by an inline <style> block inside each page. That
   block sits ~500 bytes BEFORE the <link> to this file, so an equal-specificity rule here already
   wins; the id is used anyway so the outcome does not depend on that ordering surviving a rebuild.
   ============================================================================================= */
#PAGES_CONTAINER > .o5-legal {
  background: rgb(250, 236, 210);
  border-radius: 2px;
  box-shadow: 0 1px 14px rgba(40, 45, 40, 0.28);
  margin-top: 26px;
  margin-bottom: 34px;
  padding-left: 2em;
  padding-right: 2em;
}
@media (max-width: 640px) {
  #PAGES_CONTAINER > .o5-legal {
    margin-top: 0;
    margin-bottom: 0;
    padding-left: 1.15em;
    padding-right: 1.15em;
    box-shadow: none;
  }
}


/* =============================================================================================
   o7 visual review: THE TWO FRAMED PICTURES ON THE HOMEPAGE LOST THEIR FRAME ON A PHONE.
   The mandala (#comp-ldfmfxv9) and the portrait (#comp-ldfmga2n) each sit in a white box with a
   1px #d9d9d9 border (#comp-ldfmft6d, #comp-ldfmfxzr), inset 10px on every side by Wix's grid
   placement (`margin:10px 0 10px 0; left:10px`, box 20px wider than the picture). Section A2 sets
   every comp- box to `margin-left:0; width:100%`, so on a phone the picture covered its frame's
   left, right and top and the frame survived only as a white strip under it (home-p3, home-p4).
   Give the picture back the same 10px inset it has on the desktop. These two ids exist on the
   homepage only. */
@media (max-width: 1099px) {
  #masterPage #comp-ldfmfxv9,
  #masterPage #comp-ldfmga2n {
    margin: 10px !important;
    width: auto !important;
    left: 0 !important;
  }
}

/* o7 visual review: THE MAP CREDIT TOUCHES THE LEFT EDGE OF THE PHONE SCREEN.
   On a phone every rich-text block gets 14px side padding (section A, [data-testid=
   "richTextElement"]), but the map component #comp-ldfmgofn.psy-map is not rich text and A2 zeroes
   its margins, so ".psy-map__credit" started at x=0 (le_cabinet_contact_horaires-p1). The map image
   stays full-bleed like every other picture; only its caption is brought in line with the copy. */
@media (max-width: 1099px) {
  .psy-map__credit { padding-left: 14px; padding-right: 14px; }
}
