Skip to content
https://googleblog.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-kwr93x
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://googleblog.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://googleblog.com/manifest.json

Manifest contains invalid JSON.

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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Form Accessibility
Action
3 of 12 controls have issues
REVIEW
3 of 12 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" id="copy-link">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="search-bar-pre-node">; <input type="text" id="search-bar-post-node">
Info::
9 control(s) properly labeled
12 controls
9 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#uni-search-bar__inputsearchAsk a question or enter a keywordaria-label
languageselectChange Regionaria-label
#uni_subscribe_emailtextEmail addressaria-label
#question-0-answer-0--nextradionone
#question-0-answer-1--nextradionone
#question-0-answer-2--nextradionone
#question-0-answer-3--nextradionone
#question-0-answer-4--nextradionone
languageselectChange Regionaria-label
#search-bar-pre-nodetext(focustrap)placeholder only
#search-bar-post-nodetext(focustrap)placeholder only
#copy-linktext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="text" id="copy-link">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

<input type="text" id="search-bar-pre-node">; <input type="text" id="search-bar-post-node">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main" MAIN CONTENTINFO footer
A
Heading Hierarchy
25 headings, 1 skip(s)
PASS
25 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Info::
5 hidden heading(s) (aria-hidden)
  • H1 New ways to create personalized images in the Gemini app
  • H3 A new way to explore the web with AI Mode in Chrome skipped
  • H3 Voting is live: Help choose the next Doodle for Google winner
  • H3 Gemini is stopping harmful ads before people ever see them
  • H2 Video spotlight
  • H3 Your inbox, your business
  • H3 More Videos
  • H4 Your inbox, your business hidden
  • H4 Change your Google Account username in a few simple steps hidden
  • H4 Explore Benjamin Franklin’s scientific discoveries on NotebookLM hidden
  • H4 Watch James Manyika talk AI and creativity with LL COOL J hidden
  • H4 Identify tax scams fast with Circle to Search & Lens hidden
  • H2 The latest from our CEO
  • H3 “No technology has me dreaming bigger than AI”
  • H2 Get the latest news from Google in your inbox.
  • H2 All stories
  • H3 A new way to explore the web with AI Mode in Chrome
  • H3 Voting is live: Help choose the next Doodle for Google winner
  • H3 New ways to create personalized images in the Gemini app
  • H3 Nest thermostats have saved users an estimated $14 billion and 200 billion kWh of energy since 2011.
  • H3 Gemini is stopping harmful ads before people ever see them
  • H3 Grow with Google's event discussed AI in the workplace with Fortune 500 company leaders.
  • H3 New ways we’re protecting businesses on Maps
  • H3 Partnering with Latin American governments on 3 new AI initiatives
  • H3 The Gemini app is now on Mac

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A
Alt Text Quality
1 of 25 images have issues
PASS
1 of 25 images have issues
Warning::
1 image(s) with filename as alt text
Info::
1 image(s) with alt text over 125 characters
Info::
15 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
25 images 8 good alt text 15 decorative 1 generic
IssueCount
filename1 image(s)
too long1 image(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)
ElementRatioRequiredFGBGResult
h1 New ways to create p…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Video spotlight21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The latest from our …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get the latest21.00:13.0:1
#000000
#FFFFFF
Pass
h2 in your inbox.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All stories21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A new way to explore…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Voting is live: Help…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemini is stopping h…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your inbox, your bus…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 More Videos21.00:13.0:1
#000000
#FFFFFF
Pass
h3 “No technology has…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 A new way to explore…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Voting is live: Help…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New ways to create p…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nest thermostats hav…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemini is stopping h…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Grow with Google's e…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 New ways we’re pro…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Partnering with Lati…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 99/100 — 2 failing, 30 passed
PASS
99

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
A new way to explore the web with AI Mode in Chrome li.nup-card > div.nup-card__article > a.nup-card__article-link > h3.uni-title-1

These are opportunities to improve keyboard navigation in your application.

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
Your inbox, your business div.uni-yt-thumbnail-group > div.uni-yt-thumbnail-group__carousel > div#uni-yt-thumbnail-group-1776360075018 > div#uni-yt-thumbnail-group-1776360075018-item-1
Change your Google Account username in a few simple steps div.uni-yt-thumbnail-group > div.uni-yt-thumbnail-group__carousel > div#uni-yt-thumbnail-group-1776360075018 > div#uni-yt-thumbnail-group-1776360075018-item-2
Explore Benjamin Franklin’s scientific discoveries on NotebookLM div.uni-yt-thumbnail-group > div.uni-yt-thumbnail-group__carousel > div#uni-yt-thumbnail-group-1776360075018 > div#uni-yt-thumbnail-group-1776360075018-item-3
Watch James Manyika talk AI and creativity with LL COOL J div.uni-yt-thumbnail-group > div.uni-yt-thumbnail-group__carousel > div#uni-yt-thumbnail-group-1776360075018 > div#uni-yt-thumbnail-group-1776360075018-item-4
Identify tax scams fast with Circle to Search & Lens div.uni-yt-thumbnail-group > div.uni-yt-thumbnail-group__carousel > div#uni-yt-thumbnail-group-1776360075018 > div#uni-yt-thumbnail-group-1776360075018-item-5
○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.
●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
●`[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 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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[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 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
○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.
○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