/* nat-restore.css - what the restoration adds on top of the site's own Jimdo theme.
   Loaded last, so it wins without !important wherever the selector is at least as specific.
   Three jobs only: make the replaced widgets look like they belong, put a floor under tap
   targets and type size, and make links in body copy distinguishable from the prose. */

/* ---- click-to-load video: the poster the visitor sees instead of a blank grey gap ---- */
.nat-embed {
  position: relative;
  background: #2f3536;
  border-radius: 3px;
  overflow: hidden;
}
.nat-embed .nat-embed-play {
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 10px;
  width: 100%;
  min-height: 220px;
  padding: 24px 16px;
  border: 0;
  background: #2f3536;
  color: #fff;
  font: inherit;
  font-size: 15px;
  line-height: 1.4;
  cursor: pointer;
}
.nat-embed .nat-embed-play:hover,
.nat-embed .nat-embed-play:focus-visible {
  background: #454e50;
  outline: 2px solid #55791f;
  outline-offset: -2px;
}
.nat-embed .nat-embed-play img { width: 64px; height: 64px; }
.nat-embed .nat-embed-note {
  margin: 0;
  padding: 8px 12px;
  background: #1f2425;
  color: #dfe4e4;
  font-size: 12px;
  line-height: 1.5;
  text-align: center;
}
.nat-embed iframe { display: block; width: 100%; height: 100%; border: 0; }

