Skip to content
https://netcraft.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
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
BANNER (missing!) MAIN CONTENTINFO (missing!)

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Netcraft | The Industry Leader in Enterprise Brand Protection ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
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 From
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
32px · top of page (header area)
h1 Predictive signals
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
32px · top of page (header area)
h1 Proactive Takedowns
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
32px · above the fold
h2 Legacy solutions = Legacy Outcomes
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · above the fold
h2 Detect. Preempt. TakeDown.
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · mid-page
h2 OUR SUPERPOWERS BECOME YOUR SUPERPOWERS
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 End-to-End Automation, Impactful AI
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Unmatched Scale and Effectiveness
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 33%
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 23B+
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 225M+
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 30M+
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 threat map
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 resources & insights
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Book a Demo Today
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
title Next-Gen Digital Risk Protection | AI-po…
1.23:1
#000000
on
#001F29
needs 4.5:1 (normal text)
16px · top of page (header area)
h4 NEXT-GEN Brand and Digital Risk Protecti…
1.23:1
#000000
on
#001F29
needs 3.0:1 (large text)
16px · top of page (header area)
p Move from threat intelligence to decisiv…
1.23:1
#000000
on
#001F29
needs 4.5:1 (normal text)
16px · above the fold
p GET Demo
1.23:1
#000000
on
#001F29
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p Request Pricing
1.23:1
#000000
on
#001F29
needs 4.5:1 (normal text)
16px · above the fold

2 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)
ElementRatioRequiredFGBGResult
h1 From1.23:13.0:1
#000000
#001F29
Fail
h1 Predictive signals1.23:13.0:1
#000000
#001F29
Fail
h1 Proactive Takedowns1.23:13.0:1
#000000
#001F29
Fail
h2 Legacy solutions = L…1.23:13.0:1
#000000
#001F29
Fail
h2 Detect. Preempt. Tak…1.23:13.0:1
#000000
#001F29
Fail
h2 OUR SUPERPOWERS BECO…1.23:13.0:1
#000000
#001F29
Fail
h2 End-to-End Automatio…1.23:13.0:1
#000000
#001F29
Fail
h2 Unmatched Scale and …1.23:13.0:1
#000000
#001F29
Fail
h2 33%1.23:13.0:1
#000000
#001F29
Fail
h2 23B+1.23:13.0:1
#000000
#001F29
Fail
h2 225M+1.23:13.0:1
#000000
#001F29
Fail
h2 30M+1.23:13.0:1
#000000
#001F29
Fail
h2 threat map1.23:13.0:1
#000000
#001F29
Fail
h2 resources & insights1.23:13.0:1
#000000
#001F29
Fail
h2 Book a Demo Today1.23:13.0:1
#000000
#001F29
Fail
title Next-Gen Digital Ris…1.23:14.5:1
#000000
#001F29
Fail
h4 NEXT-GEN Brand and D…1.23:13.0:1
#000000
#001F29
Fail
p Move from threat int…1.23:14.5:1
#000000
#001F29
Fail
p GET Demo1.23:14.5:1
#000000
#001F29
Fail
p Request Pricing1.23:14.5:1
#000000
#001F29
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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 7 failing, 21 passed
REVIEW
77

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
div.framer-6jvor7 > div.framer-130n60e > div.framer-egpevs > a.framer-ebn8ex div.framer-6jvor7 > div.framer-130n60e > div.framer-egpevs > a.framer-ebn8ex

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
AI assistant body > q-focus-sentinel > div
After AI assistant body > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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
THE CHALLENGE div.framer-5klrn8 > div.framer-1q3ul5s > p.framer-text > strong.framer-text
NEXT-GEN DISRUPTION div.framer-gessbt > div.framer-1ijbjn8 > p.framer-text > strong.framer-text
digital risk protection services div.framer-1swnmbs > div.framer-zhrvs8 > p.framer-text > a.framer-text
Cookie Policy div > p > span > a

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-1kdjgg0 > div.ssr-variant > div.framer-1tg6otl-container > iframe div.framer-1kdjgg0 > div.ssr-variant > div.framer-1tg6otl-container > iframe

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.framer-1enppxs > div.framer-b5jvhq > div.framer-1obmiwm-container > a.framer-8fusC div.framer-1enppxs > div.framer-b5jvhq > div.framer-1obmiwm-container > a.framer-8fusC

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item
div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item div.framer-FPySM > div.framer-1t89lxq > ul > li.ticker-item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Scroll to page 2 section > fieldset.framer--slideshow-controls > div > button

These items highlight common accessibility best practices.

○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
●Input buttons have discernible text.
●`[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
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●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
○`[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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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.
○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.
A
Heading Hierarchy
18 headings
PASS
18 headings
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H4 NEXT-GEN Brand and Digital Risk Protection for the AI AGE
  • H1 From
  • H1 Predictive signals duplicate H1
  • H1 to duplicate H1
  • H1 Proactive Takedowns duplicate H1
  • H2 Legacy solutions = Legacy Outcomes
  • H1 95 duplicate H1
  • H2 Detect. Preempt. TakeDown.
  • H2 OUR SUPERPOWERS BECOME YOUR SUPERPOWERS
  • H2 End-to-End Automation, Impactful AI
  • H2 Unmatched Scale and Effectiveness
  • H2 33%
  • H2 23B+
  • H2 225M+
  • H2 30M+
  • H2 threat map
  • H2 resources & insights
  • H2 Book a Demo Today

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 52 images OK
PASS
All 52 images OK
Info::
46 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
52 images 6 good alt text 46 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" id="__framer-cookie-component-button-dismiss">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#__framer-cookie-component-button-dismissbutton(none)none

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

<input type="button" id="__framer-cookie-component-button-dismiss">

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

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

Send Feedback