meraki.com Accessibility Report

Accessibility audit of meraki.com — scanned on Feb 20, 2026

Technology
0 /100
C Needs Improvement

4 issues found across 2 categories

1 Critical 3 Major

WCAG Compliance Overview

Perceivable 0 issues
Operable 4 issues
Understandable 0 issues
Robust 0 issues

Issues Found

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
4 element(s) affected
  • <a href="#">
  • <a href="#">
  • <a href="#">
  • <a href="#">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Frames missing title

Major

Iframes must have title attributes describing their content.

WCAG 2.4.1
1 element(s) affected
  • <iframe src="https://www.googletagmanager.com/ns.html?id=GTM-55HS3J">
How to fix

Add descriptive title attributes to all <iframe> elements.

Positive tabindex values

Major

Elements with tabindex > 0 disrupt natural tab order and confuse keyboard users.

WCAG 2.4.3
137 element(s) affected
  • <a tabindex="1">
  • <a tabindex="2">
  • <a tabindex="3">
  • <a tabindex="3">
  • <a tabindex="3">
How to fix

Remove positive tabindex values. Use tabindex="0" or tabindex="-1" only.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
4 element(s) affected
  • <a href="https://meraki.cisco.com/experiences/all-experiences/">learn more</a>
  • <a href="https://meraki.cisco.com/products/">learn more</a>
  • <a href="https://meraki.cisco.com/experiences/all-experiences/">learn more</a>
  • <a href="https://meraki.cisco.com/products/">learn more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Top Priority Fixes

Here are the most impactful changes meraki.com should make to improve accessibility:

  1. #1
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  2. #2
    Positive tabindex values Major

    Remove positive tabindex values. Use tabindex="0" or tabindex="-1" only.

  3. #3
    Generic link text Major

    Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Frequently Asked Questions

Is meraki.com accessible?

meraki.com scored 61/100 (grade C) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is meraki.com WCAG compliant?

Our scan found 4 accessibility issues on meraki.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is meraki.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see meraki.com's compliance status.

What accessibility issues does meraki.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for meraki.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing