Skip to content
https://pubmatic.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Alt Text Quality
Action
20 of 40 images have issues
FIX
20 of 40 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
13 image(s) with generic alt text
Info::
7 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
40 images 13 good alt text 7 decorative 13 generic 7 missing
IssueCount
missing7 image(s)
generic13 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

Learn more

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

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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

Why this matters

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

Learn more

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

Source: WCAG 2.1 SC 2.4.4

D
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: #ffffff
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::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Page not found | PubMatic Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: PubMatic
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name PubMatic 192×192 icon 512×512 icon Start URL Display Mode standalone
Name PubMatic Display Mode standalone Theme Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 AI-POWERED ADVERTISING PERFORMANCE FOR P…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
32px · bottom of viewport
h3 OUR SOLUTIONS
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CUSTOMER STORIES
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 TCL Ads and PubMatic Scale CTV Monetizat…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Butler/Till Unlocks Greater Efficiency a…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PubMatic and Agence 79 Drive 14.3% Highe…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Chevrolet Arabia Exceeds CTR Benchmarks …
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Unlocking CTV Scale & Transparency With …
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 TCL Ads and PubMatic Scale CTV Monetizat…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Butler/Till Unlocks Greater Efficiency a…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PubMatic and Agence 79 Drive 14.3% Highe…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Chevrolet Arabia Exceeds CTR Benchmarks …
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Unlocking CTV Scale & Transparency With …
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 TCL Ads and PubMatic Scale CTV Monetizat…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 UPCOMING EVENTS
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 NEWS & RECOGNITION
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SCALE THAT DELIVERS
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 AI That Powers the Future of Digital Adv…
1.13:1
#000000
on
#011524
needs 3.0:1 (large text)
19px · bottom of viewport
title AI-Powered Ad Tech for Measurable Perfor…
1.07:1
#000000
on
#010B24
needs 4.5:1 (normal text)
16px · top of page (header area)
a Contact Us
1.07:1
#000000
on
#000C20
needs 4.5:1 (normal text)
16px · top of page (header area)

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)
ElementRatioRequiredFGBGResult
h1 AI-POWERED ADVERTISI…1.13:13.0:1
#000000
#011524
Fail
h3 OUR SOLUTIONS1.13:13.0:1
#000000
#011524
Fail
h3 CUSTOMER STORIES1.13:13.0:1
#000000
#011524
Fail
h3 TCL Ads and PubMatic…1.13:13.0:1
#000000
#011524
Fail
h3 Butler/Till Unlocks …1.13:13.0:1
#000000
#011524
Fail
h3 PubMatic and Agence …1.13:13.0:1
#000000
#011524
Fail
h3 Chevrolet Arabia Exc…1.13:13.0:1
#000000
#011524
Fail
h3 Unlocking CTV Scale …1.13:13.0:1
#000000
#011524
Fail
h3 TCL Ads and PubMatic…1.13:13.0:1
#000000
#011524
Fail
h3 Butler/Till Unlocks …1.13:13.0:1
#000000
#011524
Fail
h3 PubMatic and Agence …1.13:13.0:1
#000000
#011524
Fail
h3 Chevrolet Arabia Exc…1.13:13.0:1
#000000
#011524
Fail
h3 Unlocking CTV Scale …1.13:13.0:1
#000000
#011524
Fail
h3 TCL Ads and PubMatic…1.13:13.0:1
#000000
#011524
Fail
h3 UPCOMING EVENTS1.13:13.0:1
#000000
#011524
Fail
h3 NEWS & RECOGNITION1.13:13.0:1
#000000
#011524
Fail
h3 SCALE THAT DELIVERS1.13:13.0:1
#000000
#011524
Fail
h3 AI That Powers the F…1.13:13.0:1
#000000
#011524
Fail
title AI-Powered Ad Tech f…1.07:14.5:1
#000000
#010B24
Fail
a Contact Us1.07:14.5:1
#000000
#000C20
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 22 passed
REVIEW
89

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
READ ALL NEWS div.main > section.news-section > div.container > a#home_news_view_all
LEARN MORE div.hp-popup-block > div.hp-popup-body > div.hp-popup-col-copy > a.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
OUR SOLUTIONS div.container > div.row > div.col-xs-12 > h3.text-white

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-md-6 > a > nobr > img div.col-md-6 > a > nobr > img

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.

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
`[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
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[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.
Links have a discernible name
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
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.
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.
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
27 headings, 1 skip(s)
PASS
27 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 AI-POWERED ADVERTISING PERFORMANCE FOR PREMIUM DIGITAL MEDIA
  • H3 OUR SOLUTIONS skipped
  • H4 FOR PUBLISHERS
  • H4 FOR BUYERS
  • H4 FOR COMMERCE MEDIA
  • H4 FOR AGENTS
  • H3 CUSTOMER STORIES
  • H3 TCL Ads and PubMatic Scale CTV Monetization in Latin America
  • H3 Butler/Till Unlocks Greater Efficiency and Performance with PubMatic AgenticOS
  • H3 PubMatic and Agence 79 Drive 14.3% Higher Video Performance Through Data‑Driven Curation in France
  • H3 Chevrolet Arabia Exceeds CTR Benchmarks By 70% While Avoiding Over 1 Tonne Of Carbon Emissions
  • H3 Unlocking CTV Scale & Transparency With PubMatic Activate
  • H3 TCL Ads and PubMatic Scale CTV Monetization in Latin America
  • H3 Butler/Till Unlocks Greater Efficiency and Performance with PubMatic AgenticOS
  • H3 PubMatic and Agence 79 Drive 14.3% Higher Video Performance Through Data‑Driven Curation in France
  • H3 Chevrolet Arabia Exceeds CTR Benchmarks By 70% While Avoiding Over 1 Tonne Of Carbon Emissions
  • H3 Unlocking CTV Scale & Transparency With PubMatic Activate
  • H3 TCL Ads and PubMatic Scale CTV Monetization in Latin America
  • H3 UPCOMING EVENTS
  • H4 The Future of Brands 2026
  • H4 PubMatic @ Cannes
  • H3 NEWS & RECOGNITION
  • H4 PubMatic and Amnet Launch the First Agentic Advertising Campaign in France Using the Claude LLM
  • H4 Independent Agencies Gain Advanced Agentic Media Buying Through New PubMatic and Untapped Growth Collective Partnership
  • H4 PubMatic and Abovo Maxlead Deliver PubMatic’s First Agentic AI Advertising Campaigns in Europe
  • H3 SCALE THAT DELIVERS
  • H3 AI That Powers the Future of Digital Advertising

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
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-inputtextWhat can we help you find?for/id
#search-input-mobiletextWhat can we help you find?for/id
inputsubmit(none)none

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

<input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

Send Feedback