Skip to content
https://indiatoday.in

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Heading Hierarchy
Action
112 headings, 21 skip(s)
FIX
112 headings, 21 skip(s)
Info::
Single H1 present
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.
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.
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.
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.
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::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Download App
  • H1 News
  • H2 Trump extends Iran ceasefire, awaits unified proposal amid Pakistan request
  • H4 Global skipped
  • H2 Peace talks doomed? JD Vance's Pak trip on hold after Iran snubs US terms
  • H4 Bengaluru News skipped
  • H2 Bengaluru woman ties lover to car to 'propose in western style', burns him alive
  • H4 Education skipped
  • H2 Rs 25 lakh for coaching, 99 percentile in JEE Mains, yet no IIT
  • H2 MBA graduate ditches Rs 25 LPA job to become taxi driver, earns Rs 6.5 lakh monthly
  • H2 IPL 2026
  • H3 Abhishek's Hyderabadi special gives DC bitter aftertaste of tactical errors
  • H3 IPL 2026 Points table
  • H4 SCIENCE
  • H2 19 of the world's 20 hottest cities today are in India. Is yours one?
  • H4 EXCLUSIVE skipped
  • H2 India must pursue energy independence; fuel price cushion won't last: Gita Gopinath
  • H4 Global skipped
  • H2 Piracy, state terrorism: Iran's big charges against US as ceasefire nears end
  • H4 Features skipped
  • H2 iPhone is now more affordable in India, full credit goes to Apple CEO Tim Cook
  • H2 India Today Insight
  • H3 From the India Today archives (2024) | How to make workplaces safe for women
  • H3 Why actor Jim Sarbh thinks 'Unani Ki Kahaani' deserves the spotlight
  • H3 How Yogi govt plans to power on through summer electricity demand
  • H3 Will MVA's lone-seat chance run into Mahayuti wall in MLC polls?
  • H3 How Mumbai's missing rail tracks, flagged in PAC report, are a study in infra land traps
  • H4 Jobs
  • H2 MBA graduate ditches Rs 25 LPA job to become taxi driver, earns Rs 6.5 lakh monthly
  • H4 West Bengal Election skipped
  • H2 Bikes banned at night, no pillion riding in day: Mandate in Bengal before polls
  • H4 Global skipped
  • H2 Ahead of Pak talks, Trump's praise for Iran and a warning
  • H4 Middle East War skipped
  • H2 Live: Oil facilities of Gulf states would be hit if war resumes, Iran commander warns
  • H2 Play Puzzle Games
  • H3 Word!
  • H3 Sliding Puzzle
  • H3 Spot the difference
  • H3 Word Search
  • H3 The Daily
  • H3 Word on WORD
  • H4 Hollywood
  • H2 Anne Hathaway says Inshallah during interview. Watch video here
  • H4 UK News skipped
  • H2 Indian man who lost wife, daughter in Air India crash faces deportation from UK
  • H4 Global skipped
  • H2 Donnyland in Donbas? Ukraine proposes renaming war-torn region after Trump
  • H4 Global skipped
  • H2 US-Iran talks in limbo, ceasefire nearing end: What will Trump do next?
  • H4 SCIENCE skipped
  • H2 When India built a satellite inside a church, and Isro was born
  • H4 Trending News skipped
  • H2 Bengaluru entrepreneur uses Porsche bonnet to fix pothole. Video goes viral
  • H4 Global skipped
  • H2 Israel claims Hezbollah fired missiles at troops in Lebanon amid ceasefire
  • H4 West Bengal Election skipped
  • H2 BJP's Anurag Thakur relishes maach bhaat during Bengal campaign, AAP takes swipe
  • H4 Beyond News skipped
  • H2 Who's Zahoor, the Norway-wanted fraudster seen with JD Vance in Pakistan?
  • H4 Tamil Nadu Election skipped
  • H2 Mallikarjun Kharge calls PM a terrorist, then clarifies. BJP gives no quarter
  • H4 West Bengal Election skipped
  • H2 Military-style takeover: TMC slams massive central forces meet in Bengal
  • H4 Bollywood skipped
  • H2 Dhurandhar 2 box office Day 33: Can Aditya Dhar's film become 2nd biggest worldwide?
  • H2 LATEST STORIES
  • H2 India Today Podcasts
  • H4 News at 7 skipped
  • H3 April 21- Pakistan Extends Airspace Ban On Indian Flights; EC Curbs Two-Wheelers In WB; India-Singapore Push Digital Maritime Ties
  • H4 Health Wealth
  • H3 The Annual Health Tests SCAM | What are the RIGHT tests for you? | Dr Arjun Dang | Doctor vs Internet
  • H4 News at 2
  • H3 April 21- Japan Lifts Ban On Lethal Weapons Exports; Rajnath Singh Begins 3-Day Visit To Germany; Tamil Nadu Poll Campaigning To End
  • H4 News at 7
  • H3 April 20- India-Russia Operationalise RELOS Pact; Indian Navy Boosts Security Near Hormuz; VP Radhakrishnan Concludes 2-Day Sri Lanka Visit
  • H4 News at 2
  • H3 April 20- Uttarakhand CM Dhami Scraps State Madrasa Board; Delhi HC To Rule On Kejriwal Recusal Pleas; Delhi May Face Higher Power Tariffs
  • H4 UnPolitics with Preeti
  • H3 Dilip Ghosh Exclusive Podcast with Preeti Choudhry | UnPolitics | Ep 36
  • H4 Nothing But The Truth
  • H3 THE BIG POLL SHOWDOWN| Nothing But The Truth S2 | Ep 133
  • H4 (empty)
  • H3 From Rs 10 Bottle To Rs 2800 Cr. The Story Behind India's Fastest Growing Desi Drink - Lahori Zeera
  • H4 Rajdeep Sardesai
  • H4 Gaurav C Sawant
  • H4 Preeti Choudhry
  • H4 Akshita Nandagopal
  • H4 Suyesha Savant
  • H4 Monday to Friday at 09:00 pm
  • H4 Monday to Friday at 08:00 pm
  • H4 Monday to Friday at 10:00 pm
  • H4 Monday to Friday at 07:00 pm
  • H4 Monday to Friday at 05:00 pm
  • H4 Monday to Friday at 06:00 pm
  • H2 WHAT’S HAPPENING IN
  • H2 Trending Videos
  • H3 Najam Sethi explains what role Pakistan is playing in US-Iran peace talks
  • H3 India Today unmasks Pahalgam terror attack mastermind hiding in Pakistan
  • H3 Gita Gopinath decodes Iran war's impact on India and global economy
  • H3 PUBLICATIONS
  • H3 TELEVISION
  • H3 EVENTS
  • H3 RADIO
  • H3 GAMING
  • H3 USEFUL LINKS
  • H3 PRINTING
  • H3 WELFARE
  • H3 DISTRIBUTION
  • H3 SYNDICATIONS
  • H3 WEBSITES
  • H3 EDUCATION

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

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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #c04a4a
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 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.

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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Alt Text Quality
Action
33 of 123 images have issues
REVIEW
33 of 123 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
32 image(s) with generic alt text
Info::
59 decorative image(s) correctly marked
Info::
31 image(s) with good alt text
123 images 31 good alt text 59 decorative 32 generic 1 missing
IssueCount
missing1 image(s)
generic32 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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page 404, Latest News, Latest Headlines Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
10 icon(s) detected
REVIEW
10 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 Present
Multiple Sizes Present
A
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

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

A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearcharia-label
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Indiatoday
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Indiatoday 192×192 icon 512×512 icon Start URL https://www.indiatoday.in Display Mode standalone
Name Indiatoday Display Mode standalone Theme Color #C04A4A Background Color #fff Icons 7 icon(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 News17.46:13.0:1
#000000
#EAEAEA
Pass
h2 IPL 202617.46:13.0:1
#000000
#EAEAEA
Pass
h2 India Today Insight17.46:13.0:1
#000000
#EAEAEA
Pass
h2 Play Puzzle Games17.46:13.0:1
#000000
#EAEAEA
Pass
h2 LATEST STORIES17.46:13.0:1
#000000
#EAEAEA
Pass
h2 WHAT’S HAPPENING I…17.46:13.0:1
#000000
#EAEAEA
Pass
h2 Trending Videos17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Download App17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Abhishek's Hyderabad…17.46:13.0:1
#000000
#EAEAEA
Pass
h3 IPL 2026 Points tabl…17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Word!17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Sliding Puzzle17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Spot the difference17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Word Search17.46:13.0:1
#000000
#EAEAEA
Pass
h3 The Daily17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Word on WORD17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Najam Sethi explains…17.46:13.0:1
#000000
#EAEAEA
Pass
h3 India Today unmasks …17.46:13.0:1
#000000
#EAEAEA
Pass
h3 Gita Gopinath decode…17.46:13.0:1
#000000
#EAEAEA
Pass
h3 PUBLICATIONS17.46:13.0:1
#000000
#EAEAEA
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.

A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 26 passed
PASS
94

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
Your daily capsule for quick news div.widgetstyle__wrap > div.presso_lgn_widget > div.presso_head > span.shrttext

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
GLOBAL div.story__grid > article#0 > div.story__cat > h4.B1S3_cat__title___NXs1
BENGALURU NEWS div.story__grid > article#1 > div.story__cat > h4.B1S3_cat__title___NXs1
EDUCATION div.story__grid > article#2 > div.story__cat > h4.B1S3_cat__title___NXs1
EXCLUSIVE div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
GLOBAL div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
FEATURES div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
WEST BENGAL ELECTION div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
GLOBAL div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
MIDDLE EAST WAR div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
UK NEWS div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
GLOBAL div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
GLOBAL div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
SCIENCE div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
TRENDING NEWS div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
GLOBAL div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
WEST BENGAL ELECTION div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
BEYOND NEWS div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
TAMIL NADU ELECTION div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
WEST BENGAL ELECTION div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
BOLLYWOOD div.story__grid > article.B1S3_story__card__A_fhi > div.story__cat > h4.B1S3_cat__title___NXs1
NEWS AT 7 div.swiper-slide > div.Carousel_carousel__card__dwl0s > div.Carousel_card__desc__OdKs2 > h4.Carousel_card__slug__71HXL

These are opportunities to improve keyboard navigation in your application.

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
Image elements have `[alt]` attributes
`[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
`<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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Document has a main landmark.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
Identical links have the same purpose.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
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
`[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
Buttons have an accessible name
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 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
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
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback