Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Link & Button Quality

Action

4 issue(s) across 118 links and 32 buttons

REVIEW

4 issue(s) across 118 links and 32 buttons

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://ai.google/earth-ai/?utm_source=researchgoogle&utm_medium=google-oo&ut… ("Learn more"); https://sites.research.google/gr/wildfires/ ("Learn more")

25 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://policies.google.com/technologies/cookies?hl=en; https://research.google/programs-and-events/; https://blog.google/technology/research/new-updates-and-more-access-to-google…; https://www.youtube.com/watch?v=UZ4RaLGDXI4&list=PL95lT3XlM14ROFtYnlBDYZbKipH…; https://arxiv.org/abs/2510.18318; https://www.youtube.com/watch?v=kpeI9dbkWho&list=PL95lT3XlM14ROFtYnlBDYZbKipH…; https://www.youtube.com/watch?v=pmQlXLaHT_Y&t; https://blog.google/outreach-initiatives/sustainability/google-ai-wildfire-de…; https://www.earthfirealliance.org/; https://sites.research.google/floodforecasting/?_gl=1*127r8kr*_ga*MTA2OTMzOTE… (+15 more)

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.search-input__button (#411 on page); button.search-input__button (#414 on page)

91 link(s) with descriptive text

118 links

0 empty

2 generic text

25 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://policies.google.com/technologies…	Learn more about how Google us…	new tab	Add '(opens in new tab)' to text
https://research.google/programs-and-eve…	Collaborate with us	new tab	Add '(opens in new tab)' to text
https://ai.google/earth-ai/?utm_source=r…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: ?Utm Source=Researchgoogle&Utm Medium=Google Oo&Utm Campaign=January2026&Utm Content=Earth Ai
https://blog.google/technology/research/…	New updates and more access to…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=UZ4RaLGD…	Watch how Google Earth AI is t…	new tab	Add '(opens in new tab)' to text
https://arxiv.org/abs/2510.18318	Discover how Google is Unlocki…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/watch?v=kpeI9dbk…	Watch how Google's Geospatial …	new tab	Add '(opens in new tab)' to text
https://sites.research.google/gr/wildfir…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Wildfires
https://www.youtube.com/watch?v=pmQlXLaH…	Watch Google AI’s wildfire d…	new tab	Add '(opens in new tab)' to text
https://blog.google/outreach-initiatives…	How a new constellation of sat…	new tab	Add '(opens in new tab)' to text
https://www.earthfirealliance.org/	Learn about EFA, the nonprofit…	new tab	Add '(opens in new tab)' to text
https://sites.research.google/floodforec…	Flood Forecasting …	new tab	Add '(opens in new tab)' to text
https://sites.research.google/gr/open-bu…	Open Buildings …	new tab	Add '(opens in new tab)' to text
https://sites.research.google/gr/geospat…	Geospatial Reasoning …	new tab	Add '(opens in new tab)' to text
https://ai.google/responsibility/princip…	See how we're advancing AI	new tab	Add '(opens in new tab)' to text
https://ai.google?utm_source=researchgoo…	Google AI	new tab	Add '(opens in new tab)' to text
https://cloud.google.com/	Google Cloud	new tab	Add '(opens in new tab)' to text
https://deepmind.google/	Google DeepMind	new tab	Add '(opens in new tab)' to text
https://labs.google/	Google Labs	new tab	Add '(opens in new tab)' to text
https://x.com/GoogleResearch	Follow us on x	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/showcase/google…	Follow us on linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/c/GoogleResearch	Follow us on youtube	new tab	Add '(opens in new tab)' to text
https://github.com/google-research	Follow us on github	new tab	Add '(opens in new tab)' to text
https://about.google/	About Google	new tab	Add '(opens in new tab)' to text
https://about.google/intl/en/products/	Google Products	new tab	Add '(opens in new tab)' to text
https://policies.google.com/privacy	Privacy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Terms	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

121 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://ai.google/earth-ai/?utm_source=researchgoogle&utm_medium=google-oo&ut… ("Learn more"); https://sites.research.google/gr/wildfires/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://policies.google.com/technologies/cookies?hl=en; https://research.google/programs-and-events/; https://blog.google/technology/research/new-updates-and-more-access-to-google…; https://www.youtube.com/watch?v=UZ4RaLGDXI4&list=PL95lT3XlM14ROFtYnlBDYZbKipH…; https://arxiv.org/abs/2510.18318; https://www.youtube.com/watch?v=kpeI9dbkWho&list=PL95lT3XlM14ROFtYnlBDYZbKipH…; https://www.youtube.com/watch?v=pmQlXLaHT_Y&t; https://blog.google/outreach-initiatives/sustainability/google-ai-wildfire-de…; https://www.earthfirealliance.org/; https://sites.research.google/floodforecasting/?_gl=1*127r8kr*_ga*MTA2OTMzOTE… (+15 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.search-input__button (#411 on page); button.search-input__button (#414 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

h2 Defining the technology of today and tom…

1.00:1

#000000

needs 3.0:1 (large text)

24px · above the fold

h2 Philosophy

1.00:1

#000000

needs 3.0:1 (large text)

24px · above the fold

h2 People

1.00:1

#000000

needs 3.0:1 (large text)

24px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Research to reality	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Defining the technol…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Philosophy	1.00:1	3.0:1	#000000	#000000	Fail
h2 People	1.00:1	3.0:1	#000000	#000000	Fail
h2 Research areas	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Foundational ML & Al…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Computing Systems & …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Science, AI & Societ…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Projects	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Publications	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Shaping the future, …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Student programs	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Faculty programs	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Conferences & events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Amplifying human ing…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Watch the film	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The cyclical relatio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Read the latest	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our research drives …	21.00:1	3.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.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

28 headings

PASS

28 headings

Single H1 present

H2 Defining the technology of today and tomorrow.
H2 Philosophy
H2 People
H2 Research areas
H2 Foundational ML & Algorithms
H2 Computing Systems & Quantum AI
H2 Science, AI & Society
H2 Projects
H2 Publications
H2 Resources
H2 Shaping the future, together.
H2 Student programs
H2 Faculty programs
H2 Conferences & events
H1 Research to reality
H2 Amplifying human ingenuity
H2 Watch the film
H2 The cyclical relationship between research and real-world impact
H2 Read the latest
H2 Our research drives real-world change
H2 Google Earth AI
H2 Wildfires
H2 See our impact across other projects
H2 We work across domains
H2 One research paper started it all
H2 Responsible research is at the heart of what we do
H2 Help us shape the future
H2 Explore our other teams and product areas

Alt Text Quality

1 of 19 images have issues

PASS

1 of 19 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

18 image(s) with good alt text

19 images 18 good alt text 1 missing

Issue	Count
missing	1 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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	search	(Search)	placeholder only

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

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 29 passed

PASS

100

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.

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
APRIL 13 TO APRIL 17 · CONFERENCES & EVENTS Google at CHI 2026 `div.glue-carousel > div.glue-carousel__viewport > div.glue-carousel__list > a.glue-card`
MARCH 31 · BLOG Building better AI benchmarks: How many raters are enough? `div.glue-carousel > div.glue-carousel__viewport > div.glue-carousel__list > a.glue-card`

○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]` 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.

●`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.

●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

○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

○`[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

○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.