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

Form Accessibility

Action

4 of 12 controls have issues

FIX

4 of 12 controls have issues

3 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">; <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="search">

8 control(s) properly labeled

12 controls

8 labeled

1 placeholder only

3 unlabeled

Control	Type	Label	Method
#email-52611e5e-cc55-4960-bf4a-a2adb36291f6_52611e5e-cc55-4960-bf4a-a2adb36291f6-0	email	Email*	for/id
#site-theme-select	select	Site theme	none
#ot-group-id-SPD_BG	checkbox	Use of Personal Data	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
search	text	(Search...)	placeholder only
input	submit	(none)	none
#g-recaptcha-response	textarea	(none)	none
#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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

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

Icons 2 icon(s)

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 ✗

Link & Button Quality

Action

2 issue(s) across 134 links and 38 buttons

REVIEW

2 issue(s) across 134 links and 38 buttons

16 link(s) open in new tab without warning

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

Got: https://app.netlify.com/signup; https://www.netlify.com/contact/sales?attr=homepage&ref=talk-to-sales&id=cta-…; /docs/ai-gateway; /solutions/marketing-sites/; /docs/primitives; /solutions/ecommerce/; /solutions/internal-apps/; https://github.com/netlify; https://www.linkedin.com/company/netlify; https://bsky.app/profile/netlify.com (+6 more)

2 button(s) with no accessible text

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

Got: button (#1903 on page); button (#1913 on page)

118 link(s) with descriptive text

134 links

0 empty

0 generic text

16 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://app.netlify.com/signup	Start building	new tab	Add '(opens in new tab)' to text
https://www.netlify.com/contact/sales?at…	Talk to sales	new tab	Add '(opens in new tab)' to text
/docs/ai-gateway	Explore AI Gateway	new tab	Add '(opens in new tab)' to text
/solutions/marketing-sites/	Marketing sites on Netlify	new tab	Add '(opens in new tab)' to text
/docs/primitives	Explore platform primitives	new tab	Add '(opens in new tab)' to text
/solutions/ecommerce/	Ecommerce on Netlify	new tab	Add '(opens in new tab)' to text
/solutions/internal-apps/	Internal apps on Netlify	new tab	Add '(opens in new tab)' to text
https://github.com/netlify	GitHub	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/netlify	LinkedIn	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/netlify.com	Bluesky	new tab	Add '(opens in new tab)' to text
https://twitter.com/netlify	@keyframes appear{0%{opacity:0…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@NetlifyApp	YouTube	new tab	Add '(opens in new tab)' to text
https://answers.netlify.com/	Discourse	new tab	Add '(opens in new tab)' to text
https://www.netlify.com/privacy/	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://cookiepedia.co.uk/giving-consent…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

154 links and buttons have descriptive text

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

https://app.netlify.com/signup; https://www.netlify.com/contact/sales?attr=homepage&ref=talk-to-sales&id=cta-…; /docs/ai-gateway; /solutions/marketing-sites/; /docs/primitives; /solutions/ecommerce/; /solutions/internal-apps/; https://github.com/netlify; https://www.linkedin.com/company/netlify; https://bsky.app/profile/netlify.com (+6 more)

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 (#1903 on page); button (#1913 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

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 Netlify: Develop & deploy the best web experiences in record time ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

5 icon(s) detected

REVIEW

5 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

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Push your ideas to the web

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Site navigation

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · above the fold

h2 Actions

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Build your way.

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ship on one platform.

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 For every kind of web app.

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start your way.

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Products

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Products

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Company

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Company

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact Us

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact Us

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Stay up to date with Netlify news

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We use Cookies

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Do Not Use My Personal Information

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 The Netlify Platform

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

19px · above the fold

h3 Key Features

1.18:1

#000000

#12181F

needs 3.0:1 (large text)

19px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Push your ideas to t…	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Site navigation	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Actions	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Build your way.	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Ship on one platform…	1.18:1	3.0:1	#000000	#12181F	Fail
h2 For every kind of we…	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Start your way.	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Products	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Products	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Resources	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Resources	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Company	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Company	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Contact Us	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Contact Us	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Stay up to date with…	1.18:1	3.0:1	#000000	#12181F	Fail
h2 We use Cookies	1.18:1	3.0:1	#000000	#12181F	Fail
h2 Do Not Use My Person…	1.18:1	3.0:1	#000000	#12181F	Fail
h3 The Netlify Platform	1.18:1	3.0:1	#000000	#12181F	Fail
h3 Key Features	1.18:1	3.0:1	#000000	#12181F	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

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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

A+

Heading Hierarchy

42 headings

PASS

42 headings

Single H1 present

H2 Site navigation
H3 The Netlify Platform
H3 Key Features
H3 Why Netlify?
H3 Use Cases
H3 Where to start
H3 Project kickstarts
H2 Help
H2 Actions
H1 Push your ideas to the web
H2 Build your way.Ship on one platform.
H3 Start with code or AI
H3 Build fullstack apps
H3 Go live everywhere
H3 Prompt. Preview. Repeat.
H3 Build with agent-ready primitives.
H3 Grow on the same infrastructure.
H2 For every kind of web app.
H3 Launch AI features with one gateway
H3 Launch fast and iterate faster
H3 Build fullstack apps without managing infrastructure
H3 Run fast storefronts at global scale
H3 Create internal apps with less overhead
H2 Start your way.
H2 Products
H2 Products
H2 Resources
H2 Resources
H2 Company
H2 Company
H2 Contact Us
H2 Contact Us
H2 Stay up to date with Netlify news
H2 We use Cookies
H2 Do Not Use My Personal Information
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Use of Personal Data
H5 Social Media Cookies
H5 Targeting Cookies
H5 Performance Cookies
H3 Cookie List

Alt Text Quality

All 30 images OK

PASS

All 30 images OK

3 image(s) with alt text over 125 characters

27 image(s) with good alt text

30 images 27 good alt text

Issue	Count
too long	3 image(s)

A+

Lighthouse Accessibility Audits

Score 97/100 — 2 failing, 29 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
KUBERNETES CONTRIBUTOR, HEAD OF PROJECTS AT CNCF `figure > figcaption > div.n-blockquote-author-info > span.n-blockquote-title`

These are opportunities to improve the legibility of your content.

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
Read our Privacy Policy `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

●Input buttons have discernible text.

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

●Select elements have associated label elements.

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

○`[accesskey]` values are unique

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

○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

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

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