Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 7 REVIEW 4 FIX

Alt Text Quality

Action

4 of 46 images have issues

FIX

4 of 46 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image-in-link without alt text

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

1 image(s) with generic alt text

1 image(s) with alt text over 125 characters

31 decorative image(s) correctly marked

10 image(s) with good alt text

46 images 10 good alt text 31 decorative 1 generic 3 missing

Issue	Count
missing	3 image(s)
generic	1 image(s)
too long	1 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

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) 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

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

Heading Hierarchy

37 headings

REVIEW

37 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H4 Hot Topics
H3 DIGIDAY+ MEMBER EXCLUSIVES
H4 Future of TV Briefing: The ambitious and alarming proposal fix to TV and streaming’s identity crisis
H4 Digiday+ Research: Marketing workflows benefit from AI, but trust is still a barrier to adoption
H4 Ad Tech Briefing: The days of bloat are over, as efficiency drives ad tech’s C-suite exodus
H3 Media
H4 Bauer Media Group slashes publishing headcount in company-wide restructure
H4 Media Briefing: The ‘SaaS-pocalypse’ is spreading to publishers
H4 How college athlete Carson Roney went from TikTok dances to Gatorade commercials
H3 Marketing
H4 Puma’s AI head says the brand is still giving ‘the keys to the consumer’ as it invests in digital concierge
H4 The Rundown: Q1 dealmaking cools across ad tech and martech as AI remains the hottest ticket
H4 ‘Everything is coming down’: ChatGPT ads are getting cheaper
H3 Future of TV
H4 Future of TV Briefing: Netflix’s VOID peeks at the future of virtual product placement
H4 Future of TV Briefing: A TV advertising staple is missing from YouTube show sponsorships
H4 Future of TV Briefing: What publishers have to offer creators
H3 Media Buying
H4 As upfront negotiations near, buyers chart path through complex sports market
H4 Media Buying Briefing: As Q1 results from a few holdcos show, the market’s not panicking, yet
H4 U.K. brands increase media spend despite economic storm clouds
H3 Annual research reports
H4 Digiday+ Research: Publishers favor generative AI over predictive AI
H4 Digiday+ Research: Publishers apply AI to streamline tasks and improve audience experience
H4 Digiday+ Research: Retailers take a more complex approach to loyalty
H3 Podcasts
H4 Inside The Trade Desk’s programmatic power struggle
H4 Mondelez overhauls its $3.5 billion digital commerce strategy in era of AI search
H4 Why The Guardian’s first reader-facing AI product isn’t a chatbot
H3 Research
H4 Digiday+ Research: How Dow Jones, Forbes, The Guardian and other publisher revenue streams are shifting in 2026
H4 Digiday+ Research: Brand marketing will be the priority in 2026, after revenues fell short of expectations
H4 Digiday+ Research: Dow Jones, Business Insider and other publishers on AI-driven search
H3 DIGIDAY+
H3 My Account
H3 Newsletter
H3 Connect

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="search" name="s">; <input type="text" name="s">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
s	search	(Search …)	placeholder only
s	text	(Search)	placeholder only

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

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

Link & Button Quality

Action

2 issue(s) across 201 links and 0 buttons

REVIEW

2 issue(s) across 201 links and 0 buttons

2 link(s) with no accessible text

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

Got: #; #

9 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://digiday.com/marketing/openai-turns-on-cost-per-click-ads-inside-chatgpt/"]; a[href="https://digiday.com/marketing/marketing-strategists-search-for-a-solution-to-…"]; a[href="https://digiday.com/media/vibes-over-metrics-why-more-creators-are-holding-ir…"]; a[href="https://digiday.com/future-of-tv/future-of-tv-briefing-the-ambitious-and-alar…"]; a[href="https://digiday.com/media/how-the-financial-times-is-betting-on-personality-l…"]; a[href="https://digiday.com/podcasts/why-openai-is-running-at-lightning-speed-to-buil…"]; a[href="https://digiday.com/sponsored/how-native-ctv-is-solving-the-channels-attentio…"]; a[href="https://digiday.com/form/agencies-are-standing-out-with-human-led-service-as-…"]; a[href="https://digiday.com/marketing/digiday-research-marketing-workflows-benefit-fr…"]

190 link(s) with descriptive text

201 links

2 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://digiday.com/marketing/openai-tur…	OpenAI turns on cost-per-click…	img no alt	Add alt attribute to the image
https://digiday.com/marketing/marketing-…	Marketing strategists search f…	img no alt	Add alt attribute to the image
https://digiday.com/media/vibes-over-met…	Vibes over metrics: Why more c…	img no alt	Add alt attribute to the image
https://digiday.com/future-of-tv/future-…	Future of TV Briefing: The amb…	img no alt	Add alt attribute to the image
https://digiday.com/media/how-the-financ…	How The Financial Times is bet…	img no alt	Add alt attribute to the image
https://digiday.com/podcasts/why-openai-…	Why OpenAI is ‘running at li…	img no alt	Add alt attribute to the image
https://digiday.com/sponsored/how-native…	How native CTV is solving the …	img no alt	Add alt attribute to the image
https://digiday.com/form/agencies-are-st…	Agencies are standing out with…	img no alt	Add alt attribute to the image
https://digiday.com/marketing/digiday-re…	Digiday+ Research: Marketing w…	img no alt	Add alt attribute to the image

190 links and buttons have descriptive text

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

#; #

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://digiday.com/marketing/openai-turns-on-cost-per-click-ads-inside-chatgpt/"]; a[href="https://digiday.com/marketing/marketing-strategists-search-for-a-solution-to-…"]; a[href="https://digiday.com/media/vibes-over-metrics-why-more-creators-are-holding-ir…"]; a[href="https://digiday.com/future-of-tv/future-of-tv-briefing-the-ambitious-and-alar…"]; a[href="https://digiday.com/media/how-the-financial-times-is-betting-on-personality-l…"]; a[href="https://digiday.com/podcasts/why-openai-is-running-at-lightning-speed-to-buil…"]; a[href="https://digiday.com/sponsored/how-native-ctv-is-solving-the-channels-attentio…"]; a[href="https://digiday.com/form/agencies-are-standing-out-with-human-led-service-as-…"]; a[href="https://digiday.com/marketing/digiday-research-marketing-workflows-benefit-fr…"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Favicon & Branding

33 icon(s) detected

REVIEW

33 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

a Subscribe

1.16:1

#000000

#1E0D30

needs 4.5:1 (normal text)

16px · top of page (header area)

a Login

4.23:1

#000000

#766C81

needs 4.5:1 (normal text)

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

span Reader

1.16:1

#000000

#1E0D30

needs 4.5:1 (normal text)

16px · top of page (header area)

a FAQ

1.32:1

#000000

#1A232E

needs 4.5:1 (normal text)

16px · above the fold

a Account Overview

1.32:1

#000000

#1A232E

needs 4.5:1 (normal text)

16px · above the fold

a Logout

1.32:1

#000000

#1A232E

needs 4.5:1 (normal text)

16px · above the fold

a News

1.32:1

#000000

#1A232E

needs 4.5:1 (normal text)

16px · above the fold

a Digiday +

1.32:1

#000000

#1A232E

needs 4.5:1 (normal text)

16px · above the fold

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
h3 DIGIDAY+	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 My Account	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Newsletter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Connect	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Digiday — The home…	19.77:1	4.5:1	#000000	#F8F8F8	Pass
a Subscribe	1.16:1	4.5:1	#000000	#1E0D30	Fail
a Login	4.23:1	4.5:1	#000000	#766C81	Fail
span Reader	1.16:1	4.5:1	#000000	#1E0D30	Fail
span Digiday+ Member	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Subscribe Now	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Digiday+ homepage	8.59:1	4.5:1	#000000	#A3A6AA	Pass
a FAQ	1.32:1	4.5:1	#000000	#1A232E	Fail
a Account Overview	1.32:1	4.5:1	#000000	#1A232E	Fail
a Logout	1.32:1	4.5:1	#000000	#1A232E	Fail
a News	1.32:1	4.5:1	#000000	#1A232E	Fail
a Digiday +	1.32:1	4.5:1	#000000	#1A232E	Fail
a Podcasts	8.67:1	4.5:1	#000000	#A3A7AB	Pass
a Events	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Awards	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a News	21.00:1	4.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.

Lighthouse Accessibility Audits

Score 89/100 — 3 failing, 24 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
SUBSCRIBE `div.right > div.tinypass-menu > div.logged-out > a.subscribe`
SECURE YOUR SEAT `div.cta-promo-section > div.cta-promo-section-wrapper > div.content-part > a.action-button`
DIGIDAY+ MEMBER EXCLUSIVES `div.container > div.section-title-contain > h3.home-section-title > span.exclusives-label`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
Subscribe to Digiday+ `div#tp-member-exclusives-text > div.subscribe-contain > div.piano-logged-out > a`
MEMBER EXCLUSIVE `li.plus > div.flex-holder > div.eyebrow > a`
SPONSORED `li.sponsored > div.flex-holder > div.eyebrow > a`
MEMBER EXCLUSIVE `li.plus > div.flex-holder > div.eyebrow > a`
SPONSORED `li.sponsored > div.flex-holder > div.eyebrow > a`
MEMBER EXCLUSIVE `li.plus > div.flex-holder > div.eyebrow > a`
SPONSORED `li.sponsored > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `li.plus > div.news-content > div.eyebrow > a`
SPONSORED `li.sponsored > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
MEMBER EXCLUSIVE `div.block-text > div.news-content > div.eyebrow > a`
BEAUTY `div.col > div.featured-post-wrapper > div.data > div.upper-title`
BEAUTY `ul.media-posts > li > div.posts-content > div.upper-title`
MEMBER EXCLUSIVE `ul.media-posts > li > div.posts-content > div.upper-title`
AWARDS `ul.media-posts > li > div.posts-content > div.upper-title`
BEAUTY `ul.media-posts > li > div.posts-content > div.upper-title`
FASHION `ul.media-posts > li > div.posts-content > div.upper-title`
MEMBER EXCLUSIVE `div.col > div.featured-post-wrapper > div.data > div.upper-title`
MARKETING `ul.media-posts > li > div.posts-content > div.upper-title`
OPERATIONS `ul.media-posts > li > div.posts-content > div.upper-title`
AWARDS `ul.media-posts > li > div.posts-content > div.upper-title`
MEMBER EXCLUSIVE `ul.media-posts > li > div.posts-content > div.upper-title`
MEMBER EXCLUSIVE `ul.media-posts > li > div.posts-content > div.upper-title`

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.nav-wrapper > div.top_row > div.left > a.icon `div.nav-wrapper > div.top_row > div.left > a.icon`

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Modal Overlay Box Frame `div.newsletter > div#lightbox-inline-form-2df6713e-a3c1-45fa-aa28-db3c835d5eaa > div#lightbox-2df6713e-a3c1-45fa-aa28-db3c835d5eaa-1776888795788 > iframe#lightbox-iframe-2df6713e-a3c1-45fa-aa28-db3c835d5eaa`

These are opportunities to improve keyboard navigation in your application.

○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

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

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

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

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

○Buttons have an accessible name

○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

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

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Digiday

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Digiday ✓192×192 icon ✓512×512 icon ✓Start URL https://digiday.com ✓Display Mode standalone ✓

Name Digiday Display Mode standalone Theme Color #ffffff Icons 2 icon(s)

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