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

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-29ewo1

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

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

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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

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

1 issue(s) across 25 links and 15 buttons

REVIEW

1 issue(s) across 25 links and 15 buttons

1 link(s) with no accessible text

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

14 link(s) open in new tab without warning

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

Got: https://discuss.logseq.com; https://docs.logseq.com/; https://github.com/logseq; https://blog.logseq.com; https://github.com/logseq/logseq/releases; https://github.com/logseq/logseq/releases; https://docs.logseq.com/#/page/queries; https://docs.logseq.com/#/page/search; https://docs.logseq.com/#/page/flashcards; https://docs.logseq.com/#/page/term%2Fblock%20reference (+4 more)

10 link(s) with descriptive text

25 links

1 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://discuss.logseq.com	Forum (opens a new window)	new tab	Add '(opens in new tab)' to text
https://docs.logseq.com/	Docs (opens a new window)	new tab	Add '(opens in new tab)' to text
https://github.com/logseq	GitHub (opens a new window)	new tab	Add '(opens in new tab)' to text
https://blog.logseq.com	Blog (opens a new window)	new tab	Add '(opens in new tab)' to text
https://github.com/logseq/logseq/release…	Download for Linux	new tab	Add '(opens in new tab)' to text
https://github.com/logseq/logseq/release…	Download for Linux	new tab	Add '(opens in new tab)' to text
https://docs.logseq.com/#/page/queries	Queries	new tab	Add '(opens in new tab)' to text
https://docs.logseq.com/#/page/search	Search	new tab	Add '(opens in new tab)' to text
https://docs.logseq.com/#/page/flashcard…	Flashcards	new tab	Add '(opens in new tab)' to text
https://docs.logseq.com/#/page/term%2Fbl…	Block References	new tab	Add '(opens in new tab)' to text
https://discord.com/channels/72518256929…	oskr's comment in discord	new tab	Add '(opens in new tab)' to text
https://github.com/logseq/logseq/release…	Download for Linux	new tab	Add '(opens in new tab)' to text
https://github.com/logseq/logseq	GitHub (opens a new window)	new tab	Add '(opens in new tab)' to text
https://twitter.com/logseq	Twitter (opens a new window)	new tab	Add '(opens in new tab)' to text

25 links and buttons have descriptive text

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

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://discuss.logseq.com; https://docs.logseq.com/; https://github.com/logseq; https://blog.logseq.com; https://github.com/logseq/logseq/releases; https://github.com/logseq/logseq/releases; https://docs.logseq.com/#/page/queries; https://docs.logseq.com/#/page/search; https://docs.logseq.com/#/page/flashcards; https://docs.logseq.com/#/page/term%2Fblock%20reference (+4 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Today, everyone is a

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Logseq Sync

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Whiteboards

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

32px · bottom of viewport

h2 knowledge worker.

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 New ideas will pop up with time.

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A helpful community

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Open source

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy first

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mobile apps

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Markdown files

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Strong community

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Localization

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 150+ Plugins

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 30+ Themes

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Logseq is the open toolbox for

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Using Logseq helps you organize your tho…

1.26:1

#000000

#01222A

needs 3.0:1 (large text)

19px · bottom of viewport

title Logseq: A privacy-first, open-source kno…

1.26:1

#000000

#012229

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.26:1

#000000

#012229

needs 4.5:1 (normal text)

16px · top of page (header area)

a Downloads

1.26:1

#000000

#01222A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Forum

1.26:1

#000000

