Skip to content
https://deepmind.google

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
65
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 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
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::
7 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 7 <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.
B
Heading Hierarchy
41 headings
REVIEW
41 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Explore our next generation AI systems
  • H2 Our latest AI breakthroughs and updates from the lab
  • H2 Unlocking a new era of discovery with AI
  • H2 Our mission is to build AI responsibly to benefit humanity
  • H2 Explore our next generation AI systems
  • H2 Our latest AI breakthroughs and updates from the lab
  • H2 Unlocking a new era of discovery with AI
  • H2 Our mission is to build AI responsibly to benefit humanity
  • H3 Gemma 4
  • H3 Nano Banana 2 🍌
  • H3 Lyria 3
  • H3 Genie 3
  • H3 Gemini 3
  • H3 WeatherNext 2
  • H3 Gemini Robotics
  • H3 Models
  • H4 Build with our next generation AI systems
  • H3 Gemini
  • H4 Try it in
  • H3 Nano Banana 🍌
  • H4 Try it in
  • H3 Gemma
  • H4 Build with Gemma
  • H3 Lyria
  • H4 Try it in
  • H3 Gemini Audio
  • H4 Try it in
  • H3 Veo
  • H4 Try it in
  • H3 Latest news
  • H3 Gemma 4: Byte for byte, the most capable open models
  • H3 Gemini 3.1 Flash TTS: the next generation of expressive AI speech
  • H3 Gemini Robotics-ER 1.6: Powering real-world robotics tasks through enhanced embodied reasoning
  • H3 Gemini 3.1 Flash Live: Making audio AI more natural and reliable
  • H3 Protecting people from harmful manipulation
  • H3 Lyria 3 Pro: Create longer tracks in more
  • H3 Measuring progress toward AGI: A cognitive framework
  • H3 From games to biology and beyond: 10 years of AlphaGo’s impact
  • H3 Gemini 3.1 Flash-Lite: Built for intelligence at scale
  • H3 The Podcast
  • H4 The frontier of intelligence, explained

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
h2 Explore our next generation AI systems
2.06:1
#000000
on
#134756
needs 3.0:1 (large text)
24px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Explore our next gen…2.06:13.0:1
#000000
#134756
Fail
h2 Our latest AI breakt…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unlocking a new era …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our mission is to bu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Explore our next gen…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our latest AI breakt…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unlocking a new era …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our mission is to bu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemma 421.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nano Banana 2 🍌21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Lyria 321.00:13.0:1
#000000
#FFFFFF
Pass
h3 Genie 321.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemini 321.00:13.0:1
#000000
#FFFFFF
Pass
h3 WeatherNext 221.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemini Robotics21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Models21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemini21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nano Banana 🍌21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Gemma21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Lyria21.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
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
2 of 7 <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 "Models" 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+
Alt Text Quality
All 67 images OK
PASS
All 67 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
64 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
67 images 2 good alt text 64 decorative
IssueCount
too long1 image(s)
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
EmailAddressemailnone
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 27 passed
PASS
95

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
10 years of AlphaGo: The turning point for AI Exactly one decade later, we loo… section#the-podcast > div.grid__inner > div#tabs--2bc42e7d-d9c6-4828-8a36-6edf18d265ef > div.tabs__tablist

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
Google DeepMind DeepMind div.left-menu > div.site-switcher > div.site-switcher__bar > a.site-switcher__home
○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]`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
●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
●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"]`
●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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○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.
○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