Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 6 REVIEW 3 FIX

Link & Button Quality

Action

6 issue(s) across 141 links and 16 buttons

FIX

6 issue(s) across 141 links and 16 buttons

6 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://blog.tensorflow.org/2025/08/whats-new-in-tensorflow-2-20.html; https://blog.tensorflow.org/2025/03/whats-new-in-tensorflow-2-19.html; https://blog.tensorflow.org/2024/12/introducing-wake-vision-new-dataset-for-p…; https://blog.tensorflow.org/2024/11/mlsysbookai-principles-and-practices-of-m…; https://blog.tensorflow.org/2024/10/whats-new-in-tensorflow-218.html; https://blog.tensorflow.org/2024/07/whats-new-in-tensorflow-217.html

3 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/resources/models-datasets"]; a[href="/resources/libraries-extensions"]; a[href="/resources/tools"]

2 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://colab.research.google.com/github/tensorflow/docs/blob/master/site/en/…

130 link(s) with descriptive text

141 links

6 empty

0 generic text

2 new tab

0 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://colab.research.google.com/github…	Run quickstart	new tab	Add '(opens in new tab)' to text
https://blog.tensorflow.org/2025/08/what…	(empty)	empty	Add link text or aria-label
https://blog.tensorflow.org/2025/03/what…	(empty)	empty	Add link text or aria-label
https://blog.tensorflow.org/2024/12/intr…	(empty)	empty	Add link text or aria-label
https://blog.tensorflow.org/2024/11/mlsy…	(empty)	empty	Add link text or aria-label
https://blog.tensorflow.org/2024/10/what…	(empty)	empty	Add link text or aria-label
https://blog.tensorflow.org/2024/07/what…	(empty)	empty	Add link text or aria-label
/resources/models-datasets	ML models & datasets …	img no alt	Add alt attribute to the image
/resources/libraries-extensions	Libraries & extensions …	img no alt	Add alt attribute to the image
/resources/tools	Developer tools …	img no alt	Add alt attribute to the image

146 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://blog.tensorflow.org/2025/08/whats-new-in-tensorflow-2-20.html; https://blog.tensorflow.org/2025/03/whats-new-in-tensorflow-2-19.html; https://blog.tensorflow.org/2024/12/introducing-wake-vision-new-dataset-for-p…; https://blog.tensorflow.org/2024/11/mlsysbookai-principles-and-practices-of-m…; https://blog.tensorflow.org/2024/10/whats-new-in-tensorflow-218.html; https://blog.tensorflow.org/2024/07/whats-new-in-tensorflow-217.html

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/resources/models-datasets"]; a[href="/resources/libraries-extensions"]; a[href="/resources/tools"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://policies.google.com/technologies/cookies?hl=en; https://colab.research.google.com/github/tensorflow/docs/blob/master/site/en/…

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

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 ✗

Heading Hierarchy

25 headings

REVIEW

25 headings

No H1 heading found

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

H2 Get started with TensorFlow
H2 Solve real-world problems with ML
H2 What's new in TensorFlow
H3 What's new in TensorFlow 2.20
H3 What's new in TensorFlow 2.19
H3 Introducing Wake Vision: A High-Quality, Large-Scale Dataset for TinyML Computer Vision Applications
H3 MLSysBook.AI: Principles and Practices of Machine Learning Systems Engineering
H3 What's new in TensorFlow 2.18
H3 What's new in TensorFlow 2.17
H2 Explore the ecosystem
H3 TensorFlow.js
H3 LiteRT
H3 tf.data
H3 TFX
H3 tf.keras
H3 Kaggle Models
H3 TensorFlow Datasets
H3 TensorBoard
H3 ML models & datasets
H3 Libraries & extensions
H3 Developer tools
H2 Stay connected
H2 Start building with TensorFlow
H3 Stay connected
H3 Support

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

Alt Text Quality

3 of 26 images have issues

REVIEW

3 of 26 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

13 decorative image(s) correctly marked

10 image(s) with good alt text

26 images 10 good alt text 13 decorative 3 missing

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

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Page Not Found | TensorFlow ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

12 icon(s) detected

REVIEW

12 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

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 #ff6f00 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 26 passed

REVIEW

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Updated August 19, 2025 `div.devsite-card-content-wrapper > div.devsite-card-content > div.devsite-card-section > p.devsite-card-date`
Updated March 13, 2025 `div.devsite-card-content-wrapper > div.devsite-card-content > div.devsite-card-section > p.devsite-card-date`
LIBRARY `li > a > div.tensorsite-blog-carousel__wrapper > p.tensorsite-blog-carousel__eyebrow`
LIBRARY `li > a > div.tensorsite-blog-carousel__wrapper > p.tensorsite-blog-carousel__eyebrow`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tensorsite-container > div.tensorsite-adjacent-partials-wrapper > div.tensorsite-adjacent-partials__main-section > img `div.tensorsite-container > div.tensorsite-adjacent-partials-wrapper > div.tensorsite-adjacent-partials__main-section > img`
div.tensorsite-container > div.tensorsite-adjacent-partials-wrapper > div.tensorsite-adjacent-partials__secondary-section > img `div.tensorsite-container > div.tensorsite-adjacent-partials-wrapper > div.tensorsite-adjacent-partials__secondary-section > img`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tensorsite-home-hero__main-section > div.tensorsite-home-hero__header > devsite-iframe > iframe `div.tensorsite-home-hero__main-section > div.tensorsite-home-hero__header > devsite-iframe > iframe`
div.tensorsite-stay-connected__container > div.tensorsite-stay-connected__steps-container > devsite-iframe > iframe `div.tensorsite-stay-connected__container > div.tensorsite-stay-connected__steps-container > devsite-iframe > iframe`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Form elements have associated labels

●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

●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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

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

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

○Select elements have associated label elements.

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

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

6 <nav> landmark(s) found

1 of 6 <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+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search	aria-label
input	text	Type to filter	aria-label

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: TensorFlow

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name TensorFlow ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name TensorFlow Display Mode standalone Theme Color #fb8c00 Background Color #fff Icons 8 icon(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)

Element	Ratio	Required	FG	BG	Result
h2 Get started with Ten…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h2 Solve real-world pro…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h2 What's new in Tensor…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h2 Explore the ecosyste…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h2 Stay connected	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h2 Start building with …	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 What's new in Tensor…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 What's new in Tensor…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Introducing Wake Vis…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 MLSysBook.AI: Princi…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 What's new in Tensor…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 What's new in Tensor…	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 TensorFlow.js	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 LiteRT	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 tf.data	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 TFX	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 tf.keras	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 Kaggle Models	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 TensorFlow Datasets	18.33:1	3.0:1	#000000	#E8F0FE	Pass
h3 TensorBoard	18.33:1	3.0:1	#000000	#E8F0FE	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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.