Skip to content
https://meraki.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
3 landmarks
PASS
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header MAIN CONTENTINFO footer
A
Heading Hierarchy
21 headings
PASS
21 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H4 Experiences
  • H4 Technologies
  • H4 Touchpoints
  • H4 Resources
  • H4 Experiences
  • H4 Technologies
  • H4 Touchpoints
  • H4 Resources
  • H1 It all starts with a platform.
  • H2 Everything works better on a cloud-managed network.
  • H3 Hybrid work
  • H3 Remote workforce
  • H3 Safe environments
  • H3 Smart spaces
  • H2 A network platform that grows with you.
  • H3 Simplifying IT operations and reducing costs
  • H3 Improving the customer and patient experience
  • H2 Meet the Meraki dashboard.
  • H1 Develop and deploy apps built on top of the Meraki platform. duplicate H1
  • H2 Start your cloud-managed IT journey.
  • H2 Try our technology.

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
1 of 104 images have issues
PASS
1 of 104 images have issues
Warning::
1 image(s) with generic alt text
Info::
89 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
104 images 14 good alt text 89 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#global-searchtextSearchfor/id
#mobile-global-searchtextSearchfor/id
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 It all starts with a…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Develop and deploy a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Everything works bet…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A network platform t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet the Meraki dash…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start your cloud-man…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Try our technology.21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Hybrid work21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Remote workforce21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Safe environments21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Smart spaces21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Simplifying IT opera…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Improving the custom…21.00:13.0:1
#000000
#FFFFFF
Pass
title Wi-Fi 7 | Network Se…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to primary navi…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content11.34:14.5:1
#000000
#9DCB89
Pass
a Skip to content11.34:14.5:1
#000000
#9DCB89
Pass
a Skip to footer11.34:14.5:1
#000000
#9DCB89
Pass
span United States (Engli…11.34:14.5:1
#000000
#9DCB89
Pass
a Australia (English)14.70:14.5:1
#000000
#C4E0B8
Pass

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
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 24 passed
PASS
92

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
LEARN MORE div.row > div.col-12 > div.cmp-masthead-hero__cta-wrap > a.cmp-masthead-hero__cta
EXPLORE INNOVATIONS div.row > div.col-12 > div.blade-cta-container > a#blade-cta-green
EXPLORE THE PLATFORM div.container > div.cmp-5050__content-row > div.col-12 > a.cmp-5050__cta
READ CUSTOMER STORY div.wp-block-columns > div.wp-block-column > div > a.btn
READ CASE STUDY div.container > div.row > div.col-12 > a.btn
READ CASE STUDY div.container > div.row > div.col-12 > a.btn
LEARN MORE div.container > div.cmp-5050__content-row > div.col-12 > a.cmp-5050__cta
VISIT THE MARKETPLACE div.container > div.cmp-5050__content-row > div.col-12 > a.cmp-5050__cta
BROWSE ALL PRODUCTS div.product-start-here-main > div.container > div.text-center > a.btn
SMART IOT SOLUTIONS div.row > div.col-lg-4 > div.product-start-hover > a.btn-start-btn
SECURE SD-WAN div.row > div.col-lg-4 > div.product-start-hover > a.btn-start-btn
CLOUD-MANAGED ACCESS div.row > div.col-lg-4 > div.product-start-hover > a.btn-start-btn

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Experiences div.nav-body > div.mega-menu > div.section__header > a.hash-link
Technologies div.nav-body > div.mega-menu > div.section__header > a.hash-link
Touchpoints div.nav-body > div.mega-menu > div.section__header > a.hash-link
Resources div.nav-body > div.mega-menu > div.section__header > a.hash-link
United States (English) div.lang-switcher-mobile > div.container > div.cmp-language-switcher > a.cmp-language-switcher__selector

These are opportunities to improve keyboard navigation in your application.

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
Learn More div.container > span.cmp-notification-bar__cta > b > a
○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
●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.
●ARIA attributes are used as specified for the element's role
●`[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
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○Buttons have an accessible name
○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
○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.
○`<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.
○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