Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 6 REVIEW 4 FIX

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

5 <nav> landmark(s) found

5 of 5 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

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

Link & Button Quality

Action

6 issue(s) across 20 links and 4 buttons

REVIEW

6 issue(s) across 20 links and 4 buttons

6 link(s) with no accessible text

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

Got: https://facebook.com/couchsurfing; https://x.com/couchsurfing; https://couchsurfing.tumblr.com/; https://instagram.com/couchsurfing; https://itunes.apple.com/us/app/couchsurfing/id525642917; https://play.google.com/store/apps/details?id=com.couchsurfing.mobile.android

10 link(s) open in new tab without warning

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

Got: https://itunes.apple.com/us/app/couchsurfing/id525642917; https://play.google.com/store/apps/details?id=com.couchsurfing.mobile.android; https://about.couchsurfing.com/about/about-us/; https://www.couchsurfing.com/about/safety/; https://support.couchsurfing.com/; https://blog.couchsurfing.com/; https://store.couchsurfing.com/; https://www.couchsurfing.com/about/terms-of-use; https://www.couchsurfing.com/about/privacy-policy; https://www.couchsurfing.com/places

4 link(s) with descriptive text

20 links

6 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://itunes.apple.com/us/app/couchsur…	iOS App Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Google Play Store	new tab	Add '(opens in new tab)' to text
https://about.couchsurfing.com/about/abo…	About	new tab	Add '(opens in new tab)' to text
https://www.couchsurfing.com/about/safet…	Safety	new tab	Add '(opens in new tab)' to text
https://support.couchsurfing.com/	Support	new tab	Add '(opens in new tab)' to text
https://blog.couchsurfing.com/	Blog	new tab	Add '(opens in new tab)' to text
https://store.couchsurfing.com/	Shop	new tab	Add '(opens in new tab)' to text
https://facebook.com/couchsurfing	(empty)	empty	Add link text or aria-label
https://x.com/couchsurfing	(empty)	empty	Add link text or aria-label
https://couchsurfing.tumblr.com/	(empty)	empty	Add link text or aria-label
https://instagram.com/couchsurfing	(empty)	empty	Add link text or aria-label
https://itunes.apple.com/us/app/couchsur…	(empty)	empty	Add link text or aria-label
https://play.google.com/store/apps/detai…	(empty)	empty	Add link text or aria-label
https://www.couchsurfing.com/about/terms…	Terms	new tab	Add '(opens in new tab)' to text
https://www.couchsurfing.com/about/priva…	Privacy	new tab	Add '(opens in new tab)' to text
https://www.couchsurfing.com/places	Sitemap	new tab	Add '(opens in new tab)' to text

8 links and buttons have descriptive text

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

https://facebook.com/couchsurfing; https://x.com/couchsurfing; https://couchsurfing.tumblr.com/; https://instagram.com/couchsurfing; https://itunes.apple.com/us/app/couchsurfing/id525642917; https://play.google.com/store/apps/details?id=com.couchsurfing.mobile.android

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://itunes.apple.com/us/app/couchsurfing/id525642917; https://play.google.com/store/apps/details?id=com.couchsurfing.mobile.android; https://about.couchsurfing.com/about/about-us/; https://www.couchsurfing.com/about/safety/; https://support.couchsurfing.com/; https://blog.couchsurfing.com/; https://store.couchsurfing.com/; https://www.couchsurfing.com/about/terms-of-use; https://www.couchsurfing.com/about/privacy-policy; https://www.couchsurfing.com/places

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

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 Error | not found | Couchsurfing ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 3 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Stay with Locals and…	4.82:1	3.0:1	#000000	#287FB8	Pass
h2 Share Authentic Trav…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sign Up Faster With	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sign Up With Email	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Download Our App	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Connect With Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Mobile Apps	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Meet and Stay with L…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div English	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span	9.21:1	4.5:1	#000000	#7EB2D4	Pass
a How It Works	4.82:1	4.5:1	#000000	#287FB8	Pass
a Safety	4.82:1	4.5:1	#000000	#287FB8	Pass
button Log In	4.82:1	4.5:1	#000000	#287FB8	Pass
button Facebook	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p We will never post w…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label First Name	8.80:1	4.5:1	#000000	#7CAECE	Pass
span First Name	12.32:1	4.5:1	#000000	#A9CBE1	Pass
label Last Name	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Last Name	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Email	21.00:1	4.5:1	#000000	#FFFFFF	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 89/100 — 3 failing, 23 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.

ARIA

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English `div.footer_container__SPP1V > section.footer_internalLinksRow__vQsZD > div.MuiInputBase-root > div.MuiSelect-select`

These are opportunities to improve the usage of ARIA in your application which 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
Log In `header.MuiPaper-root > nav.MuiToolbar-root > div.header_rightGroup__WNzBQ > button.MuiButtonBase-root`
Join `div.home-page_cards__Y1Lye > div.card_card__R8e1Q > form.sign-up-form_form__YEjuc > button.MuiButtonBase-root`
CONNECT WITH US `div.footer_container__SPP1V > section.footer_socialAndAppsRow__MIHUB > div.footer_socialLinks__7pShi > h3`
MOBILE APPS `div.footer_container__SPP1V > section.footer_socialAndAppsRow__MIHUB > div.footer_socialLinks__7pShi > h3`
© 1999 - 2026 Couchsurfing International, Inc. `footer.footer_footer__LUXkQ > div.footer_container__SPP1V > section.footer_legalLinksRow__xJpGG > span.footer_legalLink__fAT6O`
Terms `nav > ul > li > a.footer_legalLink__fAT6O`
Privacy `nav > ul > li > a.footer_legalLink__fAT6O`
Sitemap `nav > ul > li > a.footer_legalLink__fAT6O`

These are opportunities to improve the legibility of your content.

Names and labels

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
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`
nav > ul > li > a.MuiButtonBase-root `nav > ul > li > a.MuiButtonBase-root`

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

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

●Document has a `<title>` element

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

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

A+

Heading Hierarchy

7 headings

PASS

7 headings

Single H1 present

H1 Stay with Locals and Meet Travelers
H2 Share Authentic Travel Experiences
H3 Sign Up Faster With
H3 Sign Up With Email
H3 Download Our App
H3 Connect With Us
H3 Mobile Apps

A+

Alt Text Quality

1 of 3 images have issues

PASS

1 of 3 images have issues

1 image(s) with generic alt text

2 image(s) with good alt text

3 images 2 good alt text 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#:Rajefnjt9vikq:	text	First Name *	for/id
#:Rijefnjt9vikq:	text	Last Name *	for/id
#:R3jefnjt9vikq:	email	Email *	for/id
#:R4jefnjt9vikq:	password	Password *	for/id

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