Skip to content
https://www.obsidian.md

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Warning::
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
BANNER header MAIN (missing!) CONTENTINFO footer

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

F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 2 icon(s)
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
9 of 9 controls have issues
REVIEW
9 of 9 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">
9 controls
0 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none
inputcheckbox(none)none

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

<input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">; <input type="checkbox">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Obsidian ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
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 Sharpen your thinking.
1.09:1
#000000
on
#0E0E0E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Spark ideas.
1.09:1
#000000
on
#0E0E0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sync securely.
1.09:1
#000000
on
#0E0E0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Publish instantly.
1.09:1
#000000
on
#0E0E0E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 It’s your time to shine.
1.09:1
#000000
on
#0E0E0E
needs 3.0:1 (large text)
24px · bottom of viewport
title Obsidian - Sharpen your thinking
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Download
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Pricing
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Sync
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Publish
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a Enterprise
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a English
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a العربية
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a Deutsch
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a Español
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a Français
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a Italiano
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a 日本語
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · above the fold
a 한국어
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · mid-page
a Português (Brasil)
1.10:1
#000000
on
#0F0F0F
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Sharpen your thinkin…1.09:13.0:1
#000000
#0E0E0E
Fail
h2 Spark ideas.1.09:13.0:1
#000000
#0E0E0E
Fail
h2 Sync securely.1.09:13.0:1
#000000
#0E0E0E
Fail
h2 Publish instantly.1.09:13.0:1
#000000
#0E0E0E
Fail
h2 It’s your time to…1.09:13.0:1
#000000
#0E0E0E
Fail
title Obsidian - Sharpen y…1.10:14.5:1
#000000
#0F0F0F
Fail
a Download1.10:14.5:1
#000000
#0F0F0F
Fail
a Pricing1.10:14.5:1
#000000
#0F0F0F
Fail
a Sync1.10:14.5:1
#000000
#0F0F0F
Fail
a Publish1.10:14.5:1
#000000
#0F0F0F
Fail
a Enterprise1.10:14.5:1
#000000
#0F0F0F
Fail
a English1.10:14.5:1
#000000
#0F0F0F
Fail
a العربية1.10:14.5:1
#000000
#0F0F0F
Fail
a Deutsch1.10:14.5:1
#000000
#0F0F0F
Fail
a Español1.10:14.5:1
#000000
#0F0F0F
Fail
a Français1.10:14.5:1
#000000
#0F0F0F
Fail
a Italiano1.10:14.5:1
#000000
#0F0F0F
Fail
a 日本語1.10:14.5:1
#000000
#0F0F0F
Fail
a 한국어1.10:14.5:1
#000000
#0F0F0F
Fail
a Português (Brasil)1.10:14.5:1
#000000
#0F0F0F
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 19 passed
REVIEW
82

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Community plugins Calendar by Liam Cain Calendar view of your daily notes. Kanb… div.text-lg > div.card > div.md:h-96 > div.select-none

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
Invite by email... div.ui > div.py-4 > div.flex > div.flex-1
EX div.ui > div.py-4 > div.flex > div.w-8
Owner div.ui > div.py-4 > div.flex > div.text-xs
SA div.ui > div.py-4 > div.flex > div.w-8
Can edit div.ui > div.py-4 > div.flex > div.text-xs
LC div.ui > div.py-4 > div.flex > div.w-8
Can edit div.ui > div.py-4 > div.flex > div.text-xs
TG div.ui > div.py-4 > div.flex > div.w-8
Can edit div.ui > div.py-4 > div.flex > div.text-xs

These are opportunities to improve the legibility of your content.

Tables and lists

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Seamless editing. Publish your notes instantly from the Obsidian app, and make … div.py-16 > div.container > div.mx-auto > dl.col-span-2

Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Seamless editing. dl.col-span-2 > div.text-lg > div > dt.font-semibold
Publish your notes instantly from the Obsidian app, and make it easy for reader… dl.col-span-2 > div.text-lg > div > dd.mt-2
Customization. dl.col-span-2 > div.text-lg > div > dt.font-semibold
Control the look and feel of your site with themes, custom domains, password pr… dl.col-span-2 > div.text-lg > div > dd.mt-2
Optimized for performance. dl.col-span-2 > div.text-lg > div > dt.font-semibold
Obsidian Publish sites are fast, mobile-friendly, and optimized for SEO, no con… dl.col-span-2 > div.text-lg > div > dd.mt-2

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[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.
●ARIA attributes are used as specified for the element's role
●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 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○Form elements have associated labels
○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
○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.
○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
5 headings
PASS
5 headings
Info::
Single H1 present
  • H1 Sharpen your thinking.
  • H2 Spark ideas.
  • H2 Sync securely.
  • H2 Publish instantly.
  • H2 It’s your time to shine.
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
5 image(s) with good alt text
5 images 5 good alt text
All images have appropriate alt text.
A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback