Skip to content
https://pdftomd.tools

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
87
GRADE
B
FIX
3
REVIEW
2
PASS
19
INFO
0
Checks
24
19 PASS 2 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #070709
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 ModePartial Dark Mode
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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
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.
B
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (5 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (5 below threshold)
Info::
5 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("01"); <span> 11.0px ("02"); <span> 11.0px ("03"); <span> 11.0px ("04"); <span> 11.0px ("Preview").
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 Page not found | pdftomd.tools ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 NAV "Main" MAIN CONTENTINFO footer

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
20 headings
PASS
20 headings
Info::
Single H1 present
  • H1 PDF to MD Converter
  • H2 Clean Markdown, ready to copy
  • H2 How pdf to md works
  • H3 Drop the file
  • H3 Read and assemble
  • H3 Preview and copy
  • H3 Flip direction
  • H2 What is pdf to md
  • H2 What structure you keep with pdf to md
  • H2 Use cases for pdf to md
  • H3 Model prep
  • H3 Vault notes
  • H3 Repo docs
  • H3 Technical writing
  • H2 Privacy for in-browser pdf to md
  • H2 Need the reverse of pdf to md
  • H2 Related tools
  • H2 Start a pdf to md conversion
  • H2 Sources
  • H2 FAQ
A+
Heading Text Quality
All 20 heading(s) have substantive, well-formed text
PASS
All 20 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
13 image(s) with good alt text
13 images 13 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="file">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputcheckboxnone
inputfile(none)none

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

<input type="file">

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

A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
Favicon & Branding
8 icon(s) detected
PASS
8 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
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: pdftomd.tools — PDF to Markdown and back
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name pdftomd.tools — PDF to Markdown and back ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name pdftomd.tools — PDF to Markdown and back Display Mode standalone Theme Color #070709 Background Color #ffffff Icons 4 icon(s)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
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)
ElementRatioRequiredFGBGResult
h1 PDF to MD Converter19.39:13.0:1
#000000
#F0F7FA
Pass
h2 Clean Markdown, read…19.80:13.0:1
#000000
#F4F9FC
Pass
h2 How pdf to md works19.80:13.0:1
#000000
#F4F9FC
Pass
h2 What is pdf to md19.80:13.0:1
#000000
#F4F9FC
Pass
h2 What structure you k…19.80:13.0:1
#000000
#F4F9FC
Pass
h2 Use cases for pdf to…19.80:13.0:1
#000000
#F4F9FC
Pass
h2 Privacy for in-brows…19.80:13.0:1
#000000
#F4F9FC
Pass
h2 Need the reverse of …19.80:13.0:1
#000000
#F4F9FC
Pass
h2 Related tools19.80:13.0:1
#000000
#F4F9FC
Pass
h2 Start a pdf to md co…19.80:13.0:1
#000000
#F4F9FC
Pass
h2 Sources19.80:13.0:1
#000000
#F4F9FC
Pass
h2 FAQ19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Drop the file19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Read and assemble19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Preview and copy19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Flip direction19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Model prep19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Vault notes19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Repo docs19.80:13.0:1
#000000
#F4F9FC
Pass
h3 Technical writing19.80:13.0:1
#000000
#F4F9FC
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 93/100 — 3 failing, 28 passed
PASS
93

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
.tools span.contents > a.inline-flex > span.wm > span.wm-tld
Runs in your browser · nothing uploaded div.flex > div.flex > span.flex > span
15s product demo div.home-container > section.home-section > div.mx-auto > span.eyebrow-pill
A quarterly PDF report converts into formatted headings, text, and bullet point… div.home-container > section.home-section > div.mx-auto > p.sec-sub
Workflow div.home-container > section.home-section > div.mx-auto > span.eyebrow-pill
Four short steps, all inside this browser tab. div.home-container > section.home-section > div.mx-auto > p.sec-sub
Go to the tool ol.mt-12 > li > a.surface-card > span.card-cta
Go to the tool ol.mt-12 > li > a.surface-card > span.card-cta
Go to the tool ol.mt-12 > li > a.surface-card > span.card-cta
Reverse converter ol.mt-12 > li > a.surface-card > span.card-cta
Overview div.grid > div > div > span.eyebrow-pill
standardized as ISO 32000 div > div.mt-5 > p > a.rlink
John Gruber published in 2004 div > div.mt-5 > p > a.rlink
Preview div.lg:pt-2 > figure.surface-card > div.mb-4 > span.chip-m
Use cases div > section.home-section > div.mx-auto > span.eyebrow-pill
Where clean Markdown saves the most cleanup time. div > section.home-section > div.mx-auto > p.sec-sub
for-LLM scene page div.mt-12 > a.surface-card > p.card-p > span.font-medium
For-LLM scene page section.home-section > div.mt-12 > a.surface-card > span.card-cta
Obsidian scene page div.mt-12 > a.surface-card > p.card-p > span.font-medium
Obsidian scene page section.home-section > div.mt-12 > a.surface-card > span.card-cta
Python guide page div.mt-12 > a.surface-card > p.card-p > span.font-medium
Python guide section.home-section > div.mt-12 > a.surface-card > span.card-cta
Open the tool section.home-section > div.mt-12 > a.surface-card > span.card-cta
Local-first div.grid > div.surface-card > div.flex > span.eyebrow-pill
Read the privacy policy div.grid > div.surface-card > div.mt-auto > a.inline-flex
Other direction div.grid > div.surface-card > div.flex > span.eyebrow-pill
Tool suite div > section.home-section > div.mx-auto > span.eyebrow-pill
Focused pages for the next step, each one a click away. div > section.home-section > div.mx-auto > p.sec-sub
A standalone converter page with the same local engine. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
Run the conversion locally, without uploading anything. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
Turn Markdown back into a printable document. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
Render notes or a README as a clean print layout. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
Keep headings, lists and tables intact when converting files. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
Prepare tidy text before you paste it into a chat model. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
Bring documents into a vault with headings intact. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
Script the same job locally with common Python libraries. div.mt-12 > a.surface-card > span.min-w-0 > span.tool-desc
— Daring Fireball ol.mt-4 > li.flex > span > span
, 2004 ol.mt-4 > li.flex > span > span
— ISO ol.mt-4 > li.flex > span > span
, 2020 ol.mt-4 > li.flex > span > span
— GitHub ol.mt-4 > li.flex > span > span
— Mozilla ol.mt-4 > li.flex > span > span
Questions div > section#faq > div.mx-auto > span.eyebrow-pill
Short answers on privacy, scans, and tables. div > section#faq > div.mx-auto > p.sec-sub
.tools div > a.inline-flex > span.wm > span.wm-tld
Free in-browser PDF ↔ Markdown conversion. Files stay on your device for the on… div.grid > div.col-span-3 > div > p.mt-2
Reverse converter div.col-span-3 > div > p.mt-4 > a.font-medium
Contact: we do not publish an email address yet. div.grid > div.col-span-3 > div > p.mt-3
ChatGPT div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
Perplexity div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
Claude div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
Gemini div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
Grok div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
豆包 div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
DeepSeek div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
Kimi div.col-span-3 > div.mt-5 > div.mt-2 > a.ask-a
PDF to MD div > ul.mt-4 > li > a.foot-link
MD to PDF div > ul.mt-4 > li > a.foot-link
Converter div > ul.mt-4 > li > a.foot-link
Convert PDF to MD div > ul.mt-4 > li > a.foot-link
Markdown to PDF div > ul.mt-4 > li > a.foot-link
Batch div > ul.mt-4 > li > a.foot-link
For LLM div > ul.mt-4 > li > a.foot-link
Obsidian div > ul.mt-4 > li > a.foot-link
Python div > ul.mt-4 > li > a.foot-link
Blog div > ul.mt-4 > li > a.foot-link
About div > ul.mt-4 > li > a.foot-link
Privacy div > ul.mt-4 > li > a.foot-link
Terms div > ul.mt-4 > li > a.foot-link
LLMs.txt div > ul.mt-4 > li > a.foot-link
English div.mx-auto > div.mt-10 > nav.flex > a.foot-link
Deutsch div.mx-auto > div.mt-10 > nav.flex > a.foot-link
Français div.mx-auto > div.mt-10 > nav.flex > a.foot-link
Español div.mx-auto > div.mt-10 > nav.flex > a.foot-link
Italiano div.mx-auto > div.mt-10 > nav.flex > a.foot-link
Português div.mx-auto > div.mt-10 > nav.flex > a.foot-link
Nederlands div.mx-auto > div.mt-10 > nav.flex > a.foot-link
日本語 div.mx-auto > div.mt-10 > nav.flex > a.foot-link
한국어 div.mx-auto > div.mt-10 > nav.flex > a.foot-link
简体中文 div.mx-auto > div.mt-10 > nav.flex > a.foot-link
繁體中文 div.mx-auto > div.mt-10 > nav.flex > a.foot-link
© 2026 pdftomd.tools team. Built for developers and technical writers. body.font-sans > footer.border-t > div.mx-auto > p.mt-10

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tool-card > div.grid > div.flex > input.sr-only div.tool-card > div.grid > div.flex > input.sr-only

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Drop a PDF here, or click to browse Text PDFs only. Scans need OCR, which this… div.tool-card > div.grid > div.flex > div.h-[300px]
Install App main.min-h-[70vh] > div.pointer-events-none > div.group > button.inline-flex
○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
●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
●`[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.
●`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
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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 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
○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.
○`<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.
○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.

Send Feedback