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 3 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://optimizely.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://optimizely.com/manifest.json

Manifest contains invalid JSON.

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: #080736

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 ✗

Form Accessibility

Action

4 of 12 controls have issues

REVIEW

4 of 12 controls have issues

1 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

3 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="searchInput" id="searchInput-d3b6ab79-8f79-496b-9648-b4fbec71ddea">; <input type="text" name="searchInput" id="searchInput-b2f0a090-9ec0-4aa4-a272-03b8d8a1a289">; <input type="text" name="searchInput" id="searchInput-4c2dcf38-1ee1-4d45-800b-f01824138a86">

8 control(s) properly labeled

12 controls

8 labeled

3 placeholder only

1 unlabeled

Control	Type	Label	Method
#ef474ec4-6d5f-4973-aac2-1c2b4577256e	email	Work email	for/id
#a4719c00-8c5e-42f1-933d-e2bd74987f14	text	First name	for/id
#7cea93dd-8b42-4a0e-a62b-cd1ed118df47	text	Last name	for/id
#b57c21bb-d504-4dc9-ac61-8f410a73a816	text	Company	for/id
#94261b87-7762-4967-8add-4fd24dcf419d	text	Job title	for/id
#7e5fc409-2421-4401-99b1-5de6cc0e478a	tel	Phone	for/id
#0d9a753c-6ebc-4a09-a5a9-b023f1305c52	radio	Yes	none
#6ab15ef0-755d-4e02-b38b-1a27730f1276	radio	No	none
#searchInput-4c2dcf38-1ee1-4d45-800b-f01824138a86	text	(Please select)	placeholder only
#searchInput-d3b6ab79-8f79-496b-9648-b4fbec71ddea	text	(Select a country)	placeholder only
#searchInput-b2f0a090-9ec0-4aa4-a272-03b8d8a1a289	text	(Please select)	placeholder only
#g-recaptcha-response-100000	textarea	(none)	none

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

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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h1 Global HQ

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Products

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Resources

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Company

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Content and experiences that do everythi…

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Test, personalize, and analyze: good thi…

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Commerce with a clever twist

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Did we mention AI?

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We’re a real team player

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get in touch

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Just a few details first

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Accelerate the entire content supply cha…

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Create meaningful 1:1 interactions, ever…

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Turn your storefront into a conversion e…

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Meet Optimizely Opal: your infinite work…

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Watch a demo

2.39:1

#000000

#6E3F19

needs 3.0:1 (large text)

19px · bottom of viewport

title World's leading AI-powered digital exper…

1.13:1

#000000

#0E131B

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Global HQ	2.39:1	3.0:1	#000000	#6E3F19	Fail
h1 Products	2.39:1	3.0:1	#000000	#6E3F19	Fail
h1 Resources	2.39:1	3.0:1	#000000	#6E3F19	Fail
h1 Company	2.39:1	3.0:1	#000000	#6E3F19	Fail
h2 Everything you need …	14.43:1	3.0:1	#000000	#BEDAEC	Pass
h2 Ready, set, scale: M…	19.18:1	3.0:1	#000000	#F0F6F3	Pass
h2 Content and experien…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h2 Test, personalize, a…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h2 Commerce with a clev…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h2 Did we mention AI?	2.39:1	3.0:1	#000000	#6E3F19	Fail
h2 We’re a real team …	2.39:1	3.0:1	#000000	#6E3F19	Fail
h2 Get in touch	2.39:1	3.0:1	#000000	#6E3F19	Fail
h2 Just a few details f…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h3 Optimize every part …	9.15:1	3.0:1	#000000	#9FAEAF	Pass
h3 Accelerate the entir…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h3 Create meaningful 1:…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h3 Turn your storefront…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h3 Meet Optimizely Opal…	2.39:1	3.0:1	#000000	#6E3F19	Fail
h3 Watch a demo	2.39:1	3.0:1	#000000	#6E3F19	Fail
title World's leading AI-p…	1.13:1	4.5:1	#000000	#0E131B	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.

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

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

Skip navigation link present

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

Heading Hierarchy

30 headings

PASS

30 headings

Multiple H1 headings (5 found)

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

H1 AI-powered digital experiences that turn headsAI-powered digital experiences that turn heads
H2 Everything you need to run marketing, all in One
H2 Ready, set, scale: Meet your AI agents
H3 Optimize every part of your digital experience
H4 Ditch that ‘gut-feel’
H4 35%
H2 Content and experiences that do everything but disappoint
H3 Accelerate the entire content supply chain
H4 Next level website
H4 How Valtech empowers marketing teams across the globe
H4 37%
H2 Test, personalize, and analyze: good things come in threes
H3 Create meaningful 1:1 interactions, every time
H4 12%
H4 Code smarter, not harder
H4 Crafting personalized experiences for 20 million users
H2 Commerce with a clever twist
H3 Turn your storefront into a conversion engine
H4 Gerrie Electric powers a digital B2B transformation
H4 Build better, sell faster
H2 Did we mention AI?
H3 Meet Optimizely Opal: your infinite workforce
H2 We’re a real team player
H2 Get in touch
H2 Just a few details first
H3 Watch a demo
H1 Global HQ duplicate H1
H1 Products duplicate H1
H1 Resources duplicate H1
H1 Company duplicate H1

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

All 25 images OK

PASS

All 25 images OK

3 decorative image(s) correctly marked

22 image(s) with good alt text

25 images 22 good alt text 3 decorative

All images have appropriate alt text.

A+

Link & Button Quality

53 links, 18 buttons — all OK

PASS

53 links, 18 buttons — all OK

53 link(s) with descriptive text

53 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

71 links and buttons have descriptive text

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 24 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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Set it. Sweat it. Send it. `div > svg > g > g`
Set it. Sweat it. `div > svg > g > g`
Send it. `div > svg > g > g`

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.

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
One `div.col-12 > div > h2.mb-2 > em`

These are opportunities to improve the legibility of your content.

○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

●Buttons have an accessible name

●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

●Document has a `<title>` element

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

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

●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

●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

●Elements with visible text labels have matching accessible names.

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

○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

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

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

○Identical links have the same purpose.

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