/*
 * Contact Form 7 integration styles.
 *
 * The static design's contact form used a <button> for its submit control,
 * which the theme's ".contact-form input" rule never touches. CF7's
 * [submit] tag renders an <input type="submit"> instead, which that same
 * generic rule (transparent background, bottom border only, full width)
 * also matches — silently stripping the pill-button look. Likewise the
 * [acceptance] tag renders its own internal <label>/<input>/<span>, so the
 * original ".consent" 2-column grid (which expects the checkbox and its
 * text to be direct children of the label) never applies. These rules
 * target CF7's own stable class names directly instead of depending on
 * exact markup nesting.
 */

/* Restore the pill-button look CF7's <input type="submit"> loses to the
   generic ".contact-form input" rule (higher specificity wins here). */
.contact-form input[type="submit"].wpcf7-submit {
	width: auto;
	height: 54px;
	padding: 0 25px;
	border-radius: 100px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: 1px solid transparent;
	font-size: 14px;
	cursor: pointer;
	background: #fff;
	color: var(--ink);
	margin-top: 15px;
}

.contact-form input[type="submit"].wpcf7-submit:hover {
	opacity: 0.9;
}

/* Keep the checkbox and its label text on one line regardless of CF7's
   nested acceptance markup. */
.contact-form .wpcf7-acceptance .wpcf7-list-item {
	margin: 0;
}

.contact-form .wpcf7-acceptance label {
	display: flex;
	align-items: flex-start;
	gap: 12px;
	cursor: pointer;
	font-size: 13px;
	line-height: 1.5;
	color: #ccc;
}

.contact-form .wpcf7-acceptance input[type="checkbox"] {
	flex: none;
	width: 16px !important;
	height: 16px;
	margin: 3px 0 0;
}

.contact-form .wpcf7-not-valid-tip {
	font-size: 12px;
	color: #ff8a8a;
	margin-top: 6px;
}

.contact-form .wpcf7-response-output {
	grid-column: 1 / -1;
	margin: 16px 0 0;
	border-radius: 8px;
	font-size: 13px;
}