/* restore extras — generated by restore_04_polish.py */

/* Consent overlays: the restore ships no analytics or third-party tracking at all, so there
   is nothing to consent to. Their scripts are gone too, meaning the banner can never be
   dismissed and would cover the top of every page. Removing the markup is unreliable when a
   JS bundle re-renders it, so it is hidden here as well. */
.cookies-banner, .cookies-banner-content, .cookie-banner, .cookie-consent, .cookie-notice,
.cc-window, .cc-banner, #cookie-law-info-bar, #cookieChoiceInfo, .gdpr-banner,
#tarteaucitronRoot, .consent-overlay, .cookiebar {
  display: none !important;
}
body.cookie-banner-open, body.has-cookie-banner, html.cookies-open {
  overflow: auto !important;
}

/* Dead account/login modals left by the CMS (no backend on a static host) */
.modal-login, #loginModal, .login-modal { display: none !important; }

/* Carousel slots the platform's JS bundles would have filled at runtime: without a working
   bundle they stay as <img> elements with no src and render as broken-image icons. Nothing is
   lost by hiding them — they never had content in the restore. */
img:not([src]), img[src=""], img[src="#"] { display: none !important; }

/* The client's backlink block must read as the page's own copy. Where a theme only colours
   links inside specific containers, the anchor would otherwise look like plain text — inherit
   the surrounding colour but keep an underline so it is still visibly a link. */
.content-wraparea a { color: inherit; text-decoration: underline; }

/* A few px of horizontal overflow on phones (an absolutely-positioned login list, a wide footer
   logo) makes the whole page pannable sideways, which reads as broken.
   NB: use `clip`, never `hidden`, and never on html together with height:100%. `overflow:hidden`
   turns the element into a scroll container: on themes that set html{height:100%} it stops body's
   overflow propagating to the viewport, the window stops scrolling entirely and every
   scroll-driven behaviour (sticky nav, back-to-top, in-page anchors, PageDown/End) dies.
   `clip` suppresses the sideways pan without creating a scroll container. */
body { overflow-x: clip; }
/* ---- end generated block; anything below is preserved across re-runs ---- */

/* =========================================================================================
   psiclinicaformativa.com - restoration extras.
   Scoped to the selectors they name; nothing here changes the site's type or its colours
   beyond the two legibility repairs named below.
   ========================================================================================= */

/* ---- 1. the phone. ------------------------------------------------------------------------
   GrandCollege is a 2013 Skeleton build: .container is 960px, three wrappers are 980px and
   div.top-navigation.container and div.footer-wrapper carry min-width:980px. There is not one
   @media rule in any of the theme's fourteen stylesheets, so at 390px the page measured
   1001px wide - the visitor sees the left 40% of every page and `overflow-x: clip` (already in
   the generated block above) only hides the fact that the rest is unreachable. The page meta
   already says width=device-width, so one breakpoint is enough: below the grid's own width,
   every fixed width becomes fluid and every column stacks. Nothing above 1000px is touched,
   which is where the design was built and where it still renders exactly as it did. */
