Skip to content
https://statcounter.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
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 1 <nav> element(s)
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
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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
Alt Text Quality
Action
16 of 46 images have issues
REVIEW
16 of 46 images have issues
Critical::
16 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
30 image(s) with good alt text
46 images 30 good alt text 16 missing
IssueCount
missing16 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

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 404 - Page Not Found | Statcounter ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 81/100 — 6 failing, 21 passed
REVIEW
81

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
Try it for FREE! div.header-content > div.text-container > div.signup-container > a.btn
Try it for FREE! body#section-home > div.home-join > a.btn

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.text-container > div.signup-container > div.review-stars > img div.text-container > div.signup-container > div.review-stars > img
div.text-container > div.signup-container > div.review-stars > img div.text-container > div.signup-container > div.review-stars > img
div.text-container > div.signup-container > div.review-stars > img div.text-container > div.signup-container > div.review-stars > img
div.col > div.header-content > div.image-container > img div.col > div.header-content > div.image-container > img
div.home-join > div.padded-benefits > span > img div.home-join > div.padded-benefits > span > img
div.home-join > div.padded-benefits > span > img div.home-join > div.padded-benefits > span > img
div.home-join > div.padded-benefits > span > img div.home-join > div.padded-benefits > span > img
div.section > div.row > div.card > img div.section > div.row > div.card > img
div.section > div.row > div.card > img div.section > div.row > div.card > img
div.section > div.row > div.card > img div.section > div.row > div.card > img
div.sc-row > div.sc-col > div.tip > img div.sc-row > div.sc-col > div.tip > img
div.sc-row > div.sc-col > div.user > img.image div.sc-row > div.sc-col > div.user > img.image
div.sc-row > div.sc-col > div.tip > img div.sc-row > div.sc-col > div.tip > img
div.sc-row > div.sc-col > div.user > img.image div.sc-row > div.sc-col > div.user > img.image
div.sc-row > div.sc-col > div.tip > img div.sc-row > div.sc-col > div.tip > img
div.sc-row > div.sc-col > div.user > img.image div.sc-row > div.sc-col > div.user > img.image

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

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
Web Analytics See how your website is doing at-a-glance. Track your traffic tr… div.section > div.row > div.row > a
Session Replay See how your visitors are really experiencing your website, whe… div.section > div.row > div.row > a
Heatmaps Quickly see the areas on your web pages getting the most attention, a… div.section > div.row > div.row > a
Live Visitor Feed Watch a real-time, live feed of your visitors. See individua… div.section > div.row > div.row > a
Conversion Tracking Track the percentage of visitors that reach a goal, e.g. c… div.section > div.row > div.row > a
Google Ads Integration See where your Google Ads configuration is wasting your… div.section > div.row > div.row > a
UTM Tracking Monitor your ad and marketing campaign performance at a granular … div.section > div.row > div.row > a
Traffic Sources See how visitors are finding your website and create high conv… div.section > div.row > div.row > a
Bot Detection Protect your stats from being skewed by bots. Track bot activity… div.section > div.row > div.row > 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
●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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[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
○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 a valid value for its `[lang]` attribute
○`<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.
○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.
○Identical links have the same purpose.
○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
26 headings
PASS
26 headings
Info::
Single H1 present
  • H3 Product
  • H3 Company
  • H3 Support
  • H3 Explore
  • H1 Understand your visitors the easy way.
  • H2 Crucial insights for time–strapped business owners.
  • H3 Web Analytics
  • H3 Session Replay
  • H3 Heatmaps
  • H3 Live Visitor Feed
  • H3 Conversion Tracking
  • H3 Google Ads Integration
  • H3 UTM Tracking
  • H3 Traffic Sources
  • H3 Bot Detection
  • H2 Try Statcounter for 30 days
  • H3 1. Sign up
  • H3 2. Insert the code
  • H3 3. Get visitor insights!
  • H2 Trusted on over 1 million websites worldwide.
  • H2 Works on your favourite platforms
  • H3 Product
  • H3 Get the App
  • H3 Company
  • H3 Support
  • H3 Explore
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 Understand your visi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 way.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Crucial insights for…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Try Statcounter for …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted on over 1 mi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Works on your favour…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Product21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Support21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Explore21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Web Analytics21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Session Replay21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Heatmaps21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Live Visitor Feed21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Conversion Tracking21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Google Ads Integrati…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 UTM Tracking21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Traffic Sources21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bot Detection21.00:13.0:1
#000000
#FFFFFF
Pass
h3 1. Sign up21.00:13.0:1
#000000
#FFFFFF
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.

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

Send Feedback