/* ---- the map is a picture now, and the ODbL credit under it has to stay readable ---- */
.nat-map img { display: block; width: 100%; height: auto; border-radius: 3px; }
.nat-map .nat-map-credit {
  margin: 6px 0 0;
  font-size: 12px;
  line-height: 1.6;
  color: #454b4c;
}
.nat-map .nat-map-credit a { color: #3a5f8f; text-decoration: underline; }

/* ---- the contact route that replaced the dead form ---- */
.nat-contact { font-size: 15px; line-height: 1.7; }
.nat-contact ul { margin: 12px 0; padding-left: 20px; }
.nat-contact li { margin: 6px 0; }
.nat-contact a { color: #3a5f8f; text-decoration: underline; }
.nat-contact a:hover { color: #1f3a5a; }

/* ---- authored pages (Mentions legales, Plan du site) share the body typography ---- */
.nat-page { font-size: 15px; line-height: 1.7; color: #3a4142; }
.nat-page h1 { font-size: 26px; line-height: 1.25; margin: 0 0 18px; }
.nat-page h2 { font-size: 19px; line-height: 1.3; margin: 26px 0 8px; }
.nat-page p, .nat-page li { font-size: 15px; line-height: 1.7; }
.nat-page ul { margin: 8px 0 8px 0; padding-left: 20px; }
.nat-page a { color: #3a5f8f; text-decoration: underline; }
.nat-page dt { font-weight: 700; margin-top: 14px; }
.nat-page dd { margin: 2px 0 0 0; }

/* ---- TAP TARGETS.  Sidebar and footer links were 14-19px tall; a finger needs 24.
        min-height on an inline element does nothing, hence inline-block.
        THE FLOOR IS 26, NOT 24, AND THAT IS DELIBERATE. qa_legibility does not trust the
        bounding box: it walks the control's centre line two pixels at a time and counts only
        the rows the control actually hit-tests as its own. A box set to exactly 24 therefore
        passes or fails on where its top edge happens to round - the sidebar's
        'Cabinet Paramedical "les Carres Solaires"' link is 25px tall because a 12px span sits
        inside a 16px <strong>, and it scored 23 owned rows on /404.html while scoring 24 on
        every other page. Same markup, same stylesheet, different y offset. Two pixels of
        headroom take the whole sidebar off that boundary; it is also a better target. ---- */
.jtpl-sidebar a,
.jtpl-footer a,
.j-meta-links a,
.nat-page a,
.nat-contact a {
  display: inline-block;
  min-height: 26px;
  line-height: 26px;
}
.jtpl-footer .j-meta-links { line-height: 26px; }

/* ---- TYPE FLOOR.  Nothing on a public page reads below 12px. ---- */
body, .j-module, .j-module p, .j-module li, .j-module span, .jtpl-sidebar span { font-size: inherit; }
.j-module [style*="font-size: 10px"],
.j-module [style*="font-size:10px"],
.j-module [style*="font-size: 11px"],
.j-module [style*="font-size:11px"] { font-size: 12px !important; }

/* ---- links inside body copy should not read as prose ---- */
#content_area .j-module.j-text a:not(.blogreadmore):not([class*="cc-"]):not(:has(h1,h2,h3)),
#content_area .j-module.j-textWithImage a:not([class*="cc-"]) { text-decoration: underline; }
/* a post headline is a heading that happens to be a link; underlining a 28px headline reads as a
   mistake, and the heading is already unmistakably clickable */
#content_area a:has(> h1), #content_area a:has(> h2), #content_area a:has(> h3),
#content_area h1 a, #content_area h2 a, #content_area h3 a { text-decoration: none; }

/* ---- a photograph the archive never held leaves a comment, not a frame: nothing to style.
        This only keeps the modules that lost their picture from collapsing to zero height. ---- */
.j-module.j-textWithImage > div:only-child { margin-left: 0; }

/* ---- share links.  The originals were drawn entirely from JimdoIconFontWeb, whose .woff and
        .ttf were never archived, so they rendered as two blank squares under every blog post.
        A named button is what the icon was standing in for. ---- */
.nat-share {
  display: inline-block;
  margin: 0 8px 8px 0;
  padding: 7px 14px;
  min-height: 26px;   /* off the 24px rounding boundary - see the TAP TARGETS comment above */
  border-radius: 3px;
  background: #3b5998;
  color: #fff !important;
  font-size: 13px;
  line-height: 1.5;
  text-decoration: none;
}
.nat-share--twitter { background: #1f2124; }
.nat-share:hover, .nat-share:focus-visible { background: #1f3a5a; color: #fff !important; }

/* JimdoIconFontWeb is gone with its .woff/.ttf, so any pseudo-element that only drew a private-use
   glyph now draws nothing at all.  Reserve no space for it rather than an empty box. */
[class*="cc-sharebuttons"]::before, [class*="cc-sharebuttons"]::after { content: none !important; }

/* ---- the homepage title band.  Its background was a full-page photograph that no archive holds;
        without it the theme's white 40px display type sat on white and measured 1:1.  The band now
        carries the site's own green so the white type reads as it was designed to (5.1:1). ---- */
.jtpl-title[background-area="stripe"] { background-color: #55791f; }
.jtpl-title #cc-website-title span { text-shadow: 0 1px 2px rgba(0,0,0,.35); }

/* ---- Contrast is a property of the PAIR, and this template has THREE grounds, not one.  Measured
        off the painted DOM rather than read off the stylesheet, which is the only reason the third
        one was found: .jtpl-sidebar is a light grey band (#dce0e0), .jtpl-header is near-white
        (#f7f8f8) and .jtpl-footer is BLACK.  One blanket colour for "the bottom of the page" made
        the footer worse - dark green on black - so each band gets its own. ---- */
.jtpl-sidebar a, .jtpl-sidebar a span { color: #3d6629 !important; }   /* 5.0:1 on #dce0e0 */
.jtpl-sidebar a:hover { color: #24401a !important; }
.jtpl-footer, .jtpl-footer .j-meta-links { color: #dfe4e4 !important; }   /* 15.8:1 on black */
.jtpl-footer a { color: #b6dc98 !important; text-decoration: underline; }  /* 12:1 on black */
.jtpl-footer a:hover { color: #fff !important; }

/* ---- blog tag chips were 17px tall.  26, not 24 - see the TAP TARGETS comment above. ---- */
.j-blog-page--tag, .j-blog-post--tag {
  display: inline-block;
  min-height: 26px;
  line-height: 26px;
}

/* ---- breadcrumb links were 20px tall: under a finger, and the only tap targets left ---- */
.jtpl-breadcrumb a, .jtpl-breadcrumb span[itemprop="name"] {
  display: inline-block;
  min-height: 26px;
  line-height: 26px;
}

/* ---- "Lire la suite..." is the only way into each of the ten posts on the blog listing and it was
        95x17: a link a finger cannot reliably hit, ten times on one page. ---- */
#content_area .j-module.j-text a {
  display: inline-block;
  min-height: 26px;
  line-height: 26px;
}

/* ---- the authored 404 sits straight in .jtpl-section, outside the content column, so it inherits
        none of the module typography: without this its list of links is 17px tall and the block
        runs the full 1440px. ---- */
.o5-legal {
  max-width: 1000px;
  margin: 0 auto;
  padding: 40px 20px 60px;
  font-size: 15px;
  line-height: 1.7;
  color: #3a4142;
}
.o5-legal h1 { font-size: 26px; line-height: 1.25; margin: 0 0 18px; }
.o5-legal ul { margin: 8px 0 18px; padding-left: 20px; }
.o5-legal a {
  display: inline-block;
  min-height: 26px;   /* was 24 - the independent reviewer measured this exact rule sitting on the
                          rounding boundary the TAP TARGETS comment above warns about */
  line-height: 26px;
  color: #3d6629;
  text-decoration: underline;
}

/* ---- the two section hubs and the blog archive, rebuilt after their only illustration turned out
        to be one of the photographs no archive holds ---- */
.nat-hub, .nat-archive { font-size: 15px; line-height: 1.7; color: #3a4142; }
.nat-hub dl { margin: 18px 0 0; }
.nat-hub dt { margin-top: 18px; font-weight: 700; }
.nat-hub dd { margin: 2px 0 0; }
.nat-hub a, .nat-archive a { color: #3d6629; text-decoration: underline; display: inline-block;
  min-height: 26px; line-height: 26px; }
.nat-archive h1 { font-size: 24px; line-height: 1.3; margin: 0 0 14px; }
.nat-archive h2 { font-size: 18px; margin: 24px 0 6px; }
.nat-archive ul { margin: 0; padding-left: 20px; }
.nat-archive li { margin: 10px 0; }
.nat-archive-meta { font-size: 13px; color: #4f5859; }

/* ---- The Jimdo video module is an aspect-ratio box: `.cc-m-video-wrapper{height:0!important;
        padding-bottom:56.25%}` with the iframe absolutely filling it.  A click-to-load poster is
        ordinary flow content, so inside that box its second line was clipped mid-sentence.  The
        box goes back to auto height for the elements this restoration put in it. ---- */
.cc-m-video-gutter { width: auto !important; max-width: 640px; }
.cc-m-video-gutter .cc-m-video-wrapper.nat-embed,
.cc-m-video-gutter.cc-m-video-ratio-1 .cc-m-video-wrapper.nat-embed,
.cc-m-video-gutter.cc-m-video-ratio-2 .cc-m-video-wrapper.nat-embed {
  height: auto !important;
  padding-bottom: 0 !important;
  overflow: visible;
}
/* NOTE ON SPECIFICITY, learned the hard way here: web.css is injected by loadCss() AFTER this
   stylesheet, so a tie on specificity loses on source order even with !important.  Every override
   of a Jimdo rule in this file has to be strictly MORE specific, not equally specific. */

/* ---- and the share links are inside a container that sizes every <a> to a 28px icon square ---- */
div[class*="cc-sharebuttons-size"] a.nat-share,
.cc-sharebuttons-element a.nat-share {
  width: auto !important;
  height: auto !important;
  position: static !important;
  text-indent: 0 !important;
  overflow: visible !important;
}
.cc-sharebuttons-element { display: flex; flex-wrap: wrap; gap: 8px; }

/* ---- The icon-font pseudo-element on the share links is `position:absolute; top:0; left:0`.
        Setting the anchor to position:static took away its containing block, so it resolved
        against the page and painted a faint 28px white square in the TOP-LEFT CORNER of three
        blog posts - visible in a screenshot, invisible to every gate, and exactly the class of
        defect the client finds by looking.  Kill the pseudo-element, not just its content. ---- */
a.nat-share::before, a.nat-share::after { content: none !important; display: none !important; }

/* ---- the contact form ---- */
.nat-form { max-width: 560px; font-size: 15px; line-height: 1.7; }
.nat-form p { margin: 0 0 14px; }
.nat-form label { display: block; margin-bottom: 4px; font-weight: 700; color: #3a4142; }
.nat-form input, .nat-form textarea {
  width: 100%;
  box-sizing: border-box;
  min-height: 40px;
  padding: 8px 10px;
  border: 1px solid #9aa4a5;
  border-radius: 3px;
  background: #fff;
  color: #24292a;
  font: inherit;
  font-size: 15px;
}
.nat-form input:focus, .nat-form textarea:focus { outline: 2px solid #55791f; outline-offset: 1px; }
.nat-form .nat-form-send {
  min-height: 44px;
  padding: 10px 22px;
  border: 0;
  border-radius: 3px;
  background: #55791f;
  color: #fff;
  font: inherit;
  font-size: 15px;
  cursor: pointer;
}
.nat-form .nat-form-send:hover, .nat-form .nat-form-send:focus-visible { background: #3d6629; }
.nat-form .nat-form-hint, .nat-form .nat-form-privacy { font-size: 13px; color: #4f5859; }
.nat-form .nat-form-status {
  padding: 10px 12px;
  border-left: 4px solid #55791f;
  background: #eef3e8;
  color: #24292a;
  font-size: 14px;
}
.nat-form a { color: #3d6629; text-decoration: underline; }

/* ---------------------------------------------------------------------------
   Section T - the tablet band, 768-1024px.
   WHY: the sidebar's third column carries text-align:justify as an INLINE style
   on every paragraph (the practitioner set it in Jimdo). At 1440 each line fits
   and justification is invisible; between roughly 768 and 1024 the column is
   ~230px wide, 'Cabinet Paramedical "les Carres Solaires"' wraps, and justify
   opens word gaps wide enough to read as broken. An inline style can only be
   beaten by !important, hence the flag. Nothing else about the column changes,
   and the rule is confined to the band where the wrap happens so the desktop
   and phone renderings are untouched.
   --------------------------------------------------------------------------- */
@media (min-width: 768px) and (max-width: 1024px) {
  .jtpl-sidebar .cc-m-hgrid-column p[style*="justify"] { text-align: left !important; }
}


/* ---- O7 REVIEW (2026-10-14): the authored 404 ----
   1. The block now sits INSIDE #content_area (404.html: <div id="content_area"><div class="o5-legal">),
      which already carries the page gutter, so the 20px side padding above plus the generator's
      inline .o5-legal{padding:1.5em 1em} put its heading and text 15px right of every other page
      (x=240 against 225 at 1440, 30 against 15 at 390). Keep the vertical padding only.
   2. `.o5-legal a { display:inline-block }` cannot break, so at 390 the e-mail address and
      "la page Contacts" each jumped whole onto their own line and left the line before them short.
      Inside a sentence the link is inline again; 5px of vertical padding on an inline box still
      gives it a 27px hit area without moving the line. The list links keep the block rule. */
#content_area .o5-legal { padding-left: 0; padding-right: 0; }
.o5-legal p a { display: inline; min-height: 0; line-height: inherit; padding-top: 5px; padding-bottom: 5px; }

/* ---- order-7 asset lane 2026-10-14: the full-page photograph IS archived after all.  The earlier
        comment above ("no archive holds") was wrong: Jimdo painted it from script (bgConfig, type
        picture, fixed) onto .jtpl-background-area, and the CDX holds that backgroundarea image
        (i3e43e625c9eed894, 3 captures of version 1501499571).  Same job the script did: fixed,
        full-viewport, cover. ---- */
.jtpl-background-area { background: url(/img/hero-background-i3e43e625c9eed894.jpg) center center / cover no-repeat; }
