Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 2 REVIEW 7 FIX

Mobile Keyboard & Autofill

Action

4/4 eligible field(s) missing autocomplete or inputmode

FIX

4/4 eligible field(s) missing autocomplete or inputmode

2 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email">, <input type="email">

2 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email">, <input type="email">

Tap Target Adequacy

Action

13 tap target(s) too small or too close together

FIX

13 tap target(s) too small or too close together

13 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

Action

54% of visible text renders at >= 12 CSS px (251 below threshold)

FIX

54% of visible text renders at >= 12 CSS px (251 below threshold)

251 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 11.8px ("Front page"); <a> 11.8px ("Countries"); <a> 11.8px ("Daily Reports"); <span> 11.5px ("Regulation"); <span> 10.6px ("Deteriorating").

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #031f2d

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Heading Hierarchy

16 headings

REVIEW

16 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Country watch
H2 Risk pressure by country
H2 Where pressure is highest this week
H2 Signals
H3 Flare-up watch
H3 Vigilance today
H2 Pressure across the countries we read
H2 Dario Durigan to unveil fiscal measures for stability
H2 Country briefings
H3 Argentina's Beef Exports Surge; Consumption Declines
H3 KOSPI Surges, JYP Shares Soar Amid Acquisition News
H3 Cyclone Arnab Hits Andhra, Gujarat Power Cuts
H2 Get It In Your Inbox
H3 Sections
H3 Countries
H3 Publisher

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email">; <input type="email">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	(your@email.com)	placeholder only
input	email	(your@email.com)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

All 16 heading(s) have substantive, well-formed text

PASS

All 16 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

Link & Button Quality

318 links, 5 buttons — all OK

PASS

318 links, 5 buttons — all OK

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://commons.wikimedia.org/wiki/File%3AImagens_de_Bras%C3%ADlia_(526525584…; https://unsplash.com/@jealife_pictures?utm_source=thegeopolitician&utm_medium…; https://unsplash.com/@dibakar16roy?utm_source=thegeopolitician&utm_medium=ref…; https://www.k-software.fr

314 link(s) with descriptive text

318 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://commons.wikimedia.org/wiki/File%…	Agência Senado from Brasilia,…	new tab	Add '(opens in new tab)' to text
https://unsplash.com/@jealife_pictures?u…	JEaLiFe Pictures / Unsplash	new tab	Add '(opens in new tab)' to text
https://unsplash.com/@dibakar16roy?utm_s…	Dibakar Roy / Unsplash	new tab	Add '(opens in new tab)' to text
https://www.k-software.fr	Powered by Talia (K-Software)	new tab	Add '(opens in new tab)' to text

319 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://commons.wikimedia.org/wiki/File%3AImagens_de_Bras%C3%ADlia_(526525584…; https://unsplash.com/@jealife_pictures?utm_source=thegeopolitician&utm_medium…; https://unsplash.com/@dibakar16roy?utm_source=thegeopolitician&utm_medium=ref…; https://www.k-software.fr

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

Favicon & Branding

11 icon(s) detected

PASS

11 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: The Geopolitician - Country risk, from the local press

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name The Geopolitician - Country risk, from the local press ✓192×192 icon ✓512×512 icon ✓Start URL /en/ ✓Display Mode standalone ✓

Name The Geopolitician - Country risk, from the local press Display Mode standalone Theme Color #031f2d Background Color #ffffff Icons 3 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Country watch	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Risk pressure by cou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Where pressure is hi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Signals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Pressure across the …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Country briefings	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get It In Your Inbox	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Flare-up watch	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Vigilance today	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sections	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Countries	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Publisher	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The Geopolitician \| …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
title The Geopolitician \| …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Wednesday, 28 Octobe…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span English edition	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span English	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a The Geopolitician	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Country risk, from t…	21.00:1	4.5:1	#000000	#FFFFFF	Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 28 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Elevated `tr > td > a > span.np-level`
Elevated `tr > td > a > span.np-level`
Elevated `tr > td > a > span.np-level`
Rising `ol > li.np-pressure-ranking-row > span.np-pressure-ranking-level > span.np-index-level`
Rising `ol > li.np-pressure-ranking-row > span.np-pressure-ranking-level > span.np-index-level`
Rising `ol > li.np-pressure-ranking-row > span.np-pressure-ranking-level > span.np-index-level`
Rising `ol > li.np-pressure-ranking-row > span.np-pressure-ranking-level > span.np-index-level`
Rising `ol > li.np-pressure-ranking-row > span.np-pressure-ranking-level > span.np-index-level`
Rising `ol > li.np-pressure-ranking-row > span.np-pressure-ranking-level > span.np-index-level`
Rising `ol > li.np-pressure-ranking-row > span.np-pressure-ranking-level > span.np-index-level`
Watch `ul > li.np-signals-row > span.np-signals-read > span.np-flareup-level`
Watch `ul > li.np-signals-row > span.np-signals-read > span.np-flareup-level`
Watch `ul > li.np-signals-row > span.np-signals-read > span.np-flareup-level`
Watch `ul > li.np-signals-row > span.np-signals-read > span.np-flareup-level`
Watch (1.4) — driven by internal tension and safety & health `div.np-signals-col > ul > li.np-signals-row > span.np-signals-read`
Watch `ul > li.np-signals-row > span.np-signals-read > span.np-flareup-level`
Watch (1.4) — driven by internal tension and safety & health `div.np-signals-col > ul > li.np-signals-row > span.np-signals-read`
Watch `ul > li.np-signals-row > span.np-signals-read > span.np-flareup-level`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SOUTH KOREA `ul.np-column-list > li > span.np-kicker > a`
China `div.np-footer-countries > ul > li > a`
Japan `div.np-footer-countries > ul > li > a`
Mexico `div.np-footer-countries > ul > li > a`
Canada `div.np-footer-countries > ul > li > a`
Spain `div.np-footer-countries > ul > li > a`
Poland `div.np-footer-countries > ul > li > a`
Russia `div.np-footer-countries > ul > li > a`
Ukraine `div.np-footer-countries > ul > li > a`
Indonesia `div.np-footer-countries > ul > li > a`
Malaysia `div.np-footer-countries > ul > li > a`
Iraq `div.np-footer-countries > ul > li > a`
Syria `div.np-footer-countries > ul > li > a`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

●`<td>` elements in a large `<table>` have one or more table headers.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○No element has a `[tabindex]` value greater than 0

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.