@media (max-width: 1000px) {
  .container { width: auto !important; max-width: 100%; padding-left: 14px; padding-right: 14px; }
  .container .columns, .container .column,
  .container .one.column, .container .two.columns, .container .three.columns,
  .container .four.columns, .container .five.columns, .container .six.columns,
  .container .seven.columns, .container .eight.columns, .container .nine.columns,
  .container .ten.columns, .container .eleven.columns, .container .twelve.columns,
  .container .thirteen.columns, .container .fourteen.columns, .container .fifteen.columns,
  .container .sixteen.columns, .container .fifteen.columns.wrapper,
  .container .sixteen.columns.wrapper {
    width: auto !important; float: none !important;
    margin-left: 0 !important; margin-right: 0 !important;
  }
  .gdl-page-item, .gdl-page-float-left, .gdl-page-float-right,
  .gdl-right-sidebar, .gdl-left-sidebar, .right-sidebar-wrapper {
    width: auto !important; float: none !important; margin-left: 0 !important;
  }
  div.inner-header-wrapper, div.navigation-wrapper, div.content-wrapper,
  div.content-bottom-gimmick, div.container .top-navigation-wrapper-gimmick {
    width: auto !important; margin-left: 0 !important;
    padding-left: 0 !important; padding-right: 0 !important;
  }
  div.top-navigation.container, div.footer-wrapper, div.header-wrapper,
  div.content-wrapper, body, html { min-width: 0 !important; }
  img, iframe, object, embed { max-width: 100%; height: auto; }
  table { max-width: 100%; }

  /* the menu: a horizontal superfish bar becomes a stacked list, and its hover submenus are
     laid out in flow - there is no hover on a phone, so a submenu that only appears on hover
     is a menu item a phone visitor can never reach. */
  #main-superfish-wrapper, .menu-wrapper { float: none !important; width: auto !important; }
  ul.sf-menu { float: none !important; width: auto !important; }
  ul.sf-menu > li { float: none !important; width: auto !important; display: block; }
  ul.sf-menu a { padding: 11px 14px !important; line-height: 1.3; }
  ul.sf-menu ul { position: static !important; top: auto !important; left: auto !important;
                  width: auto !important; display: block; }
  ul.sf-menu ul a { padding-left: 32px !important; font-size: 13px; }
  .sf-sub-indicator { display: none; }

  /* the header strip: logo, phone and e-mail stack instead of sitting side by side */
  .top-navigation-left, .top-navigation-right, .copyright-left, .copyright-right,
  .social-wrapper, .logo-wrapper { float: none !important; width: auto !important;
                                   text-align: left; }
  .top-navigation-right { margin-top: 6px; }

  /* widgets and sliders that were sized for the 940px column */
  .gdl-content-slider, .anythingSlider, .anythingSlider .anythingWindow,
  .flexslider, .nivoSlider, .elastislide-wrapper { width: auto !important; max-width: 100%; }
  #searchform, #search-text { width: auto !important; max-width: 100%; }
  #search-text input { width: 100% !important; box-sizing: border-box; }
}

/* ---- 2. tap targets. ------------------------------------------------------------------
   qa_legibility: "Aviso Legal" 62x14 and "Política Privacidad" 99x14 in the copyright bar are
   the only links on the site under the 24px floor. The bar's own height is unchanged; the
   links simply own the space around their text. */
.copyright-left a, .copyright-right a { display: inline-block; padding: 6px 3px; }

/* ---- 3. the grey pull-quote. -----------------------------------------------------------
   The author set color:#999999 inline on .shortcode-block-quote-center, which measures 2.85:1
   on white where 4.5 is wanted. The words and the italic voice of the quote are untouched;
   only the grey is taken down to a readable one (#636363 = 5.9:1). !important is required
   because the colour is an inline attribute on the element. */
.shortcode-block-quote-center, .shortcode-block-quote-left, .shortcode-block-quote-right {
  color: #636363 !important;
}

/* ---- 4. the search results page --------------------------------------------------------
   The theme has no styling for a result list: WordPress's own search template was never
   captured, so /buscar/ renders what js/site-search.js writes. */
