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

Link & Button Quality

Action

39 issue(s) across 113 links and 44 buttons

FIX

39 issue(s) across 113 links and 44 buttons

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="https://www.meetup.com/blog/i-used-meetup-to-make-friends-at-brunch/"]; a[href="https://www.meetup.com/blog/how-to-turn-casual-connections-into-close-friends…"]; a[href="https://www.meetup.com/blog/do-you-have-the-right-number-of-friends/"]

18 link(s) open in new tab without warning

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

Got: https://help.meetup.com/hc; https://www.meetup.com/blog/category/local-guides/; https://www.meetup.com/blog/; https://bndspn.com/join-meetup; https://www.meetup.com/blog/category/keep-connected-podcast/; https://www.facebook.com/meetup/; https://twitter.com/Meetup/; https://www.youtube.com/meetup; https://www.instagram.com/meetup/; https://www.tiktok.com/@meetup (+8 more)

39 button(s) with no accessible text

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

Got: button.inline-flex (#187 on page); button.relative (#267 on page); button.relative (#273 on page); button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"] (+29 more)

92 link(s) with descriptive text

113 links

0 empty

0 generic text

18 new tab

39 empty buttons

Element	Text	Issue	Suggested Fix
https://www.meetup.com/blog/i-used-meetu…	I used Meetup to make friends …	new tab	Add '(opens in new tab)' to text
https://www.meetup.com/blog/how-to-turn-…	How to turn casual connections…	new tab	Add '(opens in new tab)' to text
https://www.meetup.com/blog/do-you-have-…	Do you have the “right” nu…	new tab	Add '(opens in new tab)' to text
https://help.meetup.com/hc	Help	new tab	Add '(opens in new tab)' to text
https://www.meetup.com/blog/category/loc…	Local guides	new tab	Add '(opens in new tab)' to text
https://www.meetup.com/blog/	Blog	new tab	Add '(opens in new tab)' to text
https://bndspn.com/join-meetup	Careers	new tab	Add '(opens in new tab)' to text
https://www.meetup.com/blog/category/kee…	Podcast	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/meetup/	Meetup on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/Meetup/	Meetup on Twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/meetup	Meetup on YouTube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/meetup/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@meetup	TikTok	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Download app from Google Play	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/meetup/id3…	Download app from App Store	new tab	Add '(opens in new tab)' to text
https://help.meetup.com/hc/articles/3600…	Terms of service	new tab	Add '(opens in new tab)' to text
https://help.meetup.com/hc/articles/3600…	Privacy policy	new tab	Add '(opens in new tab)' to text
https://help.meetup.com/hc/articles/3600…	Cookie policy	new tab	Add '(opens in new tab)' to text
/license-attribution/index.html	License attribution	new tab	Add '(opens in new tab)' to text
https://help.meetup.com/hc	Help	new tab	Add '(opens in new tab)' to text
https://www.bendingspoons.com	bendingSpoonsWordmark icon	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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

97 links and buttons have descriptive text

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

a[href="https://www.meetup.com/blog/i-used-meetup-to-make-friends-at-brunch/"]; a[href="https://www.meetup.com/blog/how-to-turn-casual-connections-into-close-friends…"]; a[href="https://www.meetup.com/blog/do-you-have-the-right-number-of-friends/"]

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://help.meetup.com/hc; https://www.meetup.com/blog/category/local-guides/; https://www.meetup.com/blog/; https://bndspn.com/join-meetup; https://www.meetup.com/blog/category/keep-connected-podcast/; https://www.facebook.com/meetup/; https://twitter.com/Meetup/; https://www.youtube.com/meetup; https://www.instagram.com/meetup/; https://www.tiktok.com/@meetup (+8 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.inline-flex (#187 on page); button.relative (#267 on page); button.relative (#273 on page); button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"]; button[data-testid="share-btn-redesign"] (+29 more)

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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-746w5x

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://meetup.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://meetup.com/manifest.json

Manifest contains invalid JSON.

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 ✗

Favicon & Branding

8 icon(s) detected

REVIEW

8 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

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 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

Heading Hierarchy

64 headings

PASS

64 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 The people platform.Where interestsbecome friendships.
H1 The people platform.Where interestsbecome friendships.The people platform. Where interests become friendships. duplicate H1
H2 Events near New York, NY
H3 Wednesday Social Meetup Into Comedy Show!
H3 Rust NYC: Formally Verified Rust & SAT Solvers
H3 Bear Mountain Free hike!
H3 BUILDING A CAREER THAT SURVIVES AI
H3 Rust NYC x OpenAI: Safer 'unsafe' & Barnum: The agentic workflow engine.
H3 NYC Tech Mixer 2026
H3 🦜☕Saturday Language Exchange NYC Coffee Social
H3 Media/Advertising Professionals Meet
H3 Wednesday Social Meetup Into Comedy Show!
H3 Rust NYC: Formally Verified Rust & SAT Solvers
H3 Bear Mountain Free hike!
H3 BUILDING A CAREER THAT SURVIVES AI
H3 Rust NYC x OpenAI: Safer 'unsafe' & Barnum: The agentic workflow engine.
H3 NYC Tech Mixer 2026
H3 🦜☕Saturday Language Exchange NYC Coffee Social
H3 Media/Advertising Professionals Meet
H3 Wednesday Social Meetup Into Comedy Show!
H3 Rust NYC: Formally Verified Rust & SAT Solvers
H3 Bear Mountain Free hike!
H3 BUILDING A CAREER THAT SURVIVES AI
H3 Rust NYC x OpenAI: Safer 'unsafe' & Barnum: The agentic workflow engine.
H3 NYC Tech Mixer 2026
H3 🦜☕Saturday Language Exchange NYC Coffee Social
H3 Media/Advertising Professionals Meet
H2 Upcoming online events
H3 Seed Builders Circle - Wednesday Morning Session
H3 Why Motivation Fades and How to Build a Future That Pulls You Forward
H3 The Blueprint to Dating in Midlife & Beyond
H3 NEW YORK LIVE Walk: Wall Street and the Financial District
H3 Seed Builders Circle - Wednesday Morning Session
H3 Why Motivation Fades and How to Build a Future That Pulls You Forward
H3 The Blueprint to Dating in Midlife & Beyond
H3 NEW YORK LIVE Walk: Wall Street and the Financial District
H3 Seed Builders Circle - Wednesday Morning Session
H3 Why Motivation Fades and How to Build a Future That Pulls You Forward
H3 The Blueprint to Dating in Midlife & Beyond
H3 NEW YORK LIVE Walk: Wall Street and the Financial District
H2 Join Meetup
H2 Explore top categories
H2 Popular cities on Meetup
H3 New York
H3 New York
H3 San Francisco
H3 San Francisco
H3 Chicago
H3 Chicago
H3 Nashville
H3 Nashville
H3 Miami
H3 Miami
H2 How Meetup works
H3 Discover events and groups
H3 Find your people
H3 Start a group to host events
H3 Discover events and groups
H3 Find your people
H3 Start a group to host events
H2 Friendships are made on Meetup
H3 I used Meetup to make friends at brunch
H3 How to turn casual connections into close friendships
H3 Do you have the “right” number of friends?

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 197 images OK

PASS

All 197 images OK

9 decorative image(s) correctly marked

188 image(s) with good alt text

197 images 188 good alt text 9 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.

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 Events near	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h2 Upcoming online even…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h2 Join Meetup	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h2 Explore top categori…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h2 Popular cities on Me…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h2 How Meetup works	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h2 Friendships are made…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Wednesday Social Mee…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Rust NYC: Formally V…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Bear Mountain Free h…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 BUILDING A CAREER TH…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Rust NYC x OpenAI: S…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 NYC Tech Mixer 2026	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 🦜☕Saturday Lang…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Media/Advertising Pr…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Wednesday Social Mee…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Rust NYC: Formally V…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Bear Mountain Free h…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 BUILDING A CAREER TH…	20.48:1	3.0:1	#000000	#FCFCFD	Pass
h3 Rust NYC x OpenAI: S…	20.48:1	3.0:1	#000000	#FCFCFD	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.

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 24 passed

PASS

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.flex > div.flex > div.flex > button.inline-flex `div.flex > div.flex > div.flex > button.inline-flex`
header#app-header > div.flex > div.flex > button.inline-flex `header#app-header > div.flex > div.flex > button.inline-flex`
div.mb-ds2-28 > h2.ds2-b24 > div.inline-flex > button.relative `div.mb-ds2-28 > h2.ds2-b24 > div.inline-flex > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`
div.relative > div.absolute > div.opacity-100 > button.relative `div.relative > div.absolute > div.opacity-100 > button.relative`

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
Search events... `div.flex > div.flex > div.flex > span.ds2-r14`

These are opportunities to improve the legibility of your content.

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
Download on Google Play `div.flex > div.flex > div.flex > a.flex`

○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

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

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

●Identical links have the same purpose.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

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

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