/*
 * Accessibility corrections — loaded by oa-admin/accessibility.php
 *
 * Overrides Avada theme styles that remove accessibility affordances.
 * Kept separate from the theme so Avada stays updatable.
 */


/* ---------------------------------------------------------------------
 * Focus indicators (WCAG 2.4.7 Focus Visible)
 *
 * Avada's "disable outline" option puts .fusion-disable-outline on <body>
 * and then sets outline:0 across inputs, selects, textareas, buttons and
 * menu links. Keyboard users are left with no visible position on the page.
 *
 * Restored with a two-tone ring so it stays visible on both the dark and
 * cream areas of the site. :focus-visible means mouse users never see it.
 * !important is required to beat the theme's own outline:0 declarations.
 * ------------------------------------------------------------------- */

a:focus-visible,
button:focus-visible,
input:focus-visible,
select:focus-visible,
textarea:focus-visible,
summary:focus-visible,
[tabindex]:focus-visible,
[contenteditable="true"]:focus-visible {
	outline: 2px solid #1a1a1a !important;
	outline-offset: 2px !important;
	box-shadow: 0 0 0 5px #ffffff !important;
}

/* Avada scopes several outline:0 rules under the body class, which raises
   their specificity above the bare selectors above. Match that scope. */
.fusion-disable-outline a:focus-visible,
.fusion-disable-outline button:focus-visible,
.fusion-disable-outline input:focus-visible,
.fusion-disable-outline select:focus-visible,
.fusion-disable-outline textarea:focus-visible,
.fusion-disable-outline .button:focus-visible,
.fusion-disable-outline .fusion-button:focus-visible,
.fusion-disable-outline .wpcf7-submit:focus-visible,
.fusion-disable-outline .awb-menu__flyout-close:focus-visible,
.fusion-disable-outline .awb-menu_desktop.awb-menu_flyout a:focus-visible {
	outline: 2px solid #1a1a1a !important;
	outline-offset: 2px !important;
	box-shadow: 0 0 0 5px #ffffff !important;
}


/* ---------------------------------------------------------------------
 * Back-to-top control (WCAG 2.4.3 Focus Order)
 *
 * Avada hides #toTop with opacity:0 and pointer-events:none, but neither
 * removes an element from the keyboard tab order. A keyboard user tabbing
 * through the page lands on an invisible control before they have scrolled.
 *
 * visibility:hidden does remove it, and Avada already toggles
 * .fusion-to-top-active on the link when the control should appear
 * (Avada/assets/min/js/general/avada-to-top.js).
 * ------------------------------------------------------------------- */

#toTop {
	visibility: hidden;
}

#toTop.fusion-to-top-active {
	visibility: visible;
}