Skip to content
https://pypi.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 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 (404) · PyPI ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✓
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, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
a Help
4.14:1
#000000
on
#0073B7
needs 4.5:1 (normal text)
16px · above the fold
a Docs
4.14:1
#000000
on
#0073B7
needs 4.5:1 (normal text)
16px · above the fold
a Sponsors
3.91:1
#000000
on
#006FB1
needs 4.5:1 (normal text)
16px · above the fold
a Log in
3.79:1
#000000
on
#006DAD
needs 4.5:1 (normal text)
16px · above the fold
a Register
3.79:1
#000000
on
#006DAD
needs 4.5:1 (normal text)
16px · above the fold
button Menu
3.79:1
#000000
on
#006DAD
needs 4.5:1 (normal text)
16px · above the fold
a Help
3.79:1
#000000
on
#006DAD
needs 4.5:1 (normal text)
16px · above the fold
a Docs
3.79:1
#000000
on
#006DAD
needs 4.5:1 (normal text)
16px · above the fold
a Sponsors
3.79:1
#000000
on
#006DAD
needs 4.5:1 (normal text)
16px · mid-page
a Log in
3.79:1
#000000
on
#006DAD
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Find, install and pu…7.96:13.0:1
#000000
#65A7CD
Pass
h2 Help20.65:13.0:1
#000000
#FDFDFD
Pass
h2 About PyPI20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Contributing to PyPI20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Using PyPI20.65:13.0:1
#000000
#FDFDFD
Pass
title PyPI · The Python P…16.07:14.5:1
#000000
#FFDF76
Pass
a Skip to main content16.07:14.5:1
#000000
#FFDF76
Pass
button Switch to mobile ver…16.07:14.5:1
#000000
#FFDF76
Pass
span Join us in Long Beac…16.07:14.5:1
#000000
#FFDF76
Pass
a REGISTER FOR PYCON U…16.07:14.5:1
#000000
#FFDF76
Pass
a Help4.14:14.5:1
#000000
#0073B7
Fail
a Docs4.14:14.5:1
#000000
#0073B7
Fail
a Sponsors3.91:14.5:1
#000000
#006FB1
Fail
a Log in3.79:14.5:1
#000000
#006DAD
Fail
a Register3.79:14.5:1
#000000
#006DAD
Fail
button Menu3.79:14.5:1
#000000
#006DAD
Fail
a Help3.79:14.5:1
#000000
#006DAD
Fail
a Docs3.79:14.5:1
#000000
#006DAD
Fail
a Sponsors3.79:14.5:1
#000000
#006DAD
Fail
a Log in3.79:14.5:1
#000000
#006DAD
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.

A+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
6 <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 navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
5 headings
PASS
5 headings
Info::
Single H1 present
  • H1 Find, install and publish Python packages with the Python Package Index
  • H2 Help
  • H2 About PyPI
  • H2 Contributing to PyPI
  • H2 Using PyPI
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
10 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
11 images 1 good alt text 10 decorative
All images have appropriate alt text.
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
#searchtextSearch PyPIfor/id
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 26 passed
PASS
96

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Site map footer.footer > div.footer__text > p > a
English form > ul > li > button.language-switcher__selected
español form > ul > li > button
français form > ul > li > button
日本語 form > ul > li > button
português (Brasil) form > ul > li > button
українська form > ul > li > button
Ελληνικά form > ul > li > button
Deutsch form > ul > li > button
中文 (简体) form > ul > li > button
中文 (繁體) form > ul > li > button
русский form > ul > li > button
עברית form > ul > li > button
Esperanto form > ul > li > button
한국어 form > ul > li > button

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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`<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
○Select elements have associated label elements.
○No element has a `[tabindex]` value greater than 0
○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.
○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