/* Accessibility overrides for the Google Translate widget.

   Translate injects a decorative loading spinner at the end of body:
   div.VIpgJd-ZVi9od-aZ2wEe-wOHMyf, holding an svg with no role, no accessible name, no title
   element and no aria-hidden. The container computes position: fixed; top: -1000px; left: -1000px,
   so it is invisible - but off-screen is not hidden, and measuring it on the deployed site
   confirmed nothing removed it from the accessibility tree. That is the unlabeled "graphic" near
   the copyright line a JAWS user reported: NOVA-5912, counsel workbook row 13, WCAG 1.1.1
   Non-text Content (Level A).

   It is decorative, so removal from the tree is the correct remedy rather than alt text, and
   counsel's recommendation explicitly allows either.

   display: none is used in preference to a scripted aria-hidden because a CSS rule applies
   whether the node exists yet or not and survives Google re-creating it, with no observer to
   mis-fire. The element was already parked off-screen, so nothing changes visually and the
   language picker is unaffected.

   This lives in its own file rather than in Site.css on purpose. Site.css is served under the
   site-wide 7-day static max-age, and Azure Front Door can ignore the ?v= cache key - the same
   reason the ClaimForm scripts are served by versioned filename. A new file has no cached copy to
   serve stale, so the fix reaches returning claimants immediately.

   ViewScripts/translate-a11y.js is the structural fallback for Google renaming this obfuscated
   class, which they have done before. */
.VIpgJd-ZVi9od-aZ2wEe-wOHMyf {
  display: none !important;
}