Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Landmark Structure

2 landmarks

REVIEW

2 landmarks

<main> landmark present

No <nav> landmark found

No contentinfo (footer) 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

p In response to browser and device provid…

3.37:1

#000000

#845639

needs 4.5:1 (normal text)

16px · above the fold

p This page explains opt-out choices for T…

2.18:1

#000000

#673918

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

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
h1 Control Over Your Pe…	15.68:1	3.0:1	#000000	#DADFE6	Pass
h2 Cookie Based Opt-Out	4.86:1	3.0:1	#000000	#91745E	Pass
h2 Industry Opt Out Pag…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Device/Apps Opt Out	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Opting Out of Other …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Data Access Portal \|…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Looking for the Unif…	20.08:1	4.5:1	#000000	#F4FBFE	Pass
p By following the ins…	12.00:1	4.5:1	#000000	#BDC4D3	Pass
p In response to brows…	3.37:1	4.5:1	#000000	#845639	Fail
p This page explains o…	2.18:1	4.5:1	#000000	#673918	Fail
p Some things to keep …	8.52:1	4.5:1	#000000	#AFA399	Pass
li If you use more than…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
li If you clear or dele…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
li Even after opting ou…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
li After you opt-out, y…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Please note that if …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a You can opt-out of t…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span A Trade Desk opt out…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span An error occurred wh…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p The online advertisi…	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 83/100 — 3 failing, 15 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
Looking for the Unified ID Solution? `body > header#masthead > div#right > a`
YOU CAN OPT-OUT OF TARGETED ADVERTISING BASED ON THE TRADE DESK'S BROWSER COOKI… `div.negative-top > div.page-content > div#opt-out > a.button`
www.aboutads.info/choices `div.page-content > ul > li > a`
www.networkadvertising.org/choices `div.page-content > ul > li > a`
www.youradchoices.ca/choices `div.page-content > ul > li > a`
www.youronlinechoices.com `div.page-content > ul > li > a`
here. `div.page-content > ul > li > a`
here. `div.page-content > ul > li > a`
liveramp.com/opt-out `div.page-content > ul > li > a`
transparentadvertising.org `div.page-content > ul > li > a`
transparentadvertising.eu `div.page-content > ul > li > a`
here. `div.negative-top > div.page-content > p > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
www.youradchoices.ca/choices `div.page-content > ul > li > a`
www.youronlinechoices.com `div.page-content > ul > li > a`
here. `div.page-content > ul > li > a`
here. `div.page-content > ul > li > a`
liveramp.com/opt-out `div.page-content > ul > li > a`
here. `div.negative-top > div.page-content > p > a`

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
body > header#masthead > a `body > header#masthead > 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.

○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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

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

○No element has a `[tabindex]` value greater than 0

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

Heading Hierarchy

5 headings

PASS

5 headings

Single H1 present

H1 Control Over Your Personal Information
H2 Cookie Based Opt-Out
H2 Industry Opt Out Pages
H2 Device/Apps Opt Out
H2 Opting Out of Other Identifiers

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

1 issue(s) across 14 links and 0 buttons

PASS

1 issue(s) across 14 links and 0 buttons

1 link(s) with no accessible text

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

Got: https://www.thetradedesk.com/industry-initiatives/unified-id-solution

13 link(s) with descriptive text

14 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.thetradedesk.com/industry-in…	(empty)	empty	Add link text or aria-label

13 links and buttons have descriptive text

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

https://www.thetradedesk.com/industry-initiatives/unified-id-solution

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

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