/* Hide the JS-driven verification UI so the spinner can't imply false progress */ .body { display: none !important; } /* The page canvas has to match .noscript-screen. <body> is painted with --fill-tertiary from the main stylesheet, which already resolves to white in light mode and black in dark — these rules restate both so the no-JS screen doesn't silently inherit a future change to that token. */ body { background-color: #ffffff; } /* Light is the default; dark is applied via prefers-color-scheme below. Foreground values mirror the main stylesheet's light palette (--glyph-gray, --glyph-gray-secondary, --glyph-blue) and the background is pure white, matching the JS page's --fill-tertiary, so the no-JS screen and the JS screen read as the same product. :root already declares `color-scheme: light dark`, so UA chrome (scrollbars, focus rings) follows the system setting here too. */ .noscript-screen { --ns-bg: #ffffff; --ns-fg: #1d1d1f; /* headings */ --ns-fg-body: #1d1d1f; /* primary body */ --ns-fg-dim: #6e6e73; /* translated body */ --ns-line: rgba(0, 0, 0, 0.12); --ns-link: #0066cc; /* Apple system blue on light */ background: var(--ns-bg); color: var(--ns-fg-body); font-family: -apple-system, BlinkMacSystemFont, "SF Pro Text", "Helvetica Neue", Helvetica, Arial, sans-serif; text-rendering: optimizeLegibility; line-height: 1.5; min-height: 100vh; display: flex; justify-content: center; /* No padding-top: the headline's per-tier margin-top owns the space above the content, so a container padding would stack on top of it. */ padding: 0 24px 72px; } @media (prefers-color-scheme: dark) { /* Pure black canvas, matching the JS page's dark --fill-tertiary. Foregrounds stay a softened off-white rather than #fff to limit halation against it (astigmatism/dyslexia). Antialiased smoothing is scoped to dark on purpose: it thins strokes, which helps light-on-dark but makes dark-on-light text look washed out. */ body { background-color: #000000; } .noscript-screen { --ns-bg: #000000; --ns-fg: #f0f0f2; --ns-fg-body: #d2d2d7; --ns-fg-dim: #a1a1a6; --ns-line: rgba(255, 255, 255, 0.14); --ns-link: #2997ff; /* Apple system blue on dark */ -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale; } } .ns-wrap { width: 100%; max-width: 940px; } .ns-brand { display: flex; justify-content: center; margin-bottom: 40px; } .ns-brand svg { width: 44px; height: auto; fill: var(--ns-fg); display: block; } .ns-headline { color: var(--ns-fg); /* Matches the JS page's title stack (.verification-title). LARGE values here; M/S override font-size and line-height per tier. */ font-family: "SF Pro Text", "SF Pro Icons", "Helvetica Neue", "Helvetica", "Arial", sans-serif; font-size: 40px; line-height: 1.1; font-weight: 600; letter-spacing: 0em; text-align: center; /* No max-width: the headline is a single short string and must stay on one line. A ch-based cap wraps it, since 1ch is the width of "0" and the string is wider than any sensible cap. If it ever has to wrap on a very narrow viewport, balance the lines rather than orphaning a word. */ /* Bottom margin is 0: the gap to the lede is owned by .ns-lede's margin-top (25px). Leaving a bottom margin here would collapse against it, making the effective gap the larger of the two and harder to reason about. margin-top is set per tier below. */ margin: 0 auto; text-wrap: balance; } .ns-lede { /* 17/25 regular at every tier, so there are no per-tier overrides. */ font-family: "SF Pro Text", "SF Pro Icons", "Helvetica Neue", "Helvetica", "Arial", sans-serif; font-size: 17px; line-height: 1.4705882353; font-weight: 400; letter-spacing: -0.022em; text-align: center; /* No max-width, matching .ns-headline: the measure cap wrapped this onto a second line well before the viewport ran out of room. Width is still bounded by .ns-wrap (940px). At 86 characters it needs ~700px, so it fits on one line from roughly 750px up and balances the lines below. */ /* Constant across all three tiers, so it lives here rather than being repeated in L/M/S. Paired with margin-bottom: 0 on .ns-headline, the gap is exactly 25px and does not depend on margin collapsing. */ margin: 25px auto 0; text-wrap: balance; } .noscript-screen a:focus-visible { outline: 2px solid var(--ns-link); outline-offset: 4px; border-radius: 4px; } .ns-rule { border: 0; height: 1px; background: var(--ns-line); max-width: 940px; /* 32px is the LARGE value; M and S drop to 28px below. Was an asymmetric 52/44 — now symmetric, per spec. */ margin: 32px auto; } /* All 8 non-English locales are shown at once: JS locale detection is impossible here. Ideally the server reorders by Accept-Language so the visitor's language leads; English is the deliberate primary anchor. */ .ns-grid { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); /* Row and column gap are the same value per tier — 32px LARGE, 28px in M/S below — so one `gap` covers both axes. Column gap only has a visible effect while the grid is two columns (> 640px). */ gap: 32px; } .ns-lang h2 { color: var(--ns-fg); /* 19/23 semibold at every tier, so no per-tier overrides. SF Pro has no CJK or Arabic coverage; those six sections fall back to the platform's script fonts via the trailing sans-serif, which is the intended behaviour — the metrics below still apply. */ font-family: "SF Pro Text", "SF Pro Icons", "Helvetica Neue", "Helvetica", "Arial", sans-serif; font-size: 19px; line-height: 1.2105263158; font-weight: 600; letter-spacing: 0.012em; /* Bottom margin is 0 — the gap to the paragraph is owned by .ns-lang p's margin-top, so the two can't collapse against each other and the 11px is exact. */ margin: 0; } .ns-lang p { color: var(--ns-fg-dim); /* SF Pro Text — body copy, same as .ns-lede. 14/20 regular at every tier, so no per-tier overrides. */ font-family: "SF Pro Text", "SF Pro Icons", "Helvetica Neue", "Helvetica", "Arial", sans-serif; font-size: 14px; line-height: 1.4285714286; font-weight: 400; letter-spacing: -0.016em; /* 11px gap from the h2 above; same at every breakpoint. */ margin: 11px 0 0; } .ns-lang[dir="rtl"] { text-align: right; } /* ------------------------------------------------------------------ Viewport tiers ------------------------------------------------------------------ Breakpoints match the main stylesheet (1068px / 734px) so the no-JS screen and the JS screen break at the same widths. Ordered large → small and written as max-width, so they cascade: a 500px viewport matches medium AND small, and small wins by source order. Put a declaration in the widest tier where it should first take effect. ------------------------------------------------------------------ */ /* LARGE — desktop, > 1068px. Base rules above already cover this tier; add here only to override the default (unqualified) styling. */ @media (min-width: 1069px) { .ns-headline { /* 40 / 44 semibold */ font-size: 40px; line-height: 1.1; margin-top: 64px; } .ns-rule { margin-block: 32px; } .ns-grid { gap: 32px; } } /* MEDIUM — tablet / small laptop, 735px–1068px. */ @media (max-width: 1068px) { .ns-headline { /* 32 / 36 semibold */ font-size: 32px; line-height: 1.125; margin-top: 56px; } .ns-rule { margin-block: 28px; } .ns-grid { gap: 28px; } } /* SMALL — phone, <= 734px. */ @media (max-width: 734px) { .ns-headline { /* 28 / 32 semibold */ font-size: 28px; line-height: 1.1428571429; margin-top: 48px; } .ns-rule { margin-block: 28px; } .ns-grid { gap: 28px; } } /* Single-column collapse for phones — two columns of CJK/Arabic are cramped. Row gap is deliberately NOT set here: it comes from the SMALL tier above (28px). The old `gap: 36px` shorthand was removed because it overrode that row-gap below 640px and would have broken the 32/28/28 spec. */ @media (max-width: 640px) { .noscript-screen { /* Top stays 0 here too — otherwise this shorthand would put the container padding back and double up with .ns-headline's margin. */ padding: 0 22px 56px; } .ns-grid { grid-template-columns: 1fr; } }

This page needs JavaScript

Reload the page. If the page won’t load, turn off content blockers or switch networks.

Esta página requiere JavaScript

Volver a cargar la página. Si la página no se carga, desactiva los bloqueadores de contenido o cambia de red.

这个页面需要使用 JavaScript

重新载入页面。如果页面无法载入，请关闭内容拦截器或切换网络。

Cette page nécessite JavaScript

Rechargez la page. Si la page ne se charge pas, désactivez les bloqueurs de contenu ou changez de réseau.

Für diese Seite ist JavaScript erforderlich.

Lade die Seite neu. Wenn die Seite nicht geladen wird, deaktiviere Inhaltsblocker oder wechsle das Netzwerk.

تتطلب هذه الصفحة JavaScript

أعد تحميل الصفحة. إذا تعذر تحميل الصفحة، فأوقف أدوات حظر المحتوى أو بدّل شبكة الاتصال.

Esta página requer JavaScript

Recarregue a página. Se a página não carregar, desative os bloqueadores de conteúdo ou troque de rede.

このページにはJavaScriptが必要です

ページを再読み込みしてください。ページが読み込まれない場合は、コンテンツブロッカーを無効にするか、ネットワークを切り替えてください。

이 페이지에는 JavaScript가 필요합니다.

페이지를 다시 로드합니다. 페이지가 로드되지 않으면 콘텐츠 차단기를 끄거나 네트워크를 전환합니다.

Verifying connection...

Vérification de la connection

연결을 확인하는중...

接続を確認しています...

Verbindung überprüfen ...

正在验证连接...

Verificando Conexión

Проверка соединения...

جاري التحقق من الاتصال...

Invalid connection

Connection invalide

유효하지 않은 연결입니다

不正な接続

Ungültige Verbindung

无效的连接

Conexión inválida

Неверное соединение

اتصال غير صالح

Security verification in progress. Please wait while we verify your browser to protect against automated access.