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 3 REVIEW 6 FIX

Link & Button Quality

Action

17 issue(s) across 85 links and 2 buttons

FIX

17 issue(s) across 85 links and 2 buttons

15 link(s) with no accessible text

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

Got: https://mastodon.social/@PyData; https://pycon.am/; https://juliacon.org/2026/; https://pydata.org/events/pydata-global-2/; https://pydata.org/london2026/; https://www.scipy2026.scipy.org/; https://pycon.am/; https://juliacon.org/2026/; https://pydata.org/events/pydata-global-2/; https://pydata.org/london2026/ (+5 more)

3 link(s) open in new tab without warning

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

Got: https://pydata.org/wp-content/uploads/2022/03/PyData-2022-Sponsorship-Prospec…; https://pydata.org/wp-content/uploads/2022/03/PyData-2022-Sponsorship-Prospec…; https://pydata.org/wp-content/uploads/2019/04/sponsor-prospectus.pdf

2 button(s) with no accessible text

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

Got: button.owl-prev (#391 on page); button.owl-next (#393 on page)

67 link(s) with descriptive text

85 links

15 empty

0 generic text

3 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://pydata.org/wp-content/uploads/20…	Sponsor Prospectus	new tab	Add '(opens in new tab)' to text
https://pydata.org/wp-content/uploads/20…	Sponsor Prospectus	new tab	Add '(opens in new tab)' to text
https://mastodon.social/@PyData	(empty)	empty	Add link text or aria-label
https://pycon.am/	(empty)	empty	Add link text or aria-label
https://juliacon.org/2026/	(empty)	empty	Add link text or aria-label
https://pydata.org/events/pydata-global-…	(empty)	empty	Add link text or aria-label
https://pydata.org/london2026/	(empty)	empty	Add link text or aria-label
https://www.scipy2026.scipy.org/	(empty)	empty	Add link text or aria-label
https://pycon.am/	(empty)	empty	Add link text or aria-label
https://juliacon.org/2026/	(empty)	empty	Add link text or aria-label
https://pydata.org/events/pydata-global-…	(empty)	empty	Add link text or aria-label
https://pydata.org/london2026/	(empty)	empty	Add link text or aria-label
https://www.scipy2026.scipy.org/	(empty)	empty	Add link text or aria-label
https://pycon.am/	(empty)	empty	Add link text or aria-label
https://numfocus.org/?__hstc=95495811.1c…	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://pydata.org/wp-content/uploads/20…	Become a Sponsor	new tab	Add '(opens in new tab)' to text
https://numfocus.org/?__hstc=95495811.1c…	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

67 links and buttons have descriptive text

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

https://mastodon.social/@PyData; https://pycon.am/; https://juliacon.org/2026/; https://pydata.org/events/pydata-global-2/; https://pydata.org/london2026/; https://www.scipy2026.scipy.org/; https://pycon.am/; https://juliacon.org/2026/; https://pydata.org/events/pydata-global-2/; https://pydata.org/london2026/ (+5 more)

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

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

https://pydata.org/wp-content/uploads/2022/03/PyData-2022-Sponsorship-Prospec…; https://pydata.org/wp-content/uploads/2022/03/PyData-2022-Sponsorship-Prospec…; https://pydata.org/wp-content/uploads/2019/04/sponsor-prospectus.pdf

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.owl-prev (#391 on page); button.owl-next (#393 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

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Lighthouse Accessibility Audits

Action

Score 67/100 — 7 failing, 14 passed

FIX

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mec-event-carousel-type2 > div.mec-owl-crousel-skin-type2 > div.owl-nav > button.owl-prev `div.mec-event-carousel-type2 > div.mec-owl-crousel-skin-type2 > div.owl-nav > button.owl-prev`
div.mec-event-carousel-type2 > div.mec-owl-crousel-skin-type2 > div.owl-nav > button.owl-next `div.mec-event-carousel-type2 > div.mec-owl-crousel-skin-type2 > div.owl-nav > button.owl-next`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-content-container > div.header-content > div.et_pb_header_content_wrapper > a `div.header-content-container > div.header-content > div.et_pb_header_content_wrapper > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-image > a`
div.et_pb_module > div.et_pb_text_inner > p > a `div.et_pb_module > div.et_pb_text_inner > p > a`
div.et_pb_module > div.et_pb_video_overlay > div.et_pb_video_overlay_hover > a.et_pb_video_play `div.et_pb_module > div.et_pb_video_overlay > div.et_pb_video_overlay_hover > a.et_pb_video_play`
div#text-6 > div.textwidget > p > a `div#text-6 > div.textwidget > p > a`

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.

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
Aug 10 - 15, 2026 `div.event-carousel-type2-head > div.mec-event-carousel-content-type2 > span.mec-event-date-info > span.mec-start-date-label`
Become a Member `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
View All Meetups `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
Start a Meetup `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
Become a Sponsor `div.header-content > div.et_pb_header_content_wrapper > p > a.et_pb_button`
Subscribe `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a#subscribe-btn`
2026 — Design by Skytemple `div.container > p#footer-info > div#footer-editor-info > p`
Skytemple `p#footer-info > div#footer-editor-info > p > a`

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
Privacy Policy `div#text-5 > div.textwidget > p > a`
admin@pydata.org `div#text-4 > div.textwidget > 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
PYDATA PYCON YEREVAN `article.mec-event-article > div.event-carousel-type2-head > div.mec-event-carousel-content-type2 > h4.mec-event-carousel-title`
CONTACT US `div#footer-widgets > div.footer-widget > div#text-4 > h4.title`

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`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Image elements have `[alt]` attributes

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○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 use only permitted ARIA attributes

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

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

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

14 headings, 2 skip(s)

REVIEW

14 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 A community for developers and users of open source data tools
H4 PyData PyCon Yerevan skipped
H4 JuliaCon 2026
H4 PyData Global
H4 PyData London 2026
H4 SciPy 2026
H4 PyData PyCon Yerevan
H4 JuliaCon 2026
H4 PyData Global
H4 PyData London 2026
H4 SciPy 2026
H4 PyData PyCon Yerevan
H2 Join our PyData Newsletter
H4 Contact Us skipped

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Favicon & Branding

4 icon(s) detected

REVIEW

4 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 Missing

✓ Multiple Sizes Present

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

14 decorative image(s) correctly marked

2 image(s) with good alt text

16 images 2 good alt text 14 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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 ✓Page Title 404 Not Found | PyData ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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
h1 A community for deve…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join our PyData News…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title PyData \|	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Events	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Upcoming Events	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Past Events	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Organize a Conferenc…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Find a Meetup	19.85:1	4.5:1	#000000	#F6F9FA	Pass
a Start a Meetup	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Volunteer	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Code of Conduct	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Diversity & Inclusio…	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Sponsor Prospectus	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Resources	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Video Library	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a FAQs	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a About	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a PyData Strategic Com…	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Community Discord	20.02:1	4.5:1	#000000	#F7FAFB	Pass
a Sponsor PyData	20.02:1	4.5:1	#000000	#F7FAFB	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.