Skip to content
https://yourstory.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Heading Hierarchy
Action
107 headings, 12 skip(s)
FIX
107 headings, 12 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.
  • H4 Follow Us
  • H4 Follow Us
  • H1 Yourstory
  • H2 Top Picks
  • H4 Kabeer Biswas's new startup raises Rs 102 Cr from PeakXV, Blume, and CRED skipped
  • H2 The CapTable
  • H4 How Sri Chaitanya is rewriting its playbook skipped
  • H4 India’s $100-billion GCC bet remains a six-metro story
  • H4 Lahori Zeera’s biggest problem is one most brands would kill for
  • H4 Kabeer Biswas's new startup raises Rs 102 Cr from PeakXV, Blume, and CRED
  • H2 Top Picks
  • H2 The CapTable
  • H2 Conversations
  • H3 AI at Scale: Powering 650M+ Users | Tech Transformers with Rahul Chari, PhonePe
  • H3 From Beating P.T Usha to Building Future Champions | Ashwini Nachappa on Identity, Woman & Courage
  • H3 From Silent Suffering to Systemic Change | Dr. Garima Sawhney on Women, Work & Healthcare |SheSparks
  • H3 From Olympic Pressure & Privilege to Boardroom Power: Aparna Popat on Winning Beyond Sport | SheSparks
  • H3 From Self-Doubt to CEO |Closing the confidence gap: Radhika Gupta on Money, Motherhood & Ambition
  • H2 Featured Series
  • H3 In conversation with Shradha Sharma
  • H3 Beyond Borders
  • H3 The Mass Effect - a spark that ignites a flame, a catalyst for a chain reaction
  • H3 Mavericks - Season 3
  • H3 Disruptor Dialogues - Innovative Insights, Strategic Breakdowns
  • H3 Money Matters with Ipsita Basu
  • H3 Fabulous Workplaces
  • H3 In conversation with Shradha Sharma
  • H3 Beyond Borders
  • H3 The Mass Effect - a spark that ignites a flame, a catalyst for a chain reaction
  • H3 Mavericks - Season 3
  • H3 Disruptor Dialogues - Innovative Insights, Strategic Breakdowns
  • H3 Money Matters with Ipsita Basu
  • H3 Fabulous Workplaces
  • H2 Spotlight
  • H4 Your desk is now an AI lab: RP Tech, an NVIDIA Partner, demos NVIDIA DGX Spark in Bangalore skipped
  • H4 Freshworks to host webinar on tackling IT complexity in the age of AI
  • H4 Reworking the economics of farming, with OpenAI in the loop
  • H4 From jugaad to systems: The shift Indian startups can’t ignore
  • H2 Spotlight
  • H4 Your desk is now an AI lab: RP Tech, an NVIDIA Partner, demos NVIDIA DGX Spark in Bangalore skipped
  • H4 Freshworks to host webinar on tackling IT complexity in the age of AI
  • H4 Reworking the economics of farming, with OpenAI in the loop
  • H4 From jugaad to systems: The shift Indian startups can’t ignore
  • H2 Founder First
  • H4 D2C vs marketplace: What Indian founders should choose skipped
  • H4 The ultimate 90-day execution plan for startup founders
  • H4 Antler India launches 3rd cohort of US market entry programme for startups
  • H2 Just In
  • H4 Startup news and updates: Daily roundup (March 26, 2026) skipped
  • H4 Pentathlon Ventures raises Rs 255 Cr in Fund II
  • H4 Burma Burma raises Rs 38 Cr in funding
  • H4 Swiggy partners with Sarvam for voice led multi-lingual services
  • H4 Rocketlane raises $60M led by Insight Partners
  • H2 Founder First
  • H4 Antler India launches 3rd cohort of US market entry programme for startups skipped
  • H4 D2C vs marketplace: What Indian founders should choose
  • H4 The ultimate 90-day execution plan for startup founders
  • H4 Don’t let these 5 founder mistakes destroy your startup
  • H4 Founder's dilemma: Build for India or build for the world?
  • H2 Just In
  • H2 Leadership Lens
  • H4 How two Bengaluru brothers are building a GitHub alternative for the AI age from Finland skipped
  • H4 India Post is the most important delivery and logistics chain in the country: Jyotiraditya Scindia
  • H4 How Ankit Agrawal built InsuranceDekho, one district at a time
  • H4 ‘Happiness is an exponential function of awareness. Just awareness’
  • H4 The coming 20 years will decide India’s next 100, says Zoho’s Vembu on building Bharat
  • H2 Leadership Lens
  • H4 How two Bengaluru brothers are building a GitHub alternative for the AI age from Finland skipped
  • H4 The coming 20 years will decide India’s next 100, says Zoho’s Vembu on building Bharat
  • H4 India Post is the most important delivery and logistics chain in the country: Jyotiraditya Scindia
  • H4 How Ankit Agrawal built InsuranceDekho, one district at a time
  • H4 ‘Happiness is an exponential function of awareness. Just awareness’
  • H2 In-Depth
  • H4 When data is scarce: How India is building military AI differently skipped
  • H4 From menu cuts to electric grills: How Indian restaurants are tiding over the LPG crisis
  • H4 Intelligent fields: How AI is powering the future of Indian agriculture
  • H4 He sold butter on a bicycle, now his GRB is India’s ghee king
  • H2 In-Depth
  • H4 He sold butter on a bicycle, now his GRB is India’s ghee king skipped
  • H4 When data is scarce: How India is building military AI differently
  • H4 From menu cuts to electric grills: How Indian restaurants are tiding over the LPG crisis
  • H4 Intelligent fields: How AI is powering the future of Indian agriculture
  • H4 Republic Day 2026: The Indian startups building strategic tech for the world
  • H2 Featured
  • H2 Featured
  • H2 Interview
  • H4 AI at Scale: Powering 650M+ Users | Tech Transformers with Rahul Chari, PhonePe skipped
  • H4 This Silicon Valley founder wants to redefine AI compute forever!
  • H4 UpClose with AI thought leader & Futurist Zack Kass
  • H4 How Snowflake’s New CEO, Sridhar Ramaswamy, Plans to Scale the $50.96B Giant
  • H4 Setting the standard for responsible and impactful AI
  • H2 Explore
  • H2 Discover More
  • H2 Startup
  • H2 Just In
  • H2 Technology
  • H2 Business Ideas
  • H2 Books
  • H2 Campaign
  • H2 Story
  • H2 Sports
  • H2 Resources
  • H2 Marketing & Sales
  • H2 Funding
  • H2 Social & Green News
  • H3 YS Buzz
  • H4 Follow Us

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
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-eqco2w
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.

D
Favicon & Branding
Action
9 icon(s) detected
FIX
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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 MAIN 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

B
Form Accessibility
4 of 6 controls have issues
REVIEW
4 of 6 controls have issues
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="emailId">; <input type="email" id="emailId">; <input type="email" id="emailId">; <input type="text" id="emailId">
Info::
2 control(s) properly labeled
6 controls
2 labeled
4 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputcheckboxnone
inputcheckboxnone
#emailIdemail(Email Address)placeholder only
#emailIdtext(Enter your Email)placeholder only
#emailIdtext(Enter your Email)placeholder only
#emailIdemail(Enter your Email)placeholder only

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

<input type="text" id="emailId">; <input type="email" id="emailId">; <input type="email" id="emailId">; <input type="text" id="emailId">

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
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: YourStory
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name YourStory ✓192×192 icon ✗512×512 icon ✓Start URL ./?utm_source=homescreen ✓Display Mode standalone ✓
Name YourStory Display Mode standalone Theme Color #ef4136 Background Color #fff Icons 8 icon(s)
B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 24 passed
REVIEW
84

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
YourStory From Beating P.T Usha to Building Future Champions | Ashwini Nachapp… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
YourStory From Silent Suffering to Systemic Change | Dr. Garima Sawhney on Wom… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
YourStory From Olympic Pressure & Privilege to Boardroom Power: Aparna Popat o… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
YourStory From Self-Doubt to CEO |Closing the confidence gap: Radhika Gupta on… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Startups The Mass Effect - a spark that ignites a flame, a catalyst for a chai… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Startups Mavericks - Season 3 div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Startups Disruptor Dialogues - Innovative Insights, Strategic Breakdowns div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
FinTech Money Matters with Ipsita Basu div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Recruitment Fabulous Workplaces div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Startup D2C vs marketplace: What Indian founders should choose Marketplace or… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Startup The ultimate 90-day execution plan for startup founders Ready to laun… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Startup Don’t let these 5 founder mistakes destroy your startup Most startups… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Startup Founder's dilemma: Build for India or build for the world? Indian fou… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
From National Fiber Scheme to Rs 10,000 Cr SME Growth Fund: Textiles, MSMEs get… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
Budget 2026: Manufacturing MSMEs want predictable cash flows, not just new sche… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
3 How Madhi Foundation is transforming early learning in India div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
4 These non-profits are keeping India’s culture and heritage alive div.slick-slider > div.slick-list > div.slick-track > div.slick-slide
5 How these social enterprises are turning India’s waste crisis into livelihoo… div.slick-slider > div.slick-list > div.slick-track > div.slick-slide

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.Header__SideDrawer-sc-2f1b81c1-2 > div.z-[10000] > div.flex > button.bg-[#FF0000] div.Header__SideDrawer-sc-2f1b81c1-2 > div.z-[10000] > div.flex > button.bg-[#FF0000]
section.container > div#conversation_section > div.slick-slider > button.absolute section.container > div#conversation_section > div.slick-slider > button.absolute
section.container > div#conversation_section > div.slick-slider > button.absolute section.container > div#conversation_section > div.slick-slider > button.absolute

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
I hereby consent to the processing of the personal data that I have provided an… div.inline-block > div.border-[1px] > div > p.text-[13px]
In Depth div.flex > div.flex > a.text-inherit > p.font-semibold
In Depth div.flex > div.flex > a.text-inherit > p.font-semibold
In Depth div.flex > div.flex > a.text-inherit > p.font-semibold
In Depth div.flex > div.flex > a.text-inherit > p.font-semibold
Advertise with Newsletter div#app_root > footer.bg-[#fff] > section#ys-footer > a.inline-block

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
Kabeer Biswas's new startup raises Rs 102 Cr from PeakXV, Blume, and CRED div.mx-[1rem] > div.border > a.text-inherit > h4.text-semilarge
Your desk is now an AI lab: RP Tech, an NVIDIA Partner, demos NVIDIA DGX Spark … div.flex > div.relative > a.text-inherit > h4.text-white
Antler India launches 3rd cohort of US market entry programme for startups div.min-h-[485px] > div.flex > a.text-inherit > h4.text-semilarge
How two Bengaluru brothers are building a GitHub alternative for the AI age fro… div.md:w-3/12 > div > a.text-inherit > h4.text-[28px]
He sold butter on a bicycle, now his GRB is India’s ghee king div.w-full > div.flex > a.text-inherit > h4.text-[28px]
5 organisations reimagining breast cancer care in India div.flex > div.text-left > a.text-inherit > h4.text-semilg
AI at Scale: Powering 650M+ Users | Tech Transformers with Rahul Chari, PhonePe div.w-full > div.flex > a.text-inherit > h4.text-[34px]

These are opportunities to improve keyboard navigation in your application.

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
Interview div.flex > div.w-3/5 > div.flex > a.text-inherit
Interview div.flex > div.w-3/5 > div.flex > a.text-inherit
Interview div.flex > div.w-3/5 > div.flex > a.text-inherit
In Depth div.w-full > div.flex > div.flex > a.text-inherit
In Depth div.w-full > div.flex > div.flex > a.text-inherit
In Depth div.w-full > div.flex > div.flex > a.text-inherit
In Depth div.w-full > div.flex > div.flex > a.text-inherit
In Depth div.w-full > div.flex > div.flex > a.text-inherit
Rekha Balakrishnan div.flex > div.flex > div.min-w-[70%] > a.text-inherit
Rekha Balakrishnan div.flex > div.flex > div.min-w-[70%] > a.text-inherit
Rekha Balakrishnan div.flex > div.flex > div.min-w-[70%] > a.text-inherit
Rekha Balakrishnan div.flex > div.flex > div.min-w-[70%] > a.text-inherit
YourStory div.w-full > div.flex > div.flex > a.text-inherit

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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.
○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>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.
A+
Alt Text Quality
All 115 images OK
PASS
All 115 images OK
Info::
5 decorative image(s) correctly marked
Info::
110 image(s) with good alt text
115 images 110 good alt text 5 decorative
All images have appropriate alt text.
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 Yourstory21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Top Picks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CapTable21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Top Picks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The CapTable21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Conversations21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Series21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Spotlight21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Spotlight21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Founder First21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Just In21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Founder First21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Just In21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Leadership Lens21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Leadership21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Lens21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In-Depth21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In-Depth21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured21.00:13.0:1
#000000
#FFFFFF
Pass

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

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

Send Feedback