Skip to content
https://adweek.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Heading Hierarchy
Action
79 headings, 10 skip(s)
FIX
79 headings, 10 skip(s)
Warning::
Multiple H1 headings (10 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Beyond the Myths: Your Guide to Unleashing the Power of Streaming TV
  • H3 How Big Catalyzing Ideas Become Living Stories
  • H3 Where Bold Ideas Meet Big Results: Celebrating the 2025 Meta Agency Award Winners
  • H3 Decisions, Decisions: The Marketer’s Journey to Long-Term Success With Twitch
  • H3 Newsletters
  • H4 The Art of Making Fintech Cool With Catherine Ferdon of Coinbase.
  • H3 How AI Can Turn Social Media Marketing Into a Measurable Growth Engine
  • H3 How Big Catalyzing Ideas Become Living Stories
  • H3 Making a Splash—How Tree Hut Fast-Tracked New Product Momentum
  • H3 Beyond the Myths: Your Guide to Unleashing the Power of Streaming TV
  • H3 Think Outside the AI (Black) Box
  • H3 Decisions, Decisions: The Marketer’s Journey to Long-Term Success With Twitch
  • H3 How AI Can Turn Social Media Marketing Into a Measurable Growth Engine
  • H3 How Big Catalyzing Ideas Become Living Stories
  • H3 Making a Splash—How Tree Hut Fast-Tracked New Product Momentum
  • H3 Beyond the Myths: Your Guide to Unleashing the Power of Streaming TV
  • H3 Think Outside the AI (Black) Box
  • H3 Decisions, Decisions: The Marketer’s Journey to Long-Term Success With Twitch
  • H3 Beyond the Myths: Your Guide to Unleashing the Power of Streaming TV
  • H3 How Big Catalyzing Ideas Become Living Stories
  • H3 Where Bold Ideas Meet Big Results: Celebrating the 2025 Meta Agency Award Winners
  • H3 Decisions, Decisions: The Marketer’s Journey to Long-Term Success With Twitch
  • H3 Newsletters
  • H4 The Art of Making Fintech Cool With Catherine Ferdon of Coinbase.
  • H1 After Building In-House Agencies for Brands, Jeffrey Gorder Is Back Leading One
  • H4 Focus on Partnerships, Not Paychecks: Why Agencies Must Reinvent Themselves skipped
  • H4 Known Strengthens Client Leadership to Support Bigger Global Briefs
  • H4 FTC Orders WPP, Publicis, and Dentsu to Stop Alleged Brand Safety Collusion
  • H3 Juanjo Duran, Global Head of Media and Entertainment Content Partnerships at Google
  • H3 Vassili Samolis, Head of Ad Product, DoorDash
  • H3 Chris Riedy, Chief Revenue Officer, Ibotta
  • H1 Tim Cook Grew Apple by Reducing Its Ambition duplicate H1
  • H4 EXCLUSIVE: Mars Petcare’s CGO Najoh Tita-Reid is Exiting to Pursue Career in AI skipped
  • H4 Every Brand Needs An Enemy
  • H4 Gallo’s Britt West on Fixing Wine’s Relevance Problem and Recruiting the Next Generation
  • H3 How AI Can Turn Social Media Marketing Into a Measurable Growth Engine
  • H3 How Big Catalyzing Ideas Become Living Stories
  • H3 Making a Splash—How Tree Hut Fast-Tracked New Product Momentum
  • H3 Beyond the Myths: Your Guide to Unleashing the Power of Streaming TV
  • H3 Think Outside the AI (Black) Box
  • H3 Decisions, Decisions: The Marketer’s Journey to Long-Term Success With Twitch
  • H3 How AI Can Turn Social Media Marketing Into a Measurable Growth Engine
  • H3 How Big Catalyzing Ideas Become Living Stories
  • H3 Making a Splash—How Tree Hut Fast-Tracked New Product Momentum
  • H3 Beyond the Myths: Your Guide to Unleashing the Power of Streaming TV
  • H3 Think Outside the AI (Black) Box
  • H3 Decisions, Decisions: The Marketer’s Journey to Long-Term Success With Twitch
  • H1 Tim Cook Grew Apple by Reducing Its Ambition duplicate H1
  • H4 Meta Has Made Child Exploitation a Cost of Doing Business skipped
  • H4 The Cockroach of Marketing Concepts Will Never Die
  • H4 The Job That Broke Gucci Also Built Hermès
  • H1 Expedia Courts Non-Travel Brands With New Adtech Deal duplicate H1
  • H4 Pacvue Enters AI Agent Race With Amazon-Focused Tool skipped
  • H4 Audio Ads Are Coming to 6,000 More Dollar General Stores
  • H4 EXCLUSIVE: Intuit Is Shutting Down Its Ad Network for Small Businesses
  • H1 5 Ways Apple’s Marketing Evolved in the Tim Cook Era duplicate H1
  • H4 Beats and Jennie Are Back Together With an Unreleased Song and New Headphones skipped
  • H4 6 Coachella Brand Activations That Were Actually Worth Waiting in Line For
  • H4 Casper Returns to Advertising With Daymares You Can Finally Sleep Off
  • H1 Expedia Courts Non-Travel Brands With New Adtech Deal duplicate H1
  • H4 American Express Rolls Out New Tools In Big Bet on Agentic Shopping skipped
  • H4 Pacvue Enters AI Agent Race With Amazon-Focused Tool
  • H4 Audio Ads Are Coming to 6,000 More Dollar General Stores
  • H1 EXCLUSIVE: Leaked Deck Reveals StackAdapt’s Playbook for ChatGPT Ads duplicate H1
  • H4 Jellyfish Wants You to Use Large Language Models to Plan Your Ad Buys skipped
  • H4 Anthropic Debuts Claude Design for Building Marketing Assets, Decks, and UIs
  • H4 EXCLUSIVE: Complex Is Scaling Its Food Festival Family Style Into a Year-Round Media Brand
  • H1 Inside Paramount’s 2026 Upfront Dinners duplicate H1
  • H4 Netflix Ad Revenue Set to Reach $3 Billion in 2026, New Ad Products Coming skipped
  • H4 ESPN Reveals Football-Focused Creator Program Ahead of 2027 Super Bowl
  • H4 How The Daily Show Is Outsmarting the Social Media Algorithm
  • H1 The Power of Creator and Brand Collaboration Put to the Test duplicate H1
  • H4 Bringing Brands and Creators Together in the Participation Economy skipped
  • H4 Inside Coachella’s Off-Site Events That Are Rewriting the Festival’s Landscape
  • H4 ‘Brands Can’t Guide Culture’: Creators and Marketers on Ditching Skin-Deep Allyship
  • H1 Anthropic Debuts Claude Design for Building Marketing Assets, Decks, and UIs duplicate H1
  • H4 What Dove, Netflix, and Nike Didn’t Do on Reddit Is Why They’re Winning skipped
  • H4 FTC Orders WPP, Publicis, and Dentsu to Stop Alleged Brand Safety Collusion
  • H4 Google is Migrating Dynamic Search Ads to AI Max

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

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

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

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

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

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

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

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

D
404 Error Page
Action
HTTP 404, custom page
FIX
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓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
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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
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.
C
Landmark Structure
Action
20 landmarks
REVIEW
20 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (15 found)
A page should have only one <main> landmark.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN ASIDE CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #000 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 25 passed
REVIEW
85

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.nav-right-col > div.row > div.user-nav-and-hamburger-search > button#aw-nav-menu-icon div.nav-right-col > div.row > div.user-nav-and-hamburger-search > button#aw-nav-menu-icon
div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot
div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot
div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot
div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot
div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot
div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot div.adw-block > div.branded-squares-row-container-mobile > div.branded-squares-row-dots-mobile > button.branded-squares-row-dot

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#page > div#aw-nav-root > div.aw-logo-wrapper > a.toggle-light div#page > div#aw-nav-root > div.aw-logo-wrapper > a.toggle-light
div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a.homepage-list-first-image-link div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a.homepage-list-first-image-link
div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a
div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a
div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a
div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a div.adw-block > div.homepage-list-vertical-list > div.homepage-list-item > a

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.

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
ADWEEK div.mobile-alert-container > div.alert-content > div.alert-label > span.alert-brand
ALERT: div.mobile-alert-container > div.alert-content > div.alert-label > span.alert-type
TV UPFRONTS div.wp-block-column > section.teaser_partner_more > div.section--teaser_kicker > div.section__kickerlabel
More Podcasts div.container > div.row > div.col-xl-4 > a.btn

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
©2026 Adweek - All Rights Reserved Do not sell my personal information Terms of… div.row > div.col-12 > nav.footer-small-nav > ul.nav

These are opportunities to improve the experience of reading tabular or list data using 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
●Form elements have associated labels
●`[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
●`[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.
●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
●ARIA IDs are unique
●Identical links have the same purpose.
○`[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
○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
○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.
A
Alt Text Quality
4 of 143 images have issues
PASS
4 of 143 images have issues
Warning::
4 image(s) with generic alt text
Info::
41 decorative image(s) correctly marked
Info::
98 image(s) with good alt text
143 images 98 good alt text 41 decorative 4 generic
IssueCount
generic4 image(s)
A
Form Accessibility
1 of 9 controls have issues
PASS
1 of 9 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="text" id="aw-default-input">
Info::
8 control(s) properly labeled
9 controls
8 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#newsletter-id-4903013checkboxADWEEK Dailyfor/id
#newsletter-id-7622387checkboxAI, Tech & Moneyfor/id
#newsletter-id-7623895checkboxOn Backgroundfor/id
#newsletter-subscribe-email-inputemailEmailfor/id
#newsletter-id-4903013checkboxADWEEK Dailyfor/id
#newsletter-id-7622387checkboxAI, Tech & Moneyfor/id
#newsletter-id-7623895checkboxOn Backgroundfor/id
#newsletter-subscribe-email-inputemailEmailfor/id
#aw-default-inputtext(none)none

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

<input type="text" id="aw-default-input">

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

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Beyond the Myths: Yo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How Big Catalyzing…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Where Bold Ideas Mee…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Decisions, Decisions…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Newsletters21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How AI Can Turn Soci…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How Big Catalyzing…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Making a Splash—Ho…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Beyond the Myths: Yo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Think Outside the AI…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Decisions, Decisions…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How AI Can Turn Soci…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How Big Catalyzing…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Making a Splash—Ho…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Beyond the Myths: Yo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Think Outside the AI…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Decisions, Decisions…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Beyond the Myths: Yo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How Big Catalyzing…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Where Bold Ideas Mee…21.00:13.0: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.

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

Send Feedback