Skip to content
https://philstar.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
39
GRADE
F
FIX
7
REVIEW
6
PASS
0
INFO
0
Checks
13
6 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

F
Heading Hierarchy
Action
115 headings, 27 skip(s)
FIX
115 headings, 27 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Philstar.com | Latest Philippine news and multimedia
  • H2 Digital portal of the STAR Group of Publications: Delivers the latest news and views, multimedia, analyses and in-depth reports on the Philippines, sports, business, entertainment, lifestyle and cultu
  • H2 AMLC flags VP Sara’s P6.7 billion bank transactions
  • H2 Romualdez: Don’t force me to squeal
  • H2 HDO issued: Sandiganbayan bars Romualdez from overseas travel
  • H2 Trillanes says Duterte, Honeylet got P181.6 million from ‘drug lord’
  • H2 Airfares up as fuel surcharge soars
  • H4 Latest skipped
  • H2 Dutertes got P181.6M from drug lord, Trillanes says at House impeachment hearing
  • H2 P6 billion in bank movement, P88-million wealth: VP Sara figures questioned by House solons
  • H2 Palace OKs VP trip to 5 countries
  • H2 VP Sara net worth hits P88.5 million over 6 years, SALNs show no cash or deposits
  • H2 LIVE: House probe into VP Sara impeachment complaints on April 22
  • H4 Latest skipped
  • H2 An evening of denim and diamonds: Czarina Ablaza Syquia’s 55th birthday at Manila Polo Club
  • H6 Daily Bread skipped
  • H2 Jesus—The True Peacemaker
  • H6 Daily Bread skipped
  • H2 MMDA to extend NCAP vs litterbugs
  • H6 Nation skipped
  • H2 Belmonte to barangays: Reduce energy use
  • H6 Nation skipped
  • H2 Senate labor panel tackles anti-endo bills
  • H6 Nation skipped
  • H2 18,350 pass UPCAT
  • H6 Nation skipped
  • H2 Government agencies adopt rules on POGO ban
  • H6 Nation skipped
  • H2 Grassroots transport alliance wins prize in New York City
  • H6 Nation skipped
  • H2 25 OFWs return from Israel, Lebanon
  • H6 Nation skipped
  • H2 2 Chinese caught with P278.8 million shabu
  • H6 Nation skipped
  • H2 Fire hits Sierra Madre
  • H6 Nation skipped
  • H2 Mayon monitoring equipment cables stolen
  • H6 Nation skipped
  • H2 9 charged over hazing of 22 PNPA cadets
  • H6 Nation skipped
  • H2 3 Laguna cop chiefs relieved for poor performance
  • H6 Nation skipped
  • H2 PNP probes minor’s death in GenSan ‘shootout’
  • H6 Nation skipped
  • H2 New chemotherapy center in Laguna opened
  • H6 Nation skipped
  • H2 Technician nabbed over bomb joke
  • H6 Nation skipped
  • H2 ICC rejects Duterte jurisdiction appeal
  • H6 Headlines skipped
  • H2 DOJ chief leaves for Prague to get Zaldy Co
  • H6 Headlines skipped
  • H2 Liberal Party not giving up on Leni
  • H6 Headlines skipped
  • H3 PANOORIN: Duterte bigo sa ICC appeal
  • H3 Dutertes got P181.6M from drug lord, Trillanes says at House impeachment hearing
  • H3 LIVE: ICC ruling on Duterte jurisdiction challenge on April 22
  • H3 How 1 practical move multiplied a shop into 3
  • H3 An evening of denim and diamonds: Czarina Ablaza Syquia’s 55th birthday at Manila Polo Club
  • H3 Downgrade
  • H3 Tragic
  • H3 The need for a family constitution
  • H3 Multilateralism: The EU and the Philippines working together
  • H3 All hell breaks lose
  • H3 Mimiyuuuh meets Hollywood idols, opens up on bashers
  • H3 ASEAN for peace and prosperity, trade with China
  • H3 Structural reforms for long-term progress
  • H3 When legacy becomes a battleground
  • H3 Not invincible
  • H3 Putting out fires is the priority
  • H3 AMLC flags VP Sara’s P6.7 billion bank transactions
  • H3 Romualdez: Don’t force me to squeal
  • H3 Trillanes says Duterte, Honeylet got P181.6 million from ‘drug lord’
  • H3 EDITORIAL - Our power, our planet
  • H3 Downgrade
  • H3 Tragic
  • H3 3 million servings strong: Birch Tree Fortified Nutrition mission goes nationwide
  • H3 6 ways to make the most of an iconic summer staycation at Hilton Manila Newport World Resorts
  • H3 Cobra at 20: Honoring the ‘liwanag’ and winning spirit of the Filipinos
  • H3 MMDA to extend NCAP vs litterbugs
  • H3 Belmonte to barangays: Reduce energy use
  • H3 Senate labor panel tackles anti-endo bills
  • H3 Trump extends ceasefire, says giving Iran time to negotiate
  • H3 Police search for poisoned baby food in Austria in extortion scheme
  • H3 As Iran war strains ties with Trump's US, UK looks to Europe
  • H3 ‘Philippines credit downgrade unlikely’
  • H3 Palay harvest seen falling to 10-year low
  • H3 BSP tightening expected as inflation risks broaden
  • H3 Bossing end skid with huge upset
  • H3 Blazers stun Spurs after Wemby injury
  • H3 Cool Smashers seek series sweep
  • H3 Janella Salvador, Elisse Joson show resilience of a single mom
  • H3 DOT extends kudos to BINI, Katseye’s Sophia at Coachella
  • H3 Diego Loyzaga: We’re all main characters in life
  • H3 Italy watchdog probes travel giant Booking.com
  • H3 3 million servings strong: Birch Tree Fortified Nutrition mission goes nationwide
  • H3 All-American Turkey in Vietnamese sandwich
  • H2 Yaman ni VP Sara lumobo sa loob ng 6 taon
  • H4 SARA DUTERTE skipped
  • H2 Leni nag-iisang pantapat kay VP Sara
  • H4 SARA DUTERTE skipped
  • H2 ‘Di kami namimigay ng papremyo sa e-wallet - VP Sara
  • H4 SARA DUTERTE skipped
  • H2 TRO vs impeachment ni VP Sara, inihain ng maraming abogado
  • H4 IMPEACHMENT skipped
  • H2 AMLC binuking P6.7-B transactions ni VP Sara, mister
  • H4 SARA DUTERTE skipped
  • H3 Pharmacists Licensure Examination
  • H3 Real Estate Brokers Licensure Examination
  • H3 Midwives Licensure Examination
  • H3 Physicians Licensure Examination
  • H3 Civil Engineers Licensure Examination
  • H3 "Where do you see humans working for peace?"
  • H2 Get Updated:
  • H1 Opt out of the sale or sharing of personal information duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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

F
Alt Text Quality
Action
15 of 146 images have issues
FIX
15 of 146 images have issues
Critical::
12 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
9 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
3 image(s) with generic alt text
Info::
12 image(s) with alt text over 125 characters
Info::
4 decorative image(s) correctly marked
Info::
115 image(s) with good alt text
146 images 115 good alt text 4 decorative 3 generic 12 missing
IssueCount
missing12 image(s)
generic3 image(s)
too long12 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Pushnami
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Pushnami ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Pushnami Display Mode standalone
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
4 of 5 controls have issues
REVIEW
4 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" id="cookie-button">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="search_field">; <input type="text" id="ps_email">; <input type="password" id="ps_password">
Info::
1 control(s) properly labeled
5 controls
1 labeled
3 placeholder only
1 unlabeled
ControlTypeLabelMethod
#ps_remembercheckboxREMEMBER MEfor/id
#ps_emailtext(EMAIL)placeholder only
#ps_passwordpassword(PASSWORD)placeholder only
#search_fieldtext(Enter search item)placeholder only
#cookie-buttonbutton(none)none

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

<input type="button" id="cookie-button">

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" id="search_field">; <input type="text" id="ps_email">; <input type="password" id="ps_password">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error 404 Page Not Found | Philstar.com ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Philstar.com | Lates…9.11:13.0:1
#000000
#6DB4D2
Pass
h1 Opt out of the sale …18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Digital portal of th…9.94:13.0:1
#000000
#90B4ED
Pass
h2 Get Updated:18.10:13.0:1
#000000
#EEEEEE
Pass
title Philstar.com | Lates…5.60:14.5:1
#000000
#178DBF
Pass
span Philstar.com5.59:14.5:1
#000000
#4582E6
Pass
a HOME11.71:14.5:1
#000000
#AAC3EB
Pass
a Headlines18.10:14.5:1
#000000
#EEEEEE
Pass
a Opinion18.10:14.5:1
#000000
#EEEEEE
Pass
a Nation18.10:14.5:1
#000000
#EEEEEE
Pass
a World18.10:14.5:1
#000000
#EEEEEE
Pass
a Business18.10:14.5:1
#000000
#EEEEEE
Pass
a Sports18.10:14.5:1
#000000
#EEEEEE
Pass
a Entertainment18.10:14.5:1
#000000
#EEEEEE
Pass
a Lifestyle18.10:14.5:1
#000000
#EEEEEE
Pass
a Other Sections18.10:14.5:1
#000000
#EEEEEE
Pass
a The Philippine Star18.10:14.5:1
#000000
#EEEEEE
Pass
span Pilipino Star Ngayon18.10:14.5:1
#000000
#EEEEEE
Pass
a HOME18.10:14.5:1
#000000
#EEEEEE
Pass
a Bansa18.10:14.5:1
#000000
#EEEEEE
Pass

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

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 8 failing, 24 passed
REVIEW
79

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
‹ div#home_columnists_content > div#home_columnists_actual > div.owl-nav > button.owl-prev
› div#home_columnists_content > div#home_columnists_actual > div.owl-nav > button.owl-next
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot
div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot div#home_columnists_content > div#home_columnists_actual > div.owl-dots > button.owl-dot

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.carousel__items > div.carousel__item > div.carousel__item__image > a div.carousel__items > div.carousel__item > div.carousel__item__image > a
div.carousel__items > div.carousel__item > div.carousel__item__image > a div.carousel__items > div.carousel__item > div.carousel__item__image > a
div.tiles > div.ribbon > div.ribbon_image > a div.tiles > div.ribbon > div.ribbon_image > a
tbody > tr > td.inside_cell > a tbody > tr > td.inside_cell > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Subscribe div#nav_container > div#div-navig > div#loginLink > a
HEADLINES div.carousel__items > div.carousel__item > div.carousel__item__section > a
Jose Rodel Clapano div.carousel__items > div.carousel__item > div.carousel__item__author > a
HEADLINES div.carousel__items > div.carousel__item > div.carousel__item__section > a
Delon Porcalla div.carousel__items > div.carousel__item > div.carousel__item__author > a
HEADLINES div.carousel__items > div.carousel__item > div.carousel__item__section > a
Ian Laqui div.carousel__items > div.carousel__item > div.carousel__item__author > a
HEADLINES div.carousel__items > div.carousel__item > div.carousel__item__section > a
Jose Rodel Clapano div.carousel__items > div.carousel__item > div.carousel__item__author > a
HEADLINES div.carousel__items > div.carousel__item > div.carousel__item__section > a
Elijah Felice Rosales... div.carousel__items > div.carousel__item > div.carousel__item__author > a
TRENDING div#section_checker > div#section_checker_contents > ul#section_checker_sections > li.section_switcher
BrandSpace Video div.ribbon > div.ribbon_content > div.ribbon_elapsed > a
How 1 practical move multiplied a shop into 3 div.ribbon_content > div.ribbon_title > h3 > a
ADVERTISEMENT div#news_main > div.jscroll-inner > div.adp-interscroller-container > div.adp-interscroller-ad-label-top
div#cookie-message > div#cookie-text > div#cookie-close > input#cookie-button div#cookie-message > div#cookie-text > div#cookie-close > input#cookie-button

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 div.jscroll-inner > div.news_column > div.typeNews > h4
DAILY BREAD div.ribbon_elapsed > div.ribbon_section > a > h6
DAILY BREAD div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
NATION div.ribbon_elapsed > div.ribbon_section > a > h6
HEADLINES div.ribbon_elapsed > div.ribbon_section > a > h6
HEADLINES div.ribbon_elapsed > div.ribbon_section > a > h6
HEADLINES div.ribbon_elapsed > div.ribbon_section > a > h6

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody > tr > td.inside_cell > a tbody > tr > td.inside_cell > a
EDITORIAL - Our power, our planet td.inside_cell > div.inside_cell_title_main > h3 > a
Downgrade ul > li > h3 > a
Tragic ul > li > h3 > a
Belmonte to barangays: Reduce energy use ul > li > h3 > a
Senate labor panel tackles anti-endo bills ul > li > h3 > a
Palay harvest seen falling to 10-year low ul > li > h3 > a
BSP tightening expected as inflation risks broaden ul > li > h3 > a
Blazers stun Spurs after Wemby injury ul > li > h3 > a
Cool Smashers seek series sweep ul > li > h3 > a
DOT extends kudos to BINI, Katseye’s Sophia at Coachella ul > li > h3 > a
Diego Loyzaga: We’re all main characters in life ul > li > h3 > a

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HEADLINES AMLC flags VP Sara’s P6.7 billion bank transactions 2 hours ago Rom… div#news_main > div.jscroll-inner > div#inside_philstar > table#inside_philstar_cells
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback