Skip to content
https://chrome.google.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Alt Text Quality
Action
5 of 50 images have issues
FIX
5 of 50 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 image(s) with alt text over 125 characters
Info::
18 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
50 images 24 good alt text 18 decorative 5 missing
IssueCount
missing5 image(s)
too long3 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

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
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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
14 icon(s) detected
REVIEW
14 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
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
3 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "navigation menu" 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

A+
Heading Hierarchy
52 headings
PASS
52 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 The browser built to be f a s t s
  • H2 The f a s t way to do things online
  • H3 Prioritize performance
  • H3 Stay on top of tabs
  • H3 Optimized for your device
  • H3 Automatic updates
  • H3 Prioritize performance
  • H3 Stay on top of tabs
  • H3 Optimized for your device
  • H3 Automatic updates
  • H2 Browsing boosted with built-in
  • H3 Gemini in Chrome: Your AI browsing assistant
  • H2 Stay s a f e while you browse
  • H2 Stay s a f e while you browse
  • H3 PASSWORD MANAGER
  • H4 Use strong passwords on every site.
  • H3 ENHANCED SAFE BROWSING
  • H4 Browse with the confidence that you're staying safer online.
  • H3 SAFETY CHECK
  • H4 Check your safety level in real time with just one click.
  • H3 PRIVACY GUIDE
  • H4 Keep your privacy under your control with easy-to-use settings.
  • H2 Make it y o u r s and take it with you
  • H2 Make it y o u r s and take it with you
  • H3 Customize your Chrome
  • H3 Browse across devices
  • H3 Save time with autofill
  • H3 Customize your Chrome
  • H3 Browse across devices
  • H3 Save time with autofill
  • H3 Extend your experience
  • H2 The browser b u i l t by Google
  • H3 GOOGLE SEARCH
  • H4 The search bar you love, built right in.
  • H3 GOOGLE PAY
  • H4 Pay for things as quick as you click.
  • H3 Google Lens
  • H4 See anything, search anything.
  • H2 Frequently asked questions
  • H3 How do I install Chrome?
  • H3 Does Chrome work on my operating system?
  • H3 How do I make Chrome my default browser?
  • H3 What are Chrome’s safety settings?
  • H2 Take your browser with you
  • H3 Follow us
  • H4 Chrome Family
  • H4 Enterprise
  • H4 Education
  • H4 Dev and Partners
  • H4 Support
  • H2 Get Chrome for Linux
  • H3 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#language-selectorselectChange language or regionaria-label
#debianradio64 bit .deb (For Debian/Ubuntu)for/id
#fedoraradio64 bit .rpm (For Fedora/openSUSE)for/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
h2 Frequently asked que…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Take your browser wi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get Chrome for Linux21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Prioritize performan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Stay on top of tabs21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Optimized for your …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Automatic updates21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Prioritize performan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Stay on top of tabs21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Optimized for your …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Automatic updates21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemini in Chrome: Yo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 PASSWORD MANAGER21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ENHANCED SAFE BROWSI…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 SAFETY CHECK21.00:13.0:1
#000000
#FFFFFF
Pass
h3 PRIVACY GUIDE21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Customize your Chrom…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Browse across device…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Save time with autof…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Customize your Chrom…21.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.

A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 26 passed
PASS
96

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Explore Get Chrome body.l10n > div#jump-content > section#hero > div.chr-jumplinks-mobile
Browsing boosted with built-in section#ai > div.chr-pill-section-title > h2.chr-base-text > span

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.

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
Go to AI Innovations div#jump-content > div.chr-promo-banner > div.chr-promo-banner__button-wrapper > a.chr-link
Explore Gemini in Chrome div.chr-grid-default > div.chr-section-text-block__container > div.chr-text-block__body-wrapper > a.chr-link
○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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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>`).
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○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
○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
○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.
○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