Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 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

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.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Basecamp — Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

5 icon(s) detected

REVIEW

5 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

19 landmarks

PASS

19 landmarks

<main> landmark present

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

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

A+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H1 Wrestling with projects? It doesn’t have to be this hard.
H2 Let’s walk through it.
H3 10 seconds after you sign up, clarity sets in.
H3 Projects get teams — and keep teams — organized.
H3 Reports give you confidence to hold people accountable.
H3 Visualizations are for seeing, not squinting.
H3 Ping! Hey! It’s for you.
H3 Got clients? Be partners, not adversaries.
H3 The answer is YES!
H2 You wouldn’t be here if the way you’ve been working was working. It’s time for Basecamp.
H3 I have questions about your company…
H3 I have questions about security and our data…
H3 I have other questions…

A+

Alt Text Quality

All 25 images OK

PASS

All 25 images OK

25 image(s) with good alt text

25 images 25 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="checkbox" id="nav-active">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#mce-EMAIL	email	Your email address	aria-label
#nav-active	checkbox	(none)	none

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

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

Link & Button Quality

93 links, 27 buttons — all OK

PASS

93 links, 27 buttons — all OK

17 link(s) open in new tab without warning

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

Got: https://launchpad.37signals.com/signin; https://37signals.com; https://www.37status.com; https://37signals.com/policies/refund/; https://37signals.com/policies/security/; https://37signals.com/policies/security/37signals%20Security%20Overview.pdf; https://3.basecamp-help.com/article/150-export-your-basecamp-data; https://github.com/basecamp/bc3-api; https://launchpad.37signals.com/signin; https://www.hey.com (+7 more)

76 link(s) with descriptive text

93 links

0 empty

0 generic text

17 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://launchpad.37signals.com/signin	Sign in	new tab	Add '(opens in new tab)' to text
https://37signals.com	37signals	new tab	Add '(opens in new tab)' to text
https://www.37status.com	Status Page	new tab	Add '(opens in new tab)' to text
https://37signals.com/policies/refund/	Our refund policy	new tab	Add '(opens in new tab)' to text
https://37signals.com/policies/security/	full security write-up	new tab	Add '(opens in new tab)' to text
https://37signals.com/policies/security/…	prepared a summary security PD…	new tab	Add '(opens in new tab)' to text
https://3.basecamp-help.com/article/150-…	Here’s how exporting works	new tab	Add '(opens in new tab)' to text
https://github.com/basecamp/bc3-api	Basecamp has a full-featured A…	new tab	Add '(opens in new tab)' to text
https://launchpad.37signals.com/signin	Sign in to Basecamp	new tab	Add '(opens in new tab)' to text
https://www.hey.com	If you love Basecamp, you’ll…	new tab	Add '(opens in new tab)' to text
/	Basecamp	new tab	Add '(opens in new tab)' to text
https://37signals.com	37signals	new tab	Add '(opens in new tab)' to text
https://www.hey.com	HEY	new tab	Add '(opens in new tab)' to text
https://launchpad.37signals.com/signin	Sign in	new tab	Add '(opens in new tab)' to text
https://www.37status.com	Status	new tab	Add '(opens in new tab)' to text
https://updates.37signals.com	Updates	new tab	Add '(opens in new tab)' to text
https://37signals.com/policies	Policies	new tab	Add '(opens in new tab)' to text

103 links and buttons have descriptive text

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

https://launchpad.37signals.com/signin; https://37signals.com; https://www.37status.com; https://37signals.com/policies/refund/; https://37signals.com/policies/security/; https://37signals.com/policies/security/37signals%20Security%20Overview.pdf; https://3.basecamp-help.com/article/150-export-your-basecamp-data; https://github.com/basecamp/bc3-api; https://launchpad.37signals.com/signin; https://www.hey.com (+7 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

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 Wrestling with proje…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 It doesn’t have to…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Basecamp — Project…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p We’d like to use c…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Yes, that’s fine	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Basecamp	21.00:1	3.0:1	#000000	#FFFFFF	Pass
div is the	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span simply powerful	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong project management s…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
strong 37signals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
a Real world results	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Paths	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Pricing	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sign in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sign up free	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Real world results	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Features	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Paths	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Pricing	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 31 passed

PASS

100

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.

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

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

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●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

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

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

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

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