Skip to content
https://casalemedia.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Landmark Structure
Action
9 landmarks
FIX
9 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://casalemedia.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://casalemedia.com/manifest.json

Manifest contains invalid JSON.

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::
3 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 3 <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.
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h2 We’re a global supply-side platform re…
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Bringing more quality, efficiency, and t…
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 See what sets us apart
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The latest from Index Explains
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest from the blog
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We’re here to help
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Solutions
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Platform
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get in Touch
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Customer Access
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Streaming TV
1.34:1
#000000
on
#012920
needs 3.0:1 (large text)
19px · mid-page
h3 Inventory Packages
1.32:1
#000000
on
#00281F
needs 3.0:1 (large text)
19px · mid-page
h3 Partners and Integrations
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Index Explains →
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Innovators Unscripted →
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Our DEI&B Philosophy →
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Candidate FAQs →
1.85:1
#000000
on
#034333
needs 3.0:1 (large text)
19px · bottom of viewport

2 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 Elevating ad tech to…11.32:13.0:1
#FFFFFF
#034333
Pass
h2 We’re a global sup…1.85:13.0:1
#000000
#034333
Fail
h2 Bringing more qualit…1.85:13.0:1
#000000
#034333
Fail
h2 See what sets us apa…1.85:13.0:1
#000000
#034333
Fail
h2 The latest from Inde…1.85:13.0:1
#000000
#034333
Fail
h2 Latest from the blog1.85:13.0:1
#000000
#034333
Fail
h2 We’re here to help1.85:13.0:1
#000000
#034333
Fail
h2 Solutions1.85:13.0:1
#000000
#034333
Fail
h2 Platform1.85:13.0:1
#000000
#034333
Fail
h2 Resources1.85:13.0:1
#000000
#034333
Fail
h2 Get in Touch1.85:13.0:1
#000000
#034333
Fail
h2 About1.85:13.0:1
#000000
#034333
Fail
h2 Customer Access1.85:13.0:1
#000000
#034333
Fail
h3 Streaming TV1.34:13.0:1
#000000
#012920
Fail
h3 Inventory Packages1.32:13.0:1
#000000
#00281F
Fail
h3 Partners and Integra…1.85:13.0:1
#000000
#034333
Fail
h3 Index Explains →1.85:13.0:1
#000000
#034333
Fail
h3 Innovators Unscripte…1.85:13.0:1
#000000
#034333
Fail
h3 Our DEI&B Philosophy…1.85:13.0:1
#000000
#034333
Fail
h3 Candidate FAQs →1.85:13.0:1
#000000
#034333
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.

A+
Heading Hierarchy
48 headings
PASS
48 headings
Info::
Single H1 present
  • H4 Exchange Standards
  • H4 Products
  • H3 Streaming TV
  • H3 Inventory Packages
  • H4 For Media Owners
  • H4 For Media Buyers
  • H4 Partners
  • H3 Partners and Integrations
  • H4 Learn
  • H4 Connect
  • H3 Index Explains →
  • H3 Innovators Unscripted →
  • H4 Our Company
  • H4 Our Values
  • H3 Our DEI&B Philosophy →
  • H4 Working at Index
  • H4 Open Roles
  • H3 Candidate FAQs →
  • H1 Elevating ad tech to exceptional standards
  • H2 We're Excited to be at POSSIBLE 2026
  • H2 We’re a global supply-side platform revolutionizing ad technology
  • H2 Bringing more quality, efficiency, and transparency to every channel
  • H2 See what sets us apart
  • H3 Our vision is to deliver total market efficiency
  • H3 Our team is changing ad tech for the better
  • H2 The latest from Index Explains
  • H3 Why Duration-Based Ad Measurement Matters for Streaming TV Publishers
  • H3 Why Duration-Based Ad Measurement Matters for Streaming TV Publishers
  • H3 Key Questions Media Owners Should Ask About Programmatic Curation
  • H3 Key Questions Media Owners Should Ask About Programmatic Curation
  • H3 Why Programmatic Efficiency Matters in the Age of AI
  • H3 Why Programmatic Efficiency Matters in the Age of AI
  • H3 Who’s Who in the Programmatic Brand Safety Landscape
  • H3 Who’s Who in the Programmatic Brand Safety Landscape
  • H3 Understanding Ad Fraud and How To Safeguard Your Campaigns
  • H3 Understanding Ad Fraud and How To Safeguard Your Campaigns
  • H2 Latest from the blog
  • H3 Sell-Side Decisioning for Media Owners: How To Create More Value in Programmatic
  • H3 AI’s Impact on Publishers: Why News Is Emerging as a Resilient and Valuable Category
  • H3 Programmatic’s Agentic Future Needs a Stronger Foundation
  • H2 We’re here to help
  • H2 Solutions
  • H2 Platform
  • H2 Resources
  • H2 Get in Touch
  • H2 About
  • H2 Customer Access
  • H2 Get the latest advertising news, trends, and expert opinions delivered straight to your inbox.
A+
Alt Text Quality
All 32 images OK
PASS
All 32 images OK
Info::
18 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
32 images 14 good alt text 18 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearch(Type to search)placeholder only

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

<input type="search" name="s">

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

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

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.

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#page > header#masthead > div.row > button#hamburger-menu div#page > header#masthead > div.row > button#hamburger-menu

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
Index Linkedin profile div.menu-footer-social-links-container > ul#menu-footer-social-links > li#menu-item-2016222 > a
Index Exchange Twitter profile div.menu-footer-social-links-container > ul#menu-footer-social-links > li#menu-item-2016237 > a
Index Exchange Youtube profile div.menu-footer-social-links-container > ul#menu-footer-social-links > li#menu-item-2016223 > a
Index Exchange Instagram account div.menu-footer-social-links-container > ul#menu-footer-social-links > li#menu-item-2016238 > a
footer#colophon > div.site-info > div.p-0 > a.custom-logo footer#colophon > div.site-info > div.p-0 > a.custom-logo

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
●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
●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
●Background and foreground colors have a sufficient contrast ratio
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback