Skip to content
https://pdflib.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="tx_indexedsearch_pi2[search][sword]" id="tx-indexedsearch-searchbox-sword">; <input type="text" name="tx_indexedsearch_pi2[search][sword]" id="tx-indexedsearch-searchbox-sword">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#tx-indexedsearch-searchbox-swordtext(Searchword)placeholder only
#tx-indexedsearch-searchbox-swordtext(Searchword)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="tx_indexedsearch_pi2[search][sword]" id="tx-indexedsearch-searchbox-sword">; <input type="text" name="tx_indexedsearch_pi2[search][sword]" id="tx-indexedsearch-searchbox-sword">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 PDFlib Logo ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA
h1 PDFlib GmbH
1.59:1
#000000
on
#002F64
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Apryse acquires PDFlib
1.59:1
#000000
on
#002F64
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What is PDFlib?
1.59:1
#000000
on
#002F64
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PDFlib 11
1.59:1
#000000
on
#002F64
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cookbooks
1.59:1
#000000
on
#002F64
needs 3.0:1 (large text)
24px · bottom of viewport
h2 TET 6
1.59:1
#000000
on
#002F64
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PDF Knowledge Base
1.59:1
#000000
on
#002F64
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 PDFlib GmbH1.59:13.0:1
#000000
#002F64
Fail
h2 Apryse acquires PDFl…1.59:13.0:1
#000000
#002F64
Fail
h2 What is PDFlib?1.59:13.0:1
#000000
#002F64
Fail
h2 PDFlib 111.59:13.0:1
#000000
#002F64
Fail
h2 Cookbooks1.59:13.0:1
#000000
#002F64
Fail
h2 TET 61.59:13.0:1
#000000
#002F64
Fail
h2 PDF Knowledge Base1.59:13.0:1
#000000
#002F64
Fail
title PDFlib: PDFlib GmbH …14.27:14.5:1
#000000
#FFD000
Pass
a skip navigation16.43:14.5:1
#000000
#FFE366
Pass
a Suche:21.00:14.5:1
#000000
#FFFFFF
Pass
a Products21.00:14.5:1
#000000
#FFFFFF
Pass
a Product Overview21.00:14.5:1
#000000
#FFFFFF
Pass
a PDFlib Product Famil…21.00:14.5:1
#000000
#FFFFFF
Pass
a What is PDFlib?21.00:14.5:1
#000000
#FFFFFF
Pass
a PDFlib21.00:14.5:1
#000000
#FFFFFF
Pass
a PDFlib+PDI21.00:14.5:1
#000000
#FFFFFF
Pass
a PDFlib Personalizati…21.00:14.5:1
#000000
#FFFFFF
Pass
a Comparison PDFlib/PD…21.00:14.5:1
#000000
#FFFFFF
Pass
a PDFlib 11 Features21.00:14.5:1
#000000
#FFFFFF
Pass
a Deprecated API Metho…21.00:14.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
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+
Heading Hierarchy
7 headings
PASS
7 headings
Info::
Single H1 present
  • H1 PDFlib GmbH
  • H2 Apryse acquires PDFlib
  • H2 What is PDFlib?
  • H2 PDFlib 11
  • H2 Cookbooks
  • H2 TET 6
  • H2 PDF Knowledge Base
A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
7 decorative image(s) correctly marked
7 images 7 decorative
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 94/100 — 1 failing, 16 passed
PASS
94

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
PDF Knowledge Base div#c32 > a > div.mfc_bg > h2
Settings div.sg-cookie-optin-box > div.sg-cookie-optin-banner-content > div.sg-cookie-optin-banner-button > button.sg-cookie-optin-banner-button-settings

These are opportunities to improve the legibility of your content.

○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>`
●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.
●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
●Skip links are focusable.
●Document has a main landmark.
●Identical links have the same purpose.
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback