Skip to content
https://www.flipkart.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
3 landmarks
FIX
3 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
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 (missing!) CONTENTINFO footer

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
Alt Text Quality
Action
67 of 95 images have issues
FIX
67 of 95 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
14 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
53 image(s) with generic alt text
Info::
28 image(s) with good alt text
95 images 28 good alt text 53 generic 14 missing
IssueCount
missing14 image(s)
generic53 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

F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 403 Page Title Flipkart reCAPTCHA Custom Styling Navigation Homepage Link Search Form
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">; <input type="text" name="q">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtext(Search for Products, Brands and More)placeholder only
qtext(Search for Products, Brands and More)placeholder only

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

<input type="text" name="q">; <input type="text" name="q">

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

C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 10 pass AA only
title Online Shopping Site for Mobiles, Electr…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
div Location not set
2.87:1
#1F1F1F
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
div Select delivery location
1.06:1
#1254E7
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
span Login
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Flipkart: India's Ul…3.66:13.0:1
#000000
#666666
Pass
h2 What Can You Buy fro…3.66:13.0:1
#000000
#666666
Pass
h2 Flipkart Loyalty and…3.66:13.0:1
#000000
#666666
Pass
h2 Payment and Affordab…3.66:13.0:1
#000000
#666666
Pass
h2 Flipkart Flights: Bo…3.66:13.0:1
#000000
#666666
Pass
h2 Flipkart Minutes: Gr…3.66:13.0:1
#000000
#666666
Pass
h2 Flipkart Reset and E…3.66:13.0:1
#000000
#666666
Pass
h2 Flipkart Kilos: Your…3.66:13.0:1
#000000
#666666
Pass
h2 Why Choose Flipkart?…3.66:13.0:1
#000000
#666666
Pass
h2 Get Exclusive Offers…3.66:13.0:1
#000000
#666666
Pass
title Online Shopping Site…3.66:14.5:1
#000000
#666666
Fail
div Location not set2.87:14.5:1
#1F1F1F
#666666
Fail
div Select delivery loca…1.06:14.5:1
#1254E7
#666666
Fail
span Login3.66:14.5:1
#000000
#666666
Fail
span New customer?8.33:14.5:1
#000000
#A3A3A3
Pass
span Sign Up21.00:14.5:1
#000000
#FFFFFF
Pass
div My Profile21.00:14.5:1
#000000
#FFFFFF
Pass
div Flipkart Plus Zone19.95:14.5:1
#000000
#F9F9F9
Pass
div Orders21.00:14.5:1
#000000
#FFFFFF
Pass
div Wishlist21.00:14.5:1
#000000
#FFFFFF
Pass

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

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 4 failing, 13 passed
REVIEW
77

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
Hang on, loading content div.FWmYMm > div.css-g5y9jx > div.css-g5y9jx > div.css-146c3p1

These are opportunities to improve the legibility of your content.

Names and labels

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._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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.useInterFont html.useInterFont

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Touch targets have sufficient size and spacing.
The page contains a heading, skip link, or landmark region
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
Buttons have an accessible name
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<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
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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
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+
Heading Hierarchy
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 Flipkart: India's Ultimate One-Stop Online Shopping Destination
  • H2 What Can You Buy from Flipkart?
  • H2 Flipkart Loyalty and Rewards Program
  • H2 Payment and Affordability: Shop Smart, Pay Smarter
  • H2 Flipkart Flights: Book Your Next Getaway Effortlessly
  • H2 Flipkart Minutes: Groceries and Gadgets in a Flash
  • H2 Flipkart Reset and Exchange Program: Trade-in Your Old Device
  • H2 Flipkart Kilos: Your Online Grocery Supermarket
  • H2 Why Choose Flipkart? The Unbeatable Advantages
  • H2 Get Exclusive Offers and Deals in Popular Sale Events
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback