Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 3 REVIEW 8 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

Action

334 headings, 117 skip(s)

FIX

334 headings, 117 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

18 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Subscribe to our daily newsletter
H4 LATEST STORIES skipped
H6 business skipped
H2 Stocks fall, oil climbs amid uncertainty over US-Iran talks
H6 April 22, 2026 06:58 AM skipped
H6 CEBU DAILY NEWS
H2 Material girl: Madonna offers reward for missing clothes
H6 April 22, 2026 06:39 AM skipped
H6 globalnation
H2 Iran urges UN condemnation after US seizes cargo ship
H6 April 22, 2026 06:34 AM skipped
H6 newsinfo
H2 Hot, humid weather forecast in most parts of PH on Wednesday -- Pagasa
H6 April 22, 2026 06:31 AM skipped
H6 globalnation
H2 Florida investigating ChatGPT role in mass shooting
H6 April 22, 2026 06:24 AM skipped
H6 globalnation
H2 Trump extends ceasefire, says giving Iran time to negotiate
H6 April 22, 2026 06:15 AM skipped
H6 CEBU DAILY NEWS
H2 License of female vlogger revoked by LTO for traffic violations
H6 April 22, 2026 06:15 AM skipped
H6 CEBU DAILY NEWS
H2 CDN Top Stories [April 22] - Another road crash in Metro Cebu claims young student’s life
H6 April 22, 2026 06:00 AM skipped
H6 newsinfo
H2 Romualdez on corruption probe: ‘I’m no scapegoat’
H6 April 22, 2026 05:55 AM skipped
H6 newsinfo
H2 Remulla: Romualdez can’t leave; asset freeze sought
H6 April 22, 2026 05:50 AM skipped
H6 newsinfo
H2 Galvez resigns; Sarmiento next Marcos peace adviser
H6 April 22, 2026 05:45 AM skipped
H6 newsinfo
H2 Gov’t to agencies, LGUs: Don’t delay food trucks
H6 April 22, 2026 05:40 AM skipped
H6 newsinfo
H2 VP impeach hearing takes up SALN, SEC, BIR papers—and Trillanes
H6 April 22, 2026 05:35 AM skipped
H6 newsinfo
H2 Leni Robredo rules out national run in ’28
H6 April 22, 2026 05:25 AM skipped
H6 globalnation
H2 Wildlife hospital keeps rescued animals wild
H6 April 22, 2026 05:20 AM skipped
H6 opinion
H2 Pax Silica: What’s in it for PH
H6 April 22, 2026 05:10 AM skipped
H6 opinion
H2 Giving thanks
H6 April 22, 2026 05:06 AM skipped
H6 opinion
H2 The boring road to real change
H6 April 22, 2026 05:05 AM skipped
H6 opinion
H2 Circular history
H6 April 22, 2026 05:04 AM skipped
H6 opinion
H2 Someone has to build the floor first
H6 April 22, 2026 05:03 AM skipped
H6 opinion
H2 The career that measures character
H6 April 22, 2026 05:02 AM skipped
H6 opinion
H2 The Rainbow and the Storm: Hope Amidst Sociopolitical Turmoil
H6 April 22, 2026 05:01 AM skipped
H6 globalnation
H2 2 Filipino domestic helpers killed by employer in Lebanon
H6 April 22, 2026 05:00 AM skipped
H6 newsinfo
H2 Cops nab 2 men in second ‘gas-and-run’ case in QC
H6 April 22, 2026 04:55 AM skipped
H6 newsinfo
H2 QC students back Pope’s call for peace through paper cranes
H6 April 22, 2026 04:50 AM skipped
H6 newsinfo
H2 Army: NPA leadership in Negros wiped out
H6 April 22, 2026 04:45 AM skipped
H6 newsinfo
H2 Bicol farm losses reach P4.8M amid lack of rain
H6 April 22, 2026 04:40 AM skipped
H6 newsinfo
H2 On Earth Day, Zamboanga geologist shares life behind explorations
H6 April 22, 2026 04:35 AM skipped
H6 sports
H2 Creamline flexes ‘experienced’ game, throttles Cignal in Game 1
H6 April 22, 2026 04:30 AM skipped
H6 newsinfo
H2 Iloilo air stays safe as haze affects other areas
H6 April 22, 2026 04:30 AM skipped
H6 sports
H2 UAAP: Tigresses take first step in ‘long, tough road’ to top
H6 April 22, 2026 04:20 AM skipped
H6 sports
H2 Gilas women’s 3x3 chasing outright Olympic berth
H6 April 22, 2026 04:15 AM skipped
H6 sports
H2 NGVL target: Provide girls all over PH a chance to play
H6 April 22, 2026 04:05 AM skipped
H6 sports
H2 PBA: Ex-Laguna resident shines as Black Knights finally score
H6 April 22, 2026 04:05 AM skipped
H6 business
H2 Women as frontline guardians of PH biodiversity
H6 April 22, 2026 02:12 AM skipped
H6 business
H2 ‘Pansa-nopen’: Baguio bats for recycling culture
H6 April 22, 2026 02:11 AM skipped
H6 business
H2 Renewables could have cushioned PH oil price shock
H6 April 22, 2026 02:10 AM skipped
H6 business
H2 Harnessing storms: From deluge to water assets
H6 April 22, 2026 02:09 AM skipped
H6 business
H2 Bamboo, agro-forest waste eyed as biomass fuel
H6 April 22, 2026 02:08 AM skipped
H6 business
H2 How decades-old policy keeps Marikina City trash-free
H6 April 22, 2026 02:07 AM skipped
H6 business
H2 Ligao’s coastal waters get new lease on life
H6 April 22, 2026 02:06 AM skipped
H6 business
H2 Hopes dim for Philippines' credit rating upgrade
H6 April 22, 2026 02:05 AM skipped
H6 business
H2 Jaza vacates head seat at Globe board
H6 April 22, 2026 02:04 AM skipped
H6 newsinfo
H2 Sara, Rodrigo Duterte’s alleged joint bank account still active – solon
H6 April 22, 2026 01:28 AM skipped
H6 newsinfo
H2 LOOK: Strike divides transport workers in Iloilo City
H6 April 22, 2026 12:58 AM skipped
H6 newsinfo
H2 Alleged ‘high-value’ drug suspect busted; P680,000 shabu seized in Rizal
H6 April 22, 2026 12:50 AM skipped
H6 entertainment
H2 Love Knots, April 22, 2026
H6 April 22, 2026 12:15 AM skipped
H6 entertainment
H2 Tuldok, April 22, 2026
H6 April 22, 2026 12:10 AM skipped
H6 entertainment
H2 Crazy Jhenny, April 22, 2026
H6 April 22, 2026 12:05 AM skipped
H6 newsinfo
H2 P1.4M in suspected shabu seized from elderly suspect in Butuan City
H6 April 21, 2026 11:41 PM skipped
H2 VIDEOS
H3 VIEW ALL VIDEOS
H2 Stratbase backs Balikatan, cites need for stronger PH defense in WPS
H2 'WPS is ours': Atin Ito launches Cebu caravan for nat'l awareness
H2 Chinese fishermen’s use of cyanide in Ayungin is ‘unacceptable’ — DFA
H2 Sailors cite repeated cyanide fishing in Ayungin, China claim rejected
H2 JM de Guzman payat na: Malinis na lifestyle, wala na akong alak, softdrinks
H2 Mark Herras, Nicole Donesa balak iwan ang Pinas, magma-migrate sa US!?
H2 Katrina Halili sa pagbabalikan daw nila ni Kris: Secret! Bawal sumagot!
H2 Kim Atienza: Matibay ang bata ngayon pero ang attack sa utak nila marami
H2 Pax Silica: What’s in it for PH
H3 Giving thanks
H3 The boring road to real change
H2 Baguio adopts circular tourism model amid rising waste, resource strain
H2 PH academic freedom slips amid campus pressures, red-tagging
H2 EXPLAINER: How to keep your solar panels safe from fire
H2 Palawan’s fishing ban stirs renewed debate over municipal waters
H2 property
H6 Latest Property News skipped
H3 Rising temperatures call for smarter building practices
H4 (empty)
H6 Latest Property News skipped
H3 Beat the heat: Simple ways to cool your home
H6 Architecture skipped
H3 When campuses shape cities
H6 Latest Property News skipped
H3 Six crises, six years: How resilient is Philippine real estate?
H2 business
H6 Energy (Oil, Electricity, Coal) skipped
H3 Stocks fall, oil climbs amid uncertainty over US-Iran talks
H4 (empty)
H6 Headlines skipped
H3 Women as frontline guardians of PH biodiversity
H6 Headlines skipped
H3 ‘Pansa-nopen’: Baguio bats for recycling culture
H6 Headlines skipped
H3 Renewables could have cushioned PH oil price shock
H2 sports
H6 Headlines skipped
H3 Creamline flexes ‘experienced’ game, throttles Cignal in Game 1
H4 (empty)
H6 Headlines skipped
H3 UAAP: Tigresses take first step in ‘long, tough road’ to top
H6 Basketball skipped
H3 Gilas women’s 3x3 chasing outright Olympic berth
H6 Headlines skipped
H3 NGVL target: Provide girls all over PH a chance to play
H2 entertainment
H6 Love Knots skipped
H3 Love Knots, April 22, 2026
H4 (empty)
H6 Print Comics skipped
H3 Tuldok, April 22, 2026
H6 Crazy Jhenny skipped
H3 Crazy Jhenny, April 22, 2026
H6 Celebrities and Showbiz skipped
H3 Izzy Trazona's trans daughter Sofia undergoes breast augmentation
H2 lifestyle
H6 LIFESTYLE.INQ Latest skipped
H3 Hello Kitty's parent company to make own video games
H4 (empty)
H6 LIFESTYLE.INQ Entertainment skipped
H3 Ramona doesn’t need your approval
H6 LIFESTYLE.INQ F&B Report skipped
H3 A strawberry cake fit for a queen
H6 LIFESTYLE.INQ Health & Wellness skipped
H3 I had 2,000 platelets, and my body was attacking itself—here’s how I came back
H2 usa
H6 Headlines skipped
H3 Trump extends ceasefire in Iran war: Here's what to know
H4 (empty)
H6 Entertainment skipped
H3 Katseye’s Sophia Laforteza, Leon Barretto spotted at Wrestlemania 42
H6 Food skipped
H3 Chicken inasal among world’s top 3 chicken dishes
H6 Celebrities skipped
H3 LOOK: Anne Curtis recreates ‘Breakfast at Tiffany’s’ scene in NYC
H2 cebudailynews
H6 News skipped
H3 Material girl: Madonna offers reward for missing clothes
H4 (empty)
H6 Headlines skipped
H3 License of female vlogger revoked by LTO for traffic violations
H6 Headlines skipped
H3 CDN Top Stories [April 22] - Another road crash in Metro Cebu claims young student’s life
H6 FAITH skipped
H3 Daily Gospel, April 22, 2026
H2 NOLISOLI
H6 (empty)
H3 Exploring Maranao food around Metro Manila
H4 April 20, 2026
H6 (empty)
H3 Gets mo ba?—How we Filipinos talk to each other
H6 (empty)
H3 Museum workers now deserve the spotlight
H6 (empty)
H3 ‘Saglit Lang’: A deep dive into mentors and mentorship
H2 globalnation
H6 World skipped
H3 Iran urges UN condemnation after US seizes cargo ship
H4 (empty)
H6 World skipped
H3 Florida investigating ChatGPT role in mass shooting
H6 World skipped
H3 Trump extends ceasefire, says giving Iran time to negotiate
H6 Europe skipped
H3 Wildlife hospital keeps rescued animals wild
H2 technology
H6 Gaming skipped
H3 Alex Valdez, Filipino developer of Sepak U, shares his journey with the upcoming game
H4 (empty)
H6 Advertorial skipped
H3 Infinite NOTE 60 Pro: a level up in all aspects
H6 latest stories skipped
H3 John Ternus is new CEO of Apple, Tim Cook is executive chairman
H6 Telecommunication skipped
H3 GCash rolls out programs to help make everyday transactions more affordable
H2 world
H6 World skipped
H3 14-year-old qualifies as candidate for US state governor
H4 (empty)
H6 World skipped
H3 Passenger surge still seen despite conflict in Middle East
H6 World skipped
H3 Gov’t urged: Ask Iran to let PH-bound oil tankers pass
H6 Regions skipped
H3 2 suspects busted, P5.4 M shabu seized in Iligan City - PDEA
H2 metro
H6 Headlines skipped
H3 Cops nab 2 men in second ‘gas-and-run’ case in QC
H4 (empty)
H6 Headlines skipped
H3 QC students back Pope’s call for peace through paper cranes
H6 Metro skipped
H3 P1.53-M shabu seized, 2 nabbed in Parañaque drug sting
H6 Metro skipped
H3 PNP orders probe into cold kidnap-for-ransom cases
H2 regions
H6 Headlines skipped
H3 Army: NPA leadership in Negros wiped out
H4 (empty)
H6 Headlines skipped
H3 Bicol farm losses reach P4.8M amid lack of rain
H6 Headlines skipped
H3 On Earth Day, Zamboanga geologist shares life behind explorations
H6 Headlines skipped
H3 Iloilo air stays safe as haze affects other areas
H2 pop
H6 BrandRoom skipped
H3 Salu Salo Market at The Corner House presents 'Uptown Girls': A celebration of creativity, entrepreneurship, and community
H4 (empty)
H6 BrandRoom skipped
H3 SB19 reaffirms reign as P-pop kings in ‘Wakas at Simula: The Trilogy Finale’ concert
H6 BrandRoom skipped
H3 SM Skating Seaside Cebu reopens with fresh looks, honors Filipino skating champions
H6 Netflix skipped
H3 What is ‘Netflix lighting’ and why are viewers feeling uneasy about it?
H2 INTERESTING TOPICS
H6 Headlines skipped
H3 Trump extends ceasefire in Iran war: Here’s what to know
H6 Travel skipped
H3 What consumers can do as Iran war impacts cost, availability of flights
H6 Headlines skipped
H3 Trump and Pope Leo square off over Iran war: Here’s what to know
H6 Fil-Am skipped
H3 Automatic US military draft registration: What Fil-Ams need to know
H2 radyo
H6 Featured skipped
H3 Plunder case vs Escudero, Romualdez ikakasa ng Ombudsman
H4 (empty)
H6 Featured skipped
H3 Petroleum lockdown fake news peddlers kakasuhan – Palasyo
H6 Featured skipped
H3 Semana Santa ‘tigil-putak‘ hiniling ng Palasyo sa mga kritiko
H6 Featured skipped
H3 Don’t panic, no hoarding, bilin ng DTI sa mga konsyumer
H5 The Inquirer Channels skipped
H5 Services
H5 The Inquirer Company
H5 Partners
H5 © Copyright 1997-2026 INQUIRER.net
H5 For any security issues please contact itsec@inquirer.net

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Form Accessibility

Action

30 of 30 controls have issues

FIX

30 of 30 controls have issues

3 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="text" name="email_address_check">; <input type="text" name="email_address_check">; <input type="text" name="email_address_check">

27 control(s) rely on placeholder only

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

Got: <input type="text" name="EMAIL" id="EMAIL">; <input type="text" name="CHANNEL" id="CHANNEL">; <input type="text" name="COUNTRY" id="COUNTRY">; <input type="text" name="CATEGORY" id="CATEGORY">; <input type="text" name="EMBED_URL" id="EMBED_URL">; <input type="text" name="NEWSLETTER_LOCATION" id="NEWSLETTER_LOCATION">; <input type="text" name="REFER_URL" id="REFER_URL">; <input type="text" name="TAG" id="TAG">; <input type="text" name="USER_IP" id="USER_IP">; <input type="text" name="EMAIL" id="EMAIL"> (+17 more)

30 controls

0 labeled

27 placeholder only

3 unlabeled

Control	Type	Label	Method
#EMAIL	text	(Email Address)	placeholder only
#CHANNEL	text	(CHANNEL)	placeholder only
#COUNTRY	text	(COUNTRY)	placeholder only
#CATEGORY	text	(CATEGORY)	placeholder only
#EMBED_URL	text	(EMBED_URL)	placeholder only
#NEWSLETTER_LOCATION	text	(NEWSLETTER_LOCATION)	placeholder only
#REFER_URL	text	(REFER_URL)	placeholder only
#TAG	text	(TAG)	placeholder only
#USER_IP	text	(USER_IP)	placeholder only
#EMAIL	text	(Subscribe to our newsletter)	placeholder only
#CHANNEL	text	(CHANNEL)	placeholder only
#COUNTRY	text	(COUNTRY)	placeholder only
#CATEGORY	text	(CATEGORY)	placeholder only
#EMBED_URL	text	(EMBED_URL)	placeholder only
#NEWSLETTER_LOCATION	text	(NEWSLETTER_LOCATION)	placeholder only
#REFER_URL	text	(REFER_URL)	placeholder only
#TAG	text	(TAG)	placeholder only
#USER_IP	text	(USER_IP)	placeholder only
#EMAIL	text	(Email Address)	placeholder only
#CHANNEL	text	(CHANNEL)	placeholder only
#COUNTRY	text	(COUNTRY)	placeholder only
#CATEGORY	text	(CATEGORY)	placeholder only
#EMBED_URL	text	(EMBED_URL)	placeholder only
#NEWSLETTER_LOCATION	text	(NEWSLETTER_LOCATION)	placeholder only
#REFER_URL	text	(REFER_URL)	placeholder only
#TAG	text	(TAG)	placeholder only
#USER_IP	text	(USER_IP)	placeholder only
email_address_check	text	(none)	none
email_address_check	text	(none)	none
email_address_check	text	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="EMAIL" id="EMAIL">; <input type="text" name="CHANNEL" id="CHANNEL">; <input type="text" name="COUNTRY" id="COUNTRY">; <input type="text" name="CATEGORY" id="CATEGORY">; <input type="text" name="EMBED_URL" id="EMBED_URL">; <input type="text" name="NEWSLETTER_LOCATION" id="NEWSLETTER_LOCATION">; <input type="text" name="REFER_URL" id="REFER_URL">; <input type="text" name="TAG" id="TAG">; <input type="text" name="USER_IP" id="USER_IP">; <input type="text" name="EMAIL" id="EMAIL"> (+17 more)

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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-mwh33o

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://inquirer.net/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://inquirer.net/manifest.json

Manifest contains invalid JSON.

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: #ffffff

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 ✗

Link & Button Quality

Action

4 issue(s) across 294 links and 3 buttons

REVIEW

4 issue(s) across 294 links and 3 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#inq-close

3 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://opinion.inquirer.net/191230/pax-silica-whats-in-it-for-ph ("READ MORE"); https://opinion.inquirer.net ("READ MORE"); https://newsinfo.inquirer.net/tag/inqfocus ("Read More")

10 link(s) open in new tab without warning

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

Got: https://services.inquirer.net/user-agreement/; https://services.inquirer.net/privacy-policy/; https://clicks.inquirer.net/92; https://clicks.inquirer.net/63; https://services.inquirer.net/user-agreement/; https://services.inquirer.net/privacy-policy/; https://www.facebook.com/inquirerdotnet/; https://twitter.com/inquirerdotnet; https://www.youtube.com/user/inquirernews; https://www.instagram.com/inquirerdotnet/

280 link(s) with descriptive text

294 links

1 empty

3 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://services.inquirer.net/user-agree…	Terms of Use	new tab	Add '(opens in new tab)' to text
https://services.inquirer.net/privacy-po…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://clicks.inquirer.net/92	Dunkin-I-Like-Apr12-May11	new tab	Add '(opens in new tab)' to text
https://clicks.inquirer.net/63	PCSO ribbon lotto2 – Apr19-M…	new tab	Add '(opens in new tab)' to text
https://services.inquirer.net/user-agree…	Terms of Use	new tab	Add '(opens in new tab)' to text
https://services.inquirer.net/privacy-po…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/inquirerdotnet/	follow social media facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/inquirerdotnet	follow social media twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/inquirernew…	follow social media youtube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/inquirerdotnet…	follow social media instagram	new tab	Add '(opens in new tab)' to text
https://opinion.inquirer.net/191230/pax-…	READ MORE	generic text	Replace with descriptive text
Before: READ MORE Suggested: Pax Silica Whats In It For Ph
https://opinion.inquirer.net	READ MORE	generic text	Replace with descriptive text
Before: READ MORE Suggested: Opinion.Inquirer.Net
https://newsinfo.inquirer.net/tag/inqfoc…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Inqfocus

283 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#inq-close

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

https://opinion.inquirer.net/191230/pax-silica-whats-in-it-for-ph ("READ MORE"); https://opinion.inquirer.net ("READ MORE"); https://newsinfo.inquirer.net/tag/inqfocus ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://services.inquirer.net/user-agreement/; https://services.inquirer.net/privacy-policy/; https://clicks.inquirer.net/92; https://clicks.inquirer.net/63; https://services.inquirer.net/user-agreement/; https://services.inquirer.net/privacy-policy/; https://www.facebook.com/inquirerdotnet/; https://twitter.com/inquirerdotnet; https://www.youtube.com/user/inquirernews; https://www.instagram.com/inquirerdotnet/

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

Favicon & Branding

18 icon(s) detected

REVIEW

18 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

title Latest Philippines Headlines, Breaking N…

4.09:1

#000000

#0B72B5

needs 4.5:1 (normal text)

16px · top of page (header area)

a Global Nation

3.83:1

#000000

#716766

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Subscribe to our dai…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 VIDEOS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Stratbase backs Bali…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 'WPS is ours': Atin …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Chinese fishermen’…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sailors cite repeate…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 JM de Guzman payat n…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Mark Herras, Nicole …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Katrina Halili sa pa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Kim Atienza: Matibay…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Baguio adopts circul…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 PH academic freedom …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 EXPLAINER: How to ke…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Palawan’s fishing …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 INTERESTING TOPICS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Latest Philippines H…	4.09:1	4.5:1	#000000	#0B72B5	Fail
div July 10, 2022	8.34:1	4.5:1	#000000	#6DAAD3	Pass
i search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a News	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Global Nation	3.83:1	4.5:1	#000000	#716766	Fail

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.

A+

Alt Text Quality

All 38 images OK

PASS

All 38 images OK

15 decorative image(s) correctly marked

23 image(s) with good alt text

38 images 23 good alt text 15 decorative

All images have appropriate alt text.

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 20 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
OPINION `div#gtm_track_opinion > a > div.flx-m-cat > span.opinion_clr`
div#gtm_track_business > a > div.flx-m-cat > span.business_clr `div#gtm_track_business > a > div.flx-m-cat > span.business_clr`
section > ul > li > h5 `section > ul > li > h5`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`
li > ul > li > a `li > ul > li > a`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LATEST STORIES `div#popular_left > div#inq_popular_lbl > a > h4`
BUSINESS `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:58 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:39 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:34 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:31 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:24 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 06:00 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:55 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:50 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:45 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:40 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:35 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:25 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:20 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:10 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:06 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:04 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:03 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:02 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:01 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 05:00 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:55 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:50 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:45 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:40 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:35 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:30 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:30 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:20 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 04:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:12 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:11 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:10 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:09 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:08 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:07 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:06 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 02:04 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 01:28 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:58 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:50 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:15 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:10 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 22, 2026 12:05 AM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
APRIL 21, 2026 11:41 PM `div.swiper-wrapper > div.swiper-slide > div#tr_boxs3 > h6`
div#inq_channels_wrap > div#track_property > div > h6 `div#inq_channels_wrap > div#track_property > div > h6`
div#inq_channels_wrap > div#track_business > div > h6 `div#inq_channels_wrap > div#track_business > div > h6`
div#inq_channels_wrap > div#track_sports > div > h6 `div#inq_channels_wrap > div#track_sports > div > h6`
div#inq_channels_wrap > div#track_entertainment > div > h6 `div#inq_channels_wrap > div#track_entertainment > div > h6`
div#inq_channels_wrap > div#track_lifestyle > div > h6 `div#inq_channels_wrap > div#track_lifestyle > div > h6`
div#inq_channels_wrap > div#track_usa > div > h6 `div#inq_channels_wrap > div#track_usa > div > h6`
div#inq_channels_wrap > div#track_cebudailynews > div > h6 `div#inq_channels_wrap > div#track_cebudailynews > div > h6`
div#inq_channels_wrap > div#track_nolisoli > div > h6 `div#inq_channels_wrap > div#track_nolisoli > div > h6`
div#inq_channels_wrap > div#track_globalnation > div > h6 `div#inq_channels_wrap > div#track_globalnation > div > h6`
div#inq_channels_wrap > div#track_technology > div > h6 `div#inq_channels_wrap > div#track_technology > div > h6`
div#inq_channels_wrap > div#track_world > div > h6 `div#inq_channels_wrap > div#track_world > div > h6`
div#inq_channels_wrap > div#track_metro > div > h6 `div#inq_channels_wrap > div#track_metro > div > h6`
div#inq_channels_wrap > div#track_regions > div > h6 `div#inq_channels_wrap > div#track_regions > div > h6`
div#inq_channels_wrap > div#track_pop > div > h6 `div#inq_channels_wrap > div#track_pop > div > h6`
div#inq_channels_wrap > div#track_west_philippine_sea > div > h6 `div#inq_channels_wrap > div#track_west_philippine_sea > div > h6`
div#inq_channels_wrap > div#track_radyo > div > h6 `div#inq_channels_wrap > div#track_radyo > div > h6`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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>`

●`[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

●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

●Touch targets have sufficient size and spacing.

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○`[role]` values are valid

○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.

○Skip links are focusable.

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

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

○`<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>`.

○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.

○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.

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