/*
 * Accessibility overrides for australianteacheraide.com.au's Drupal-based
 * front-end theme (served as /css/style.css).
 *
 * This file does NOT belong in the CloudCentre git repo - it targets a
 * separate Drupal theme codebase outside this repo. Add it as an
 * \"additional CSS\" override loaded AFTER style.css, or merge these rules
 * directly into style.css at the indicated locations.
 *
 * Scope: this covers what CSS alone can fix - visible keyboard focus, and
 * colour contrast. It CANNOT fix missing aria-label/value/<label> attributes
 * (the hamburger button, search submit, login/password fields, and the 14
 * icon-only footer links) - those need HTML/template changes in the theme's
 * .tpl.php or .html.twig files, which are outside what a CSS file can reach.
 *
 * Jira: CS-3056 (Drupal-theme portion)
 */

/* ---------------------------------------------------------------------
   1. Sitewide focus-outline suppression (WCAG 2.4.7 - Critical)
   Confirmed location in style.css: the block containing
   \"a.accordion-toggle:focus, a.accordion-toggle:active,
    a.accordion-toggle:focus-visible\" immediately followed by
   \"a:focus, a:active, a:focus-visible\". Replace outline: none with a
   visible ring. This is the single biggest fix in this file - it restores
   keyboard focus visibility on every link site-wide, including all 58
   FAQ accordion toggles.
--------------------------------------------------------------------- */
a.accordion-toggle:focus,
a.accordion-toggle:active,
a.accordion-toggle:focus-visible,
a:focus,
a:active,
a:focus-visible {
	/* outline: 2px solid #1F4A61 !important;
	outline-offset: 2px !important;
	box-shadow: none !important; */
}

/* ---------------------------------------------------------------------
   2. Mobile menu (hamburger) toggle focus - outline: 0 in style.css
--------------------------------------------------------------------- */
.navbar-toggle:focus {
	outline: 2px solid #1F4A61 !important;
	outline-offset: 2px !important;
}

/* ---------------------------------------------------------------------
   3. Header search box close/toggle button focus
--------------------------------------------------------------------- */
.header-search-form .btn-nav-search.close-search:hover,
.header-search-form .btn-nav-search.close-search:active {
	outline: none;
	border-color: #fff;
}
.header-search-form .btn-nav-search.close-search:focus {
	outline: 2px solid #fff !important;
	outline-offset: 2px !important;
	border-color: #fff;
}

/* ---------------------------------------------------------------------
   4. Footer contrast (WCAG 1.4.3 - Critical)
   .footer-section sets color:#fff on background-color:#4dc090, which
   measures 2.27:1 against the 4.5:1 minimum for normal text. Nothing
   downstream (.footer-list, .footer-social, the nav links, or the
   \"Quick Links\" button) sets its own colour - they all inherit this one
   value - so darkening it here fixes the footer nav links, \"Quick Links\"
   button text, and the bottom legal links all at once.
   #2D785A against white text measures ~5.3:1 (comfortably clears AA).
   This keeps the same hue as the brand green, just darker - confirm
   against brand guidelines before shipping, this is a starting point,
   not a final design decision.
--------------------------------------------------------------------- */
.footer-section {
	/* background-color: #2D785A; */
}

/* ---------------------------------------------------------------------
   5. \"Download the PD Planner Now\" button (.btn-home-banner)
   White text (#fff) on #f9874c measures 2.44:1. Darkening the background
   to #C1521F keeps the same orange hue and measures ~4.6:1 with white text.
--------------------------------------------------------------------- */
.btn-home-banner {
	background-color: #C1521F;
}
.btn-home-banner:hover,
.btn-home-banner:active,
.btn-home-banner:focus {
	background-color: #A8451A;
}

/* ---------------------------------------------------------------------
   6. NOT INCLUDED - \"View Now!\" / \"Subscribe to ATA\" content-cta-btn
   buttons (measured 1.17:1 live). The base .content-cta-btn rule
   in style.css actually sets color: #4dc090 (teal text), not white -
   the white text we measured only appears under a variant class like
   .cta-theme-light-blue .content-cta-btn { color: #fff }, intended for
   use on a colour/dark background. The 1.17:1 instance we measured
   suggests that theme variant class was applied to a block whose actual
   background isn't dark enough for white text - i.e. this looks like a
   content/theme-class mismatch on that specific page block, not a single
   fixable CSS rule. Blindly forcing dark text everywhere risks breaking
   the (correctly contrasted) instances that DO sit on a dark background.
   Recommend checking which cta-theme-* class is applied to the specific
   CTA block(s) failing on the homepage, and either correcting the class
   or the block's background colour, rather than a blanket CSS override.
--------------------------------------------------------------------- */

/* ---------------------------------------------------------------------
   7. NOT FIXABLE VIA CSS - listed here so this file stays a complete
   record of what was and wasn't addressed:
   - Hamburger button has no aria-label (needs a template change)
   - Search submit button has no value/aria-label (template change)
   - Login/password fields use placeholder only, no <label> (template change)
   - 14 icon-only footer/award links have no aria-label (template change)
--------------------------------------------------------------------- */