ul.gdl-search-results { list-style: none; margin: 18px 0 0; padding: 0; }
ul.gdl-search-results li { padding: 14px 0; border-bottom: 1px solid #e3e3e3; }
ul.gdl-search-results li a { font-size: 17px; font-weight: 600; text-decoration: none; }
ul.gdl-search-results li a:hover { text-decoration: underline; }
.gdl-search-snip { display: block; margin-top: 4px; color: #5d5d5d; font-size: 14px; line-height: 1.5; }
#site-search-results h3 { margin: 0 0 6px; }

/* ---- 5. the home's video slider --------------------------------------------------------
   The four YouTube embeds are gone with their player; what is left is the still the restore
   saved, plus the video's own title. */
img.restored-video-still { display: block; width: 100%; height: auto; border-radius: 3px; }

/* ---- 6. the answer written next to the contact form's Enviar button --------------------- */
.restore-formsay { margin: .75em 0 0; padding: .6em .8em; border-radius: 4px; font-size: .95em; line-height: 1.45; }
.restore-formsay.is-good { color: #14532d; background: #dcfce7; border: 1px solid #86efac; }
.restore-formsay.is-bad { color: #7f1d1d; background: #fee2e2; border: 1px solid #fca5a5; }

/* ---- 7. the home's "Videos" widget. ----------------------------------------------------
   AnythingSlider sizes its window from the first panel at init time, and the panels here hold
   lazy-loaded stills that the theme's own preloader keeps invisible until it has finished - so
   the window came out 180x35 at 1440 and zero-height at 390, showing a sliver of one photograph
   and six nav dots floating over the next heading. The six entries are a fixed list of four
   video stills and two Dailymotion links; there is nothing to slide through that a grid does not
   show at once, and a grid cannot be mis-sized by a race with an image load. The slider's own
   controls go with it - a dead arrow is worse than no arrow. Scoped to .gdl-content-slider,
   which exists on the homepage only. */
.gdl-content-slider div.anythingSlider,
.gdl-content-slider .anythingWindow,
.gdl-content-slider .anythingBase {
  width: auto !important; height: auto !important; position: static !important;
  left: auto !important; top: auto !important; overflow: visible !important;
  padding: 0 !important; margin: 0 !important;
}
.gdl-content-slider ul {
  display: grid !important; grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 24px 26px; list-style: none !important;
  margin: 12px 0 0 !important; padding: 0 !important;
  width: auto !important; height: auto !important; position: static !important;
}
.gdl-content-slider ul > li {
  width: auto !important; height: auto !important; float: none !important;
  display: block !important; position: static !important; margin: 0 !important; padding: 0 !important;
}
.gdl-content-slider ul > li.cloned { display: none !important; }
.gdl-content-slider ul > li > div > div[style] { max-width: 100% !important; }
.gdl-content-slider .anythingControls, .gdl-content-slider .arrow,
.gdl-content-slider .start-stop, .gdl-content-slider .thumbNav { display: none !important; }
.gdl-content-slider ul > li strong { display: block; margin-top: 8px; line-height: 1.4; }
@media (max-width: 760px) { .gdl-content-slider ul { grid-template-columns: 1fr; } }

/* ---- 8. "Nueva Aula Virtual". ----------------------------------------------------------
   The block's text is white (inline style, the author's own) and its background is
   under-slider-right.png - a 14x88 WHITE gradient at alpha 2-58/255, i.e. an overlay meant to
   sit on a dark panel. Whatever was dark behind it is not in the capture, so the block rendered
   white on white and the words were invisible at both widths. The panel is given the same dark
   tone the hero's own caption box uses (sampled: rgb(73,71,68)), which is what the overlay and
   the white type were drawn for. Nothing in the markup changes. */
div.under-slider-right { background-color: #494744; }
div.under-slider-right h5 { margin-bottom: 6px; }

/* ---- 9. the page title's rule line on narrow screens. ---------------------------------
   div.gdl-page-caption is a fixed-height bordered strip that the theme floats beside the title.
   When the title wraps - which it does at 390px - the line crosses the second line of the
   heading. Below the grid width it becomes an ordinary rule under the whole title. */
@media (max-width: 1000px) {
  /* NOTE, with the evidence: `display:none` on this divider was tried and REVERTED. The theme's
     own rule gives it `overflow:hidden`, which makes it a block formatting context, and hiding it
     let the page body wrap around the <h1> on every inner page at 390px - the title ended up in a
     left-hand column with the running text beside it (seen on /aviso-legal/ at 390). The version
     below is the one measured good on the legal pages. On the HOMEPAGE a 1px rule still crosses
     the second line of the wrapped title: that line is NOT this element (hiding this element did
     not remove it), and identifying it needs one live measurement of what paints there. */
  div.gdl-page-caption { float: none !important; clear: both; width: auto !important;
                         height: 0 !important; padding: 0 !important; margin: 10px 0 18px; }
}

/* ---- 10. the rest of the tap targets. -------------------------------------------------
   qa_legibility, round 2: the sidebar widgets' titles, the "Leer Más" of the director's card,
   and "Seguir Leyendo →" on the blog templates are 14-19px tall links that are not inside a
   sentence, so WCAG 2.5.8's prose exemption does not cover them. They own their line box
   instead; no text, colour or position changes. */
.right-sidebar-wrapper a, .footer-widget-wrapper a,
.recent-post-widget-title a, .personnal-widget-excerpt a,
.gdl-recent-post-widget a, .blog-continue-reading, a.blog-continue-reading {
  display: inline-block; padding-top: 5px; padding-bottom: 5px; line-height: 1.45;
}
.right-sidebar-wrapper .recent-post-widget-thumbnail a,
.footer-widget-wrapper .recent-post-widget-thumbnail a { padding: 0; }

/* ---- 11. recent-post widgets with no thumbnail. ---------------------------------------
   66 of these sidebar/footer items pointed at a photograph the archive never captured. The empty
   95px box has been taken out of the markup; the theme's indent beside it is cancelled here, for
   any item that has no thumbnail image at all, so the title starts at the edge of the column. */
.recent-post-widget:not(:has(.recent-post-widget-thumbnail img)) .recent-post-widget-context {
  margin-left: 0 !important;
}

/* ---- 12. the course tables on a phone. -------------------------------------------------
   /talleres/ and the 13 course pages print a three-column table (code, title, teacher) that is
   wider than 390px: its third column simply ran off the right edge, unreachable, because
   `overflow-x: clip` on body stops the page panning sideways. Making the table its own scroll
   container at narrow widths keeps every column reachable without the page itself moving. */
@media (max-width: 1000px) {
  table.course-table, .gdl-page-content table, .blog-thumbnail-context table {
    display: block; width: 100% !important; max-width: 100%;
    overflow-x: auto; -webkit-overflow-scrolling: touch;
  }
}

/* ---- 13. blog and listing titles as tap targets. --------------------------------------
   A post title is the whole text of its heading, so WCAG 2.5.8's "link in a sentence" exemption
   does not cover it and qa_legibility measures the line box: at 390px "Artículo de interés 2"
   owned 22 of the 24 rows it needs. The type is unchanged; the anchor owns four pixels above
   and below its line. */
.blog-thumbnail-title a, .blog-item-holder h2 a, h2.blog-thumbnail-title a {
  display: inline-block; padding: 4px 0; line-height: 1.35;
}

/* ---- 14. the three blocking classes qa_legibility found on the homepage. ---------------
   (a) OVERFLOW 685px in a 390px viewport: div.under-slider-left is 660px wide and
   div.under-slider-right 280px, both floated, and the faux-column trick on the right one
   (margin-bottom:-1000px; padding-bottom:1000px) keeps a phone-height band of colour below the
   fold. None of that was in the responsive layer above because the rule lives in style.css under
   a different name than the grid's.
   (b) "TEXT under 12px x13": the theme sets the post dates and the blog info line in 11px. A gate
   that blocks body copy under 12px is right about a date line a visitor is meant to read; 12px is
   the smallest size that passes and the smallest change that fixes it.
   (c) The portfolio title "Máster Psicología Clínica. IX Edición" is a 17px-tall standalone link.
   Same treatment as the blog titles: it owns the space around its own line. */
@media (max-width: 1000px) {
  div.under-slider-left, div.under-slider-right {
    width: auto !important; float: none !important; margin-left: 0 !important;
    margin-bottom: 0 !important; padding-bottom: 14px !important;
  }
}
div.blog-item-holder .blog-item0 .blog-thumbnail-date,
div.blog-item-holder .blog-item1 .blog-thumbnail-info,
div.blog-item-holder .blog-thumbnail-date { font-size: 12px; }
h2.portfolio-thumbnail-title a, .portfolio-thumbnail-title a {
  display: inline-block; padding: 4px 0; line-height: 1.35;
}

/* ---- 4. order-7 fixer: the shortcode columns stack on a phone. ---------------------------
   The homepage's "Proximos Cursos Online / Presenciales" pair is `div.shortcode1-2 >
   div.eight.columns`. The theme sizes the wrapper by PERCENTAGE (`.shortcode1-2{width:48%;
   float:left}`), and section 1 above only released the `.container .eight.columns` width, not the
   wrapper, so at 390 the two courses sat side by side with ~80px of text each and the copy was
   cut mid-word ("Modul", "Reconocimie"). The same rule covers the client's block that sits in the
   second column. Every fractional shortcode wrapper becomes a full-width block below 768px. */
@media (max-width: 768px) {
  .shortcode1-2, .shortcode1-3, .shortcode2-3, .shortcode1-4 {
    width: auto !important; float: none !important; margin-right: 0 !important;
  }
  .shortcode1-2 .columns, .shortcode1-3 .columns, .shortcode2-3 .columns {
    width: auto !important; float: none !important; margin-left: 0 !important; margin-right: 0 !important;
  }
  .shortcode1-2 .blog-thumbnail-image, .shortcode1-3 .blog-thumbnail-image { max-width: 100%; }
}

/* ---- 5. order-7 fixer: the section-heading dropcap was white on white. --------------------
   `div.gdl-header-dropcap` is a 32px circle holding a 10x10 all-white icon (/img/Search-*.png).
   The colour that should fill the circle came from the theme's generated colour sheet, which was
   never archived, so every section heading ("Noticias", "Videos", "Servicios", "Direccion"...)
   was indented ~42px behind an invisible disc. Inventing the colour would be a guess, so the empty
   disc is withdrawn and the headings sit on the content's left edge. */
div.gdl-header-dropcap { display: none !important; }

/* ---- 15. order-7 round of 2026-10-20: three layout slips the visual review named. -----------
   (a) THE TWO PAGES WE WROTE (/404.html, /politica-de-cookies/) put their <h1> straight into
   .content-wrapper, without the theme's page-title frame (div.sixteen.columns > h1.gdl-page-title
   + div.gdl-page-caption) that every archived page uses. On the 404 the theme's own
   h1.gdl-page-title{float:left} then pulled the first paragraph up beside the title; on the
   cookies page the bare <h1> had no rule and no gutter. This gives a title that is the FIRST
   CHILD of .content-wrapper - which only those two pages have, every archived page nests it - the
   frame's look: the same 18px Georgia, the same #65a2be rule under it, the same 10px column
   gutter the sixteen-column grid gives the text on /aviso-legal/. No words change. */
div.content-wrapper > h1:first-child {
  float: none !important; height: auto !important; display: block;
  font-size: 18px; line-height: 1.3; font-weight: normal;
  margin: 10px 10px 20px; padding: 0 22px 13px 0;
  border-bottom: 1px solid #65a2be;
}
div.content-wrapper > h1:first-child ~ p { margin-left: 10px; margin-right: 10px; }
/* (b) /servicios/ AT 390: the theme floats every "Leer Más" button (a.portfolio-read-more
   {float:left}). On a desktop each teaser is itself a floated column and so contains it; once the
   phone layer above un-floats the columns, the button escaped its teaser and the next teaser's
   heading - "Terapia de Pareja.", the one whose thumbnail the archive did not keep - printed on
   the same line beside it. Each teaser now contains its own float. */
@media (max-width: 1000px) {
  .portfolio-item { display: flow-root; }
}
/* (c) /contacto/ AT 390: the form's first label sat on the last line of the opening hours with no
   gap; at 1440 the two-column layout separates them. The form gets the gap its own list items
   already keep between fields (20px). */
@media (max-width: 1000px) {
  div.contact-form-wrapper { margin-top: 20px; }
}
/* (d) On those same two pages of ours the in-text links ("página principal", "contacto") were the
   body grey with no underline, i.e. invisible as links on the one page whose whole job is to send
   the visitor somewhere else. Underlined in their own colour; scoped like (a). */
div.content-wrapper > h1:first-child ~ p a { text-decoration: underline; }

/* ---- 16. o7 r6 (2026-10-20): what the gate's six-page sample never measured. ---------------
   o4_accept runs qa_legibility on 6 of this site's 51 pages, and they passed. Run over all 51 at
   all four widths, the gate FAILED: 12 blocking findings, all on two pages outside the sample.
   (a) /matricularse/: the WooCommerce breadcrumb ("Inicio / Matricularse") is .woocommerce
       .woocommerce-breadcrumb {font-size: .92em} of 12px = 11px type, and its one link, back to the
       homepage, owned a 12px line - 4 x TEXT under 12px and 4 x UNDER24. 11 -> 12px (one pixel, the
       same step section 14 took for the theme's own small type) and a 24px line for the link.
   (b) /taller-autoestima/: the course's own presentation PDF ("Descragar Presentacion del Curso",
       the clinic's spelling, kept) is the h5 under "Precio", an inline link 14px tall - 4 x UNDER24.
       It is the only <h5><a> on the site (measured), and the only way to the course's poster.
       Made an inline-block on a 24px line; type, colour and words unchanged. */
.woocommerce nav.woocommerce-breadcrumb, .woocommerce-page nav.woocommerce-breadcrumb { font-size: 12px; line-height: 24px; }
.woocommerce nav.woocommerce-breadcrumb a, .woocommerce-page nav.woocommerce-breadcrumb a { display: inline-block; line-height: 24px; }
h5 > a[href$=".pdf"] { display: inline-block; line-height: 24px; }
/* (c) THE PAGE TITLE'S RULE THROUGH ITS OWN SECOND LINE - the line section 9 could not identify.
       It is the title's own border: the theme writes h1.gdl-page-title { height: 18px;
       border-bottom: 1px solid #65a2be } - a box pinned to ONE line - so a title that wraps keeps
       an 18px box and its rule is drawn through the second line of text. Measured with the theme's
       Georgia 18px over all 29 titled pages: 11 wrap at 390 (the homepage's among them) and one,
       /course/trastorno-deficit-...-tdah-.../ (985px of text in a 918px column), wraps on desktop
       too. Below 1000px the divider beside the title is already turned into a rule under it
       (section 9), so the title's box may simply follow its text there. On desktop the 18px box is
       what keeps the blue rule level with the divider's grey one on every one-line title (its text
       would be 18.5px, the inherited line-height), so it is released on the one page that wraps,
       by that page's own body class. */
@media (max-width: 1000px) { h1.gdl-page-title { height: auto; } }
body.postid-1874 h1.gdl-page-title { height: auto; }
