Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 6 REVIEW 4 FIX

Link & Button Quality

Action

11 issue(s) across 80 links and 6 buttons

FIX

11 issue(s) across 80 links and 6 buttons

4 link(s) with no accessible text

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

Got: /the-tapad-graph; /the-tapad-graph; https://www.facebook.com/tapadinc; https://www.linkedin.com/company/tapad

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /solutions/switchboard ("LEARN MORE")

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.experian.com/blogs/marketing-forward/; https://engineering.tapad.com/; https://www.eprivacy.eu/en/customers/awarded-seals/company/tapad-inc/

6 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.hamburger-button (#112 on page); button.owl-prev (#299 on page); button.owl-next (#302 on page); button.owl-dot (#305 on page); button.owl-dot (#307 on page); button.owl-dot (#309 on page)

72 link(s) with descriptive text

80 links

4 empty

1 generic text

3 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://www.experian.com/blogs/marketing…	Experian Marketing Blog	new tab	Add '(opens in new tab)' to text
https://engineering.tapad.com/	Engineering Blog	new tab	Add '(opens in new tab)' to text
/solutions/switchboard	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Switchboard
/the-tapad-graph	(empty)	empty	Add link text or aria-label
/the-tapad-graph	(empty)	empty	Add link text or aria-label
https://www.eprivacy.eu/en/customers/awa…	EDAA Certification	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/tapadinc	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/tapad	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

72 links and buttons have descriptive text

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

/the-tapad-graph; /the-tapad-graph; https://www.facebook.com/tapadinc; https://www.linkedin.com/company/tapad

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

Generic link text like 'click here' doesn't describe the destination.

/solutions/switchboard ("LEARN MORE")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.experian.com/blogs/marketing-forward/; https://engineering.tapad.com/; https://www.eprivacy.eu/en/customers/awarded-seals/company/tapad-inc/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.hamburger-button (#112 on page); button.owl-prev (#299 on page); button.owl-next (#302 on page); button.owl-dot (#305 on page); button.owl-dot (#307 on page); button.owl-dot (#309 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

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

7 landmarks

REVIEW

7 landmarks

<main> landmark present

5 <nav> landmark(s) found

5 of 5 <nav> elements are unlabeled

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

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

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

Heading Hierarchy

32 headings, 1 skip(s)

REVIEW

32 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 The Tapad Graph
H3 Switchboard
H3 Hashed Email
H3 Mobile Connections
H3 CTV
H3 IP Onboarding
H3 Brands
H3 Agencies
H3 Platforms
H3 Experian Marketing Blog
H3 Engineering Blog
H3 About us
H3 Leadership
H3 Privacy
H3 News
H3 Careers
H3 Find Us
H3 Tapad Life
H1 Adapt with Tapad
H3 We provide the world’s leading digital cross-device graph skipped
H2 Enabling a better understanding of the consumer decision journey
H3 We enable brands, agencies and platforms to unlock results
H4 Target and measure
H4 Reach and scale
H4 Data enrichment
H4 Personalization
H3 As your partner, we make The Tapad Graph work for you
H3 (empty)
H3 Identity
H3 Solutions
H3 Resources
H3 Company

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Tapad ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

7 icon(s) detected

REVIEW

7 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

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: tapad

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name tapad ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Name tapad Theme Color #ffffff Icons 2 icon(s)

Lighthouse Accessibility Audits

Action

Score 78/100 — 4 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.

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
nav#nav-primary > div#mobile-nav > div#mobile-nav-toggle > button.hamburger-button `nav#nav-primary > div#mobile-nav > div#mobile-nav-toggle > button.hamburger-button`
div.content-slider-wrapper > div.content-slider > div.owl-nav > button.owl-prev `div.content-slider-wrapper > div.content-slider > div.owl-nav > button.owl-prev`
div.content-slider-wrapper > div.content-slider > div.owl-nav > button.owl-next `div.content-slider-wrapper > div.content-slider > div.owl-nav > button.owl-next`
div.content-slider-wrapper > div.content-slider > div.owl-dots > button.owl-dot `div.content-slider-wrapper > div.content-slider > div.owl-dots > button.owl-dot`
div.content-slider-wrapper > div.content-slider > div.owl-dots > button.owl-dot `div.content-slider-wrapper > div.content-slider > div.owl-dots > button.owl-dot`
div.content-slider-wrapper > div.content-slider > div.owl-dots > button.owl-dot `div.content-slider-wrapper > div.content-slider > div.owl-dots > button.owl-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.owl-item > div.container1 > div.row > a `div.owl-item > div.container1 > div.row > a`
div.owl-item > div.container1 > div.row > a `div.owl-item > div.container1 > div.row > a`
div.row > div.footer-icons > div.social-icons > a `div.row > div.footer-icons > div.social-icons > a`
div.row > div.footer-icons > div.social-icons > a `div.row > div.footer-icons > div.social-icons > 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
WE PROVIDE THE WORLD’S LEADING DIGITAL CROSS-DEVICE GRAPH `div.container > div.d-flex > div.home-intro-paragraph-inner > h3`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.fontawesome-i2svg-active `html.fontawesome-i2svg-active`

These are opportunities to improve the interpretation of your content by users in different locales.

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Uses ARIA roles only on compatible elements

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

○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 a valid value for its `[lang]` attribute

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

○Links are distinguishable without relying on color.

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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

Alt Text Quality

4 of 35 images have issues

PASS

4 of 35 images have issues

4 image(s) with generic alt text

1 decorative image(s) correctly marked

30 image(s) with good alt text

35 images 30 good alt text 1 decorative 4 generic

Issue	Count
generic	4 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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)

Element	Ratio	Required	FG	BG	Result
h1 Adapt with Tapad	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Enabling a better un…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The Tapad Graph	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Switchboard	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hashed Email	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Mobile Connections	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 CTV	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 IP Onboarding	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Brands	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Agencies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Platforms	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Experian Marketing B…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Engineering Blog	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Leadership	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Privacy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Careers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Find Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Tapad Life	21.00:1	3.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.