Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 5 REVIEW 7 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

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

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

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://pearltrees.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://pearltrees.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 ✗

Lighthouse Accessibility Audits

Action

Score 50/100 — 4 failing, 5 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.

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
Organize everything `div.inner-item > div.logo-and-text-row > div.logo-and-text-container > div.logo-text`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.inner-item > div.logo-and-text-row > div.logo-and-text-container > img.logo-container `div.inner-item > div.logo-and-text-row > div.logo-and-text-container > img.logo-container`

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.

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`

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

●Document has a `<title>` element

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

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

●Document has a main landmark.

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[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

○`[role]` values are valid

○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

○Buttons have an accessible name

○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

○Heading elements appear in a sequentially-descending order

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

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

○Links have a discernible name

○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

○Touch targets have sufficient size and spacing.

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

Heading Hierarchy

1 headings

REVIEW

1 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H4 lostPassword

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Form Accessibility

2 of 18 controls have issues

REVIEW

2 of 18 controls have issues

2 control(s) without accessible label

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

Got: <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

16 control(s) properly labeled

18 controls

16 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#log_username	text	label	for/id
#log_password	password	label	for/id
#hiddenId	text	label	for/id
#hiddenpassId	password	label	for/id
#username	text	label	for/id
#email	text	label	for/id
#password	password	label	for/id
#password_confirm	password	label	for/id
#form-username	text	label	for/id
#form-bio	text	label	for/id
#form-realname	text	label	for/id
#form-email	text	label	for/id
#form-signuptype	text	label	for/id
#form-tid	text	label	for/id
#cpn	text	hide	for/id
#form-invitationKey	text	invitationkey:	for/id
input	submit	(none)	none
#g-recaptcha-response-100000	textarea	(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

Action

2 issue(s) across 12 links and 3 buttons

REVIEW

2 issue(s) across 12 links and 3 buttons

9 link(s) open in new tab without warning

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

Got: https://www.pearltrees.com/about; https://www.pearltrees.com/info/aboutPearltreesAIEn; https://apps.apple.com//app/pearltrees/id463462134?mt=8; https://play.google.com/store/apps/details?id=com.pearltrees.android.prod; https://www.pearltrees.com/contact; https://www.pearltrees.com/popular; https://www.pearltrees.com/info/privacy; https://www.pearltrees.com/info/terms; http://www.pearltrees.com/s/faq/en

2 button(s) with no accessible text

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

Got: button (#152 on page); button (#207 on page)

3 link(s) with descriptive text

12 links

0 empty

0 generic text

9 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.pearltrees.com/about	About Pearltrees	new tab	Add '(opens in new tab)' to text
https://www.pearltrees.com/info/aboutPea…	About Pearltrees AI	new tab	Add '(opens in new tab)' to text
https://apps.apple.com//app/pearltrees/i…	iOS app	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Android app	new tab	Add '(opens in new tab)' to text
https://www.pearltrees.com/contact	Contact	new tab	Add '(opens in new tab)' to text
https://www.pearltrees.com/popular	Popular	new tab	Add '(opens in new tab)' to text
https://www.pearltrees.com/info/privacy	Privacy policy	new tab	Add '(opens in new tab)' to text
https://www.pearltrees.com/info/terms	Terms of service	new tab	Add '(opens in new tab)' to text
http://www.pearltrees.com/s/faq/en	FAQs	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

4 links and buttons have descriptive text

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

https://www.pearltrees.com/about; https://www.pearltrees.com/info/aboutPearltreesAIEn; https://apps.apple.com//app/pearltrees/id463462134?mt=8; https://play.google.com/store/apps/details?id=com.pearltrees.android.prod; https://www.pearltrees.com/contact; https://www.pearltrees.com/popular; https://www.pearltrees.com/info/privacy; https://www.pearltrees.com/info/terms; http://www.pearltrees.com/s/faq/en

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 (#152 on page); button (#207 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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 14 pass AA only

div Collaborate, share and discover your way

2.94:1

#000000

#3D5A79

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Pearltrees	6.60:1	4.5:1	#000000	#6495C0	Pass
a About Pearltrees	6.60:1	4.5:1	#000000	#6495C0	Pass
a About Pearltrees AI	6.60:1	4.5:1	#000000	#6495C0	Pass
a iOS app	6.60:1	4.5:1	#000000	#6495C0	Pass
a Android app	6.60:1	4.5:1	#000000	#6495C0	Pass
a Contact	6.60:1	4.5:1	#000000	#6495C0	Pass
a Popular	6.60:1	4.5:1	#000000	#6495C0	Pass
a Privacy policy	6.60:1	4.5:1	#000000	#6495C0	Pass
a Terms of service	11.34:1	4.5:1	#000000	#91C5E7	Pass
a FAQs	10.73:1	4.5:1	#000000	#9BBED6	Pass
div Organize, collaborat…	7.45:1	4.5:1	#000000	#959B9C	Pass
div Add and transform yo…	14.11:1	4.5:1	#000000	#B5D9ED	Pass
div Organize, customize …	6.35:1	4.5:1	#000000	#918D85	Pass
div Collaborate, share a…	2.94:1	4.5:1	#000000	#3D5A79	Fail
div Create your account …	6.60:1	4.5:1	#000000	#6495C0	Pass
span Organize everything	6.60:1	4.5:1	#000000	#6495C0	Pass
span Log in to Pearltrees	7.12:1	4.5:1	#000000	#6C9BC4	Pass
label label	6.60:1	4.5:1	#000000	#6495C0	Pass
label label	6.60:1	4.5:1	#000000	#6495C0	Pass
span Join	6.60:1	4.5:1	#000000	#6495C0	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+

Alt Text Quality

All 14 images OK

PASS

All 14 images OK

14 image(s) with good alt text

14 images 14 good alt text

All images have appropriate alt text.

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