Skip to content
https://netgear.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://netgear.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://netgear.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #0176d3
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="autocomplete-0-input">; <input>
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#field-:R766jaimaalf9:inputEnter email addressfor/id
#autocomplete-0-inputsearch(Search)placeholder only
inputinput(Search countries…)placeholder only

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

<input type="search" id="autocomplete-0-input">; <input>

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error | NETGEAR ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
title NETGEAR: Advanced WiFi & Networking
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to Content
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · top of page (header area)
a Enterprise
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home WiFi
1.29:1
#000000
on
#202020
needs 4.5:1 (normal text)
16px · top of page (header area)
a Mobile WiFi
1.14:1
#000000
on
#141414
needs 4.5:1 (normal text)
16px · above the fold
a Support
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
a Shop Deals
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
a About NETGEAR
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
span Powering
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
span Extraordinary Experiences,
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
span Everywhere
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
span Enterprise
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
span Home WiFi
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · above the fold
span Mobile WiFi
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
span Your security & privacy are our top prio…
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
p All NETGEAR products are aligned with th…
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
u Learn More
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
span Smarter Networking
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
span for Small and Medium
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
span Enterprises
1.08:1
#000000
on
#0D0D0D
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title NETGEAR: Advanced Wi…1.29:14.5:1
#000000
#202020
Fail
a Skip to Content1.29:14.5:1
#000000
#202020
Fail
a Enterprise1.29:14.5:1
#000000
#202020
Fail
a Home WiFi1.29:14.5:1
#000000
#202020
Fail
a Mobile WiFi1.14:14.5:1
#000000
#141414
Fail
a Support1.08:14.5:1
#000000
#0D0D0D
Fail
a Shop Deals1.08:14.5:1
#000000
#0D0D0D
Fail
a About NETGEAR1.08:14.5:1
#000000
#0D0D0D
Fail
span Powering1.08:14.5:1
#000000
#0D0D0D
Fail
span Extraordinary Experi…1.08:14.5:1
#000000
#0D0D0D
Fail
span Everywhere1.08:14.5:1
#000000
#0D0D0D
Fail
span Enterprise1.08:14.5:1
#000000
#0D0D0D
Fail
span Home WiFi1.08:14.5:1
#000000
#0D0D0D
Fail
span Mobile WiFi1.08:14.5:1
#000000
#0D0D0D
Fail
span Your security & priv…1.08:14.5:1
#000000
#0D0D0D
Fail
p All NETGEAR products…1.08:14.5:1
#000000
#0D0D0D
Fail
u Learn More1.08:14.5:1
#000000
#0D0D0D
Fail
span Smarter Networking1.08:14.5:1
#000000
#0D0D0D
Fail
span for Small and Medium1.08:14.5:1
#000000
#0D0D0D
Fail
span Enterprises1.08:14.5:1
#000000
#0D0D0D
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+
Landmark Structure
15 landmarks
PASS
15 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN ASIDE CONTENTINFO (missing!)
A
Heading Hierarchy
9 headings, 1 skip(s)
PASS
9 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 PoweringExtraordinary Experiences, Everywhere
  • H2 Your security & privacy are our top priority
  • H2 Smarter Networking for Small and Medium Enterprises
  • H4 NETGEAR Enterprise skipped
  • H4 NETGEAR AV
  • H3 Connected Home
  • H4 Experience the most powerful & advanced Orbi
  • H4 WiFi 7 power. Nighthawk performance.
  • H2 Three Decades of Connecting What Matters Most

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

A
Alt Text Quality
1 of 42 images have issues
PASS
1 of 42 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
40 image(s) with good alt text
42 images 40 good alt text 1 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 28 passed
PASS
97

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
Extraordinary Experiences, div.css-rg9omw > h1.chakra-heading > span.chakra-text > span.chakra-text

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
English div.dg-app > div.dg-header > div.dg-main-language-dropdown > button.language-dropdown-trigger
○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]` 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
●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
●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
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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
○`[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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○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.

Send Feedback