#01222A

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Today, everyone is a	1.26:1	3.0:1	#000000	#01222A	Fail
h1 Logseq Sync	1.26:1	3.0:1	#000000	#01222A	Fail
h1 Whiteboards	1.26:1	3.0:1	#000000	#01222A	Fail
h2 knowledge worker.	1.26:1	3.0:1	#000000	#01222A	Fail
h2 New ideas will pop u…	1.26:1	3.0:1	#000000	#01222A	Fail
h2 A helpful community	1.26:1	3.0:1	#000000	#01222A	Fail
h2 Open source	1.26:1	3.0:1	#000000	#01222A	Fail
h2 Privacy first	1.26:1	3.0:1	#000000	#01222A	Fail
h2 Mobile apps	1.26:1	3.0:1	#000000	#01222A	Fail
h2 Markdown files	1.26:1	3.0:1	#000000	#01222A	Fail
h2 Strong community	1.26:1	3.0:1	#000000	#01222A	Fail
h2 Localization	1.26:1	3.0:1	#000000	#01222A	Fail
h2 150+ Plugins	1.26:1	3.0:1	#000000	#01222A	Fail
h2 30+ Themes	1.26:1	3.0:1	#000000	#01222A	Fail
h3 Logseq is the open t…	1.26:1	3.0:1	#000000	#01222A	Fail
h3 Using Logseq helps y…	1.26:1	3.0:1	#000000	#01222A	Fail
title Logseq: A privacy-fi…	1.26:1	4.5:1	#000000	#012229	Fail
a Home	1.26:1	4.5:1	#000000	#012229	Fail
a Downloads	1.26:1	4.5:1	#000000	#01222A	Fail
a Forum	1.26:1	4.5:1	#000000	#01222A	Fail

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.

Heading Hierarchy

54 headings

PASS

54 headings

Multiple H1 headings (14 found)

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

H1 Today, everyone is a
H2 knowledge worker.
H3 Logseq is the open toolbox for
H4 workflows that deal with lots of information:
H1 Review notes duplicate H1
H2 Capture, structure, and review all of your class notes with ease using the Linked References, Queries, and Search features.
H1 Memorize facts duplicate H1
H2 Remember facts and insights using the Flashcards feature.
H1 Outline essays duplicate H1
H2 Organize your thoughts and ideas, and quickly turn them into outlines using Block References.
H1 Braindump everything into.New ideas will pop up with time. duplicate H1
H2 New ideas will pop up with time.
H3 Using Logseq helps you organize your thoughts and ideas
H4 so that you can come up with new outputs more easily.
H1 ✍️Beginner duplicate H1
H2 Get in the habit of writing thoughts down every day.
H3 Tip 1: Think in sections, use indentation.
H1 🔍️Intermediate duplicate H1
H2 Always find what you’re looking for.
H3 Tip 1: Use CMD-K to search with ease.
H1 💼️Expert duplicate H1
H2 Create your own processes.
H3 Tip 1: Use queries to generate tables of relevant information.
H2 A helpful community
H1 Overwhelmed and constantly afraid of losing your thoughts? duplicate H1
H2 Everyday you’re bombarded with information.Your non-connected notes lead to missing context when you need it. That gets future-you into trouble.
H2 Logseq helps you turn this daily mess into structured information.
H1 Gain clarity in your everyday life: duplicate H1
H1 A safe space for your thoughts. duplicate H1
H2 Designed to store your interests, questions, ideas, favorite quotes, reminders, reading and meeting notes easily and future-proof:
H2 Open source
H3 Free forever for personal use
H2 Privacy first
H3 You own your data locally forever
H2 Mobile apps
H3 Available for iOS & Android
H2 Markdown files
H3 Open your notes in other tools
H2 Strong community
H3 2312 users online currently
H2 Localization
H3 Translated in many languages
H2 150+ Plugins
H3 Extend functionality to your needs
H2 30+ Themes
H3 Customize look and feel
H1 Logseq Sync BETA duplicate H1
H2 Always up-to-date notes between all your devices.
H3 With encrypted file syncing, you'll always have your notes backed up and securely available in real-time on any device.
H1 Whiteboards BETA duplicate H1
H2 A new canvas for your thoughts.
H3 Place any of your thoughts from the knowledge base or new ones next to each other on an infinite canvas to connect, associate and understand in new ways.
H1 Think faster, think better! duplicate H1
H2 By thinking and writing with Logseq, you'll gain confidence in what you know and stop worrying about forgetting anything.

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

Alt Text Quality

4 of 9 images have issues

PASS

4 of 9 images have issues

4 image(s) with generic alt text

4 decorative image(s) correctly marked

1 image(s) with good alt text

9 images 1 good alt text 4 decorative 4 generic

Issue	Count
generic	4 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 23 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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

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

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

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

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