Skip to content
https://pytorch.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Heading Hierarchy
Action
30 headings, 4 skip(s)
FIX
30 headings, 4 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.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 JOIN US
  • H3 PyTorch Conference North America October 20-21, 2026 San Jose, CA #PyTorchCon skipped
  • H3 Optimizing Effective Training Time for Meta’s Internal Recommendation/Ranking Workloads
  • H3 PyTorch Conference Europe 2026: A Landmark Moment for Open Source AI in Paris
  • H3 Faster Diffusion on Blackwell: MXFP8 and NVFP4 with Diffusers and TorchAO
  • H2 Join PyTorch Foundation
  • H2 Key Features & Capabilities
  • H5 Production Ready skipped
  • H5 Distributed Training
  • H5 Robust Ecosystem
  • H5 Cloud Support
  • H2 Install PyTorch
  • H3 Quick Start With Cloud Partners
  • H3 Amazon Web Services
  • H3 Google Cloud Platform
  • H3 Microsoft Azure
  • H3 Lightning Studios
  • H2 Ecosystem
  • H5 Featured Projects skipped
  • H4 Captum
  • H4 PyTorch Geometric
  • H4 skorch
  • H2 Companies & Universities Using PyTorch
  • H5 Amazon Advertising skipped
  • H5 Salesforce
  • H5 Stanford University
  • H3 Docs
  • H3 Tutorials
  • H3 Resources
  • H2 Stay in touch for updates, event info, and the latest news

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

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

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

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

D
Form Accessibility
Action
5 of 9 controls have issues
FIX
5 of 9 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="country_dropdown" id="country_dropdown-2fb2231c-000b-4ec5-88a0-1ab242549c9e">; <input type="submit">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="firstname" id="firstname-2fb2231c-000b-4ec5-88a0-1ab242549c9e">; <input type="text" name="lastname" id="lastname-2fb2231c-000b-4ec5-88a0-1ab242549c9e">; <input type="email" name="email" id="email-2fb2231c-000b-4ec5-88a0-1ab242549c9e">
Info::
4 control(s) properly labeled
9 controls
4 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
#osano-cm-dialog-toggle--category_MARKETINGcheckboxnone
#osano-cm-dialog-toggle--category_PERSONALIZATIONcheckboxnone
#osano-cm-dialog-toggle--category_ANALYTICScheckboxnone
stextSearcharia-label
#firstname-2fb2231c-000b-4ec5-88a0-1ab242549c9etext(First Name*)placeholder only
#lastname-2fb2231c-000b-4ec5-88a0-1ab242549c9etext(Last Name*)placeholder only
#email-2fb2231c-000b-4ec5-88a0-1ab242549c9eemail(Email*)placeholder only
#country_dropdown-2fb2231c-000b-4ec5-88a0-1ab242549c9eselect(none)none
inputsubmit(none)none

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

<select name="country_dropdown" id="country_dropdown-2fb2231c-000b-4ec5-88a0-1ab242549c9e">; <input type="submit">

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" name="firstname" id="firstname-2fb2231c-000b-4ec5-88a0-1ab242549c9e">; <input type="text" name="lastname" id="lastname-2fb2231c-000b-4ec5-88a0-1ab242549c9e">; <input type="email" name="email" id="email-2fb2231c-000b-4ec5-88a0-1ab242549c9e">

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

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
4 navigation landmark(s) detected
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.
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 JOIN US
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Join PyTorch Foundation
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Key Features & Capabilities
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Install PyTorch
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ecosystem
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Companies & Universities Using PyTorch
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 for updates, event info, and the latest …
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h3 PyTorch Conference North America
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 October 20-21, 2026
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 San Jose, CA
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 #PyTorchCon
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Optimizing Effective Training Time for M…
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PyTorch Conference Europe 2026: A Landma…
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Faster Diffusion on Blackwell: MXFP8 and…
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Quick Start With Cloud Partners
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Docs
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tutorials
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Resources
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
title PyTorch
4.38:1
#000000
on
#CC2F90
needs 4.5:1 (normal text)
16px · top of page (header area)
span Opens in a new window
4.38:1
#000000
on
#CC2F90
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 JOIN US1.32:13.0:1
#000000
#222222
Fail
h2 Join PyTorch Foundat…1.32:13.0:1
#000000
#222222
Fail
h2 Key Features & Capab…1.32:13.0:1
#000000
#222222
Fail
h2 Install PyTorch1.32:13.0:1
#000000
#222222
Fail
h2 Ecosystem1.32:13.0:1
#000000
#222222
Fail
h2 Companies & Universi…1.32:13.0:1
#000000
#222222
Fail
h2 for updates, event i…1.32:13.0:1
#000000
#222222
Fail
h3 PyTorch Conference N…1.32:13.0:1
#000000
#222222
Fail
h3 October 20-21, 20261.32:13.0:1
#000000
#222222
Fail
h3 San Jose, CA1.32:13.0:1
#000000
#222222
Fail
h3 #PyTorchCon1.32:13.0:1
#000000
#222222
Fail
h3 Optimizing Effective…1.32:13.0:1
#000000
#222222
Fail
h3 PyTorch Conference E…1.32:13.0:1
#000000
#222222
Fail
h3 Faster Diffusion on …1.32:13.0:1
#000000
#222222
Fail
h3 Quick Start With Clo…1.32:13.0:1
#000000
#222222
Fail
h3 Docs1.32:13.0:1
#000000
#222222
Fail
h3 Tutorials1.32:13.0:1
#000000
#222222
Fail
h3 Resources1.32:13.0:1
#000000
#222222
Fail
title PyTorch4.38:14.5:1
#000000
#CC2F90
Fail
span Opens in a new windo…4.38:14.5:1
#000000
#CC2F90
Fail

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.

B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 26 passed
REVIEW
84

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
Targeted Advertising ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Personalization ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Analytics ul#osano-cm-dialog-toggle-group > li.osano-cm-list__list-item > label.osano-cm-list-item__toggle > span.osano-cm-toggle__label
Save div.osano-cm-window > div#02018d62-a1cd-44e1-b0a8-63229b4389b4 > div.osano-cm-dialog__buttons > button.osano-cm-save
Accept All div.osano-cm-window > div#02018d62-a1cd-44e1-b0a8-63229b4389b4 > div.osano-cm-dialog__buttons > button.osano-cm-accept-all
Reject Non-Essential div.osano-cm-window > div#02018d62-a1cd-44e1-b0a8-63229b4389b4 > div.osano-cm-dialog__buttons > button.osano-cm-denyAll
install previous versions of PyTorch div.wpb_wrapper > div.wpb_text_column > p > a
Stable (2.11.0) div.col-md-9 > div.row > div#stable > div.option-text
Linux div.col-md-9 > div.row > div#linux > div.option-text
Pip div.col-md-9 > div.row > div#pip > div.option-text
Python div.col-md-9 > div.row > div#python > div.option-text
CUDA 12.6 div.col-md-9 > div.row > div#cuda.x > div.option-text
Previous versions of PyTorch div.vc_column-inner > div.wpb_wrapper > a.nectar-button > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
install previous versions of PyTorch div.wpb_wrapper > div.wpb_text_column > p > a

These are opportunities to improve the legibility of your content.

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
PyTorch Conference North America October 20-21, 2026 San Jose, CA #PyTorchCon div.vc_column-inner > div.wpb_wrapper > div.wpb_text_column > h3.tribe-events-single-event-title
PRODUCTION READY div.vc_column-inner > div.wpb_wrapper > div.wpb_text_column > h5
FEATURED PROJECTS div.wpb_wrapper > div.wpb_text_column > div > h5
AMAZON ADVERTISING div.vc_column-inner > div.wpb_wrapper > div.wpb_text_column > h5

These are opportunities to improve keyboard navigation in your application.

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.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select Country* Afghanistan Åland Islands Albania Algeria American Samoa Andorr… form#hsForm_2fb2231c-000b-4ec5-88a0-1ab242549c9e > div.hs_country_dropdown > div.input > select#country_dropdown-2fb2231c-000b-4ec5-88a0-1ab242549c9e

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.

○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
●Input buttons have discernible text.
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.
A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 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 "Skip links" 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 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – PyTorch ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback