Skip to content
https://google-analytics.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 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
No navigation patterns
FIX
No navigation patterns
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
5 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Error 404 (Not Found)!!1 Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only
span Analytics
2.72:1
#000000
on
#5C5147
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Overview
4.33:1
#000000
on
#886D4A
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Get essential custom…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 See what’s in i…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Dive into the detail…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Designed to work tog…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Lider increases conv…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h3 McDonald’s Hong Ko…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Control how data is …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The Future of Analyt…21.00:13.0:1
#000000
#FFFFFF
Pass
title Analytics Tools & So…21.00:14.5:1
#000000
#FFFFFF
Pass
span Marketing Platform21.00:14.5:1
#000000
#FFFFFF
Pass
a For Small Businesses21.00:14.5:1
#000000
#FFFFFF
Pass
a For Enterprises14.40:14.5:1
#000000
#D9D5D2
Pass
a Resources6.77:14.5:1
#000000
#AA8D74
Pass
a Blog6.42:14.5:1
#000000
#A6896C
Pass
a Partners13.25:14.5:1
#000000
#D6CBCA
Pass
a Support12.70:14.5:1
#000000
#D1C7C6
Pass
span Analytics2.72:14.5:1
#000000
#5C5147
Fail
a Overview4.33:14.5:1
#000000
#886D4A
Fail
a Benefits13.68:14.5:1
#000000
#D6D0C4
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 24 passed
REVIEW
84

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 4 div.highlights-module__carousel > div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list
1 2 3 4 5 div.highlights-module__carousel > div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list
1 2 3 div.h-c-page > div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
2 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
3 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
4 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
1 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
2 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
3 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
4 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
5 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
1 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
2 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
3 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
2 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
3 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
4 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
1 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
2 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
3 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
4 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
5 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
1 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
2 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container
3 div.glue-pagination > div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
2 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
3 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
4 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
1 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
2 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
3 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
4 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
5 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
1 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
2 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button
3 div.h-c-carousel__navigation > ul.glue-pagination-page-list > li.glue-o-pagination__button-container > button.glue-o-pagination__button

These items highlight common accessibility best practices.

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
Buttons have an accessible name
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.
Select elements have associated label elements.
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
Background and foreground colors have a sufficient contrast ratio
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>`).
No element has a `[tabindex]` value greater than 0
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 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
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
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
27 headings
PASS
27 headings
Info::
Single H1 present
  • H1 Get essential customer insights.
  • H2 Get a complete understanding of your customers across devices and platforms. Google Analytics gives you the tools, free of charge, to understand the customer journey and improve marketing ROI.
  • H3 See what’s in it for you.
  • H4 Unlock customer-centric measurement.
  • H4 Get smarter insights to improve ROI.
  • H4 Connect your insights to results.
  • H4 Make your data work for you.
  • H4 Unlock customer-centric measurement.
  • H3 Google Analytics allows us to look at our data across platforms — web and app — to understand the full journey of our users. We’ve been able to cut our reporting time by 50%.
  • H3 Dive into the details.
  • H3 Designed to work together.
  • H4 Google Ads
  • H4 Search Ads 360
  • H4 Display & Video 360
  • H4 Google Cloud
  • H4 Google Search Console
  • H4 Google Ads
  • H3 Lider increases conversion rate 18X with Google Analytics.
  • H3 Resources
  • H3 McDonald’s Hong Kong uses Google Analytics 4 to increase in-app orders by 550%
  • H3 Control how data is used in Google Analytics
  • H3 The Future of Analytics
  • H4 About Google Marketing Platform
  • H4 Learning & support
  • H4 Developers & partners
  • H4 Related products
  • H4 More from Google
A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
10 image(s) with good alt text
10 images 10 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#lang-selectorselectChange language or regionfor/id
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback