Skip to content
https://networkadvertising.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
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
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 - The NAI: Network Advertising Initiative ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
a How to Opt Out
1.15:1
#000000
on
#10064C
needs 4.5:1 (normal text)
16px · top of page (header area)
a For Members
1.24:1
#000000
on
#1A1052
needs 4.5:1 (normal text)
16px · top of page (header area)
a Careers
1.15:1
#000000
on
#10064C
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Get the latest.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy, Trust21.00:13.0:1
#000000
#FFFFFF
Pass
h2 & Accountability21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Footer21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Public Policy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Blog21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Press Releases21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Public Policy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Blog21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Press Releases21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Public Policy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Blog21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Press Releases21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Public Policy21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Blog21.00:13.0:1
#000000
#FFFFFF
Pass
title Home - The NAI: Netw…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
a How to Opt Out1.15:14.5:1
#000000
#10064C
Fail
a For Members1.24:14.5:1
#000000
#1A1052
Fail
a Careers1.15:14.5:1
#000000
#10064C
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 80/100 — 4 failing, 18 passed
REVIEW
80

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Public Policy The NAI Provides Input on CalPrivacy Preliminary Comment Invitati… div#tns1-mw > div#tns1-iw > div#tns1 > div.w-screen
Blog The NAI Publishes Annual Report: 2025 Privacy Review Cycle Read More The … div#tns1-mw > div#tns1-iw > div#tns1 > div.w-screen
Press Releases Statement from NAI President & CEO Leigh Freund on the CalPrivac… div#tns1-mw > div#tns1-iw > div#tns1 > div.w-screen
Press Releases Statement from NAI President & CEO Leigh Freund on the CalPrivac… div#tns1-mw > div#tns1-iw > div#tns1 > div#tns1-item1
Public Policy The NAI Provides Input on CalPrivacy Preliminary Comment Invitati… div#tns1-mw > div#tns1-iw > div#tns1 > div#tns1-item2
Blog The NAI Publishes Annual Report: 2025 Privacy Review Cycle Read More The … div#tns1-mw > div#tns1-iw > div#tns1 > div.w-screen
Press Releases Statement from NAI President & CEO Leigh Freund on the CalPrivac… div#tns1-mw > div#tns1-iw > div#tns1 > div.w-screen
Public Policy The NAI Provides Input on CalPrivacy Preliminary Comment Invitati… div#tns1-mw > div#tns1-iw > div#tns1 > div.w-screen
Blog The NAI Publishes Annual Report: 2025 Privacy Review Cycle Read More The … div#tns1-mw > div#tns1-iw > div#tns1 > div.w-screen

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.py-12 > div.w-full > div.relative > button.latest-prev-2 div.py-12 > div.w-full > div.relative > button.latest-prev-2
div.w-full > div.relative > div.px-3 > button.latest-bullet div.w-full > div.relative > div.px-3 > button.latest-bullet
div.w-full > div.relative > div.px-3 > button.latest-bullet div.w-full > div.relative > div.px-3 > button.latest-bullet
div.w-full > div.relative > div.px-3 > button.latest-bullet div.w-full > div.relative > div.px-3 > button.latest-bullet
div.py-12 > div.w-full > div.relative > button.latest-next-2 div.py-12 > div.w-full > div.relative > button.latest-next-2

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
Press div.py-12 > div.px-6 > div.flex > button.text-lg
Public Policy div.py-12 > div.px-6 > div.flex > button.text-lg

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.relative > div.px-3 > button.latest-bullet div.w-full > div.relative > div.px-3 > button.latest-bullet
div.w-full > div.relative > div.px-3 > button.latest-bullet div.w-full > div.relative > div.px-3 > button.latest-bullet
div.w-full > div.relative > div.px-3 > button.latest-bullet div.w-full > div.relative > div.px-3 > button.latest-bullet

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>`
●`[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 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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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.
○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
Landmark Structure
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer
A
Heading Hierarchy
50 headings
PASS
50 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Get the latest.
  • H3 Public Policy
  • H4 The NAI Provides Input on CalPrivacy Preliminary Comment Invitation to Reduce Friction in Privacy Rights and Opt-Out Signals
  • H4 The NAI Sends Letter to CalPrivacy Supporting New Regulations under CCPA
  • H4 The NAI and IAB Comment on CFPB ANPRM
  • H3 Blog
  • H4 The NAI Publishes Annual Report: 2025 Privacy Review Cycle
  • H4 The NAI Develops Factor Analysis for Health-Related Sensitive Personal Information
  • H4 MCP and Agents: Perils and Prospects
  • H3 Press Releases
  • H4 Statement from NAI President & CEO Leigh Freund on the CalPrivacy Settlement with PlayOn Sports Decision
  • H4 Press Release: NEW Board of Directors for 2026/2027 Term
  • H4 The NAI Issues Statement on California’s Enactment of AB 566
  • H3 Public Policy
  • H4 The NAI Provides Input on CalPrivacy Preliminary Comment Invitation to Reduce Friction in Privacy Rights and Opt-Out Signals
  • H4 The NAI Sends Letter to CalPrivacy Supporting New Regulations under CCPA
  • H4 The NAI and IAB Comment on CFPB ANPRM
  • H3 Blog
  • H4 The NAI Publishes Annual Report: 2025 Privacy Review Cycle
  • H4 The NAI Develops Factor Analysis for Health-Related Sensitive Personal Information
  • H4 MCP and Agents: Perils and Prospects
  • H3 Press Releases
  • H4 Statement from NAI President & CEO Leigh Freund on the CalPrivacy Settlement with PlayOn Sports Decision
  • H4 Press Release: NEW Board of Directors for 2026/2027 Term
  • H4 The NAI Issues Statement on California’s Enactment of AB 566
  • H3 Public Policy
  • H4 The NAI Provides Input on CalPrivacy Preliminary Comment Invitation to Reduce Friction in Privacy Rights and Opt-Out Signals
  • H4 The NAI Sends Letter to CalPrivacy Supporting New Regulations under CCPA
  • H4 The NAI and IAB Comment on CFPB ANPRM
  • H3 Blog
  • H4 The NAI Publishes Annual Report: 2025 Privacy Review Cycle
  • H4 The NAI Develops Factor Analysis for Health-Related Sensitive Personal Information
  • H4 MCP and Agents: Perils and Prospects
  • H3 Press Releases
  • H4 Statement from NAI President & CEO Leigh Freund on the CalPrivacy Settlement with PlayOn Sports Decision
  • H4 Press Release: NEW Board of Directors for 2026/2027 Term
  • H4 The NAI Issues Statement on California’s Enactment of AB 566
  • H3 Public Policy
  • H4 The NAI Provides Input on CalPrivacy Preliminary Comment Invitation to Reduce Friction in Privacy Rights and Opt-Out Signals
  • H4 The NAI Sends Letter to CalPrivacy Supporting New Regulations under CCPA
  • H4 The NAI and IAB Comment on CFPB ANPRM
  • H3 Blog
  • H4 The NAI Publishes Annual Report: 2025 Privacy Review Cycle
  • H4 The NAI Develops Factor Analysis for Health-Related Sensitive Personal Information
  • H4 MCP and Agents: Perils and Prospects
  • H1 NAI Membership Benefits
  • H2 Privacy, Trust & Accountability
  • H1 Understanding Digital Advertising duplicate H1
  • H2 Join the NAI
  • H2 Footer

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

A
Alt Text Quality
13 of 92 images have issues
PASS
13 of 92 images have issues
Warning::
13 image(s) with generic alt text
Info::
78 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
92 images 1 good alt text 78 decorative 13 generic
IssueCount
generic13 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
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.

Send Feedback