Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

No <nav> landmark found

No contentinfo (footer) landmark

Skip navigation link is missing (WCAG 2.4.1)

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

Page Structure — as a screen reader sees it

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA / WCAG 2.4.1

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 2.4.1

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

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

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Link & Button Quality

Action

3 issue(s) across 21 links and 3 buttons

REVIEW

3 issue(s) across 21 links and 3 buttons

2 link(s) with no accessible text

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

Got: https://www.glance.com/; https://www.1weatherapp.com/brand/

1 link(s) with generic text

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

Got: https://advertising.inmobi.com ("Learn More")

9 link(s) open in new tab without warning

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

Got: https://www.inmobi.com/cookie-policy/; https://www.inmobi.com/website-cookie-policy; https://glance.com/; https://www.1weatherapp.com/brand/; https://advertising.inmobi.com/; https://advertising.inmobi.com/company/press; https://glance.com/newsroom; https://glance.com/careers; https://advertising.inmobi.com

9 link(s) with descriptive text

21 links

2 empty

1 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.inmobi.com/cookie-policy/	cookie policy	new tab	Add '(opens in new tab)' to text
https://www.inmobi.com/website-cookie-po…	cookie policy	new tab	Add '(opens in new tab)' to text
https://glance.com/	Glance	new tab	Add '(opens in new tab)' to text
https://www.1weatherapp.com/brand/	1Weather	new tab	Add '(opens in new tab)' to text
https://advertising.inmobi.com/	InMobi Advertising	new tab	Add '(opens in new tab)' to text
https://advertising.inmobi.com/company/p…	InMobi Advertising Press	new tab	Add '(opens in new tab)' to text
https://glance.com/newsroom	Glance Press	new tab	Add '(opens in new tab)' to text
https://glance.com/careers	Glance Careers	new tab	Add '(opens in new tab)' to text
https://www.glance.com/	(empty)	empty	Add link text or aria-label
https://www.1weatherapp.com/brand/	(empty)	empty	Add link text or aria-label
https://advertising.inmobi.com	Logo	new tab	Add '(opens in new tab)' to text
https://advertising.inmobi.com	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Advertising.Inmobi.Com

12 links and buttons have descriptive text

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

https://www.glance.com/; https://www.1weatherapp.com/brand/

Why this matters

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

Source: WCAG 2.1 SC 2.4.4

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

https://advertising.inmobi.com ("Learn More")

Why this matters

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

Learn more ▾

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

Source: WCAG 2.4.4 / Google Search Central

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

https://www.inmobi.com/cookie-policy/; https://www.inmobi.com/website-cookie-policy; https://glance.com/; https://www.1weatherapp.com/brand/; https://advertising.inmobi.com/; https://advertising.inmobi.com/company/press; https://glance.com/newsroom; https://glance.com/careers; https://advertising.inmobi.com

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title InMobi - Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 The

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h1 of the Consumer Internet

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

title Redefining the mobile experience for con…

1.02:1

#000000

#050309

needs 4.5:1 (normal text)

16px · top of page (header area)

p We use necessary and (optional) analytic…

1.47:1

#000000

#2B2A2E

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a cookie policy

1.02:1

#000000

#050309

needs 4.5:1 (normal text)

16px · top of page (header area)

p to understand how we use cookies. You ma…

1.06:1

#000000

#0C0817

needs 4.5:1 (normal text)

16px · top of page (header area)

a Accept

1.13:1

#000000

#160E2B

needs 4.5:1 (normal text)

16px · above the fold

a Decline

1.12:1

#000000

#130E28

needs 4.5:1 (normal text)

16px · above the fold

a cookie policy

1.10:1

#000000

#0E0D23

needs 4.5:1 (normal text)

16px · above the fold

button Decline

2.72:1

#0B4DCC

#0A0C1E

needs 4.5:1 (normal text)

16px · above the fold

button Customize

2.74:1

#0B4DCC

#080B1B

needs 4.5:1 (normal text)

16px · above the fold

button Accept All

2.77:1

#0B4DCC

#060A19

needs 4.5:1 (normal text)

16px · above the fold

span InMobi

1.06:1

#000000

#050917

needs 4.5:1 (normal text)

