/*
 * Alfa Constructions — design tokens and site CSS.
 *
 * WHERE THIS CAME FROM
 * Migrated (Nov 2026) out of the WordPress Customizer's "Additional CSS"
 * (wp_custom_css post 6418, 10,088 bytes). That CSS lived only in the database:
 * unversioned, invisible to anyone reading the theme, and larger than the whole
 * child theme on disk. The Customizer field is now empty and points here.
 *
 * THREE SELECTOR BUGS WERE FIXED ON MIGRATION
 * Each was a misplaced comma that silently turned a scoped rule into a global
 * one. They are marked "BUG FIX" below with the original text, because fixing
 * them changes rendering site-wide and that change should be traceable.
 *
 * CONVENTION
 * The asset CDN serves theme CSS with no version string and caches it for a
 * long time, so changing this file means bumping its name (-v3, -v4, ...) and
 * the enqueue in functions.php. Same convention as ac-elements-v2.css.
 */

/* ===================================================================
 * Tokens
 * =================================================================== */

:root {
	/* Brand.
	   --ac-olive is the fill. It measures 3.41:1 on white, which clears the 3:1
	   bar for large text, fills and graphics but fails the 4.5:1 bar for body
	   text, so it must not carry 14-16px copy.
	   --ac-olive-ink is the text-safe companion: 6.69:1 on white, and 6.69:1
	   under white text, so it works as ink and as a filled background. */
	--ac-olive: #7b953c;
	--ac-olive-ink: #4f6320;
	--ac-olive-hover: #637732;

	/* Neutrals */
	--ac-ink: #2b2b2b;
	--ac-white: #ffffff;
	--ac-grey-mid: #444444;
	--ac-grey-soft: #cccccc;
	--ac-grey-wash: #f7f7f7;
	--ac-footer-bg: #111111;

	/* The hairline every form field already draws itself with. Named here so a
	   new control inherits the right one instead of guessing. */
	--ac-field-border: #dedede;

	/* The one hue outside the palette, and only for errors — Contact Form 7
	   prints its validation tips in exactly this red, so the field border and
	   the summary banner match it rather than introducing a second one. */
	--ac-error: #dc3232;

	/* Type scale, as the site actually uses it. */
	--ac-text-sm: 14px;
	--ac-text-base: 16px;
	--ac-text-lg: 22px;
	--ac-text-xl: 28px;

	/* Reading measure. Expressed in rem, NOT ch: `ch` resolves against the
	   font-size of the element it is used on, so 68ch on a 28px heading is
	   1089px while 68ch on 16px body copy is 622px — capped blocks would not
	   line up with each other.
	   NOTE the root here is 10px (this theme sets html{font-size:10px}), not
	   the usual 16px, so 1rem = 10px. 62.2rem is 622px, which is 68ch of
	   16px Open Sans (1ch measures 9.14px). If the root size ever changes,
	   this number has to change with it. */
	--ac-measure: 62.2rem;

	/* Spacing */
	--ac-space-sm: 20px;
	--ac-space-md: 30px;
	--ac-space-lg: 40px;
}

/* ===================================================================
 * Γενικά Στυλ & Διορθώσεις Plugin
 * =================================================================== */

/* Στυλ για τα στοιχεία λίστας του Contact Form 7 */
span.wpcf7-list-item {
	display: inline-block;
	padding-right: 5px;
}

.single-page-section { margin-top: 35px; }

.navbar-nav li.drop ul.dropdown li a { text-align: left; }
/* Both dropdown states put white words on the fill, which makes the fill ink:
   white on --ac-olive measured 3.38:1, on --ac-olive-ink it is 6.69:1. */
.navbar-nav li.drop ul.dropdown li a:hover {
	background-color: var(--ac-olive-ink);
	color: var(--ac-white);
}
.navbar-nav li.drop ul.dropdown li.active > a {
	background-color: var(--ac-olive-ink);
	color: var(--ac-white) !important;
}

.blog-section .blog-box .blog-post img { width: 100%; }

/* Γενικό στυλ για όλους τους συνδέσμους (links).
 * THE FILL-AND-INK RULE (DESIGN.md): --ac-olive is a fill, --ac-olive-ink is
 * ink. Link text is ink. The old var(--ac-olive) measured 3.41:1 on white and
 * failed WCAG 1.4.3 for normal text; --ac-olive-ink is 6.69:1 and passes. On
 * the two other page backgrounds the site uses it is 5.9:1 (#f1f1f1) and
 * 6.3:1 (#f7f7f7). Owner decision, Nov 2026.
 *
 * Darkening the links costs something, and it is paid for in the rule below.
 * Body copy on this site is #0c0c0c (the theme's Redux typography option emits
 * `body{color:#0c0c0c}` inline). The old olive stood 5.7:1 clear of it; the ink
 * stands only 2.9:1 clear, under the 3:1 WCAG 1.4.1 asks for when colour is a
 * link's only cue. So the fix for 1.4.3 would have opened a 1.4.1 hole, and
 * links in running copy now carry an underline. `text-decoration: none` stays
 * the default for every other link — navigation, buttons, cards and project
 * tiles are identified by position and shape, not by colour, so none of them
 * needs one.
 *
 * Hover is untouched: koncecpt/css/color.php carries `a:hover {color:#0C0505}`
 * at a specificity this rule cannot reach, so hovered links go near-black.
 * That is why the underline below thickens rather than changes colour — on
 * hover the colour cue disappears entirely and the underline is all there is. */
a {
	color: var(--ac-olive-ink);
	text-decoration: none !important;
}

/* Inline links in running copy — the only place on this site where a link is
 * surrounded by text it has to be told apart from. Two prose containers exist:
 * .post-content-text (the single blog post template, which is where every one
 * of the site's real inline links lives) and .wpb_text_column (WPBakery's text
 * block, which is how all 19 pages are built — it carries no prose links today,
 * and is named here so that the next one an editor adds is covered without
 * anybody remembering this rule).
 *
 * The tag lists are excluded deliberately. ul.post-tags and ul.single-post-tags
 * are rows of chips, not sentences: nothing surrounds them that they need to be
 * told apart from, and underlining four of them under every post title is noise.
 * Buttons are excluded by class for the same reason — a button is already a
 * shape.
 *
 * Longhands, not the `text-decoration` shorthand. The blanket rule above is a
 * shorthand carrying `!important`, so it sets text-decoration-thickness to
 * `auto` with importance; a normal longhand can never beat that, whatever its
 * specificity. Using the shorthand here would have the same problem in reverse
 * — it would reset the thickness it is trying to set. Checked in the browser:
 * with the shorthand, computed thickness came back `auto`. */
.post-content-text p a:not(.vc_btn3):not(.ac-btn),
.post-content-text ul:not(.post-tags):not(.single-post-tags) li a:not(.vc_btn3):not(.ac-btn),
.post-content-text ol li a:not(.vc_btn3):not(.ac-btn),
.wpb_text_column p a:not(.vc_btn3):not(.ac-btn),
.wpb_text_column li a:not(.vc_btn3):not(.ac-btn) {
	text-decoration-line: underline !important;
	text-decoration-thickness: 1px !important;
	text-underline-offset: 0.15em;
}
.post-content-text p a:not(.vc_btn3):not(.ac-btn):hover,
.post-content-text ul:not(.post-tags):not(.single-post-tags) li a:not(.vc_btn3):not(.ac-btn):hover,
.post-content-text ol li a:not(.vc_btn3):not(.ac-btn):hover,
.wpb_text_column p a:not(.vc_btn3):not(.ac-btn):hover,
.wpb_text_column li a:not(.vc_btn3):not(.ac-btn):hover {
	text-decoration-thickness: 2px !important;
}

/* -------------------------------------------------------------------
 * The Fill-and-Ink Rule, reaching content the stylesheet otherwise can't
 * ------------------------------------------------------------------- */

/* Editors type the brand olive straight into WPBakery as an inline style, and
 * an inline style outranks every stylesheet declaration that is not !important.
 * Across all 183 published URLs there are 59 such declarations, on 8 pages:
 *
 *     39  color             28 plain spans + 3 icons + 7 button labels + 1 caret
 *     12  background-color  a.uc_more — a fill, and fills may be olive
 *      7  border-color      vc_btn3 outlines, always paired with a label
 *      1  caret-color       nested inside an olive span; inherits either way
 *
 * Measured in the browser on the homepage before this rule: of 20 olive text
 * elements, 11 failed AA — 16px/400 links at 3.38:1, 14px/400 at 3.16:1, and
 * three 18px/700 headings at 3.38:1, since 18px bold misses the 18.66px
 * large-text threshold by two thirds of a pixel. The other 9 cleared the bar
 * only because they are large. The Fill-and-Ink Rule allows no size exception,
 * so all of them move to ink.
 *
 * The exclusions are not decoration:
 *   - "color:#7b953c" is a substring of "background-color:#7b953c", so without
 *     :not() the twelve fills would be recoloured as text.
 *   - it is equally a substring of "border-color:" and "caret-color:", and an
 *     element could carry one of those beside a text colour of its own.
 *   - icons are graphics, not words. 3.41:1 already clears the 3:1 that WCAG
 *     1.4.11 asks of them, and DESIGN.md allows olive for graphics.
 * Both spacings are matched because editors write the hex both ways.
 *
 * This is a safety net, not a licence: the hex still does not belong in page
 * content. See "Don't put running text in #7b953c" in DESIGN.md. */
/* Three value forms, not one. The saved HTML carries the hex, but JavaScript
 * rewrites some inline styles in place — Popup Maker does it to its triggers —
 * and the browser then serialises the colour as rgb(). A hex-only selector
 * missed the homepage's "Ενδιαφέρομαι" button for exactly that reason, which is
 * why this matches the computed form as well. The `i` flag covers #7B953C.
 *
 * Matching the value anywhere in the attribute, rather than "color: <value>",
 * is deliberate: it is form-agnostic, and the three :not()s below already
 * remove every element where the olive belongs to a property other than the
 * text colour. */
[style*="#7b953c" i]:not(.vc_icon_element-icon):not([style*="background-color" i]):not([style*="border-color" i]):not([style*="caret-color" i]),
[style*="rgb(123, 149, 60)" i]:not(.vc_icon_element-icon):not([style*="background-color" i]):not([style*="border-color" i]):not([style*="caret-color" i]),
[style*="rgb(123,149,60)" i]:not(.vc_icon_element-icon):not([style*="background-color" i]):not([style*="border-color" i]):not([style*="caret-color" i]) {
	color: var(--ac-olive-ink) !important;
}

/* The outline buttons set label and ring to the same colour. Moving only the
 * label would leave dark text inside a lighter ring, so they move together.
 * Scoped to .vc_btn3 and guarded against an inline fill, so a filled button
 * never has its label dragged dark. */
a.vc_btn3[style*="#7b953c" i]:not([style*="background-color" i]),
a.vc_btn3[style*="rgb(123, 149, 60)" i]:not([style*="background-color" i]),
a.vc_btn3[style*="rgb(123,149,60)" i]:not([style*="background-color" i]) {
	color: var(--ac-olive-ink) !important;
	border-color: var(--ac-olive-ink) !important;
}

/* The twelve "Περισσότερα" buttons carry their olive as an inline fill with white
 * words on it, which the Fill-and-Ink Rule does not allow: a fill with a
 * letterform on it is ink. Measured on the homepage before this rule, white on
 * the fill was 3.38:1; on ink it is 6.69:1. On /ypiresies/ the same buttons are
 * already overridden to a transparent background by a leftover ".uc_more" rule
 * from the removed Unlimited Addons plugin, so there this changes nothing. */
/* The label has to be set here too, not just the fill. These buttons render
 * differently per page: on the homepage the plugin leftovers do not apply and
 * the label is white, but on /ypiresies/ a `.uc_more {color:#000!important}`
 * rule survives, and this selector outranks it — so filling the button without
 * naming the label would have put black text on the ink at 3.14:1, which is how
 * it first shipped. White on ink is 6.69:1 on every page. The label lives in a
 * child <span> with no colour of its own, so it inherits this. */
a.uc_more[style*="#7b953c" i],
a.uc_more[style*="rgb(123, 149, 60)" i],
a.uc_more[style*="rgb(123,149,60)" i] {
	background-color: var(--ac-olive-ink) !important;
	color: var(--ac-white) !important;
}

/* ---- Olive fills set by WPBakery and by removed plugins ----
 *
 * Three WPBakery rows carry a brand-olive background with white and #EBEBEB
 * copy on it — about 8,000 characters in all, measured at 2.84–3.38:1. Each
 * row's background comes from a generated `.vc_custom_<timestamp>` rule in an
 * inline <style> block, with `!important`, so reaching it needs both a higher
 * specificity than the single class and an `!important` of our own; `.vc_row`
 * supplies the first.
 *
 * Checked before changing them: every piece of text directly on these fills is
 * white or #EBEBEB (6.69:1 and 5.62:1 on ink). The #666666 and #0c0c0c text
 * inside the longest row sits on white inner panels, not on the olive, so
 * darkening the fill does not touch it.
 *
 * THESE CLASS NAMES ARE BRITTLE. WPBakery regenerates the timestamp when an
 * editor re-edits the row's design settings, and this override then silently
 * stops applying. The durable fix is to set the row's background to #4f6320 in
 * the page builder; until someone does, this holds the line. Pages affected,
 * November 2026: ⁥1760707220865 on ten service pages, ⁥1759829721574 on
 * /ypiresies/anakainiseis-spition/, ⁥1759828314904 on /ypiresies/. */
.vc_row.vc_custom_1760707220865,
.vc_row.vc_custom_1759829721574,
.vc_row.vc_custom_1759828314904 {
	background-color: var(--ac-olive-ink) !important;
}

/* Hover fills left behind by the removed "Unlimited Addons" plugin and by
 * WPBakery's button presets. Each puts white text on the olive on hover, so
 * each is a fill with letterforms on it. */
a.uc_more:hover,
.uc_classic_banner .uc_left_text a:hover,
.vc_btn3.vc_btn3-size-md.vc_btn3-icon-right:not(.vc_btn3-o-empty):hover {
	background-color: var(--ac-olive-ink) !important;
}

/* WPBakery's left-positioned tab set paints the active tab olive with white
 * text. No page rendered it when this was written — the pages that carry the
 * rule use a different tab layout — but the rule ships on nine of them, so one
 * design-setting change in the builder would bring it back at 3.38:1. */
.vc_tta-tab.vc_active > a {
	background-color: var(--ac-olive-ink) !important;
}

/* ---- The homepage strapline ----
 *
 * Με εξειδίκευση στην Ανακαίνιση Σπιτιού... — the sentence under the homepage
 * H1 that says what the company actually does. An editor set it to #808080,
 * which on the #f9f9f9 it sits on is 3.75:1 and fails 1.4.3 for 16px text. It
 * was the last contrast failure left on the site.
 *
 * --ac-grey-mid is 9.25:1 there. It keeps the editor's intent — the line is
 * meant to read as secondary to the near-black H1 above it — while the size
 * step (36px -> 18px -> 16px) carries the hierarchy, which is where hierarchy
 * belongs. Body ink would have flattened the distinction the editor wanted.
 *
 * Scoped to .wpb_text_column on purpose. A washed grey is always wrong in a
 * prose block on a light page, but #808080 is perfectly legitimate on a dark
 * panel, and an unscoped rule would darken it there and make it worse. Exactly
 * one element on the site carries this declaration today. */
.wpb_text_column [style*="color: #808080" i],
.wpb_text_column [style*="color:#808080" i] {
	color: var(--ac-grey-mid) !important;
}

/* ---- A reading measure is for reading ----
 *
 * `.wpb_text_column { max-width: var(--ac-measure) }` caps prose at 622px, which
 * is right for prose and wrong for everything else that an editor drops into a
 * text block. Measured: the Google map on /epikoinonia/ is authored at
 * width="100%" and 480px tall and was rendering 622px wide inside a 1895px row,
 * with 636px of white either side; the hero photograph on
 * /ypiresies/anakainisi-koyzinas/ is a 1280px-wide file rendering at 622px in
 * the same situation. A map and a photograph are not text and do not want a
 * 68-character measure.
 *
 * `:only-child` is doing the real work here. Across all 183 URLs there are 12
 * text columns holding an image or an embed: 11 hold nothing else, and one — on
 * /blog/anakainisi-mpanioy-2/ — wraps 2,147 characters of Greek prose around an
 * image and MUST keep its cap. Matching the wrapper's sole child distinguishes
 * them without guessing: a media-only column has one child, a column with prose
 * around the media has several. Checked live against all three pages before
 * this shipped: 1 match on /epikoinonia/, 1 on the kitchen page (of 15 columns),
 * 0 on the blog post. */
.wpb_text_column:has(> .wpb_wrapper > :only-child iframe),
.wpb_text_column:has(> .wpb_wrapper > :only-child img) {
	max-width: none;
}

/* Un-capping the column let the photograph take the whole row, and the whole
 * row is wider than the photograph: the kitchen hero is a 1280px file and was
 * being stretched to 1895px, a 1.48x upscale on a site whose entire argument is
 * the sharpness of its finished rooms. `width: auto` hands the decision back to
 * the file — it renders at its own 1280px, centred, and still fills anything
 * narrower. No magic number, so it keeps working whatever an editor uploads
 * next. Measured here before and after: 1.48x -> 1.00x.
 *
 * Images only. The map is an iframe authored at width="100%" with no intrinsic
 * size to fall back on, so it keeps the full row. */
.wpb_text_column:has(> .wpb_wrapper > :only-child img) img {
	display: block;
	width: auto;
	max-width: 100%;
	height: auto;
	margin-inline: auto;
}

/* ---- The two dropdowns on the quote form ----
 *
 * The quote form is the only conversion this site has, and its two <select>
 * fields were shipping as raw browser controls: 344x26 and 236x26 against the
 * 750x52 of every input beside them, each a different width, with the UA's own
 * #767676 border instead of the system's #dedede. 26px is also well under the
 * 44px target floor, on the form a visitor fills on a phone.
 *
 * These are now the same field as the ones above and below them. The native
 * arrow is replaced rather than kept: an unstyled dropdown arrow is one of the
 * browser surfaces that belongs to no design system, and the chevron here is
 * drawn to the system's square, 1px, Soft Ink language. `padding-right` clears
 * it so a long Greek option never runs underneath. */
.wpcf7-form select {
	-webkit-appearance: none;
	-moz-appearance: none;
	appearance: none;
	width: 100%;
	height: 52px;
	margin: 0 0 var(--ac-space-sm);
	padding: 12px 44px 12px 20px;
	font-family: inherit;
	font-size: var(--ac-text-base);
	line-height: 1.6;
	color: var(--ac-ink);
	background-color: var(--ac-white);
	border: 1px solid var(--ac-field-border);
	border-radius: 0;
	background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='12' height='8' viewBox='0 0 12 8'%3E%3Cpath d='M1 1l5 5 5-5' fill='none' stroke='%232b2b2b' stroke-width='1.5' stroke-linecap='square'/%3E%3C/svg%3E");
	background-repeat: no-repeat;
	background-position: right 18px center;
	background-size: 12px 8px;
}

/* ---- The last two raw controls, both on the job form ----
 *
 * `.wpcf7-text` is the class the parent theme dresses, and Contact Form 7 only
 * puts it on text/email/tel/url. A [number] gets `wpcf7-number` and a [file]
 * gets `wpcf7-file`, so on /synergates-anakainisis/ both shipped as the
 * browser's own control: the years box 207x32 inside the UA's 2px #767676
 * border, the CV button 312x26 with no border and no background at all, on a
 * form where every other field measures 555x52. The CV is the one thing that
 * page exists to collect and it was the smallest target on it, 26px against a
 * 44px floor.
 *
 * Same move the dropdown got in the November pass: these become the same field
 * as their neighbours. Form 6 is the only form on the site with either field
 * type, so these two rules reach nothing else.
 *
 * The spinner goes rather than gets restyled. It is a ~10px target the browser
 * draws, on an optional number that takes one keystroke to type. */
.wpcf7-form input[type="number"] {
	-moz-appearance: textfield;
	appearance: textfield;
	width: 100%;
	height: 52px;
	margin: 0 0 var(--ac-space-sm);
	padding: 12px 20px;
	font-family: inherit;
	font-size: var(--ac-text-base);
	line-height: 1.6;
	color: var(--ac-ink);
	background-color: var(--ac-white);
	border: 1px solid var(--ac-field-border);
	border-radius: 0;
}
.wpcf7-form input[type="number"]::-webkit-outer-spin-button,
.wpcf7-form input[type="number"]::-webkit-inner-spin-button {
	-webkit-appearance: none;
	margin: 0;
}

/* The native input stays — CF7 posts the file through it — and is dressed as
 * the field with a button sitting inside it. 9px padding + a 32px button + 2px
 * of border lands on the same 52px as every other control; `min-height` rather
 * than `height` so nothing clips if a browser draws its button taller.
 *
 * The button is the one olive on this form, and it is the filled olive-ink:
 * white on it is 6.69:1. Its LABEL is the browser's, localised by the browser
 * and not by this site, so a visitor on an English-language Chrome reads
 * "Choose File" next to Greek copy. Neither CSS nor CF7 can set that text;
 * changing it needs markup, and the markup belongs to CF7. */
.wpcf7-form input[type="file"] {
	display: block;
	width: 100%;
	min-height: 52px;
	margin: 0 0 var(--ac-space-sm);
	padding: 9px 12px;
	font-family: inherit;
	font-size: var(--ac-text-base);
	line-height: 32px;
	color: var(--ac-ink);
	background-color: var(--ac-white);
	border: 1px solid var(--ac-field-border);
	border-radius: 0;
	cursor: pointer;
}
.wpcf7-form input[type="file"]::file-selector-button {
	height: 32px;
	margin-right: 14px;
	padding: 0 16px;
	font-family: inherit;
	font-size: var(--ac-text-base);
	font-weight: 600;
	line-height: 32px;
	color: var(--ac-white);
	background-color: var(--ac-olive-ink);
	border: 0;
	border-radius: 0;
	cursor: pointer;
}
.wpcf7-form input[type="file"]::file-selector-button:hover {
	background-color: var(--ac-ink);
}

/* What the visitor types should be as readable as the label asking for it.
   The fields inherited #666666; DESIGN.md's input-text component says ink. */
.wpcf7-form input[type="text"],
.wpcf7-form input[type="email"],
.wpcf7-form input[type="tel"],
.wpcf7-form textarea {
	color: var(--ac-ink);
}

/* The submit button is the single most important control on the site and its
 * label was shipping at 13px/400 — smaller than every other word on the page.
 * DESIGN.md's button-primary is 16px/600. The selector needs the extra weight:
 * koncecpt/style.css sets `input[type="submit"] {font-size:13px}` at (0,1,1),
 * which beats a bare `.wpcf7-submit` at (0,1,0) — the first attempt at this
 * fix changed the weight and silently lost the size.
 *
 * The near-black fill is left alone: it is the same dark the mobile action bar
 * gives its quote half, so it is a convention rather than drift. Worth knowing
 * that the rule underneath it is `input[type="submit"] {background:#ffba00}` —
 * the demo amber, one cascade accident away from the page. */
.wpcf7-form input[type="submit"] {
	font-size: var(--ac-text-base);
	font-weight: 600;
}

/* Contact Form 7 disables this button until the consent box is ticked, and
 * nothing said so: at rest the disabled button and the working one were pixel
 * for pixel identical, so a visitor who missed the checkbox clicked a dead
 * control and got no answer. (The 0.7 opacity already in the theme is the
 * :hover state, not a disabled one.) Disabled now reads as disabled, and does
 * not respond to the cursor. */
.wpcf7-form input[type="submit"]:disabled,
.wpcf7-form input[type="submit"]:disabled:hover {
	opacity: 0.45;
	cursor: not-allowed;
}

/* ---- Error states on the quote form ----
 *
 * A failed submit marked nothing on the field itself: the border stayed
 * #dedede and the only signal was a line of red text underneath. With five
 * required fields that is five tips to read and no way to see at a glance
 * which box to go back to. The border now carries the same #dc3232 the tip is
 * already printed in — CF7 renders that red regardless, so this introduces no
 * colour the page did not already have — and it doubles to 2px so the mark is
 * not colour alone.
 *
 * This is the one place the Photograph-Supplies-the-Colour Rule gives way: an
 * error cannot be olive, and it cannot be grey. */
.wpcf7-form .wpcf7-not-valid {
	border: 2px solid var(--ac-error);
}

/* CF7's own summary banner is bordered #ffb900 — the parent theme's demo amber
   to within one digit, and the Amber Exclusion says a sighting is a bug. It is
   an error message, so it takes the error colour. */
.wpcf7 form.invalid .wpcf7-response-output,
.wpcf7 form.unaccepted .wpcf7-response-output {
	border-color: var(--ac-error);
}

/* Text selection ships from the browser and belongs to no design system.
   White on Deep Olive Ink is 6.69:1, and it is the one accent this page owns. */
::selection {
	background-color: var(--ac-olive-ink);
	color: var(--ac-white);
}

/* ---- The dark footer is the one place ink is the wrong direction ----
 *
 * Moving links to --ac-olive-ink broke the three tel: links in the footer text
 * widget: ink on the #111111 footer is 2.82:1, where the lighter olive had been
 * 5.54:1. Nothing in the footer should be olive at all — white on #111111 is
 * 18.9:1 — and the per-widget rules further down only ever covered the menu
 * widgets and the acceptance row, so each new footer link failed on its own.
 * This covers the footer as a whole instead.
 *
 * The hover is a pre-existing bug, not one of mine: koncecpt/css/color.php puts
 * `a:hover {color:#0C0505}` on every link on the site, which inside the footer
 * is 1.07:1 — a link that vanishes under the cursor. --ac-grey-soft on #111111
 * is 11.6:1, and is already what the acceptance row uses. */
footer .up-footer a,
footer p.copyright a {
	color: var(--ac-white);
}
footer .up-footer a:hover,
footer p.copyright a:hover {
	color: var(--ac-grey-soft) !important;
}

/* Απόκρυψη του κουμπιού εναλλαγής μενού (hamburger icon) σε desktop */
.navbar-toggle { display: none; }

/* Κουμπί υποβολής του Contact Form 7 να πιάνει όλο το πλάτος */
.wpcf7-submit { width: 100%; }

/* Γενικό στυλ για τις ετικέτες (labels) φορμών */
label {
	display: inline-block;
	max-width: 100%;
	margin-bottom: 5px;
	font-weight: 700;
	width: 100% !important;
}

/* Κρύβει το "Log In" link του WordPress στο header.
   Was `.top-line p a {display:none!important}`, which hid EVERY link in the
   top bar — including the phone number once it became a tel: link, which then
   needed its own counter-rule to undo. Scoped to the login link itself, so the
   phone link needs no exception. */
.top-line p a[href*="wp-login"] { display: none !important; }

/* Στοχεύει μόνο τις σελίδες που είναι 'single portfolio' */
.single-portfolio .wpb_single_image img {
	max-width: 100%;
	object-fit: contain;
	height: 600px;
}

.vc_empty_space { display: none; }

/* Change share buttons colour */
.single-page-section .project-content-box ul li span { color: var(--ac-white); }

/* ===================================================================
 * Αλλαγή Σειράς Τίτλου & Εικόνας στις Σελίδες Έργων (Portfolio)
 * =================================================================== */

.single-portfolio .project-content-box {
	display: flex;
	flex-direction: column;
}
.single-portfolio .project-content-box > .vc_row:first-of-type { order: 1; }
.single-portfolio .project-content-box > h1.project-title { order: 2; }
.single-portfolio .project-content-box > .vc_row:not(:first-of-type) { order: 3; }
#dpsp-content-bottom { order: 4; }
.single-page-section .dpsp-share-text { order: 5; }

/* ===================================================================
 * Στυλ για την ενότητα του Blog
 * =================================================================== */

.blog-section .blog-box .blog-post { margin-bottom: var(--ac-space-lg); }

/* BUG FIX 1 — was:
 *   .blog-section .blog-box .blog-post h2, a { ... }
 * The bare `a` applied display:inline-block, text-align:center, font-size:1.3em
 * and line-height:1.2 to EVERY link on the site. Body links measurably rendered
 * centred at 1.2 leading before this fix (verified in-browser).
 * NOTE: an earlier analysis attributed the detector's tight-leading findings to
 * this rule. That was wrong — a real-browser scan puts them on .wpb_text_column,
 * span.citation and blockquote > p, none of which are links, and the counts are
 * unchanged by this fix.
 * Now scoped to the blog-post heading it was written for. */
.blog-section .blog-box .blog-post h2 {
	display: inline-block;
	text-decoration: none;
	transition: all .2s ease-in-out;
	text-transform: none;
	text-align: center;
	font-size: 1.3em;
	font-weight: 400;
	line-height: 1.2;
}

/* BUG FIX 2 — was:
 *   .blog-section .blog-box .blog-post p, a, li {font-size:14px;}
 * The bare `a` and `li` forced EVERY link and list item site-wide to 14px,
 * including navigation, footer menus and bullet lists in body copy. It also
 * meant inline body links were charged against the 4.5:1 contrast bar for
 * normal text rather than the 3:1 large-text bar. Now scoped. */
.blog-section .blog-box .blog-post:not(.single-post) p,
.blog-section .blog-box .blog-post:not(.single-post) a {
	font-size: var(--ac-text-sm);
}
/* `li` is deliberately NOT included. The original rule's bare `li` never won
   against the theme's own 16px rule, so list items rendered at 16px; scoping it
   here would have made them 14px — a change the original never actually had,
   and the wrong direction for reading. */

