@media only screen and (max-width: 480px) {

.new-btn-position-aware {
    padding: 18px 17px;
    font-size: 14px;
}

.main-butn .main-butn-txt {
        font-size: 14px;
    }

.office-address {
    padding-top: 20px;
}
.cercle {
    display: none;
}

.experience-sec .abt-btn {
    margin-top: 20px;
}
.get-in-touch .get-in-touch-content h2.cta-stacked > span:last-child {
    align-items: center;
}

.form-consent-text {
    padding-left: 0;
    margin-left: 0;
    position: relative;
    left: 0;
    width: 100%;
}

.form-consent-label {
    display: block !important;
}
#closeMenu {
    font-size: 22px !important; 
}
.drawer-header button {
    font-size: 40px;
}

.submenu-btn span {
    font-size: 26px;
}


}

/* ---- CTA on phones: button under the copy, statue last ----------------------
   Wanted order is subtitle -> heading -> button -> image, but the markup nests
   `.hand-image` inside `.get-in-touch-content` while `.button-cta-flex` is that
   wrapper's next sibling. The two are not siblings, so `order` on its own has
   nothing to swap.

   `display: contents` drops the wrapper's own box and promotes the subtitle,
   heading and image into `.purple-box`'s flex flow, putting all four items on
   one level where a single `order` sequence settles them. The wrapper stays in
   the DOM, so its descendant selectors and inherited centring still apply.

   768px matches the breakpoint where site.css brings the button back. */
@media only screen and (max-width: 768px) {
    .get-in-touch .purple-box {
        display: flex;
        flex-direction: column;
    }

    .get-in-touch .purple-box .get-in-touch-content {
        display: contents;
    }

    .get-in-touch .purple-box .subtitle {
        order: 1;
    }

    .get-in-touch .purple-box .get-in-touch-content h2 {
        order: 2;
    }

    .get-in-touch .purple-box .button-cta-flex {
        order: 3;
        margin-top: 10px;
    }

    .get-in-touch .purple-box .hand-image {
        order: 4;
        margin-top: 24px;
    }
}