.raleway-tvgshowcase {
  font-family: "Raleway", sans-serif;
  font-optical-sizing: auto;
  font-style: normal;
}
body {
  text-align: center;
  margin: 0;
  overflow-x: hidden;
}
img {
  display: none;
}

body.dark{
  background-color: black;
  color: white;
  font-weight: 500;
}
body.dark.top-logo .tvgla-logo.dark{
  display: inline-block;
}
body.dark.bottom-logo .tvgla-logo-footer.dark{
  display: inline-block;
}

body.bright{
  background-color: white;
  color: black;
  font-weight: 700;
}
body.bright.top-logo .tvgla-logo.bright{
  display: inline-block;
}
body.bright.bottom-logo .tvgla-logo-footer.bright{
  display: inline-block;
}

.row{
  width: 100%;
  min-width: 400px;
  text-align: center;
  float: none;
  margin: 1%;
}

.row p{
  width:100%;
}
span.bigger {
  font-size: 1.2em;
}
span.smaller {
  font-size: .75em;
}

/* The player itself is now Video.js (see /shared/js/vendor/video.min.js and
   /shared/css/vendor/video-js.min.css, loaded before this file). Video.js
   renders its own consistent control bar across desktop, mobile, and
   fullscreen — including a real captions/subtitles button whenever a
   <track> is present — instead of us overlaying custom DOM buttons on top
   of whatever a given browser's native controls happen to be. .single just
   constrains the player's width; Video.js's `fluid: true` option handles
   the responsive scaling inside it. */
.single {
  width: 80%;
  max-width: 1200px;
  min-width: 400px;
  margin: 0 auto;
}

/* Fallback sizing for the raw <video class="video-js"> element. Once
   Video.js initializes, it swaps in its own player wrapper and this rule no
   longer matters (fluid:100% is handled by video-js.min.css instead). But
   if the Video.js script hasn't run yet, or fails to load, the plain
   <video> tag has no intrinsic width to fall back on and renders tiny —
   this keeps it responsive either way. */
video.video-js {
  width: 100%;
  height: auto;
  display: block;
}

/* Custom "Transcript" control bar button, registered in main.js and added
   to the Video.js control bar like any built-in button. */
.vjs-transcript-toggle .vjs-icon-placeholder:before {
  content: "T";
  font-family: Arial, Helvetica, sans-serif;
  font-weight: 700;
  font-size: 18px;
}
.vjs-transcript-toggle-active .vjs-icon-placeholder:before {
  text-decoration: underline;
}

.header-parent-container{
  width: 100%;
  text-align: center;
}
.tvgla-logo{
  width: 40%;
  max-width: 300px;
  min-width: 100px;
  margin: 0px;
}

.content {
  padding-top:  50px;
  margin-bottom: 80px;
}

.footer-parent-container{
  width: 100%;
  text-align: center;
}
.tvgla-logo-footer{
  width: 40%;
  max-width: 200px;
  min-width: 100px;
  margin: 0px;
}

/* Accessibility: skip link, visible only on keyboard focus */
.skip-link{
  position: absolute;
  left: -9999px;
  top: 0;
  background: #000;
  color: #fff;
  padding: 12px 16px;
  z-index: 1000;
  text-decoration: underline;
}
.skip-link:focus{
  left: 10px;
  top: 10px;
}

/* Accessibility: keep native focus outlines visible on all interactive elements */
a:focus-visible,
video:focus-visible,
button:focus-visible{
  outline: 3px solid #2684ff;
  outline-offset: 2px;
}

/* Mobile Safari/WebKit quirk: focusable elements (buttons, but also the
   Video.js CC menu's <li> items once its popup opens) can be left showing
   the browser's own native focus ring after a tap, even though the tap
   wasn't a keyboard interaction and :focus-visible above never matched.
   This explicitly clears that native outline whenever focus-visible
   doesn't apply, without touching real keyboard focus (Tab), which still
   gets the blue ring from the rule above. The wildcard inside .video-js
   covers the popup menu items specifically, since those aren't <a>,
   <video>, or <button> elements. */
a:focus:not(:focus-visible),
video:focus:not(:focus-visible),
button:focus:not(:focus-visible),
.video-js *:focus:not(:focus-visible){
  outline: none;
}

h1.raleway-tvgshowcase{
  font-size: 1.3em;
  margin: 0;
}

/* Accessibility: on-page transcript. Collapsed by default and styled as a
   quiet, secondary link rather than a bold section heading — most visitors
   get the same content from captions, so this shouldn't compete visually
   with the video. It stays in the DOM (not display:none) so it's always
   reachable for screen readers and, via main.js, auto-opens if the video
   itself fails to load. */
.transcript{
  text-align: left;
  max-width: 800px;
  margin: 12px auto 0;
  padding: 0 5%;
  font-size: 0.85em;
  line-height: 1.6;
  font-weight: 400;
}
.transcript[hidden]{
  display: none;
}
body.dark .transcript{
  font-weight: 400;
}
.transcript .visual-note{
  opacity: 0.8;
}
.transcript .visual-note em{
  font-style: italic;
}
.transcript .video-error-note{
  opacity: 1;
  font-weight: 700;
}

@media( max-width: 1253px ) {
  .single{
    max-width: 800px;
  }
}
@media( max-width: 1230px ) {
  .row p{
    width: 90%;
    padding-right: 5%;
    padding-left: 5%;
  }
}
@media( max-width: 818px ) {}