Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 421, bare page

FIX

HTTP 421, bare page

Unexpected status code: HTTP 421

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

Got: HTTP 421

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 421 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

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

HTML icon links detected

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

✗ favicon.ico Missing

✓ PNG Icons Present

✗ 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

15 landmarks

REVIEW

15 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

6 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA

h1 Simplify cookie compliance and consent m…

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Featured Products

1.00:1

#000000

needs 3.0:1 (large text)

24px · mid-page

h2 Regulatory Solutions

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 OneTrust Platform

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Self-Service Resources

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Training & Events

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Support

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Solutions

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Featured Products

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Regulatory Solutions

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 OneTrust Platform

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Self-Service Resources

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Training & Events

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Support

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Cookie Consent

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Operationalize cookie consent

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to get started?

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Top Searches

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 News

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Simplify cookie comp…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Solutions	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Featured Products	1.00:1	3.0:1	#000000	#000000	Fail
h2 Regulatory Solutions	1.00:1	3.0:1	#000000	#000000	Fail
h2 OneTrust Platform	1.00:1	3.0:1	#000000	#000000	Fail
h2 Self-Service Resourc…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Training & Events	1.00:1	3.0:1	#000000	#000000	Fail
h2 Support	1.00:1	3.0:1	#000000	#000000	Fail
h2 Solutions	1.00:1	3.0:1	#000000	#000000	Fail
h2 Featured Products	1.00:1	3.0:1	#000000	#000000	Fail
h2 Regulatory Solutions	1.00:1	3.0:1	#000000	#000000	Fail
h2 OneTrust Platform	1.00:1	3.0:1	#000000	#000000	Fail
h2 Self-Service Resourc…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Training & Events	1.00:1	3.0:1	#000000	#000000	Fail
h2 Support	1.00:1	3.0:1	#000000	#000000	Fail
h2 Cookie Consent	1.00:1	3.0:1	#000000	#000000	Fail
h2 Operationalize cooki…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Ready to get started…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Top Searches	1.00:1	3.0:1	#000000	#000000	Fail
h2 News	1.00:1	3.0:1	#000000	#000000	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.

A+

Heading Hierarchy

39 headings

PASS

39 headings

Single H1 present

H2 Solutions
H2 Featured Products
H2 Regulatory Solutions
H2 OneTrust Platform
H2 Self-Service Resources
H2 Training & Events
H2 Support
H2 Solutions
H2 Featured Products
H2 Regulatory Solutions
H2 OneTrust Platform
H2 Self-Service Resources
H2 Training & Events
H2 Support
H2 Cookie Consent
H1 Simplify cookie compliance and consent management
H2 Operationalize cookie consent
H3 Audit your website
H3 Automatically categorize cookies and trackers
H3 Easily configure the consent experience
H3 Enable cookie auto-blocking to ensure compliance
H3 Automate scanning and maintain records
H3 Optimize your cookie consent banner to maximize opt-ins
H3 Extend your consent options
H4 PWC x OneTrust: Youth privacy, safety & smarter consent experiences
H3 Related products
H3 Mobile App Consent
H3 OTT and CTV Consent
H3 Privacy Operations
H2 Ready to get started?
H3 See how OneTrust Consent & Preferences can help your organization build trusted digital experiences.
H2 Top Searches
H2 News
H2 Resources
H2 Company
H2 Glossary
H2 Contact Us
H2 Platform
H2 Our policies

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

2 image(s) with alt text over 125 characters

13 image(s) with good alt text

15 images 13 good alt text

Issue	Count
too long	2 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search query	aria-label
q	text	Search query	aria-label

A+

Link & Button Quality

1 issue(s) across 146 links and 37 buttons

PASS

1 issue(s) across 146 links and 37 buttons

1 link(s) with generic text

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

Got: /resources/youth-privacy-safety-and-smarter-consent-experiences-webinar/ ("Read more")

145 link(s) with descriptive text

146 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/resources/youth-privacy-safety-and-smar…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Youth Privacy Safety And Smarter Consent Experiences Webinar

182 links and buttons have descriptive text

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

/resources/youth-privacy-safety-and-smarter-consent-experiences-webinar/ ("Read 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

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 30 passed

PASS

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
April 30, 2026 `div.cmp-teaser__content-container > div.cmp-teaser__content > div.eyebrow > span.cmp-teaser__resourceDate`

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
Consent & Preferences `div#navigation-footer-link-list-v1-id-528519311 > ul.navigation-footer-link-list-v1-list-wrapper > li.navigation-footer-link-list-v1-list-item > a.navigation-footer-link-list-v1-list-item-link`
Third-Party Management `div#navigation-footer-link-list-v1-id-528519311 > ul.navigation-footer-link-list-v1-list-wrapper > li.navigation-footer-link-list-v1-list-item > a.navigation-footer-link-list-v1-list-item-link`
Resources `div#navigation-footer-link-list-v1-id-1791224624 > ul.navigation-footer-link-list-v1-list-wrapper > li.navigation-footer-link-list-v1-list-item > a.navigation-footer-link-list-v1-list-item-link`
Demo Videos `div#navigation-footer-link-list-v1-id-1791224624 > ul.navigation-footer-link-list-v1-list-wrapper > li.navigation-footer-link-list-v1-list-item > a.navigation-footer-link-list-v1-list-item-link`
Pricing and Packaging `div#navigation-footer-link-list-v1-id-1197725300 > ul.navigation-footer-link-list-v1-list-wrapper > li.navigation-footer-link-list-v1-list-item > a.navigation-footer-link-list-v1-list-item-link`
OneTrust Integrations `div#navigation-footer-link-list-v1-id-1197725300 > ul.navigation-footer-link-list-v1-list-wrapper > li.navigation-footer-link-list-v1-list-item > a.navigation-footer-link-list-v1-list-item-link`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mobile App Consent `div.filterable-card-grid__container > div.filterable-card-grid__card-row > div.filterable-card-grid__card-column > a.filterable-card-grid__card-container`
OTT and CTV Consent `div.filterable-card-grid__container > div.filterable-card-grid__card-row > div.filterable-card-grid__card-column > a.filterable-card-grid__card-container`
Privacy Operations `div.filterable-card-grid__container > div.filterable-card-grid__card-row > div.filterable-card-grid__card-column > a.filterable-card-grid__card-container`
Cookie Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

●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

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

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

●Buttons have an accessible name

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

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

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●`[lang]` attributes have a valid value

●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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

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

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

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

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