16px · above the fold

span Consumer Brands

1.05:1

#000000

#040914

needs 4.5:1 (normal text)

16px · mid-page

a Glance

1.05:1

#000000

#030811

needs 4.5:1 (normal text)

16px · mid-page

a 1Weather

1.04:1

#000000

#02070F

needs 4.5:1 (normal text)

16px · mid-page

span Enterprise Platforms

1.03:1

#000000

#02060C

needs 4.5:1 (normal text)

16px · mid-page

a InMobi Advertising

1.03:1

#000000

#01050A

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

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

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 The	1.00:1	3.0:1	#000000	#000000	Fail
h1 of the Consumer Inte…	1.00:1	3.0:1	#000000	#000000	Fail
title Redefining the mobil…	1.02:1	4.5:1	#000000	#050309	Fail
p We use necessary and…	1.47:1	4.5:1	#000000	#2B2A2E	Fail
a cookie policy	1.02:1	4.5:1	#000000	#050309	Fail
p to understand how we…	1.06:1	4.5:1	#000000	#0C0817	Fail
a Accept	1.13:1	4.5:1	#000000	#160E2B	Fail
a Decline	1.12:1	4.5:1	#000000	#130E28	Fail
div We use third-party c…	18.93:1	4.5:1	#FFFFFF	#110D26	Pass
a cookie policy	1.10:1	4.5:1	#000000	#0E0D23	Fail
div for more details.	19.26:1	4.5:1	#FFFFFF	#0C0C21	Pass
button Decline	2.72:1	4.5:1	#0B4DCC	#0A0C1E	Fail
button Customize	2.74:1	4.5:1	#0B4DCC	#080B1B	Fail
button Accept All	2.77:1	4.5:1	#0B4DCC	#060A19	Fail
span InMobi	1.06:1	4.5:1	#000000	#050917	Fail
span Consumer Brands	1.05:1	4.5:1	#000000	#040914	Fail
a Glance	1.05:1	4.5:1	#000000	#030811	Fail
a 1Weather	1.04:1	4.5:1	#000000	#02070F	Fail
span Enterprise Platforms	1.03:1	4.5:1	#000000	#02060C	Fail
a InMobi Advertising	1.03:1	4.5:1	#000000	#01050A	Fail

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

Lighthouse Accessibility Audits

Score 85/100 — 4 failing, 20 passed

REVIEW

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
DECLINE `div.accept-cookie > div.accept-cookie-inner > div.button-continer > button.btn`
CUSTOMIZE `div.accept-cookie > div.accept-cookie-inner > div.button-continer > button.btn`
ACCEPT ALL `div.accept-cookie > div.accept-cookie-inner > div.button-continer > button.btn`

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
About InMobi `div.lazyload-wrapper > section.singlecol_singleColWrapper__9JY3Z > div.singlecol_contentWrapper__Brtdo > h4.uCenter`

These are opportunities to improve keyboard navigation in your application.

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.productscard_slideContainer__tGF4r > div.productscard_panel__U_A76 > div.productscard_cardContainer__j_Pjb > a.productscard_ctaUrl___ys8y `div.productscard_slideContainer__tGF4r > div.productscard_panel__U_A76 > div.productscard_cardContainer__j_Pjb > a.productscard_ctaUrl___ys8y`
div.productscard_slideContainer__tGF4r > div.productscard_panel__U_A76 > div.productscard_cardContainer__j_Pjb > a.productscard_ctaUrl___ys8y `div.productscard_slideContainer__tGF4r > div.productscard_panel__U_A76 > div.productscard_cardContainer__j_Pjb > a.productscard_ctaUrl___ys8y`

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`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

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

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

○`<td>` elements in a large `<table>` have one or more table headers.

Heading Hierarchy

4 headings, 1 skip(s)

PASS

4 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

H1 The Intelligence Layerof the Consumer Internet
H4 About InMobi skipped
H4 Your Intelligent Shopping Agent
H4 Your Weather App

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

A+

Alt Text Quality

1 of 38 images have issues

PASS

1 of 38 images have issues

1 image(s) with generic alt text

17 decorative image(s) correctly marked

20 image(s) with good alt text

38 images 20 good alt text 17 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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