Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 4 REVIEW 2 FIX

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation

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.

Landmark Structure

30 landmarks

REVIEW

30 landmarks

<main> landmark present

No <nav> landmark found

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

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

Link & Button Quality

1 issue(s) across 108 links and 46 buttons

REVIEW

1 issue(s) across 108 links and 46 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /stats/ ("Learn more")

5 link(s) open in new tab without warning

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

Got: /signup/?src=main_banner&custom=ai-seo&redirect_to=%2Fseo%2F&trial=force; https://enterprise.semrush.com/; /one/?utm_source=semrush&utm_medium=header; https://www.spotlightconf.com/register?utm_source=semrush&utm_medium=resource…; https://ai-visibility-index.semrush.com/

102 link(s) with descriptive text

108 links

0 empty

1 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/signup/?src=main_banner&custom=ai-seo&r…	Try Semrush One for free …	new tab	Add '(opens in new tab)' to text
https://enterprise.semrush.com/	Enterprise	new tab	Add '(opens in new tab)' to text
/one/?utm_source=semrush&utm_medium=head…	Try Semrush One for Free …	new tab	Add '(opens in new tab)' to text
https://www.spotlightconf.com/register?u…	Get Your Ticket Now …	new tab	Add '(opens in new tab)' to text
/stats/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Stats
https://ai-visibility-index.semrush.com/	Explore the index	new tab	Add '(opens in new tab)' to text

148 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/stats/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

/signup/?src=main_banner&custom=ai-seo&redirect_to=%2Fseo%2F&trial=force; https://enterprise.semrush.com/; /one/?utm_source=semrush&utm_medium=header; https://www.spotlightconf.com/register?utm_source=semrush&utm_medium=resource…; https://ai-visibility-index.semrush.com/

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

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 Page not found | Semrush ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

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 #f6f7f8 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Heading Hierarchy

45 headings

PASS

45 headings

Single H1 present

H3 Start Here
H3 Find the Right Tools
H3 Platform
H3 Top Apps
H3 Grow with Semrush
H3 Explore Free Tools
H3 About Semrush
H1 Be found everywhere search happens
H2 Your edge to win every search
H2 Bigger scale. Bigger advantage.
H2 Solutions ( 9 )
H3 Get seen. Get cited. Be the answer.
H3 Semrush one
H4 Grow your digital brand visibility
H3 SEO
H4 Outrank the rest with better SEO
H3 AI Visibility
H4 Get LLMs to cite your brand
H3 Traffic and Market
H4 Analyze traffic on any website
H3 Content
H4 Craft SEO and AI-ready content in minutes
H3 Local
H4 Own your local presence
H3 Advertising
H4 Make every ad dollar work harder
H3 AI PR
H4 Build AI trust through earned press
H3 Social
H4 Manage social all in one place
H2 Stats and facts
H3 The data you need to outrank the competition
H2 AI Visibility Index
H2 Our customers
H3 How we help marketers win
H2 Resources ( 7 )
H3 Stay ahead of what’s next
H3 Direct Access to Semrush Data in ChatGPT
H3 Our AI Visibility Index Reveals Who’s Winning in AI Search (and How)
H3 How We’re Driving LLM Visibility at Semrush
H3 Sharpen Your Digital Marketing Skills with Our Free Webinars
H3 Enterprise AIO Adds Persona-Based Prompt Generation
H3 Semrush AI Overviews Study: What SEO Data Reveals about the Shift in Search
H3 Where Ambitious Marketers Take Center Stage
H2 Get started with Semrush today

A+

Alt Text Quality

All 55 images OK

PASS

All 55 images OK

19 decorative image(s) correctly marked

36 image(s) with good alt text

55 images 36 good alt text 19 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#index-search-input	text	Enter your website	aria-label

Favicon & Branding

8 icon(s) detected

PASS

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Semrush

192x192 icon present

512x512 icon present

Display mode: minimal-ui

PWA Install Criteria ✓ Installable

Name Semrush ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=web_app_manifest ✓Display Mode minimal-ui ✓

Name Semrush Display Mode minimal-ui Theme Color #ba4717 Background Color #fff Icons 4 icon(s)

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)

Element	Ratio	Required	FG	BG	Result
h1 Be found everywhere …	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Your edge to win	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 every search	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Bigger scale.	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Bigger advantage.	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Solutions	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Stats and facts	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 AI Visibility Index	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Our customers	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Resources	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h2 Get started with Sem…	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h3 Start Here	17.11:1	3.0:1	#000000	#E0E9F2	Pass
h3 Find the Right Tools	16.86:1	3.0:1	#000000	#E4E5F8	Pass
h3 Platform	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h3 Top Apps	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h3 Grow with Semrush	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h3 Explore Free Tools	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h3 About Semrush	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h3 Get seen. Get cited.…	17.18:1	3.0:1	#000000	#EBE5FF	Pass
h3 Semrush one	17.18:1	3.0:1	#000000	#EBE5FF	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 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
43T `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
Build credibility with the largest database on the market. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`
808M `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
Your (secret) market insights superpower. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`
142 `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
You’re covered all around the world. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`
213M+ `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
Monitor more prompts. Grow your visibility faster. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`

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
US `div.mp-search__input-wrapper > div.flags-wrap > div.flags-select > button.flags-select__dropdown`

○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

●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

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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○Links are distinguishable without relying on color.

○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

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

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