/* Brand button.
 * Was an override of WPBakery's "juicy-pink" preset to olive, which meant an
 * editor had to pick "juicy pink" in the page builder to get a brand button,
 * and anyone picking a different preset got an off-brand colour. The preset
 * override is kept so existing pages do not change, but .ac-btn is the one to
 * use from here on. White on --ac-olive-ink is 6.69:1; white on the old
 * --ac-olive was 3.41:1 and failed AA for button text. */
.ac-btn,
.vc_btn3.vc_btn3-color-juicy-pink,
.vc_btn3.vc_btn3-color-juicy-pink.vc_btn3-style-flat {
	background-color: var(--ac-olive);
}
.ac-btn:hover,
.vc_btn3.vc_btn3-color-juicy-pink:hover,
.vc_btn3.vc_btn3-color-juicy-pink.vc_btn3-style-flat:hover {
	background-color: var(--ac-olive-hover);
}
.ac-btn {
	display: inline-block;
	padding: 14px 28px;
	background-color: var(--ac-olive-ink);
	color: var(--ac-white) !important;
	font-size: var(--ac-text-base);
	font-weight: 600;
	line-height: 1.2;
	border: 0;
}

.blog-section .blog-box .blog-post h4 {
	color: var(--ac-olive);
	line-height: 1.4;
}

.blog-section .blog-box .single-post h1,
.project-title {
	text-transform: none;
	font-weight: 500;
	font-size: var(--ac-text-xl);
	color: var(--ac-olive);
	text-align: left;
	margin-bottom: var(--ac-space-sm);
}

/* Εφαρμόζουμε το στυλ τόσο στην ενότητα "Νέα" της αρχικής σελίδας
 * όσο και στη σελίδα του blog. */
.news-section .news-post p,
.blog-section .blog-box .single-post p {
	overflow: hidden;
	text-overflow: ellipsis;
	display: -webkit-box;
	-webkit-line-clamp: 3;
	-webkit-box-orient: vertical;
}

/* ...but never the article body. The rule above is an excerpt clamp, and its
   `.single-post p` arm also matched the paragraphs inside .post-content-text —
   the actual article — so every blog post rendered 3 lines per paragraph with
   an ellipsis and roughly two thirds of its text hidden. That predates this
   file (the rule is migrated verbatim from the Customizer), but capping the
   measure made it much more visible, since 3 lines now hold far less text.
   Scoped to body.single-post, which WordPress sets only on a single post, so
   blog index and homepage news cards keep their excerpt clamp. */
/* The selector is long on purpose: the excerpt rule above is
   (0,3,1), so this must out-rank it on specificity rather than rely on
   source order. This chain is (0,5,2). */
body.single-post .blog-section .blog-box .single-post .post-content-text p {
	overflow: visible;
	text-overflow: clip;
	display: block;
	-webkit-line-clamp: none;
}

/* Tag links under a post title. 14px link text, so they are charged against
 * the 4.5:1 bar; ink, not fill. They sit in a row of their own, not inside a
 * sentence, so they take no underline. */
.blog-section .blog-box .blog-post ul.post-tags li a {
	font-size: var(--ac-text-sm);
	color: var(--ac-olive-ink);
}

/* ===================================================================
 * Στυλ για το Υποσέλιδο (Footer)
 * =================================================================== */

/* BUG FIX 3 — was:
 *   .footer-widget .acceptance-row a, h4 { color:#fff; text-decoration:underline }
 * The bare `h4` made EVERY h4 on the site white and underlined. Most homepage
 * h4s carry an inner coloured span that masked the colour, but text-decoration
 * propagates to descendants and cannot be undone by a child's colour, so those
 * section headings rendered underlined. The "Privacy Overview" h4 in the cookie
 * modal rendered white on a light background. Now scoped to the footer link. */
.footer-widget .acceptance-row a {
	color: var(--ac-white);
	text-decoration: underline;
}

/* Headings in the dark footer. These were white only as a side effect of the
   bare `h4` in BUG FIX 3 above; scoping that rule left "Λάβετε Ιδέες &
   Προσφορές" at the inherited #0c0c0c on the #111111 footer — 1.0:1, invisible.
   Declared properly here, white on --ac-footer-bg is 18.9:1. They are headings,
   so unlike the acceptance link they carry no underline. */
footer .up-footer h4,
.footer-widget h4 {
	color: var(--ac-white);
}
.footer-widget .acceptance-row a:hover { color: var(--ac-grey-soft); }
.footer-widget .acceptance-row .wpcf7-response-output { color: var(--ac-white); }

footer .up-footer { background-color: var(--ac-footer-bg); }

/* Χρώμα συνδέσμων για τα widgets στο footer */
.widget_recent_entries ul li a,
.widget_categories ul li a,
.widget_nav_menu ul li a {
	color: var(--ac-white);
}

footer .up-footer p { color: var(--ac-white) !important; }

/* ===================================================================
 * Στυλ για την Πλοήγηση (Navigation Bar)
 * =================================================================== */

/* Κρύβει την ενότητα του banner της σελίδας.
   NOTE: this also hides koncecpt_breadcrumb(), which is rendered inside
   .page-banner-section — so service, blog and project pages have no breadcrumb
   and no "you are here". Left as-is: restoring it is a design decision. */
.page-banner-section {
	padding: 0;
	display: none !important;
}

/* Ειδικό στυλ για το στοιχείο μενού #menu-item-3849 (ΕΡΓΑ) */
#menu-item-3849 a { color: var(--ac-grey-mid) !important; }
/* Was var(--ac-olive) on this --ac-grey-wash fill: 3.2:1, a menu label failing
 * AA on hover. Ink on the same wash is 6.3:1. */
#menu-item-3849 a:hover {
	color: var(--ac-olive-ink) !important;
	background: var(--ac-grey-wash) !important;
}

/* ===================================================================
 * Διάφορες Διορθώσεις & Κανόνες
 * =================================================================== */

/* Απόκρυψη συγκεκριμένου στοιχείου στο header */
header a.elemadded { display: none; }

/* NOTE: this is why no blog post shows a date — one line, hiding every
   published date on the site. Left as-is: showing dates again is a content
   decision, but it is the cause of the "44 undated articles" problem. */
.post-date { display: none; }

/* Override για το πλάτος της στήλης .col-md-9 (πιθανόν από Bootstrap) */
.col-md-9 {
	width: 100%;
	display: block;
	position: relative;
	margin-top: var(--ac-space-md);
	padding-left: var(--ac-space-md);
	padding-right: var(--ac-space-md);
}

/* Στυλ για το slogan στο banner */
.banner-slogan {
	font-size: 24px;
	line-height: 1.1;
}

/* ===================================================================
 * Responsive Στυλ για Tablet & Κινητά
 * =================================================================== */

@media only screen and (max-width: 1024px) {
	.top-line,
	.top-line ul.social-icons { display: none; }

	.single-page-section {
		margin-top: 0;
		padding: 0 5%;
		max-width: 100vw;
	}

	/* Στοχεύει μόνο τις σελίδες που είναι 'single portfolio' */
	.single-portfolio .wpb_single_image img {
		width: 100vw;
		object-fit: contain;
		max-width: 100vw;
		margin-left: calc(50% - 50vw);
		height: 400px;
	}

	#container > header > nav > div.container { max-width: 100vw; }

	.vc_custom_1644245664748 { display: none; }

	.blog-section .blog-box .single-post h1 {
		font-size: var(--ac-text-lg);
		text-align: center;
	}
}

.navbar-brand > img { max-height: 120px; padding: 0; }
.navbar-right { margin-top: var(--ac-space-md); }

/* The five separate max-width:768px blocks this replaced were applied in this
   order and fought over the same properties. Declarations are kept in their
   original order so the resolved values are unchanged; the ones that never win
   are marked. Resolved on a phone today: logo max-height 70px (the
   .navbar-brand > img rule outranks every `header img` rule on specificity),
   max-width 120px, margin-top -5px; header padding 2px 12px 6px. */
@media only screen and (max-width: 768px) {
	.navbar-brand > img {
		max-height: 70px !important;
		width: auto !important;
		padding: 0 !important;
	}
	.navbar-brand {
		padding-top: 10px !important;
		padding-bottom: 10px !important;
	}
	.navbar-right { margin-top: 10px !important; }
	.navbar-toggle {
		display: block !important;
		margin-top: 18px !important;
	}
}

@media (max-width: 768px) {
	header img {
		max-width: 120px !important;
		max-height: 55px !important; /* overridden below by 50px */
		height: auto !important;
		width: auto !important;
		margin-top: -10px !important; /* overridden below by -5px */
	}

	header {
		min-height: auto !important;
		padding: 8px 12px !important; /* top/bottom overridden below */
	}

	.site-header,
	header {
		padding-top: 2px !important;
		padding-bottom: 6px !important;
	}

	header img { margin-top: -5px !important; }

	header img {
		max-height: 50px !important;
		width: auto !important;
	}

	/* Βγάζει το header από overlay */
	header,
	.site-header,
	.header-wrapper {
		position: relative !important;
		background: var(--ac-white) !important;
		z-index: 999 !important;
	}

	/* Κατεβάζει το slider */
	.rev_slider_wrapper,
	.smart-slider { margin-top: 90px !important; }
}

/* ===================================================================
 * Typography
 *
 * Added Nov 2026. Three problems, all measured before the change:
 *   - Body copy ran 123-142 characters per rendered line at 1440px against a
 *     comfortable maximum near 70. The detector's line-length rule was the
 *     single most frequent finding on the site.
 *   - body{line-height:21px} on 16px is 1.31. Greek carries τόνοι and
 *     διαλυτικά above the x-height (ά έ ή ί ό ύ ώ ϊ ϋ), so tight leading
 *     crowds the accents into the descenders of the line above.
 *   - The article body rendered smaller than the homepage marketing copy:
 *     reading type set smaller than selling type.
 * =================================================================== */

/* Reading measure. max-width only ever constrains, so columns already narrower
   than this are untouched — in practice only full-width rows are affected.
   The blocks are centred so that a capped block in a wide row does not sit
   against the left edge while its text is centred inside it. */
.wpb_text_column,
.post-content-text,
.project-content-box > p {
	max-width: var(--ac-measure);
	margin-inline: auto;
}

/* Leading for Greek body copy. Set on the reading elements rather than on
   body, so buttons, navigation and other tight UI keep their own values. An
   element's own declaration beats an inherited one, so no !important is needed
   against the theme's inline body{line-height:21px}. */
p,
li,
blockquote,
dd {
	line-height: 1.6;
}

/* Article body back to 16px. .post-content-text is the article itself
   (single.php line 41); blog index cards keep the smaller size. */
.post-content-text p,
.post-content-text li {
	font-size: var(--ac-text-base);
}

/* Line breaking. Capping the measure above shortened every line, which made
   orphans and lopsided heading wraps more visible — the detector's straggler
   and unbalanced-heading counts both rose when the cap landed. These two
   properties are the fix for exactly that, and they degrade to normal wrapping
   in browsers that do not support them.
     balance — evens out the lines of a short block (headings)
     pretty  — avoids leaving a single short word on the last line */
h1, h2, h3, h4, h5, h6,
.project-title,
.banner-slogan {
	text-wrap: balance;
}

p,
li,
blockquote {
	text-wrap: pretty;
}


/* ===================================================================
 * Portfolio
 *
 * The index is a WPBakery basic grid using the built-in
 * "basicGrid_NoAnimation" item template: the photo is zone-a, and the project
 * name and date sit in zone-b, an absolutely positioned overlay at opacity 0
 * that only appears on hover. The detector measured 77% of the page's text
 * (6,960 of 9,013 characters) hidden at rest, and a touch device never fires
 * hover at all — so on a phone the neighbourhood names, which are the most
 * persuasive thing on the page, were simply unreachable.
 *
 * This turns zone-b from a hover overlay into a caption that always sits under
 * its tile. The !important flags are unavoidable rather than lazy: WPBakery
 * writes the heading colour and size as inline style attributes on the
 * elements themselves, which nothing but !important can override.
 * =================================================================== */

/* Only grids whose zone-b actually carries a post title become captions. The
   homepage project carousel uses the same markup with an EMPTY zone-b — it is
   purely a hover-darkening layer — and treating that as a caption left a 28px
   dead strip under each of its six tiles. :has() keeps the rule where the
   content is; where it is unsupported, zone-b simply stays a hover overlay,
   which is the behaviour this replaces. */
.vc_grid-item .vc_gitem-animated-block:has(.vc_gitem-zone-b .vc_gitem-post-data-source-post_title) {
	height: auto !important;
}

.vc_grid-item .vc_gitem-zone-b:has(.vc_gitem-post-data-source-post_title) {
	position: static !important;
	opacity: 1 !important;
	height: auto !important;
	/* the template's 30% black scrim belongs on an overlay, not a caption */
	background-color: transparent !important;
	background-image: none !important;
	padding: 10px 2px 4px;
}

/* Zone-b carried an aspect-ratio spacer (::before with padding-top equal to the
   photo's height) so that, as an overlay, it covered zone-a exactly. As a
   caption that spacer is 458px of empty space above the text, so it goes.
   Zone-a keeps its own spacer, which is what gives the photo its box. */
.vc_grid-item .vc_gitem-zone-b:has(.vc_gitem-post-data-source-post_title)::before {
	display: none !important;
	padding-top: 0 !important;
}

/* The caption's own link layer would otherwise cover the text. */
.vc_grid-item .vc_gitem-zone-b:has(.vc_gitem-post-data-source-post_title) > a.vc_gitem-link {
	display: none !important;
}

.vc_grid-item .vc_gitem-zone-b:has(.vc_gitem-post-data-source-post_title) .vc_gitem_row,
.vc_grid-item .vc_gitem-zone-b:has(.vc_gitem-post-data-source-post_title) .vc_gitem-zone-mini {
	position: static !important;
	transform: none !important;
}

/* Project name: readable ink on the page, not white on a photo. */
.vc_grid-item .vc_gitem-zone-b .vc_gitem-post-data-source-post_title h3 {
	color: var(--ac-ink) !important;
	font-size: 17px !important;
	line-height: 1.35 !important;
	text-align: left !important;
	margin: 0 !important;
	font-weight: 500 !important;
}

/* The date is the WordPress publish date, not the date of the work, so it
   tells the visitor nothing and competes with the name. */
.vc_grid-item .vc_gitem-zone-b .vc_gitem-post-data-source-post_date {
	display: none !important;
}

/* ---- Single project page ---- */

/* The navbar is position:fixed and 168px tall on desktop, but this template
   started its content at 100px — so the top ~68px of every project page sat
   behind the header. That predates the breadcrumb below; it was simply
   invisible when the first thing in the flow was a photo whose top edge nobody
   missed. Only desktop needs this: the Customizer CSS makes the header
   position:relative under 768px. */
@media (min-width: 768px) {
	body.single-portfolio .single-page-section {
		padding-top: 150px;
	}
}

/* Align the project title with the body copy under it. Paragraphs are capped
   to 68ch and centred, so a full-width heading starts 270px to their left. */
.single-portfolio h1.project-title {
	/* width:100% is required, not redundant: .project-content-box is a flex
	   column, and margin-inline:auto on a flex item cancels the default stretch,
	   which shrink-wrapped the heading to its text and left it 100px off the
	   body copy it heads. */
	width: 100%;
	max-width: var(--ac-measure);
	margin-inline: auto;
}


.ac-breadcrumb {
	margin: 0 0 24px;
	font-size: var(--ac-text-sm);
}
.ac-breadcrumb ul,
.ac-breadcrumb #breadcrumbs {
	list-style: none;
	margin: 0;
	padding: 0;
}
.ac-breadcrumb li {
	display: inline;
	line-height: 1.5;
}
.ac-breadcrumb li + li::before {
	content: "›";
	margin: 0 8px;
	color: #767676;
}
.ac-breadcrumb a { color: var(--ac-olive-ink); }

.ac-project-cta {
	max-width: var(--ac-measure);
	margin: 48px auto 0;
	padding: 28px var(--ac-space-md);
	background: var(--ac-grey-wash);
	text-align: center;
}
.ac-project-cta__title {
	margin: 0 0 8px;
	font-size: var(--ac-text-lg);
	line-height: 1.25;
	color: var(--ac-ink);
}
.ac-project-cta__text {
	margin: 0 0 var(--ac-space-sm);
	color: var(--ac-ink);
}
.ac-project-cta__actions {
	display: flex;
	flex-wrap: wrap;
	gap: 14px var(--ac-space-sm);
	align-items: center;
	justify-content: center;
	margin: 0;
}
.ac-project-cta__secondary {
	color: var(--ac-olive-ink);
	font-weight: 500;
}

.ac-project-nav {
	display: flex;
	flex-wrap: wrap;
	gap: var(--ac-space-sm);
	max-width: var(--ac-measure);
	margin: var(--ac-space-md) auto 0;
	padding-top: var(--ac-space-sm);
	border-top: 1px solid #e3e3e3;
}
.ac-project-nav__link {
	flex: 1 1 240px;
	min-height: 44px;
	display: flex;
	flex-direction: column;
	justify-content: center;
	gap: 2px;
	color: var(--ac-ink) !important;
}
.ac-project-nav__link--next { text-align: right; }
.ac-project-nav__label {
	font-size: 13px;
	letter-spacing: .02em;
	text-transform: uppercase;
	color: #6b6b6b;
}
.ac-project-nav__title {
	color: var(--ac-olive-ink);
	font-weight: 500;
	line-height: 1.35;
}
.ac-project-nav__link:hover .ac-project-nav__title { text-decoration: underline !important; }

@media (max-width: 600px) {
	.ac-project-nav__link,
	.ac-project-nav__link--next { text-align: left; }
}
